So, I see comments to the effect of "need some n-bit type here", "depend on
<type> being n-bits", etc. Is there a reason you did not use the int32_t and
what not types? They are part of the new C standard, so will be portable.
As part of the library API change, it would be nice if library calls were
prefixed by some library name, i.e. mad_audio_output(). This way calls for
library routines are easily separated from other code. mapplay.c has a
function called audio_init(), yet audio_output() is from libmad. This is down
right confusing. Seems some functions are defined with the mad_ prefix and
others are not.
Trying to use 64bit fpm on my pII box causes the CPU load to go up from the
average 10% that top shows to around 15%, no noticable sound change.
How difficult would it be to add support for external dsp's, like on the sound
blaster mp3 cards?
I used to own a netwinder, how is the performance on the arm chips?