Strange "Normalize" Behavior

Jay Gladwell wrote on 7/6/2005, 10:06 AM

I've been editing all day so far, including working on sound. I brough a new clip onto the timeline. Right clicked on the sound track and selected "Normalize." Instead of normalizing the track, it muted the track!

What's happened now???

Comments

CDM wrote on 7/6/2005, 10:34 AM

did you normalize while it was building peaks?

Jay Gladwell wrote on 7/6/2005, 10:39 AM

No.

Spot|DSE wrote on 7/6/2005, 10:39 AM

You have the weirdest things happen in Vegas! What are the dynamics of the audio file? filters on the audio? any other specifics? Tracks definitely not out of phase or any other weird ness like that?

BrianStanding wrote on 7/6/2005, 11:36 AM

I have this problem sporadically, too. I've never been able to identify anything odd about the files, or any other reason why it happens to some files and not others.

I usually end up normalizing in Sound Forge to take care of it.

Jay Gladwell wrote on 7/6/2005, 11:43 AM

Spot, the only thing I'm attempting to do is normalize the specific track(s)--man-on-the-street interviews--no filters or any other weirdness.

It stopped doing it and I got everything fixed, now it's doing it again!

[edit]
I just tried this... I selected that clip and rendered it as a .wav file, brought that into the project and dropped onto the timeline. It normalized without any problem!

Spot|DSE wrote on 7/6/2005, 11:49 AM

Just for sake of curiosity, duplicate the track. On the top track, right click, choose Channels, choose "Left Only" and on the bottom track, right click, choose Channels/Right only.

Then normalize. See if that works in Vegas.

B.Verlik wrote on 7/6/2005, 12:19 PM

My stock fix to this frequent problem is to cut one frame from one end of the clip, maybe both ends. If you can afford one or two frames, try it. Un-normalize, then re-normalize.
EDIT: you can always "un-do" if it doesn't work. But it's always worked for me.

Quryous wrote on 7/6/2005, 2:37 PM

This is not actually anything new. I have been reporting the same problem since I started with Version 3.0 of Vegas Video. Both here and directly to SonicFoundry, and then Sony.

I have never been able to figure out why it happens, nor how to fix it. Some of the comments about cutting frames, not normalizing while building peaks, and other things MIGHT have an effect, but I can't really tell for sure. It is very strange.