Recherche avancée

Sur d’autres sites (9168)

• Grabbing a series of frames from an RTSP stream

  30 septembre 2012, par Burbas

  I'm looking for a way to continuously grab frames, as jpg, from a RTSP stream. I've stumbled upon ffmpeg but it seems that the time between starting it and grabbing the first frame is quite high. Is there any good tool in order to do this ?

  Regards

• Microsoft Edge fails to play PlayReady DASH stream in VideoJS

  18 septembre 2023, par poepykooitje

  I have encoded some videos to x264 with ffmpeg, and packaged it to mpeg-dash with Widevine + PlayReady DRM using Shaka Packager.
With VideoJS the Widevine stream plays perfectly on both Chrome and MS Edge.
However, when I try to play the PlayReady stream on Edge, it just plays the first few seconds and then the image freezes. The audio does continue.
I see this error in the console :
VIDEOJS : ERROR : DOMException : Failed to execute 'changeType' on 'SourceBuffer' : Changing to the type provided ('video/mp4 ;codecs="avc1.4d401f"') is not supported.

  


  What I don't understand is why it says the codec is unsupported, when it plays the exact same video fine, using Widevine. The PlayReady license server also doesn't give an error at all, it's all 200 OK.

  


  The PlayReady stream works fine on other PlayReady supporting devices like a Roku or a Chromecast.

  


  Does anyone have any idea about what the problem could be here ?

  


  Thanks in advance !

  


  EDIT : It seems to be a VideoJS error, since the exact same PlayReady stream plays fine in a DRM test player (https://bitmovin.com/demos/drm). That still doesn't solve my issue though...

  


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