As I said I'm trying to run it on AWS Lambda not quite sure how to do that!
But I tried to run it with '-v 9 -loglevel 99' and strangely it worked this
time without crashing!! How could it be possible I have also move -y option
to the end before output file name. how could it be possible?!
2016-09-16 23:36 GMT+02:00 Ehsan Afzali :
> Yes I have also tried it with different ram allocation and always ends
> there. and here is the result with the latest git verision:
Please provide backtrace, disassembly and register dump
as explained on
Hi,
Yes I have also tried it with different ram allocation and always ends
there. and here is the result with the latest git verision:
"stackTrace": [
"ffmpeg version N-81664-g6f062eb-static
http://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2016 the FFmpeg
developers",
" built with
On Fri, Sep 16, 2016 at 14:16:40 +, Ehsan Afzali wrote:
> I've created a gist with both outputs here:
> https://gist.github.com/eafzali/85a056468d6449a0f4a01d4422a114e2
You should have pasted that to the list, it's not too long.
> "[mjpeg @ 0x47e6260] marker parser used 9746934 bytes
Hi,
I'm trying to run ffmpeg on AWS Lambda to convert some jpg sequence to mp4
video.
I'm Running this command:
/bin/sh -c ffmpeg -y -loglevel debug -framerate 1 -i
/tmp/ae20d930-7c13-11e6-9345-b13b0efa257b/%03d.jpg -c:v libx264 -r 30
-pix_fmt yuv420p