[MPlayer-users] mplayer benchmark interpretation

[Umar Qureshey]

Hello,

I run mplayer with:
DISPLAY=:0 ./mplayer -nosound -benchmark -lavdopts threads=4  ./1080p30_low_latency.ts

And I get:
[h264 @ 0x75be98]Missing reference picture, default is 0
[h264 @ 0x75be98]decode_slice_header error
[h264 @ 0x75be98]mmco: unref short failure
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [x11] 1920x1080 => 1920x1080 Planar YV12
[swscaler @ 0x82d278]No accelerated colorspace conversion found from yuv420p to rgb565le.
[swscaler @ 0x82d278]using unscaled yuv420p -> rgb565le special converter
V: 445.7 590/590  4% 157%  0.0% 0 0
[h264 @ 0x75be98]illegal short term buffer state detected
V: 456.7 920/920  5% 156%  0.0% 0 0
TS_PARSE: COULDN'T SYNC
V: 456.7 920/920  5% 156%  0.0% 0 0


BENCHMARKs: VC:   1.590s VO:  48.035s A:   0.000s Sys:   0.567s =   50.193s
BENCHMARK%: VC:  3.1679% VO: 95.7016% A:  0.0000% Sys:  1.1304% = 100.0000%

It looks like VO is taking 95% of the processing.
Would it be correct to assume that colorspace conversion is taking most of these cycles since it's being done in software?
Also, would compiling mplayer with openGL or directfb allow for this colorspace conversion to be offloaded to hardware assuming there is a hw colorspace converter?

Thanks.