StephanieNYC said:Hey Ed, if that thing can run at 7.5", and if you're ever gonna junk it, I wouldn't mind getting my greasy paws on it. ;D
Too late! I already bought it.
R
StephanieNYC said:Hey Ed, if that thing can run at 7.5", and if you're ever gonna junk it, I wouldn't mind getting my greasy paws on it. ;D
Kevin Tekel said:Were the Omnia-6 and DSP-X clips you uploaded processed using 50 uS or 75 uS pre-emphasis?
OK, I noticed they sound quite bright compared to American standards.Goran Tomas said:50 µs. That's what we use here in Europe![]()
Kevin Tekel said:OK, I noticed they sound quite bright compared to American standards.
I also noticed that you have the channels reversed -- at least compared to the uncompressed sample music tracks that you have uploaded.
The DSP-X Tina Arena clip sounds really really bright. Most stations here don't push the high end that much because today's music is already treble-happy right on the CD, and that's not such a good mix with 75 uS clipping. (Kelly Clarkson's "Because Of You" is a killer -- her vocals during the beginning get horribly clipped by every station I've heard it on!)Goran Tomas said:Really? I'd thought this market is not that bright, compared to some others... It would be interesting if you can make some recordings of the station where you live?
BTW, you also set the recording level on the Omnia clips a bit too high, causing some clipping in the WAV files when the peaks hit full scale (0 dBfs).Goran Tomas said:Quite possibly as I just hooked the processors to the PC for the recording (those who were not recorded off-air).
Kevin Tekel said:BTW, you also set the recording level on the Omnia clips a bit too high, causing some clipping in the WAV files when the peaks hit full scale (0 dBfs).Goran Tomas said:Quite possibly as I just hooked the processors to the PC for the recording (those who were not recorded off-air).
Goran Tomas said:No I haven't, I first recorded the clips and normalized the files afterwards to 0dBfs. But some software (Adobe Audition and Sound Forge are both examples) can indicate peaks with heavily peak processed audio as OVER, although they aren't....
Regards,
Goran Tomas
FFoti1 said:Goran Tomas said:No I haven't, I first recorded the clips and normalized the files afterwards to 0dBfs. But some software (Adobe Audition and Sound Forge are both examples) can indicate peaks with heavily peak processed audio as OVER, although they aren't....
Regards,
Goran Tomas
All the more reason why this practice is not a good idea. Who knows *exactly* what the normalizing function added to the audio? Taking audio, that has already been significantly processed, and adding further dynamics functions to it, is only asking for more trouble.
This further reduces a fair evaluation of the audio clip.
-Frank Foti
FFoti1 said:All the more reason why this practice is not a good idea. Who knows *exactly* what the normalizing function added to the audio? Taking audio, that has already been significantly processed, and adding further dynamics functions to it, is only asking for more trouble.
This further reduces a fair evaluation of the audio clip.
David Reaves said:Is the normalizing function a single, one-time level adjustment for the entire piece, or is it dynamic? If the former, no big deal; if the latter, all bets are off.
Goran Tomas said:If it would make any difference, I can just as easily make the files without normalizing. But I get a feeling you're against this practice in general, regardless of the peculiarities, so I'm pretty sure it wouldn't matter for you one way or the other...
What does normalizing do? It scans for the peak value in the file, calculates the headroom and then scales (multiples) all the samples with the coeficient that will put the highest peak(s) to 0dbfs. It's not a dynamic function of any sort and does not affect dynamics at all. And it doesn't cause any clipping, the sometimes OVER indication in some software is just the inaccuracy of the metering and it's ballistics. Afterall it's a fixed gain change and affects dynamics just as much as does the output level control on Omnia, or output level of any other processor...
I've found that I get more accurate results in Cool Edit / Adobe Audition if I scan the audio file to find the highest peak value, and then manually amplify or reduce the gain to the desired peak level. The automatic normalize feature is often off the mark by a few tenths of a dB.FFoti1 said:Also, you're putting blind faith in the normalizing function, without any proof that it's is doing as we're lead to believe. I've done plenty of 'normalizing' using various S/W packages and have found some that are not what they claim. Adding another variable to the mix creates more problems.
Kevin Tekel said:I've found that I get more accurate results in Cool Edit / Adobe Audition if I scan the audio file to find the highest peak value, and then manually amplify or reduce the gain to the desired peak level. The automatic normalize feature is often off the mark by a few tenths of a dB.
I also prefer to normalize things to at least -1 dBfs, if not even lower, just to keep some digital headroom and prevent any chance of unwanted clipping. This is especially important if you're preparing audio that will go into a lossy codec, since that often introduces peak overshoot in both the encoding and decoding/playback processes.
p.s. You can also argue that normalizing 16-bit audio adds quantization noise and raises the noise floor, but that's the nature of the beast when you're dealing with any 16-bit audio, and I'd rather have an unnoticeable increase in background noise level than a very noticeable amount of clipping!
Goran Tomas said:Why are we so nit-picking on this??