> I'd like to use the benchmark program to figure out where aviplay
> development can focus it's work on to increase efficiency by lessening sync
> time and such and the amount of cpu used for actual decompression. To
Actually avifile developers are few steps ahead :)
We already now where is the problem...
We have also tool called kprof for getting quite precise time
estimation.
> MS Media player easily in avi playback and seeking, i mean obviously. Not
> sure if it'll ever be possible to do the hardware filtering mediaplayer does
> to make edges less jagged, some kind of blurring, but that's fine.
Use CPU autoquality (Options/misc) - or set postprocessing mode manualy.
But this is CPU intensive thing and I doubt that anything bellow 400MHz
could use it.
On my G400 and Bp6 Windows Media Player is left in dust and
Linux has incomperable perfomance and smoothness all the time.
The difference between mplayer and aviplay is the autoquality setting.
This has major impact on the quality as I would be unable to play most
of the movies at Quality4 - but occasional lowering is hardly noticable
(definitely less the frame dropping)
I think for the Voodoo - there have been some notes on the SDL FAQ
how they should use Xv overlay.
bye
--
Debian GNU/Linux maintainer - www.debian.{org,cz}
Zdenek Kabelac http://i.am/kabi/ kabi@{i.am, debian.org, fi.muni.cz}
Resistance is futile. You all will be packaged
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
