[MPlayer-users] Jerky/Juddery/interruptible output - COMMON ANSWER

[Brian J. Murrell]

On Mon, Feb 25, 2002 at 10:01:16AM +0300, Nick Kurshev wrote:
> Hello, Brian!

Hi Nick,

> V - means video codec time ( rename that into VC:)
> VO - means video driver time
> A = audio codec + audio driver time
> sys - system time = kernel time + media reading time + other processes

OK, so I benchmarked my Athlon TB 800Mhz playing a 640x480x5Mb/s
stream with -vo x11 -benchmark -frames 5000:

A: 167.0 V: 167.0 A-V:  0.015 ct:  0.006  5000/5000  26% 15%  1.4% 29 0 0%
AVE BENCHMARKs: VC:  44.773s VO:  26.481s A:   2.325s Sys:  93.327s = 166.907s
AVE BENCHMARK%: VC: 26.8254% VO: 15.8658% A:  1.3931% Sys: 55.9157% = 100.0000%

MAX BENCHMARKs: VC: 447.832s VO:1063.481s A: 213.579s
MAX BENCHMARK%: VC:268.3131% VO:637.1711% A:127.9632% = 1033.4474%
TOTAL BENCHMARK: from 4971 frames should be dropped: 8 at least

So it's saying that I need a processor 103x as powerful as I have to
playback properly?

a 320x240x5Mb/s stream shows:

A: 153.2 V: 154.1 A-V: -0.861 ct: -0.128  4617/4617  12%  1%  1.4% 47 0 0%
AVE BENCHMARKs: VC:  18.694s VO:   2.692s A:   2.218s Sys: 129.742s = 153.346s
AVE BENCHMARK%: VC: 12.1906% VO:  1.7554% A:  1.4465% Sys: 84.6074% = 100.0000%

MAX BENCHMARKs: VC:  94.222s VO: 789.537s A: 138.523s
MAX BENCHMARK%: VC: 61.4440% VO:514.8726% A: 90.3335% = 666.6501%
TOTAL BENCHMARK: from 4569 frames should be dropped: 1 at least

So again, I need a processor 6x as powerful as I have?

> The diagram of my 'CPU Meter' contains cones.

My graphical processor meter never even once touches 100%, or really
even goes near it for that fact.

I find the numbers to be misleading in the least.  Maybe I am
misinterpreting them?

> > With regard to the judder I was reporting on my Radeon with vidix and
> > playing full screen, I also saw a lot of tearing last night too.
> > Should I see tearing at all, ever, if mplayer is co-ordinating with
> > vsync?
> > 
> Yes - about 2 weeks! (Finely radeon_vid driver).

Are you saying for the last 2 weeks vsync in radeon_vid has been
broken?  But it's fixed now?

b.

-- 
Brian J. Murrell