[FFmpeg-devel] [PATCH] ffmpeg: Add option to force a specific decode format

[Eoff, Ullysses A]

> -----Original Message-----
> From: ffmpeg-devel [mailto:ffmpeg-devel-bounces at ffmpeg.org] On Behalf Of Carl Eugen Hoyos
> Sent: Wednesday, May 01, 2019 2:59 AM
> To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] ffmpeg: Add option to force a specific decode format
> 
> 2019-04-30 19:48 GMT+02:00, Eoff, Ullysses A <ullysses.a.eoff at intel.com>:
> >> -----Original Message-----
> >> From: ffmpeg-devel [mailto:ffmpeg-devel-bounces at ffmpeg.org] On Behalf Of
> >> Carl Eugen Hoyos
> >> Sent: Tuesday, April 23, 2019 12:48 PM
> >> To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> >> Subject: Re: [FFmpeg-devel] [PATCH] ffmpeg: Add option to force a specific
> >> decode format
> >>
> >> 2018-11-11 15:54 GMT+01:00, Mark Thompson <sw at jkqxz.net>:
> >> > Fixes #7519.
> >>
> >> > +    { "decode_format",  OPT_VIDEO | OPT_STRING | HAS_ARG | OPT_EXPERT
> >> > |
> >> > +                        OPT_SPEC | OPT_INPUT,
> >> >      { .off = OFFSET(decode_formats) },
> >> > +        "set output format used by decoder, fail if this format is not
> >> > available", "format" },
> >>
> >> Sorry if this was already asked:
> >> Why can't you use the input option "pix_fmt"?
> >
> > Are you saying that pix_fmt is already supported as in input option
> 
> I assume the reason that you sent the patch is that this is not
> the case.
> 
> > for decode or, instead, that this patch should enable pix_fmt to be
> > used as such instead of adding a new option name?
> 
> I believe this would make user's life easier, yes.
> 

I agree.  Mark, can you update your patch?

> Carl Eugen
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".