AWS re:Invent 2017: Building a Serverless Pipeline to Transcode a Two-Hour Video in (SRV314)
Why Stack Overflow recommends it
Stack Overflow users link it when debugging FFmpeg on AWS Lambda, since the talk describes the stdin inheritance problem that breaks transcoding there.
Recommended by 1 people across 1 different months, 2018 to 2020.
What it is
An AWS re:Invent 2017 session where Verizon's Revvel team explains how it moved video transcoding from EC2 instances to a serverless pipeline built on AWS Lambda and S3. It covers massive parallelization to transcode a full movie in minutes, plus lessons on building a CI/CD pipeline for Lambda functions.
What people said
Recommends Franciszek Szombara · 2020-08 · Stack Overflow · on “FFmpeg on aws lambda - Invalid NAL unit size”
This solution is Python specific, but maybe the video linked in the answer I referred to will give you some ideas. [this video]
Cites jmkmay · 2018-08 · Stack Overflow · on “FFmpeg transcoding on Lambda results in unusable (static) audio”
Alright this is a fun one. So it turns out the Python subprocess inherits stdin from some Lambda processes going on in the background. I was watching this AWS re:Invent keynote [this video] and he was describing some issues they were having w.r.t. this issue. I added stdin=subprocess.DEVNULL to the subprocess call and the audio is now fixed. Very interesting bug if you ask me.
Cites derekhh · 2019-02 · Stack Overflow · on “FFMPEG failing in AWS Lambda”
I've run into the exact same issue today and spent hours. But finally I came across this SO answer [LINK] and found the solution. Basically you need to make sure you are not passing STDIN to the FFmpeg process. It's mentioned in the re:Invent talk on this slide [this video] .