3 ms·
It's fine for simple transcoding jobs. Once it reaches certain complexity you at the very minimum want to outsource it to a shell script to organize the argumen
by the8472 6y ago
It's fine for simple transcoding jobs. Once it reaches certain complexity you at the very minimum want to outsource it to a shell script to organize the arguments in multiple lines or switch to some other language bindings that aren't limited by shell argument parsing.
Compare the CLI and python invocation in this example:
https://github.com/kkroening/ffmpeg-python#complex-filter-graphs https://github.com/kkroening/ffmpeg-python#complex-filter-gr...
For some subsets of ffmpeg functionality (e.g. creating webm videos from other sources) there also are dedicated GUIs.
- jtchang 6y agoThat example is fantastic and really illustrates why a solid API can make things so much easier for the developer. Reading the command line I could barely tell what ffmpeg was doing. This also could mean the command line is badly designed.
- the8472 6y agoAs mentioned, splitting over multiple lines can help https://trac.ffmpeg.org/wiki/FilteringGuide#Multipleinputoverlayin2x2grid https://trac.ffmpeg.org/wiki/FilteringGuide#Multipleinputove...