Recherche avancée

Médias (2)

Mot : - Tags -/doc2img

Autres articles (71)

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • 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 (...)

Sur d’autres sites (5791)

  • fluent-ffmpeg throwing SIGSEGV in nodejs

    22 mars 2023, par C G

    I am using fluent-ffmpeg to resize a video, split into frames, etc.
Here's my code :

    


    ffmpeg("./uploads/video.mp4")
    .output("./uploads/small-video.mp4")
    .noAudio()
    .size('320x?')
    .on('end', function() {
        extractVideoFrames("./uploads/small-video.mp4")
    })
    .run()


    


    I am getting a SIGSEGV error, which I suspect might be because of some weird memory issue ?
Here's the error :

    


    Error: ffmpeg was killed with signal SIGSEGV&#xA;    at ChildProcess.<anonymous> (/home/admin/superformweb/node_modules/fluent-ffmpeg/lib/processor.js:180:22)&#xA;    at ChildProcess.emit (node:events:513:28)&#xA;    at ChildProcess._handle.onexit (node:internal/child_process:291:12)&#xA;Emitted &#x27;error&#x27; event on FfmpegCommand instance at:&#xA;    at emitEnd (/home/admin/superformweb/node_modules/fluent-ffmpeg/lib/processor.js:424:16)&#xA;    at /home/admin/superformweb/node_modules/fluent-ffmpeg/lib/processor.js:433:16&#xA;    at wrapper (/home/admin/superformweb/node_modules/async/dist/async.js:271:20)&#xA;    at next (/home/admin/superformweb/node_modules/async/dist/async.js:5795:24)&#xA;    at /home/admin/superformweb/node_modules/async/dist/async.js:327:20&#xA;    at wrapper (/home/admin/superformweb/node_modules/async/dist/async.js:271:20)&#xA;    at next (/home/admin/superformweb/node_modules/async/dist/async.js:5795:24)&#xA;    at /home/admin/superformweb/node_modules/async/dist/async.js:327:20&#xA;    at /home/admin/superformweb/node_modules/fluent-ffmpeg/lib/capabilities.js:519:16&#xA;    at handleExit (/home/admin/superformweb/node_modules/fluent-ffmpeg/lib/processor.js:170:11)&#xA;&#xA;</anonymous>

    &#xA;

    I have installed ffmpeg first : sudo apt-get install ffmpeg&#xA;Then I installed node packages :

    &#xA;

    npm install ffmpeg&#xA;npm install fluent-ffmpeg&#xA;

    &#xA;

  • 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.

    &#xA;

    Here is the fluent-ffmpeg init script :

    &#xA;

    import ffmpeg = require(&#x27;fluent-ffmpeg&#x27;);&#xA;const ffmpegPath = require(&#x27;@ffmpeg-installer/ffmpeg&#x27;).path;&#xA;const ffprobePath = require(&#x27;@ffprobe-installer/ffprobe&#x27;).path;&#xA;&#xA;ffmpeg.setFfmpegPath(ffmpegPath);&#xA;ffmpeg.setFfprobePath(ffprobePath);&#xA;&#xA;export default ffmpeg;&#xA;

    &#xA;

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

    &#xA;

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

    &#xA;

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

    &#xA;

    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;

  • Xuggler Error : Could Not Open

    22 septembre 2012, par MalTec

    I am using xuggler API to transcode Video from one format to another.

    Following the example, provided by

    http://wiki.xuggle.com/MediaTool_Introduction & http://www.javacodegeeks.com/2011/02/xuggler-tutorial-transcoding-media.html

    public void convertVideo(){

        String sourceUrl=getResourceDirectory()+"/in/AV36_1.AVI";
        String destUrl=getResourceDirectory()+"/out/output.mp4";

        IMediaReader reader = ToolFactory.makeReader(sourceUrl);

           // add a viewer to the reader, to see progress as the media is
           // transcoded
           reader.addListener(ToolFactory.makeViewer(true));

        // create a writer which receives the decoded media from
        // reader, encodes it and writes it out to the specified file
        IMediaWriter writer = ToolFactory.makeWriter(destUrl, reader);

        // add a debug listener to the writer to see media writer events
        writer.addListener(ToolFactory.makeDebugListener());


    ////
    ////        // create the media writer
           reader.addListener(ToolFactory.makeWriter(destUrl, reader));

           // read packets from the source file, which dispatch events to the
           // writer, this will continue until


           while (reader.readPacket() == null)
             do {} while(false);
       }

    Provides Could Not Open Exception :

     Exception in thread "main" java.lang.RuntimeException: could not open: D:\Malhar\project_works\VideoConvertter/resources/in/AV36_1.AVI
       at com.xuggle.mediatool.MediaReader.open(MediaReader.java:637)
       at com.xuggle.mediatool.MediaReader.readPacket(MediaReader.java:434)
       at util.VideoEncoder.convertVideo(VideoEncoder.java:38)
       at ConvertVideo.main(ConvertVideo.java:12)

    Have tried with different file to.. But, the result is same.