[MPlayer-users] differences between xv and xvidix

[Marcel Naziri]

hi,

> > is it normal that xv output is more cpu intensive than xvidix, although
> > the xv-extension supports hardware scaling? what are the differences for
> > mplayer while decoding? where comes the higher cpu-load?
>
> The difference comes from the fact that xfree86 video drivers are very
> poorly implemented (for example, some of them copy around and repack
> yuv formats with slow C loops!!) and that mplayer doesn't have access
> to video memory with xv, so at least one copy is required to get the
> picture from the shared memory buffer between mplayer and the X server
> to the video memory.

i see. and with xvidix mplayer copies the picture directly to the video 
memory, where it's accessable from the hardware scaler, right?
so, might it be, that the firegl driver segments the video-memory in an other 
way than the radeon-driver so that xvidix produces only strange patterns? or 
maybe xvidix invokes the wrong hardwarescaler?
i have uploaded a picture (fglrx.xvidix.jpg) from mplayer running with 
xvidix:radeon_vid under xfree86 started with atis firegl drivers to

http://www.uni-mainz.de/~nazim006/mplayer/

maybe these patterns are well known by some experts, so that they can examine 
what's going wrong. would be cool... :)
 
> > so are there any options to speed up xv output?
>
> You might be able to reduce the impact of this copy by using direct
> rendering (-dr) with mplayer.

with this option the movie is playing but the screen is only black... :(

greets
  marcel