Normalization

DelCallo wrote on 1/28/2006, 4:41 AM
I generally use Sound Forge or Wavelab for audio only work – no real reason for this. It’s just how I tend to do things. The other night, wavelab was giving me file size limit warnings, so, I tried normalizing a large file in Vegas (seems that no matter what I’m trying to do, Vegas seems to be able to handle it – I can’t explain why – Vegas seems the least fussy about file sizes, file types, etc.).

At any rate, I had to search the help file to find where to look for the normalization function, but, once there, I clicked to normalize, and, poof, the task was done. This surprised me, because in other applications, there is usually a long file scanning time as the software searches the peaks, then, another period where the file looks to be scanned again as the normalization is applied.

Vegas seems to react instantly, taking no more time to maximize the level than MS Word takes to change a font size.

How can this be? In what way does Vegas approach normalization differently than the other aps I’ve mentioned?

Just curious.

JC

Comments

Chienworks wrote on 1/28/2006, 7:23 AM
Vegas doesn't normalize the source file because it's a non-destructive editor. Since nothing is done, it doesn't take very long to do it! What happens is that Vegas normalizes the signal on the fly during playback and rendering. So, if normalizing the file in Sound Forge would have taken, say, 40 seconds, then you've now added 40 seconds to the time it will take to render your project.

This is the same as any other effect you add to either audio or video in Vegas. The original file isn't touched. The effect is added on the fly when you preview or render.
DelCallo wrote on 3/26/2006, 3:19 AM
Cien:
Thanks for the reply. What you say makes sense.
Del
wymondham wrote on 5/1/2006, 9:34 AM
O.k here is another question as I'm new to Vegas. Should I normalize the tracks in a project or leave them as they are to work on the tracks. Then normalize in Sound Forge the rendered stereo tracks? In other words do the tracks normalized in Vegas go on to be normalized in Sound Forge?
Geoff_Wood wrote on 5/1/2006, 3:48 PM
Don't nomalise individual tracks routinely. I only normalise if there is a 'problem' track somehow inadvertently recorded at very low level, beyond the scope of the boost provided by the track fader.

As with analogue, the less processing to your source files, the better. Repeated normaliasation will increase the noise and distortion of a track.

I do final level tweaks in a mastering sense, in CDA. I just find it easier to focus on the task than doing it in Vegas on the timeline, or as individual files in SF.

geoff
wymondham wrote on 5/2/2006, 6:39 AM
Thanks Geoff,

So I take it that the original files are untouched by what I'm doing in Vegas or CDA. But If I render down to a 2 track stereo mix, process and normalize the redered file in Sound Forge, then that is normalized with no return after saving?
drbam wrote on 5/2/2006, 6:57 AM
"But If I render down to a 2 track stereo mix, process and normalize the redered file in Sound Forge, then that is normalized with no return after saving?"

Correct. You're describing a "destructive" (permanent) edit. I always do a "save as" with a different file name (Final mix 1a, 1b, whatever) in these situations, just in case . . .

drbam