As you might know, I put up video on Udemy, which has proven to be a great way to distribute some of my video learnings.
Let's talk through the problem that we're looking to solve with Lambda Layers. Gojko Adzic's fantastic image describing this on Video Watermarking Issue
The benefit is that instead of having to bundle up our dependency with our lambda (100mb+ each time we deploy), we can inherit its functionality (deploys remain tiny). It can be referenced directly as you'll see later we can call our layer from /opt/bin/ffmpeg. The Layer itself is attached to the /opt directory of your lambda. Layers are a way to get around this by letting you mount a common piece of code to the function at runtime that can be leveraged. A lot of the time I find myself not able to use Lambda / Serverless patterns purely because of a dependency on a. Lambda Layers are a relatively new way of extending the use cases of your cloud functions. Here was my final command: ffmpeg -f "concat" -safe "0" -protocol_whitelist "file,http,https,tcp,tls" -i "./inputs.txt" -codec "copy" "./concated.Get the code for this post! t04glovern/udemy-video-utils The solution is to also add tcp to the protocol whitelist as well (also tls if you want to support HTTPS). I realized that the first word in brackets before the error was the protocol that was being rejected. Look at the very first word in those errors. Then I noticed the small diference between the previous two errors. http was clearly in the protocol whitelist.
I did not understand why my HTTP protocol input was still being rejected. I thought I would be able to solve this by simple adding -protocol_whitelist file,http,https but then the error became: Protocol not on whitelist 'file,http,https'! Then I got the error: Protocol not on whitelist 'file,crypto'! This was solved by adding the -safe 0 argument.
I was trying to use FFmpeg's concat demuxer like so: # inputs.txtįfmpeg -f "concat" -i "./inputs.txt" -codec "copy" "./concated.mp4"įirst I got the error: Unsafe file name '' Use -safe 0 and -protocol_whitelist file,http,https,tcp,tls arguments. Yo1dog blog Fix for FFmpeg "protocol not on whitelist" Error for HTTP(S) URLs May 25th, 2016
0 kommentar(er)
