Recherche avancée

Sur d’autres sites (8512)

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

• SIGSEGV from ffmpeg on Amazon Lambda

  1er août 2024, par Serge

  Trying out Amazon Lambda / nodejs 8. My goal is to launch ffmpeg, generate a short clip and upload it to S3 bucket.

  



  I created the function following the image resize tutorial. Edited the code to get output from simple linux commands like ls or cat /proc/cpuinfo - all works.

  



  Now, added the ffmpeg binary for i686 - ffmpeg static build by JohnVan Sickle (thanks !). Changed the code to launch simple ffmpeg command that is supposed to create sa 2-seconds small video clip.

  



  That fails, according to logs, with the signal SIGSEGV returned to the "close" event handler of child_process.spawn()

  



  As far as I understand, this could be caused by the ffmpeg binary incompatibility with the static build. Or by some mistake in my code.

  



  Several npm modules rely on the static builds from johnvansickle.com/ffmpeg and there are no such issues filed on their github. Maybe there's some other mistake I made ?

  



  Should I compile ffmpeg myself under Amazon Linux AMI amzn-ami-hvm-2017.03.1.20170812-x86_64-gp2 which is under the hood of AWS Lambda ?

  



  ---

  



  upd. Launched EC2 t2.micro instance from the same AMI, downloaded the same ffmpeg static build, and it works just fine from the command line. Now I doubt that it is a compilation issue.

  



  Also tried copying ffmpeg executable to /tmp/ffmpeg and chmod 755 just to make sure.
Running simple ffmpeg --help command via child_process.execSync() returns "Error : Command failed : /tmp/ffmpeg —help"

  



  ---

  



  const join = require('path').join;
const tmpdir = require('os').tmpdir;
const process = require('process');
const fs = require('fs');
const spawn = require('child_process').spawn;
const exec = require('child_process').exec;

const async = require('async');
const AWS = require('aws-sdk');
const util = require('util');

process.env['PATH'] = process.env['PATH'] + ':' + process.env['LAMBDA_TASK_ROOT'];


const tempDir = process.env['TEMP'] || tmpdir();
const filename = join(tempDir, 'test.mp4');
const s3 = new AWS.S3();


exports.handler = function(event, context, callback) {
  var dstBucket = srcBucket + "resized";
  var dstKey  = "render-test.mp4";

  async.waterfall([
    function transform(next) {
      var args = [
        '-filter_complex',
        '"testsrc=r=25:s=640x480:d=3"',
        '-an',
        '-y',
        '-hide_banner',
        '-c:v', 'libx264',
        filename,
      ];

      console.log("Will launch ffmpeg");
      const childProcess = spawn('ffmpeg', args);

      childProcess.on('close', function(e) {
        console.log('ffmpeg close event: ' + JSON.stringify(arguments));
        next();
      });

      console.log("After launched ffmpeg");
    },

    function upload(next) {
      ...
    }
  ], function (err) {
    ...
  });
};