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

[Nick Kurshev]

Hello, Brian!

On Sun, 24 Feb 2002 15:28:25 -0500 you wrote:

> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> On Sun, Feb 24, 2002 at 03:34:19PM +0300, Nick Kurshev wrote:
> > Hello!
> 
> Hi Nick,
> 
[snip]
> 
> > Source movie: 720x480 30fps MPEG4-DIVX.
> > (This beauty has length ~90 min and was fitted into 1 CDROM. Size: 690MB)
> > 
> > My benchmarks:
> > mplayer -vo xvidix -fs -zoom -benchmark -frames 5000 SecondSkin.avi
> > AVE BENCHMARKs: V:  47.457s VO:   0.010s A:   2.952s Sys: 116.429s =  166.849s
> > AVE BENCHMARK%: V: 28.4434% VO:  0.0061% A:  1.7693% Sys: 69.7813% = 100.0000%
> > 
> > MAX BENCHMARKs: V: 197.860s VO:   0.000s A:  42.400s
> > MAX BENCHMARK%: V:118.5862% VO:  0.0000% A: 25.4122% = 143.9984%
> 
> I could not find anything in DOCS about benchmarking other than the
> few words the man page has.  Can you explain the what the above
> numbers are reporting?
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

[snip]
> > Just for info:
> > benchmarks with LostInSpace.vob 720x480 30 fps (was downloaded from hungarian
> > server which was pointed by Arpi)
> > AVE BENCHMARKs: V:  18.347s VO:   0.003s A:   1.844s Sys:  43.127s =   63.321s
> > AVE BENCHMARK%: V: 28.9750% VO:  0.0048% A:  2.9116% Sys: 68.1086% = 100.0000%
> > 
> > MAX BENCHMARKs: V:  31.311s VO:   0.000s A:  14.464s
> > MAX BENCHMARK%: V: 49.4482% VO:  0.0000% A: 22.8432% =  72.2913%
> 
> So what's the difference between SecondSkin.avi and LostInSpace.vob
> that you have enough CPU to play the latter but not former?
LostInSpace.vob is DVD's stream that easy to decoding.
SecondSkin.avi is MPEG4-DIVX stream that have highest compression
(It was 8GB DVD's stream compressed into 700MB CDROM stream with
some quality losing).

> 
> > So try new benchmark first!
> 
> Would love to.  :-)
> 
> Also, if as your benchmark reports, you need 143.9984% CPU, you must
> see your CPU pegged while you are playing, no?  If not, why not?  I
> *never* see my CPU pegged just playing video files (mostly mpeg1s).
The diagram of my 'CPU Meter' contains cones.
> 
> 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).
> b.
> 
> 
> -- 
> Brian J. Murrell
> 
> _______________________________________________
> RTFM!!!  http://www.MPlayerHQ.hu/DOCS
> Search:  http://www.MPlayerHQ.hu/cgi-bin/htsearch
> http://mplayerhq.hu/mailman/listinfo/mplayer-users
> 


Best regards! Nick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-users/attachments/20020225/f7236be5/attachment.pgp>