On Mon, May 11, 2015 at 02:16:15PM +0200, Michael Niedermayer wrote:
> On Mon, May 11, 2015 at 02:26:24AM -0300, James Almer wrote:
> > On 10/05/15 10:18 PM, Michael Niedermayer wrote:
> > > Signed-off-by: Michael Niedermayer <michae...@gmx.at>
> > > ---
> > >  libavutil/opt.c |   32 ++++++++++++++++++++++++++++++++
> > >  libavutil/opt.h |   21 +++++++++++++++++++++
> > >  2 files changed, 53 insertions(+)
> > > 
> > 
> > If this is meant to solve the whole debate from the "Tell users about 
> > -use_absolute_path"
> > thread, then i think it's a bit overkill.
> 
> yes i felt similarly, but
> 
> 
> > "Set <AVOption> to <value>" is generic enough
> > that works in any situation, be it for API user or ffmpeg.c, and could be 
> > used in every
> > av_log message.
> 
> it works, but it does not work well
> 
> consider the normal/generic case of a user application using
> libavcodec and maybe libavformat amongth probably other libs
> 
> the user sees a message saying something along the lines of:
> to do this set option foo to bar
> 
> The user most likly does not know that this message comes from
> libavcodec or libavformat, another lib or the application itself
> and likely the user doesnt even know the difference anyway
> 
> but the way to set the option can and does sometimes depend on for
> what the option is
> 
> in mplayer, its one of
> -lavdopts o=XXX=YYY
> -lavcopts o=XXX=YYY
> -lavfopts o=XXX=YYY
> -lavdopts XXX=YYY
> -lavcopts XXX=YYY
> -lavfopts XXX=YYY
> 
> in ffmpeg/ffplay/ffprobe its
> -XXX YYY
> 
> then theres
> --demuxer-lavf-o=XXX=YYY
> 
> and many more
> 
> also the message may originate from a libavcodec used by another lib
> instead of the user application
> 
> I think the average user would benefit from having the option dispayed
> with a exactly useable as is syntax
> 

I support this as well. No opinion on the API itself.

-- 
Clément B.

Attachment: pgpMR5kDw8AoD.pgp
Description: PGP signature

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to