I think you will find that you have to decipher ffmpeg cmd line yourself It is like Unix awk where the definition of the language does not help you that much - by trial and error you determine the actual behavior
Also even if someone post hundreds of examples - you will find they work differently for you depending on version and input and slight variation in arguments / inputs. It will be much more meaningful if you do with your inputs - it probably sounds to people like you are asking for a understand ffmpeg by taking one pill - please make such a pill for me. Just being open Sent from my iPhone > On Mar 9, 2020, at 11:27 PM, Mark Filipak > <[email protected]> wrote: > >> On 03/09/2020 12:22 PM, Paul B Mahol wrote: >>> On 3/9/20, Mark Filipak <[email protected]> wrote: >>>> On 03/09/2020 06:38 AM, Tobias Rapp wrote: >>>>> On 08.03.2020 10:03, Mark Filipak wrote: >>>>> The documentation is long on explanations of pieces, but short on how >>>>> to create working command lines. >>>> >>>> If you are just interested in general about what FFmpeg tools can do, >>>> you can find some command-line examples in the Wiki: >>>> http://trac.ffmpeg.org/wiki#Encoding >>> >>> I want hundreds of command lines that work. >> I want to win a lotto. > > Why am I getting no constructive responses? > > _______________________________________________ > ffmpeg-user mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
