[MPlayer-users] Disable colospace conversion

[Umar Qureshey]

The platform also has openGL libs, i assume they are standard libs, I'll look into building mplayer with that too.

I compiled svn mplayer with directfb 1.4.0 support which is the only version my platform supports. Can I expect hardware colorspace conversion acceleration if mplayer is utilizing directfb? 

mplayer currently is crashing with -vo directfb but if I can expect hw colorspace conv accel I can try to investigate and send a gdb backtrace here.

I have a quad core arm cortex a9 and i have a hard time believing decoding single 1080p h.264 stream in mplayer on 4 threads is saturating cycles.  SW colorspace conversion must be very taxing and if offloaded can probably provide smooth h264 decoding/
________________________________________
From: Andy Furniss [adf.lists at gmail.com]
Sent: Thursday, June 27, 2013 4:06 PM
To: MPlayer usage questions, feature requests, bug reports
Cc: Umar Qureshey
Subject: Re: [MPlayer-users] Disable colospace conversion

Umar Qureshey wrote:
> Hi,
> I am trying to figure out what the CPU load is when decoding an H.264 stream but without the colorspace conversion.
>
>   Is there a way in mplayer to just decode a file and not do colorspace conversion?

CSC is normally done by the -vo so normally hardware (gpu) eg. -vo xv or
gl or vdpau but may be done by cpu eg -vo x11.

So I suppose -vo null will do what you want but some of the difference
in cpu usage you see may not be CSC but because you are avoiding really
displaying which may (depending on -vo implementation details) show
extra cpu use when waiting to vsync with the display.

I assume -vo null will also avoid a mem copy as well.