Hi Carl, I'm using the latter, the ffmpeg CLI. The entire command is:
ffmpeg \ -i DV_b2.mp4 \ -i SCREEN_ba.mp4 \ -i SCREEN_d9.mp4 \ -i SCREEN_6d.mp4 \ -i SCREEN_bb.mp4 \ -threads 1 \ -filter_complex 'filter here' \ -map '[cc8]' \ -c:v ffv1 \ out.avi I've also tried x264 in the matroska and mp4 containers. As for logs would you like verbose, debug, or trace level? On Thu, May 3, 2018 at 6:04 PM, Carl Eugen Hoyos <[email protected]> wrote: > 2018-05-03 23:06 GMT+02:00, Kevin Mark <[email protected]>: > >> I'm getting an OOM with the following ffmpeg complex filtergraph: > > Just a complex filtergraph? > Did you write a program that calls libavfilter functions and libavfilter > eats memory? Then please post on the libav-user mailing list. > > Or did you call ffmpeg (the cli supported here)? Then please post > your actual command line including complete, uncut console output. > Some output containers necessarily eat memory. > > Carl Eugen > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
