|
|
|
|
|
by shevy-java
96 days ago
|
|
FFmpeg is really great. The only wish I'd have is for the usage to become simpler - both for regular stuff, but also for advanced filtering. If anyone remembers, avisynth was pretty cool back in the days. You could kind
of script video/audio manipulations, a bit like a UNIX/Linux pipe, but kind of
simpler, in my opinion. FFmpeg allows for many similar operations, but remembering
anything here is ... hard. I'd love for the whole usage API to become much simpler, but it seems nobody among the ffmpeg dev team is considering this. :( I can't be the only one with that wish though ... It does not diminish ffmpeg being so great in general, but I think it could be better. |
|
Debugging commands gets hairy the more complex they get but you'll get muscle memory on how to search/replace to make line breaks to make it easier, similar to breaking up gnarly SQL. The worst part about debugging is the error messages can be misleading when it interprets the filter chain incorrectly because of some issue you've typoed in there somewhere. Even those start to become recognizable as "it thinks this, which means I probably messed up this other thing instead". To be fair, I work with ffmpeg daily using some commands that make your eyes bleed. So for someone using it every now and then, the practice from repetitive use just takes longer.
Also, saving things as shell scripts helps a lot. A simple script that does the same thing with a few adjustable params can be done with %1, %2 usage or even cleaner with getopts. You can then change small things within a tested complex command.