How do you tell if you're using aKode?
neil at hakubi.us
Fri Jul 23 21:16:57 BST 2004
-----BEGIN PGP SIGNED MESSAGE-----
On Friday 23 July 2004 09:43 am, Stefan Gehn wrote:
> Another way is detect by hearing. If you get blips and blops on seeking
> or on buggy strams then it's mpeglib, otherwise it's aKode. Or you run
> cvs up on all your kde sources at once while listening to a file on the
> same hdd. If it skips like mad on extended hdd-trashing times then it's
> mpeglib, otherwise it's aKode (yes, I can cvs up all of kde without a
> single dropout now, not even xmms managed that back when I used it).
So it does its own buffering? How much latency does akode add?
Neil Stevens - neil at hakubi.us
"The world is a dangerous place to live; not because of the people who
are evil, but because of the people who don't do anything about it."
-- Albert Einstein(?)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the kde-multimedia