[FFmpeg-cvslog] r20502 - in trunk: configure libavcodec/allcodecs.c libavcodec/h263dec.c libavcodec/imgconvert.c libavcodec/vdpau.c libavcodec/vdpau.h libavcodec/vdpau_internal.h libavutil/pixfmt.h

Uoti Urpala uoti.urpala
Thu Nov 12 00:06:48 CET 2009

On Wed, 2009-11-11 at 22:40 +0000, Carl Eugen Hoyos wrote:
> Uoti Urpala <uoti.urpala <at> pp1.inet.fi> writes:
> > > 2) I do not know of any use for --enable-vdpau so far.
> > > (It is - sadly! - only used by statically compiled MPlayer)
> > 
> > What are you you talking about? VDPAU is enabled by default if the
> > headers are detected, so explicit --enable-vdpau isn't needed to trigger
> > the problems.
> True, I had not realized that.
> > And you should know that "statically compiled MPlayer" is
> > not the only case where FFmpeg VDPAU code is used - or what are you
> > referring to?
> Sorry, Uoti, forks don't count.

What idiocy is this? The git repo has a significantly better VDPAU
driver than current MPlayer svn (I'll need to add colorspace support and
maybe MPEG4 support though I'd prefer not breaking compatibility with
older VDPAU yet; however those are much smaller changes than would be
needed to fix all the stuff broken/missing in svn). But even if you want
to ignore the best existing implementation for "political" reasons,
there's AFAIK no reason why you could not link any MPlayer version with
separately compiled FFmpeg libraries and use VDPAU through those.

More information about the ffmpeg-cvslog mailing list