--- Ira Weiny iweiny@acm.org wrote:
It might not help your immediate problem, but unless you have cycles to burn (or think you can hear 24bits of audio resolution... :-) you could try adding '--enable-speed' and eventually '--disable-debugging'
This post caught my eye. Are you saying that --enable-speed decodes to 16-bit samples instead of 24? If so what else is different by enabling speed?
Its not quite as simple as that... :-)
There are many places in MAD where there are alternative ways to code a particular operation. Sometimes you can rewrite a function faster _and_ more accurate, but usually there are trade offs. This is especially true of MAD because it contains specific optimisations for particular processor architectures.
--enable-speed basically brings in a number of go faster tweaks, but still avoids doing anything to cause a significant reduction in sound quality. It certainly hasn't been 'tuned' to give 16bits (and the final accuracy is architecture dependent anyway).
You might want to look at the decoder compliance tests on the MAD homepage:
http://www.mars.org/home/rob/proj/mpeg/compliance/
These tests (with a synthetic benchmark....) would suggest that MAD with --enable-speed still gives _better_ than 16bits.
As always though, do some of your own listening tests before you decide :-)
Andre --
____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie