Recherche avancée

Sur d’autres sites (10199)

• ffmpeg code not working aws lambda environment

  5 janvier 2021, par Akash Das

  I followed this article and deployed the Lambda functions and layers and set it up all fine.

  


  But I am facing a problem when I try converting the mp4 video into a 720p video, the ffmpeg commands that work in my Ubuntu 20.04 are not working in the Lambda and gives me error in the form of 0kb files in the destination folder.

  


  Can someone explain why this is happening ? The command that I used was :

  


  ffmpeg -i input.mp4 -s 1280x720 -c:a copy output.mp4


  


  I use this command in the Python file

  


  ffmpeg_cmd = "/opt/bin/ffmpeg -i \"" + s3_source_signed_url + "\" -f mp4 -s 1280x720 -c:a copy -" ___ . 


  


  This is the error I get :

  


  

  


  The problem is that I used a code like this to get only the audio

  


  ffmpeg_cmd = "/opt/bin/ffmpeg -i \"" + s3_source_signed_url + "\" -f mp3 -ab 192000 -vn  -" ___ . 


  


  And it works as expected.

  


• ffmpeg single output container with 4 audio channel to AWS IVS

  28 juillet 2021, par Yusufu

  Trying to send 1 video and 4 different audios to AWS IVS in single container. Which container or muxer should I use ?
FLV doesn't support multi audio, matroska doesn't support rtmp I guess link.
3GP and mp4 containers doesn't give me error but neither video showing on IVS

  


  For simple try I am using this command.

  


  ffmpeg -re -stream_loop -1 -i sample.mkv -r 30 -c:v libx264 -pix_fmt yuv420p -profile:v main -preset veryfast -x264opts "nal-hrd=cbr:no-scenecut" -minrate 3000 -maxrate 3000 -g 
60 -c:a aac -ac 2 -ar 44100 -vb 400k -maxrate 400k -minrate 400k -bufsize 800k -movflags frag_keyframe+empty_moov -f mp4 rtmps:someurls


  


  the above command doesn't include multi audio output so just trying to send except the flv format

  


• ffmpeg file conversion AWS Lamda

  10 avril 2021, par eartoolbox

  I want a .webm file to be converted to a .wav file after it hits my S3 bucket. I followed this tutorial and tried to adapt it from my use case using the .webm -> .wav ffmpeg command described here.

  


  My AWS Lambda function generally works, in that when my .webm file hits the source bucket, it is converted to .wav and ends up in the destination bucket. However, the resulting file .wav is always 0 bytes (though the .webm not, including the appropriate audio). Did I adapt the code wrong ? I only changed the ffmpeg_cmd line from the first link.

  


  import json
import os
import subprocess
import shlex
import boto3

S3_DESTINATION_BUCKET = "hmtm-out"
SIGNED_URL_TIMEOUT = 60

def lambda_handler(event, context):

    s3_source_bucket = event['Records'][0]['s3']['bucket']['name']
    s3_source_key = event['Records'][0]['s3']['object']['key']

    s3_source_basename = os.path.splitext(os.path.basename(s3_source_key))[0]
    s3_destination_filename = s3_source_basename + ".wav"

    s3_client = boto3.client('s3')
    s3_source_signed_url = s3_client.generate_presigned_url('get_object',
        Params={'Bucket': s3_source_bucket, 'Key': s3_source_key},
        ExpiresIn=SIGNED_URL_TIMEOUT)
    
    ffmpeg_cmd = "/opt/bin/ffmpeg -i \"" + s3_source_signed_url + "\" -c:a pcm_f32le " + s3_destination_filename + " -"
    
    
    command1 = shlex.split(ffmpeg_cmd)
    p1 = subprocess.run(command1, stdout=subprocess.PIPE, stderr=subprocess.PIPE)

    resp = s3_client.put_object(Body=p1.stdout, Bucket=S3_DESTINATION_BUCKET, Key=s3_destination_filename)

    return {
        'statusCode': 200,
        'body': json.dumps('Processing complete successfully')
    }