>>This is where Sound Forge really comes in handy. What I would do is right-click the event and select “Open a copy in Sound Forge” and Vegas will make a copy of the audio and add it back as a Take. Then you clean it up in Sound Forge and the take stays in sync with the video but uses a wav file. I work this way with iZotope RX sometimes too (although the RX plug-ins are available in Sound Forge as well).
OK, I have Sound Forge 9.0e (long story). Is that going to work? Or do I need Sound Forge 10b to go with x64 Vegas? Also, what is the ideal workflow?
I opened up Vegas x32 and removed the Noise Reduction 2.0 plug-ins from the timeline there. I also set the default audio editor to Sound Forge 9.0e in both x32 and x64 Vegas.
In Vegas 9.0e x64 I right clicked on the Zoom H4N audio track, opened it in Sound Forge, and applied Noise Reduction Mode 2.
Before I opened the sound tracks from the two HF S10 cameras I thought I should close the H4N file. Sound Forge asked me if I wanted to save changes to the H4N file. I selected ‘Yes’ and it closed the file. However, immediately Vegas x64 gave me a warning that it could not find the H4N file. I notice an ‘H4N Take 2’ in the Explorer that approximately half the size of the original H4N file (633 MB for two hours instead of 1.27 GB). It also did not put the sound file back in the same place on the timeline, so I will have to re-align the sound tracks (which is not a big deal).
So I assume I would want to clean up the audio files in Sound Forge first, before I line up the waveforms?
Norman Willis
http://www.nazareneisrael.org