On Tue, Aug 25, 2015 at 8:08 PM, Timothy Gu <timothyg...@gmail.com> wrote:
> On Tue, Aug 25, 2015 at 5:06 PM Ganesh Ajjanagadde <gajja...@mit.edu> wrote:
>
>> On Tue, Aug 25, 2015 at 7:47 PM, Timothy Gu <timothyg...@gmail.com> wrote:
>> > ---
>> > doc/ffmpeg.texi | 4 ++++
>> > ffmpeg_opt.c | 14 ++++++++++++++
>> > 2 files changed, 18 insertions(+)
>> >
>> > diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
>> > index 51a4ec5..e1d8562 100644
>> > --- a/doc/ffmpeg.texi
>> > +++ b/doc/ffmpeg.texi
>> > @@ -698,6 +698,10 @@ is not specified, the value of the @var{DISPLAY}
>> environment variable is used
>> > For DXVA2, this option should contain the number of the display adapter
>> to use.
>> > If this option is not specified, the default adapter is used.
>> > @end table
>> > +
>> > +@item -hwaccels
>> > +List all hardware acceleration methods supported in this build of
>> avconv.
>> > +
>>
>> This is ffmpeg, not avconv.
>>
>
> Oops. Fixed locally.
>
> Doesn't this belong in cmdutils.c?
>>
>
> No.
>
>
>> What was your rationale for placing it here?
>>
>
> cmdutils.c is shared for all ff* programs. -hwaccel is only supported in
> ffmpeg.
Why?
I don't know about this and I might be naive here,
but isn't hardware acceleration useful for decoding as well?
In this case it would be relevant to at least ffplay as well as ffmpeg.
>
> Timothy
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
