[FFmpeg-devel] [PATCH] lavf/tee: provide aliases for the f and bsfs special options
stefasab at gmail.com
Sat Aug 3 11:47:38 CEST 2013
On date Thursday 2013-08-01 22:05:01 +0000, Paul B Mahol encoded:
> On 8/1/13, Stefano Sabatini <stefasab at gmail.com> wrote:
> > On date Thursday 2013-08-01 13:55:12 +0200, Nicolas George encoded:
> >> Le tridi 13 thermidor, an CCXXI, Paul B Mahol a ecrit :
> >> > I'm against this, its just add extra overhead, and its ugly.
> >> I think I concur.
> > Dropped, especially since this doesn't avoid the problem, which is
> > private options masking global options with the same name. Right now
> > if we add a global option named "f" or "bsfs" this will be always
> > overriden by the private option with the same name.
> IMHO 'proper' solution would be giving arguments to
> in similar way as its done for filters.
> Yes this is syntax/escaping nightmare but adding prefix to each private
> option into codebase looks fishy.
One possibililty would be:
> In annother way, perhaps prefixes could be accepted from command line....
We have already a category system, and we could assume that a component
identifier in each category must be unique. This way we would have for
-muxer/flags +bar -codec/flags -bar
Note that this stills doesn't fix the generic/private namespace
conflict, which is a separate issue (happens if we add a private
option with a name already used by a generic option, or a generic
option with a name already used by a private option).
FFmpeg = Fantastic and Fundamental Maxi Purposeless Evil Genius
More information about the ffmpeg-devel