On Sun, 16 Aug 2015 14:33:18 +0200
wm4 <nfx...@googlemail.com> wrote:
> On Sat, 15 Aug 2015 21:27:58 -0700
> Philip Langdale <phil...@overt.org> wrote:
>
> > The h264 decoder reports 4.1 as its maximum level, but it will
> > decode 5.1 4K video just fine. In practice, the published level
> > limits in vdpau do not communicate anything that's actually useful.
> >
> > Signed-off-by: Philip Langdale <phil...@overt.org>
> > ---
> > ffmpeg_vdpau.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/ffmpeg_vdpau.c b/ffmpeg_vdpau.c
> > index b05e557..b0eace5 100644
> > --- a/ffmpeg_vdpau.c
> > +++ b/ffmpeg_vdpau.c
> > @@ -289,7 +289,7 @@ do {
> >
> > s->hwaccel_context = vdpau_ctx;
> > } else
> > - if (av_vdpau_bind_context(s, ctx->device,
> > ctx->get_proc_address, 0))
> > + if (av_vdpau_bind_context(s, ctx->device,
> > ctx->get_proc_address, AV_HWACCEL_FLAG_IGNORE_LEVEL)) goto fail;
> >
> > ctx->get_information_string(&vendor);
>
> If that's what you found - sounds ok. Maybe we could also add a
> suggestion to the API doxygen to always pass this flag?
It's what you found too - mpv sets this flag today. :-) This change is
specific to the command line tool, of course.
I'll add it to the doxygen.
--phil
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
