Recherche avancée

Sur d’autres sites (6870)

• Read a Bytes image from Amazon Kinesis output in python

  14 février 2020, par Varun_Rathinam

  I used imageio.get_reader(BytesIO(a),  'ffmpeg') to load a bytes image and save it as normal image.

  But the below error throws when I read the image using imageio.get_reader(BytesIO(a),  'ffmpeg')

  Traceback (most recent call last):
  
    File "<stdin>", line 1, in <module>
  
    File "/home/tango/anaconda3/lib/python3.6/site-packages/imageio/core/functions.py", line 186, in get_reader
  
      return format.get_reader(request)
  
    File "/home/tango/anaconda3/lib/python3.6/site-packages/imageio/core/format.py", line 164, in get_reader
  
      return self.Reader(self, request)
  
    File "/home/tango/anaconda3/lib/python3.6/site-packages/imageio/core/format.py", line 214, in __init__
  
      self._open(**self.request.kwargs.copy())
  
    File "/home/tango/anaconda3/lib/python3.6/site-packages/imageio/plugins/ffmpeg.py", line 323, in _open
  
      self._initialize()
  
    File "/home/tango/anaconda3/lib/python3.6/site-packages/imageio/plugins/ffmpeg.py", line 466, in _initialize
  
      self._meta.update(self._read_gen.__next__())
  
    File "/home/tango/anaconda3/lib/python3.6/site-packages/imageio_ffmpeg/_io.py", line 150, in read_frames
  
      raise IOError(fmt.format(err2))
  
  OSError: Could not load meta information
  
  === stderr ===
  
  
  
  ffmpeg version 4.2 Copyright (c) 2000-2019 the FFmpeg developers
  
    built with gcc 7.3.0 (crosstool-NG 1.23.0.449-a04d0)
  
    configuration: --prefix=/home/tango/anaconda3 --cc=/home/conda/feedstock_root/build_artifacts/ffmpeg_1566210161358/_build_env/bin/x86_64-conda_cos6-linux-gnu-cc --disable-doc --disable-openssl --enable-avresample --enable-gnutls --enable-gpl --enable-hardcoded-tables --enable-libfreetype --enable-libopenh264 --enable-libx264 --enable-pic --enable-pthreads --enable-shared --enable-static --enable-version3 --enable-zlib --enable-libmp3lame
  
    libavutil      56. 31.100 / 56. 31.100
  
    libavcodec     58. 54.100 / 58. 54.100
  
    libavformat    58. 29.100 / 58. 29.100
  
    libavdevice    58.  8.100 / 58.  8.100
  
    libavfilter     7. 57.100 /  7. 57.100
  
    libavresample   4.  0.  0 /  4.  0.  0
  
    libswscale      5.  5.100 /  5.  5.100
  
    libswresample   3.  5.100 /  3.  5.100
  
    libpostproc    55.  5.100 / 55.  5.100
  
  [matroska,webm @ 0x5619b9da3cc0] File ended prematurely
  
  [matroska,webm @ 0x5619b9da3cc0] Could not find codec parameters for stream 0 (Video: h264, none, 1280x720): unspecified pixel format
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  Input #0, matroska,webm, from '/tmp/imageio_zm6hhpgr':
  
    Metadata:
  
      title           : Kinesis Video SDK
  
      encoder         : Kinesis Video SDK 1.0.0
  
      AWS_KINESISVIDEO_FRAGMENT_NUMBER: 91343852333183888465720004820715065721442989478
  
      AWS_KINESISVIDEO_SERVER_TIMESTAMP: 1580791384.096
  
      AWS_KINESISVIDEO_PRODUCER_TIMESTAMP: 1580791377.843
  
    Duration: N/A, bitrate: N/A
  
      Stream #0:0(eng): Video: h264, none, 1280x720, SAR 1:1 DAR 16:9, 1k tbr, 1k tbn, 2k tbc (default)
  
      Metadata:
  
        title           : kinesis_video
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native))
  
  Press [q] to stop, [?] for help
  
  Cannot determine format of input stream 0:0 after EOF
  
  Error marking filters as finished
  
  Conversion failed!
  
  </module></stdin>

  The above approach to read a MKV bytes file was done based on this thread

  Or is there is any approach to parse and read the MKV bytes file.

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