For Cley Faye,
The structure of my command is:
- first I input images with:
-framerate 30 -loop 1 -t no_seconds -i 'path_to_resource'
- for input I add a background and silent audio
-r 30 -f lavfi -i color=black -f lavfi -i aevalsrc=0
- I add output framere
-r 30
- then I start a complex filter where I use
scale/crop/setpts/format/fade to adjust resource as I need,
then every variable resulting in format are overlayed, first over the
background and the next one on the last variable created like here:
[background_resource_index:v]scale=iw*min(854/iw\,480/ih):ih*min(854/iw\,480/ih),
pad=854:480:(854-iw*min(854/iw\,480/ih))/2:(480-ih*min(854/iw\,480/ih))/2,trim=duration=total_duration[over0];[over0][va0]overlay[over1];
In the end, last variable will be named [outv].
The output specifications are:
-vcodec libx264 -shortest -acodec libfaac -ab "96k" -ac 2 -map 55:0
-threads 0 -map "[outv]" -t 378 -vprofile main -movflags faststart
-preset medium -b:v 800k -minrate 500k -maxrate 800k -bufsize 1600k -g
120 -refs 2 -keyint_min 25 -sc_threshold 40 -flags +loop -qmin 10
-qmax 51 -qdiff 4 -i_qfactor 0.71 -partitions
+parti4x4+partp8x8+partb8x8 -me_method umh -pix_fmt yuv420p -rc_eq
'blurCplx^(1-qComp)'
Is this enough ? I need to say that I have a very large ( huge ) command
that is being executed so a paste isn't good, and once I attaced to the
output specification the '-report' and the report already had over 100k
lines for 30s of output, while my total time is over 360.
On 09.05.2016 01:17, Cley Faye wrote:
2016-05-09 0:04 GMT+02:00 ionut <ionut.raduc...@webland.ro>:
My output is .mp4 and I am using like 50-100 images to create it. Image
resolutions are very big and I do a lot of complex filtering. I have some
cases that my cmd run out of memory and the ffmpeg process is killed.
One more thing, I have the next warning:
[png_pipe @ 0x1f9c480] Stream #0: not enough frames to estimate rate;
consider increasing probesize
But if I add some big analyze and probesize values like: ( saw in an
example over the internet )
-analyzeduration 6000M -probesize 6000M
The process is killed even faster.
I'm curious, it seem that you're piping the images into the ffmpeg
process, so I'm tempted to say you need to specify the framerate in the
command line. However, on a recent ffmpeg version it simply defaults to 25.
Obviously setting such high probesize is probably never useful anyway...
Can somebody give me some tips about why is this happening ?
I know that I haven't given you to many details, please hit me back for
more details, thank you!
To begin with, the full command and output log would be useful. Preferably
a minimal working example if you have a really complex filter. The problem
might be on the way you provide the source images to ffmpeg (just a hunch).
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
