large filtergraph yields abysmal performance
|Reported by:||mldwrp||Owned by:|
|Version:||4.3.5||Keywords:||performance, filter_complex, filters|
|Blocking:||Reproduced by developer:||no|
|Analyzed by developer:||no|
This looks like either a bug in design or some configuration mistake: a large filtergraph (I'm stiching small pieces of several streams together, the filtergapth is > 200KB) makes the process run for like 60 hours (with the [correct] result just over 200MB).
You're welcome to examine the offending filtergraph here: https://gist.githubusercontent.com/costa/14aff290d6b30edf131500fc6823147b/raw/37520d452df8ded3649899adf90d0204f8a9f75d/ffmpeg-filtergraph-script
I'm willing to try things if you have any clue, so, any help is greatly appreciated.
p.s. if you're wondering how this filtergraph is generated, see the Ruby FFmpeg-micro-engine gem: https://rubygems.org/gems/ffmprb