Recherche avancée

Sur d’autres sites (8494)

• FFMPEG failing in AWS Lambda

  18 février 2019, par Zaid Amir

  I am trying to create a transcoding function for short videos. The function is hosted on AWS Lambda. The problem is that AWS lambda seems to be missing something that FFMPEG requires, at least according to Amazon.

  I contacted Amazon earlier and this is their response to the issue :

  We found that the FFMPEG operations require at least libx264 and an
  acc library, both of which will have dependencies of their own. To
  troubleshoot the issue it will involve diving deeper into the full
  dependency chain. We can see that it works in the Amazon Linux
  environment however, the environment is similar but not identical to
  the lambda environment. There can be some dependencies that exist in
  Amazon Linux but not in lambda environment as Lambda runs on the
  container. Here, as FFmpeg is a third party software, diving deeper
  into the dependency chain and verifying the version compatibilities is
  very hard to do. Unfortunately going further, this is bound to go into
  architecture and code support which is out of AWS Support scope 1. I
  hope you understand our limitations. However should FFmpeg support
  have any questions specific to the Lambda platform, please do let us
  know and we will be happy to assist. We will be in better position to
  investigate further once you receive an update from the FFmpeg support
  suggesting an issue from Lambda end.

  Upon AWS suggestion, I contacted FFMPEG on the developers mailing list, my message was rejected with the reason being that its more suited to ffmpeg users mailing list than developers. I sent an email to ’ffmpeg-user@ffmpeg.org’ a week ago and did not get any response yet.

  I then went and built a dynamically linked ffmpeg version making sure to package all libraries, checked ddl on each one, then made a small lambda function that looped over all binaries and ddled each one of them, compared that to the output I got from Amazon Linux and the same dependencies/versions exists on both lambda and the AWS Linux instance yet ffmpeg still fails on lambda.

  You can find a detailed log file here : https://www.datafilehost.com/d/6e5e21bb

  And this is a sample of the errors I’m getting, repeated across the entire log file :

  2018-08-14T12:27:10.874Z [h264 @ 0x65c2fc0] concealing 2628 DC, 2628
  AC, 2628 MV errors in P frame

  2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.11 is not
  allocated

  2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
  data found when processing input

  2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Invalid NAL unit size
  (108085662 > 1649).

  2018-08-14T12:27:10.874Z [h264 @ 0x67e86c0] Error splitting the input
  into NAL units.

  2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] channel element 2.0 is not
  allocated

  2018-08-14T12:27:10.874Z Error while decoding stream #0:1 : Invalid
  data found when processing input

  2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Invalid NAL unit size
  (71106974 > 1085).

  2018-08-14T12:27:10.874Z [h264 @ 0x68189c0] Error splitting the input
  into NAL units.

  2018-08-14T12:27:10.874Z [aac @ 0x65d2f00] Pulse tool not allowed in
  eight short sequence.

  This log is generated when trying to perform an HLS transcoding on this file : https://www.datafilehost.com/d/999a4492

  Note that the issue is not related to that file alone nor is it related to HLS, its general and happen on all videos and any ffmpeg command that tries to seek the stream, even tried extracting a single frame from a video using the simplest form possible for example : ffmpeg -ss 00:00:02 -I file.mp4 -vframes 1 -y output.jpg also fails with the same errors in the log file.

  Not sure how to debug this further. Tried enabling debug logs with ‘-loglevel debug’ but did not give me any extra info. Any help or suggestions

• Carrierwave watermark a movie

  15 mai 2016, par Felix

  I’m uploading a movie with carrierwave to amazon S3. While uploading I want to watermark the movie.

  How can I do this ? How can I use stermio-ffmpeg while uploading ?

  I’m using a Rails application.

• ffmpeg extract multiple frames from single input causing SIGSEGV in node.js child_process on lambda env

  11 octobre 2023, par Andrew Still

  I'm trying to dynamically extract multiple different frames from single video input. So the command I'm calling looking like this

  


  ffmpeg -loglevel debug -hide_banner -t 13.269541 -y -ss 0 -i "input-s3-url" -ss 13.269541 -i "same-input-s3-url" -map 0:v -vframes 1 /tmp/ca4cd7a3159743938c5362c171ea2cae.0.png -map 1:v -vframes 1 /tmp/ca4cd7a3159743938c5362c171ea2cae.13.269541.png


  


  It works and everything is good, until I deploy it to lambda. Even though I'm using 10gb of RAM it still failing with error. Locally it works like a charm but not on lambda. I'm not sure what the problem here but i'm regularly (not always) getting SIGSEGV

  


  at ChildProcess.exithandler (node:child_process:402:12)
at ChildProcess.emit (node:events:513:28) 
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process: 1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5) 
{
code: null, 
killed: false, 
signal: 'SIGSEGV'
cmd: '/opt/bin/ffmpeg -loglevel error -hide_banner -t 131.805393 -y -ss 0 -i "https: //


  


  Double-checked memory usage and it's doesn't look like a reason, but I'm not sure how correct this number

  


  Memory size : 10240 MB Max Memory used : 140 MB

  


  I'm think maybe it's because it's making requests for each input, at least that's what I saw in debug mode, but still have no idea what's the problem here, would appreciate any suggestions/optimizations/help. Thanks

  


  ffmpeg added on lambda using this layer - https://serverlessrepo.aws.amazon.com/applications/us-east-1/145266761615/ffmpeg-lambda-layer