Recherche avancée

Sur d’autres sites (9590)

• How to create movie screenshot by ffmpeg in an amazon S3 path

  5 décembre 2019, par user2004082

  I tried to create using ffmpeg a video screenshot from a remote video url in heroku console. Below is how I generated a movie instance and can see also an empty ready to be written file at S3. But the last line movie.screenshot is not working and generates this error :

  FFMPEG::Error: Failed encoding.Errors: no output file created

  Here is the code

  s3 = Aws::S3::Resource.new(region: 'us-west-1')
  
  bucket = s3.bucket("ruby-sample-kb-#{SecureRandom.uuid}")
  
  bucket.create
  
  object = bucket.object('ex-vid-test-kb.jpg')
  
  object.put(acl: "public-read-write")
  
  path = object.public_url
  
  movie = FFMPEG::Movie.new("https://www.googleapis.com/download/storage/v1/b/seppoav/o/3606137_51447286560__56BAF29C-05CB-4223-BAE6-655DF2236321.MOV?generation=1492780072394755&alt=media")
  
  movie.screenshot(path, :seek_time => 2)

  I also tried the following line just if it should be written via put. What am I missing here ?

  object.put(acl: "public-read", body: movie.screenshot(path, :seek_time => 2))

• How do I install ffmpeg on one EC2 Amazon Linux instance that can stream a mp4 ? [closed]

  12 septembre 2020, par starpebble

  Good day. How can I install ffmpeg on an EC2 amazon linux machine that can stream a mp4 ?

  


  The goal : an ffmpeg install on EC2 Amazon Linux that can stream one mp4 to one rtmps endpoint. Then, create an integration test suite with it.

  


  Is it just me or is ffmpeg a little crippled on EC2 Amazon Linux ?

  


  Example :

  


  ffmpeg -re -i input.mp4 -c:v libx264 -b:v 6000K -maxrate 6000K -pix_fmt yuv420p -s 1920x1080 -profile:v main -preset veryfast -g 120 -x264opts "nal-hrd=cbr:no-scenecut” -acodec aac -ab 160k -ar 44100 -f flv rtmps:///app/


  


  Linux OS :

  


  Linux version 4.14.193-113.317.amzn1.x86_64 (mockbuild@koji-pdx-corp-builder-60005) (gcc version 7.2.1 20170915 (Red Hat 7.2.1-2) (GCC)) #1 SMP Thu Sep 3 19:08:08 UTC 2020


  


  The stackoverflow answer to similar questions fail to install a ffmpeg that can stream.

  


  An installation script such as Install FFMPEG Library on EC2 Server fail this year.

  


  The static downloads referenced on John Van Sickle-FFmpeg Static Builds fail to stream to IVS. I tried the i686 release, my first guess for an x86_64 instance.

  


  The git source tree compiled binary fails to stream. Example : The tip of the tree isn't what I expected because the binary fails to recognize switches like -preset.

  


  I'd love to be able to explain streaming to anyone. Thanks.

  


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