However, it's useful to be able to set the normalization level (for example, Qtractor's MIDI tools allow this).
In audio: for mixing, a recommended level is -12dB, for exporting to Mastering -6dB, for the final Master -1dB...
Now, I don't know if I get the same result by normalizing to 0dB (Qtractor's current value) and then lowering it by -12dB with a gain plugin, as by directly normalizing the audio clip to -12dB.
There's a belief that plugins work better and suffer fewer distortion problems if healthy dB margins are established from the original source... but I don't know if that's just one of the many urban legends of digital audio.
yes there is, sort of... see main menu Clip > Normalize...
the idea here is quite simple: find the absolute maximum peak level of the selected audio clip (or selected range) and raise (or reduce) the clip gain accordingly to make it up (or down) to 0dBfs.
If that's the case, then it's not necessary. I'll normalize and then adjust the gain with a plugin.
Advantage: the waveforms are easier to visualize. Disadvantage: you lose the visual reference for volume level, because they'll all have the same level, but that's what the volume meter is for. So it seems like a suitable way to work.
However, I've noticed that normalization doesn't always work correctly. I've attached references.
The GIF shows how a gain exceeding 0dB is applied.
I've attached a QTZ file with the audio both unnormalized and normalized.
Look at the volume level in the last section (both in the GIF and the .qtz); it exceeds the 0dB limit.
It's not just the waveform.
I've inserted Calf Limiter here, and it's giving me peaks of up to +8dB.
Why does it work fine with some audio files and not others? I don't know, but it seems to happen more with relatively long audio files (over 10 seconds?).
after some deserved investigation, under certain circumstances, the normalization process cuts short on the clip length, thus giving erroneous results, sometimes
this is the case in fact with the uploaded audio file and session
a fix is sure coming soon, don't worry!
cheers && wholly thanks for the heads up
UPDATE: prolly fixed in qtractor >= v1.6.0.32git.e87f68
re. normalization value in audio clips...
why do need to determine it beforehand?
just do it and see what you get... if not satisfied undo it!
:)
re.2 normalization value in audio clips...
The answer is funny :D.
However, it's useful to be able to set the normalization level (for example, Qtractor's MIDI tools allow this).
In audio: for mixing, a recommended level is -12dB, for exporting to Mastering -6dB, for the final Master -1dB...
Now, I don't know if I get the same result by normalizing to 0dB (Qtractor's current value) and then lowering it by -12dB with a gain plugin, as by directly normalizing the audio clip to -12dB.
There's a belief that plugins work better and suffer fewer distortion problems if healthy dB margins are established from the original source... but I don't know if that's just one of the many urban legends of digital audio.
n̴o̴ ̴n̴o̴r̴m̴a̴l̴i̴z̴i̴n̴g̴
Stupid me. I stand corrected.
re. no normalizing...
yes there is, sort of... see main menu Clip > Normalize...
the idea here is quite simple: find the absolute maximum peak level of the selected audio clip (or selected range) and raise (or reduce) the clip gain accordingly to make it up (or down) to 0dBfs.
hth.
cheers
re. There is no difference to a gain plugin...
If that's the case, then it's not necessary. I'll normalize and then adjust the gain with a plugin.
Advantage: the waveforms are easier to visualize. Disadvantage: you lose the visual reference for volume level, because they'll all have the same level, but that's what the volume meter is for. So it seems like a suitable way to work.
However, I've noticed that normalization doesn't always work correctly. I've attached references.
The GIF shows how a gain exceeding 0dB is applied.
I've attached a QTZ file with the audio both unnormalized and normalized.
re. normalization doesn't always work correctly...
what you're seeing is kinda a visual illusion:
it indeed looks to overshoot the clip rectangle boundaries but in reality It's just a graphical drawing/scaling polygon mistake...
nothing to worry about, seriously :)
re.2 normalization doesn't always work correctly...
Look at the volume level in the last section (both in the GIF and the .qtz); it exceeds the 0dB limit.
It's not just the waveform.
I've inserted Calf Limiter here, and it's giving me peaks of up to +8dB.
Why does it work fine with some audio files and not others? I don't know, but it seems to happen more with relatively long audio files (over 10 seconds?).
here, too
Even when I convert the .ogg to .wav and import it then normalizing leads to red peaks.
re. normalization doesn't always work correctly...
Indeed it doesn't :(
after some deserved investigation, under certain circumstances, the normalization process cuts short on the clip length, thus giving erroneous results, sometimes
this is the case in fact with the uploaded audio file and session
a fix is sure coming soon, don't worry!
cheers && wholly thanks for the heads up
UPDATE: prolly fixed in qtractor >= v1.6.0.32git.e87f68
normalization Works!!!
It worked perfectly in the test I performed.
The wave no longer even extends beyond the clip.
Thank you very much.
Add new comment