Hi Thomas, > There is some code / macros in mpg123 for fixed point but they don't seem > to work atm or are not complete.
Just because I'm curious about it, which macros do you mean, in which files?? > As I see it you use mpg123 in floating point mode - on an arch without > floating point, you use kernel math emulation. The controller has got a floating point unit, but there are library functions, which I want to integrate for optimization, those are designed for fixed point arithmetic. E.g. to replace the inverse DCT part(I assume there's the most workload) would be easier using fixed point parameters. So not every part has to be in fixed point. > I didn't benchmark how well this performs (yet... I have a 486 and a 386 > system to play with - on the 486 mpg123 is clearly faster than mpg321, which > uses mad). So I assume 486 and 386 are fixed point as well, right? > > So if you want fixed point, you indeed better look into mad, because > that's the point they are very proud of: fully fixed point math. > For normal PC cpus, using the floating point math makes more sense - at > least with mpg123 it is more efficient. > Thanks a lot! Robert -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out _______________________________________________ mp3encoder mailing list mp3encoder@minnie.tuhs.org https://minnie.tuhs.org/mailman/listinfo/mp3encoder
