search for: 32768,32767

...the 32-bit integer as 0x52F30000 As far as I know that's the proper conversion, yes? Simple adding some LSB to make it 32-bit. > but if [audioFile range] is 16 (i.e. 16 bits per sample), then > after conversion, the integer PCM samples in outputBuffers > should all be in the range [-32768,32767], that's the first > thing I'd check. OH so wait... What you're saying then is that the buffers always have to be filled with 32-bit-SIZED-FIELDS, inside of which exists a low-aligned integer sample value? So the VALUES aren't 32-bit integer, but the SPACE FOR THE SAMPL...

...esampler to downsample from 48 to 16 kHz. When I look to the downsampled signal before passing it to the encoder, there seems to be a bug in saturation. On overdrive, instead of holding a too big signal value at maximum (e.g. 32767) for some samples, the sample values I get from the resampler are [-32768,32767,-32768,...], i.e. the output of the resampler alters between the biggest possible negative value and the biggest possible positive value. Does the resampler use the hardware saturation available on Blackfin, or does it saturate by software? Can you point me to the place I have to look at ins...

...n I >> look to the downsampled signal before passing it to the encoder, >> there seems to be a bug in saturation. On overdrive, instead of >> holding a too big signal value at maximum (e.g. 32767) for some >> samples, the sample values I get from the resampler are >> [-32768,32767,-32768,...], i.e. the output of the resampler alters >> between the biggest possible negative value and the biggest >> possible positive value. > > This is definitely bad. Can you send me an example file. Also, can > you reproduce that problem without the Blackfin assemb...

...the downsampled signal before passing it to the encoder, >>> there seems to be a bug in saturation. On overdrive, instead of >>> holding a too big signal value at maximum (e.g. 32767) for some >>> samples, the sample values I get from the resampler are >>> [-32768,32767,-32768,...], i.e. the output of the resampler >>> alters between the biggest possible negative value and the >>> biggest possible positive value. >> This is definitely bad. Can you send me an example file. Also, can >> you reproduce that problem without the Blac...

...n I >> look to the downsampled signal before passing it to the encoder, >> there seems to be a bug in saturation. On overdrive, instead of >> holding a too big signal value at maximum (e.g. 32767) for some >> samples, the sample values I get from the resampler are >> [-32768,32767,-32768,...], i.e. the output of the resampler alters >> between the biggest possible negative value and the biggest >> possible positive value. > > This is definitely bad. Can you send me an example file. Also, can > you reproduce that problem without the Blackfin assemb...

...pled signal before passing it to the >>>> encoder, there seems to be a bug in saturation. On overdrive, >>>> instead of holding a too big signal value at maximum (e.g. >>>> 32767) for some samples, the sample values I get from the >>>> resampler are [-32768,32767,-32768,...], i.e. the output of the >>>> resampler alters between the biggest possible negative value >>>> and the biggest possible positive value. >>> This is definitely bad. Can you send me an example file. Also, >>> can you reproduce that problem w...

...re passing it to the >>>>> encoder, there seems to be a bug in saturation. On overdrive, >>>>> instead of holding a too big signal value at maximum (e.g. >>>>> 32767) for some samples, the sample values I get from the >>>>> resampler are [-32768,32767,-32768,...], i.e. the output of the >>>>> resampler alters between the biggest possible negative value >>>>> and the biggest possible positive value. >>>> This is definitely bad. Can you send me an example file. Also, >>>> can you reproduc...

...>>>>>> the encoder, there seems to be a bug in saturation. On >>>>>> overdrive, instead of holding a too big signal value at >>>>>> maximum (e.g. 32767) for some samples, the sample values I >>>>>> get from the resampler are [-32768,32767,-32768,...], i.e. >>>>>> the output of the resampler alters between the biggest >>>>>> possible negative value and the biggest possible positive >>>>>> value. >>>>> This is definitely bad. Can you send me an example file. &g...