On 3/9/20, Mark Filipak <markfilipak.windows+ffm...@gmail.com> wrote: > On 03/09/2020 12:55 PM, Carl Eugen Hoyos wrote: >> Am Mo., 9. März 2020 um 17:45 Uhr schrieb Mark Filipak >> <markfilipak.windows+ffm...@gmail.com>: >> >>> I can't discern between command lines that work and command lines that >>> don't work and command lines that used to work but no longer and command >>> lines that should work but haven't been tested or that have bugs. >>> >>> I don't understand what's the problem? >>> >>> I simply want ff* command lines -- any type -- that are known/proven to >>> work. >> >> I (slowly) start to understand: >> This is not possible as command lines typically only work for specific >> input... > > Of course, I understand that. > >> - depending on input, a command line that is "proven to work" >> only produces an error. >> (Yes, FFmpeg is not that easily scriptable.) > > That's not correct. A command line that has worked, worked. I don't need > general templates. I just want command lines that have worked. I will > figure out why they are specific to specific cases.
Try this: https://amiaopensource.github.io/ffmprovisr/ _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
