Recherche avancée

Sur d’autres sites (11495)

• FFmpeg transcoding on Lambda results in unusable (static) audio

  17 mai 2020, par jmkmay

  I'd like to move towards serverless for audio transcoding routines in AWS. I've been trying to setup a Lambda function to do just that ; execute a static FFmpeg binary and re-upload the resulting audio file. The static binary I'm using is here.

  



  The Lambda function I'm using in Python looks like this :

  



  import boto3

s3client = boto3.client('s3')
s3resource = boto3.client('s3')

import json
import subprocess 

from io import BytesIO

import os

os.system("cp -ra ./bin/ffmpeg /tmp/")
os.system("chmod -R 775 /tmp")

def lambda_handler(event, context):

    bucketname = event["Records"][0]["s3"]["bucket"]["name"]
    filename = event["Records"][0]["s3"]["object"]["key"]

    audioData = grabFromS3(bucketname, filename)

    with open('/tmp/' + filename, 'wb') as f:
        f.write(audioData.read())

    os.chdir('/tmp/')

    try:
        process = subprocess.check_output(['./ffmpeg -i /tmp/joe_and_bill.wav /tmp/joe_and_bill.aac'], shell=True, stderr=subprocess.STDOUT)
        pushToS3(bucketname, filename)
        return process.decode('utf-8')
    except subprocess.CalledProcessError as e:
        return e.output.decode('utf-8'), os.listdir()


def grabFromS3(bucket, file):

    obj = s3client.get_object(Bucket=bucket, Key=file)
    data = BytesIO(obj['Body'].read())

    return(data)

def pushToS3(bucket, file):

    s3client.upload_file('/tmp/' + file[:-4] + '.aac', bucket, file[:-4] + '.aac')

    return


  



  You can listen to the output of this here. WARNING : Turn your volume down or your ears will bleed.

  



  The original file can be heard here.

  



  Does anyone have any idea what might be causing the encoding errors ? It doesn't seem to be an issue with the file upload, since the md5 on the Lambda fs matches the MD5 of the uploaded file.

  



  I've also tried building the static binary on an Amazon Linux instance in EC2, then zipping and porting it into the Lambda project, but the same issue persists.

  



  I'm stumped ! :(

  


• FFMPEG for aws s3 bucket signed url not working in node js

  21 août 2018, par ahmed sharief

  I am trying to create thumbnails from an amazon s3 bucket signed url. I am able to generate thumbnails when i run the command in terminal

  ffmpeg -ss 00:00:02 -i "https://test-s3-bucket.s3.ap-south-1.amazonaws.com/user_gallery_assets/5b6936069ac2bf0602085367/gallery/images/5b7be08527641dee8c1f8134.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=xxxxxxxxx%2F20180821%2Fap-south-1%2Fs3%2Faws4_request&X-Amz-Date=20180821T095101Z&X-Amz-Expires=900&X-Amz-Signature=d7f81f4eed3d6c87c04dc1b0ad06beeb946afa33d417585f57fad72aeadb3ac0&X-Amz-SignedHeaders=host" -vframes 1 -q:v 2 -f image2 output.jpg

  I am running the above command in terminal and its working fine but when i try to implement the same in node js its showing "no such file or directory error". Though i am encoding the url with double quotes then also its showign same error. Here is my node js code....

  function uploadThumbNailForVideo(obj,url, thumb_url){
  
      return new Promise((resolve, reject) => resolve(url))
  
      .then((url) => awsHelper.getImage(url))
  
      .then((result) => { 
  
  
  
          var resUrl = "\""+result+"\"";
  
  
  
          var args = [ 
  
              '-i', resUrl, 
  
              '-ss', '00:00:02', 
  
              '-vframes', '1', 
  
              '-f','image2', 
  
              'output.jpg'
  
          ]
  
          //console.log(args)
  
          var ffmpeg = require('child_process').spawn('ffmpeg', args);
  
  
  
          ffmpeg.on('error', function (err) {
  
              console.log(err);
  
          });
  
  
  
          ffmpeg.on('close', function (code) {
  
  
  
          });
  
  
  
          ffmpeg.stderr.on('data', function (data) {
  
              var tData = data.toString('utf8');
  
              var a = tData.split('\n');
  
              console.log("A",a); 
  
          });
  
  
  
          ffmpeg.stdout.on('data', function (data) {
  
              //
  
          });
  
  
  
  
  
      });

  }

  and i am getting the following error

  A [ 'ffmpeg version 4.0.2 Copyright (c) 2000-2018 the FFmpeg 
  
  developers' ]
  
  A [ '',
  
    '  built with Apple LLVM version 9.1.0 (clang-902.0.39.2)',
  
    '  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.0.2 --enable- 
  
  shared --enable-pthreads --enable-version3 --enable-hardcoded-tables -- 
  
  enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable- 
  
  gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable- 
  
  opencl --enable-videotoolbox --disable-lzma',
  
     '  libavutil      56. 14.100 / 56. 14.100',
  
     '  libavcodec     58. 18.100 / 58. 18.100',
  
    '  libavformat    58. 12.100 / 58. 12.100',
  
    '  libavdevice    58.  3.100 / 58.  3.100',
  
    '  libavfilter     7. 16.100 /  7. 16.100',
  
    '  libavresample   4.  0.  0 /  4.  0.  0',
  
    '  libswscale      5.  1.100 /  5.  1.100',
  
    '  libswresample   3.  1.100 /  3.  1.100',
  
    '  libpostproc    55.  1.100 / 55.  1.100',
  
    '"https://test-s3-bucket.s3.ap-south-1.amazonaws.com/user_gallery_assets/5b6936069ac2bf0602085367/gallery/images/5b7be08527641dee8c1f8134.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=xxxxxxxxx%2F20180821%2Fap-south-1%2Fs3%2Faws4_request&X-Amz-Date=20180821T095101Z&X-Amz-Expires=900&X-Amz-Signature=d7f81f4eed3d6c87c04dc1b0ad06beeb946afa33d417585f57fad72aeadb3ac0&X-Amz-SignedHeaders=host": No such file or directory',
  
    '' ]
  
  
  
  ffmpeg exited with code 1

• 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