hello,
i use ov_read_float in my vorbis-player-project to get my pcm data.
i've noticed, that many of these floating point values are slightly out of the "official" amplitude range between -1.0f and 1.0f.
so why is that?
is it okay, just to clip it? JACK expect values *only* in range of -1 and 1.
thank you!
marco
Full Version: amplitude range (floating point)
QUOTE (marco_mania @ Sep 24 2006, 16:39) 
hello,
i use ov_read_float in my vorbis-player-project to get my pcm data.
i've noticed, that many of these floating point values are slightly out of the "official" amplitude range between -1.0f and 1.0f.
so why is that?
is it okay, just to clip it? JACK expect values *only* in range of -1 and 1.
thank you!
marco
i use ov_read_float in my vorbis-player-project to get my pcm data.
i've noticed, that many of these floating point values are slightly out of the "official" amplitude range between -1.0f and 1.0f.
so why is that?
is it okay, just to clip it? JACK expect values *only* in range of -1 and 1.
thank you!
marco
Because the reverse transform generates transients that can peak higher than the original sound. This is common for all transform codecs - I've seen as high as 1.5 before. Most players are clipping this before outputting to the soundcard. I've seen some code that will distort the audio (via tanh or similiar) in hopes that it will sound better than clipping, and I've also seen look-ahead limiting done. These higher-than-1 peaks are one reason why ReplayGain is so popular around here
QUOTE (marco_mania @ Sep 24 2006, 22:39)
JACK expect values *only* in range of -1 and 1.
Jack applies hardclipping when converting to the pcm output, at least on my experience.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.