Recherche avancée

Médias (91)

Autres articles (44)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (5578)

  • How to resolve "ffmpeg was killed with signal SIGSEGV" in docker container

    25 juin 2024, par Gmanicus

    I have a Node.js application deployed to a docker container with fluent-ffmpeg, @ffmpeg-installer/ffmpeg, and @ffprobe-installer/ffmprobe.

    


    Here is the fluent-ffmpeg init script :

    


    import ffmpeg = require('fluent-ffmpeg');
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
const ffprobePath = require('@ffprobe-installer/ffprobe').path;

ffmpeg.setFfmpegPath(ffmpegPath);
ffmpeg.setFfprobePath(ffprobePath);

export default ffmpeg;


    


    This gets used to take a snapshot of a video and save that image to file :

    


    ffmpeg('ism manifest here')
        .inputOption(`-ss timestamp`)
        .outputOptions([
            '-vframes 1',
            '-vf crop=640:230:320:490,eq=saturation=0:contrast=1000,negate'
        ])
        .output('test.png')
        .run();


    


    Whenever any configuration of ffmpeg command is run, it nearly instantaneously fails with :

    


    Error: ffmpeg was killed with signal SIGSEGV&#xA;     at ChildProcess.<anonymous> (/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)&#xA;     at ChildProcess.emit (node:events:517:28)&#xA;     at Process.ChildProcess._handle.onexit (node:internal/child_process:292:12)&#xA;</anonymous>

    &#xA;

    I have attempted to raise the memory and CPU usage limits of the server in the docker-compose file :

    &#xA;

    ...&#xA;    deploy:&#xA;      resources:&#xA;        limits:&#xA;          cpus: &#x27;0.75&#x27;&#xA;          memory: 2G&#xA;        reservations:&#xA;          cpus: &#x27;0.50&#x27;&#xA;          memory: 1G&#xA;

    &#xA;

    But nothing has worked. Running this on my local machine works just fine. Help ?

    &#xA;

    UPDATE :

    &#xA;

    I just attempted running a small dockerized ffmpeg test script on its own in its own brand new container. Same issue. So, it doesn't seem to have anything to do with my server's configuration.

    &#xA;

  • Partial video processing using .webm

    27 octobre 2015, par Ned Rockson

    I’m currently working on taking a bunch of segments of videos that I have chopped up into 1 second chunks. What I’d like to do is to be able to, from these chunks, reconstruct a video from a given offset. When I use ffmpeg to do this, the output is garbled at best and at worst just a black frame. It appears that there are some boundary issues with .webm that I can’t find easily documented so wondering if there’s a simple way to achieve this goal.

    Currently the only solution I have is downloading all 1 second chunks, concatenating them, and then using ffmpeg to create the clip.

  • Revision 101376 : v1.1.16 : une constante _FULLTEXT_MAX_RESULTS_JOINTURES pour augmenter ...

    28 décembre 2016, par tcharlss@… — Log

    v1.1.16 : une constante _FULLTEXT_MAX_RESULTS_JOINTURES pour augmenter le nombre de résultats provenant de chaque jointure.
    Par défaut c’est limité à 100, ce qui peut exclure certains résultats pertinents.

Navigation