John Hedges <[EMAIL PROTECTED]> writes:
> On Thu, Jul 08, 2004 at 06:55:46PM +0200, Goswin von Brederlow wrote:
>> John Hedges <[EMAIL PROTECTED]> writes:
>>
>> > [snip]
>> >
>> >> > However it might be that the splay decoder is comparable to that of
>> >> > mp3lib. My quick and not so reliable tests showed it to be about 15%
>> >> > slower but that was comparing a stock i386 splay with an optimised i686
>> >> > mplayer.
>> >> >
>> >> > I'm more than happy with splay and have used it for years. Well worth a
>> >> > sponsor - I'm sure you'll agree ;)
>> >> >
>> >> > Cheers
>> >> >
>> >> > John
>> >>
>> >> Maybe you can compare them a bit more and if mpglib is faster or
>> >> comparatively the same you could port splay over to that
>> >> library. Better to have common code for a common problem.
>> >>
>> >> MfG
>> >> Goswin
>> >
>> > I doubt the output from splay is byte for byte identical to that from
>> > mpglib (mp3lib?) so the comparison is likely to be subjective.
>>
>> yes mp3lib, sorry.
>>
>> > If you can give me good evidence that mpglib is better than splay then I
>> > might consider creating a new CLI project based on mp3lib (if there
>> > aren't any out there already).
>>
>> Support for amd64 and powerpc would be two major factors. :)
>
> I like this approach to bugfixing ;) Perhaps I'll follow your advice if
> there isn't an easy fix for these problem archetectures.
Its always better to have less code doing the same. That means less
places need to be fixed for a bug and less places need to be improved
for better performance.
It also saves diskspace for people having splay and mplayer installed
for example. :)
MfG
Goswin
