[Ffmpeg-devel] [PATCH] Update docs according to new "ab" parameter unit

Benoit Fouet benoit.fouet
Tue Mar 6 14:33:04 CET 2007

Michel Bardiaux wrote:
> Michael Niedermayer wrote:
>> Hi
>> argh i cant even sleep a few hours without people flaming each other
> I wouldnt say this has reached the level of 'flame war'. Barely
> 'lively arguing'.

>> without anyone even bothering to look at the code :(
>> not to mention the thread where i asked if anyone would mind the -b
>> change ...
>> so again
>> -foobar sets  foobar for all contextx
>> -afoobar sets foobar for the audio context
>> -vfoobar sets foobar for the video context
>> that is nicely consistent but changes a few cases like -ab X -b Y in
>> unexpected ways
> And -r 25 would set the video fps *and* the audio sampling rate to 25?
> That cant be good. What foo is a reasonable bar for both A and V?
no, rate works in a different way...

>> we could of course add -b with a function which av_log()exits()
> Or keep -b as synonymous to -vb, -r as synonymous to -vr, etc...
i don't think it's worth it...

>> or we could revert the whole and find a different solution how to set
>> parameters for specific contexts with AVOption
> That might be the more prudent course.
>> one alternative solution would be to duplicate all AVOptions which are
>> usefull for more then one out of (Audio,Video,subs) in that case we
>> could
>> give each any name and default we like but it would increase the
>> number of AVOptions and the simple generic afoobar is the matching
>> part of vfoobar
>> would be lost unless we are very carefull with selecting the names
> A radical proposal: keep all existing options as compatibility
> synonyms, and go for getopt_long (--vbitrate 200k) for a new set of
> options.
> HaND,

More information about the ffmpeg-devel mailing list