[MPlayer-dev-eng] [PATCH]Prefer vdpau over xv if available

Reimar Döffinger Reimar.Doeffinger at gmx.de
Mon Mar 30 13:48:06 CEST 2009


On Mon, Mar 30, 2009 at 11:06:31AM +0000, Carl Eugen Hoyos wrote:
> Reimar Döffinger <Reimar.Doeffinger <at> gmx.de> writes:
> 
> > > Attached patch would revert r28688.
> > > Since I expect it to be controversial, I'll not commit before comments 
> > > were made.
> > 
> > "Why" is the obvious question.
> 
> Hardware de-interlacing and simpler usage of hardware-decoding (-vc ff..vdpau vs
> -vc ff..vdpau -vo vdpau).

Well, it's a bad solution for this, getting rid of the need for -vc
would be more useful, and will happen one day.

> > Xv has been tested for a long time, and
> > with this change crashes in VDPAU preinit will break MPlayer with
> > default configuration completely.
> 
> I don't disagree but where do you see the possibility for crashes in preinit()?

I had it once, probably due to library and kernel module version
mismatching (or was just no kernel module available?). I didn't write it
down, and it might not be an error anymore, but gl and vdpau seem much
more fragile when such things happen.

> > While I'd have to investigate more, VDPAU also seems to be a lot (like 4x)
> > slower than xv when the "blit" engine is used
> 
> I will try to reproduce this. (How do I see if blit is used? With older nvidia
> driers, I saw incredible tearing, but that is gone with 185.13.)

I still use 180.37 (I think), it might be something else since I
remember disabling composite so it should not longer use the "blit"
engine. Probably it got broken somehow else...



More information about the MPlayer-dev-eng mailing list