[MPlayer-users] Hich cpu uceage
Peter Christy
christy at attglobal.net
Thu Sep 22 18:20:32 CEST 2011
Thanks, Tom, that was very helpful!
The one bit of documentation I forgot to supply was my mplayer config:
### Video Drivers ###
vo=vdpau
#vo=vaapi:deint=2
### Audio Driver option ###
ao=alsa:device=hw=1.0
### Display Options ###
fs=yes
stop-xscreensaver=yes
which I pinched from my netbook, hence the commented out vaapi line. I was
half-way there!
I have now added a vc= line as suggested, and the cpu useage has dropped to
2%! Quite an improvement!
I'm still getting the sds errors, which is a bit worrying, but it all seems to
be running reasonably smoothly now!
One other question: Is the vc= line necessary for vaapi? I'm not using it on
my netbook, and it seems to be running OK, but any improvements would be
appreciated!
I just wish the developers would incorporate the vaapi patches properly, as
the splitted-desktop mplayer is quite long in the tooth now!
Thanks again for your help!
--
Pete
christy at atglobal.net
> Vaapi is not the way to go with nvidia, you want to use vdpau, not
> vaapi via vdpau. With ATI/AMD, you have to use vaapi..
>
> Mplayer is choosing vdpau as the output path for you (instead of
> xv,x11 etc), but the codec being used is (unaccelerated) ffmpeg. The
> reason for this is that you have to explicitly choose the codecs you
> want accelerated by vdpau. You can do this either on the command line,
> or in your stock mplayer config:
>
> [default]
> vo=vdpau,xv
> vc=ffh264vdpau,ffvc1vdpau,ffmpeg12vdpau,ffwmv3vdpau,
>
>
> On the command line:
>
> mplayer -vo vdpau -vc ffh264vdpau,ffvc1vdpau,ffmpeg12vdpau,ffwmv3vdpau,
>
> The trailing ',' means 'try other codecs if none of these are
> appropriate'. The precise -vc option depends upon what vdpau features
> your card supports, eg I don't have 'ffodivxvdpau' (to accelerate
> divx) as my card doesn't support it.
>
> Cheers
>
> Tom
More information about the MPlayer-users
mailing list