Hey guys I normalize all of my tracks to -1db after tracking/recording. I have my console set to monitor input levels, somehow my direct guitar tracks are going over 0db. How is this possible if they are normalized to -1db? As you can see on the image, my direct guitar recordings are going past 0db for some reason, and I have no idea why. As I said they are normalized to -1db so that’s exactly where they should stop on the console. It doesn’t make logical sense at all.
This is likely to stem from inter sample peaks, also called true peak.
There is an option in the settings/preferences that allows to show this kind of waveform in the Sample Editor.
I wonder if this might relate to panning and pan law settings, in relation to how the measurements in each mixer channel are taken. In particular, I notice you have the tracks that read higher than 0 dB having pan positions in their names, and I think, at least with some pan law settings, if you pan a track from center to left or right, the meter readings might show higher levels than if they’re panned to the center. One quick test for this might be to clear the peak readings, pan those tracks to the center, and see if you get the levels you were expecting (i.e. the -1.0 dBFS).
Besides your issue you can generally work on every level you want. But working at 0dB or -1dB isn‘t common use and has no advantage in a modern DAW. You should work at levels at -12 or -18dB. When you record with 24 bit resolution it gives you headroom to avoid issues when mixin where you add several signals to busses. Without disadvantages.
Why ? A CD with 16 bit has a dynamic range of 96dB. With 24 bit you have a dynamic range of 144dB, so 48dB headroom compared to CD. So working at -12 or -18 still leaves some headroom.
And normalizing doesn‘t improve the signal quality. When I was a beginner I tended to normalizing as well but in the meantime I learned about these facts.
Maybe you should watch a few YT about gain staging e.g. from Chris Selim, Dom Sigalas
No, it doesn’t do this with any of the other tracks in any other projects or this one. It’s always the direct guitar recording tracks, same all of my other projects as well. Panning law also does not affect the input to the console, only the output.
That could be a possibility but the fact that it doesn’t do this on any other track, only the guitars tracks (on all other projects as well) rules that possibility out.
I don’t record at 24 bit I record using 32 bit floating point.
The purpose of normalizing to -1db is that I know exactly what level my first plugin in the insert chain is being hit at which is crucial with today’s modeling plugins which also model the input. This guarantees I will not clip the input on the first plugin. I do that because that because it’s just basic logic when working with plugins that model the input of the hardware. You don’t want to clip the input, that’s basic gain staging.
Your reply did not address the issue I’m having, nor provide a reason that could be potentially causing the issue. It does not happen on any other track. Thanks anyways.
Just for a sanity check on this: Other tracks are also mono (and, with the same normalization, do not show the same symptoms on panning)? Stereo tracks may behave differently with respect to my wondering out loud – panning of a stereo track when using the simple panner (as opposed to the combined stereo panner) is really just adjusting the balance between the left and right components.
Right, but the peak readings on the console meters are for outputs, not inputs, so any difference that comes through panning would be reflected in their reading.
Correct all tracks are mono. I track everything on mono when tracking. Stereo width is provided using effects.
No, you can right click on a channel and select whether meters are input, post fader, or post panning. This is helpful when you want to gain stage into your mix buses where you need to monitor the input of the mix bus. Try it, you’ll see. I don’t know how anyone can gain stage properly not knowing this and therefore not doing it. The image I provided is showing the console meters set to input.
Rick I think you might be the one learning more from this post than me. Lol!
What does Audio → Statistics show for the peak amplitude?
Ah, okay, I’ve always just left them at their default. I typically use VU meter plugins for input gain staging purposes since I’m most frequently using other plugins that want analog-style input levels.
I checked that as well, it was actually the first thing I did, it says -1db. Just like it should.
bizarre right? I can’t figure it out at all. None of it is making any logical sense. All of my other projects do the same exact thing with only the direct guitar tracks. I’m debating re-tracking them and seeing if it changes. I think I probably will do that some time tomorrow as it is getting late where I am.
The only explanation I can think of is the clip level is turned up.
Clip level?
Yeah if you right click on a meter you’ll see “global meter settings”. From there you can choose “meter position” and then input, post-fader, or post-planner. These are crucial when you need to gain stage your tracks into your mix buses, and then your mix buses into your master bus. Without doing these switches you have no idea how hot your tracks are going into your mix buses and then into your master bus.
Yes, that would explain why the input meter doesn’t match the statistics. .
Technically it is the “audio event volume setting”. In other DAWs these things are called clips.
Ok where do I find the clip level?