Hi !
This isn't a serious problem but the restrictive acceptance of encoder delay/padding values kind of renders my mp3 editing software useless.
My app is supposed to do sample granular splitting for seamless (no gaps and no clicks) playback of tracks (split out of a large mp3) on LAME tag aware players. It's quite sophisticated (handles bitreservoir issues properly, calculates a new 'mp3 header' with appropriate encoder delay/padding settings).
To make playback really seamless and to handle bitreservoir issues properly I sometimes have to increase the encoder delay value to something around 3000.
Unfortunately Foobar (v0.8.1) only supports encoder delay values up to 1152 and ignores encoder delay/padding completely if the delay exceeds 1152 or the padding exceeds 2304.
Is this a Foobar related problem or is mpglib to blame?
Do I have to live with this or is there any chance of making the decoder more robust?
The LAME tag specification clearly allows both values to be as high as 4095. I'd be happy if encoder delays as high as 2880 (576*5) are supported (it doesn't need to be more for my purpose).
Thanks,
Sebi