Recherche avancée

Sur d’autres sites (9672)

• fluent-ffmpeg sometimes crashes entire amazon ec2 instance

  24 octobre 2020, par Mick Marsden

  I have a nodejs application where I'm using fluent-ffmpeg to convert captured video files via the html <input file="file" /> tag to mp4 format. I'm also using ffmpeg-static to provide static binaries for fluent-ffmpeg's file path. But in order for the conversion to happen, I upload the captured video file via multer, and when that completes, multer passes the video url to fluent-ffmpeg. The code looks like this :

  


  app.post("/upload-and-convert", async function(req, res) {

   var filepath;
   var path;

    try {

        const upload = util.promisify(uploadVideo());

        await upload(req, res);

        console.log(req.file);
        console.log("Success");
        filepath = req.file.filename;
        console.log(filepath);
        path = './public/uploads/' + filepath;
        console.log(path);

    } catch (e) {
       let response_json = {
                success: false,
        };
        res.setHeader("content-type", "application/json");
        res.send(response_json);
    }

    if(path != undefined)
    {

        console.log("Path not undefined, going to start FFMPEG");
        ffmpeg(path)
        .format('mp4')
        .size('720x720').autopad()
        .on('end', function() {
            console.log('file has been converted successfully');
        })
        .on('error', function(err) {
            console.log('an error happened: ' + err.message);
            let response_json = {
                success: false,
            };
            res.setHeader("content-type", "application/json");
            res.send(response_json);
        })
        .save('./public/uploads/video.mp4')
        .on('end', function() {
            console.log('file has been saved successfully');
            let response_json = {
                success: true,
                fileURL: 'https://websiteurl/uploads/video.mp4'
            };
            res.setHeader("content-type", "application/json");
            res.send(response_json);
        })

    } else
    {
        let response_json = {
            success: false,
        };
        res.setHeader("content-type", "application/json");
        res.send(response_json);
    }
});


  


  Most times, the code runs fine and returns the fileURL as intended. Sometimes however, it completely crashes the amazon ec2 instance, and requires the instance be rebooted before it works again. I've checked the logs, and the server-error logs output no issues. The server-out logs when it crashes outputs the final console log before ffmpeg starts :

  


          console.log("Path not undefined, going to start FFMPEG");


  


  The moment it reaches the ffmpeg(path), it goes down. It doesn't log any error, even though I have included error handling on the operation.

  


  This has stumped me for days. I cannot figure out the commonality to explain why sometimes it crashes, and sometimes it does not. Note that this even happened before I started using the ffmpeg-static package. My node version is 12.19.0, and ffmpeg-static currently installs ffmpeg at version 4.3.1 if I recall correctly.

  


  If anyone could help that would be great.

  


• dxva2_h264 : add a workaround for old Intel GPUs

  22 avril 2014, par Hendrik Leppkes

  dxva2_h264 : add a workaround for old Intel GPUs
  Old Intel GPUs expect the reference frame index to the actual surface,
  
  instead of the index into RefFrameList as specified by the spec.
  This workaround should be set when using one of the "ClearVideo" decoder
  
  devices.
  Signed-off-by : Anton Khirnov <anton@khirnov.net>
  

  • [DH] doc/APIchanges
  • [DH] libavcodec/dxva2.h
  • [DH] libavcodec/dxva2_h264.c
  • [DH] libavcodec/version.h

• msvc/icl : Intel Compiler support on Windows

  25 mai 2013, par Alex Smith

  msvc/icl : Intel Compiler support on Windows
  Initial support for the ICL compiler on windows. Requires a new
  
  c99wrap with ICL support (1.0.2+).
  Currently not much different speed wise compared to msvc. In the
  
  future with a few changes it can be made to support the inline asm.
  
  This would be the primary reason for using it.
  Passed all fate tests, versions tested :
  
      13.1.1.171 (2013 Update 3) x86 and x64
  
      12.1.5.344 (2011 Update 11) x86 and x64
  Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
  

  • [DBH] configure