Quote:

Thanks Mac. I'll try the plug-in's. I've used some of them for music before.

First thing I found out was it's better to correct a misake as you read. When you flub a sentence, go ahead and say it correctly right then. Then all you have to do is cut out the mistake. I recorded the fixes and pasted them it. It worked but was difficult to get the levels to match. And that was using the same mic, set-up, and everything.




By all means. A little trick: Find something that makes a continuous sound when triggered. I use a little code oscillator but I've seen pros using everything from professionally made "beep buttons" to air horns for this purpose.

When you do the misread, before doing the reread, hit that button to insert a continuous tone for a sec or so, then release the button and do the reread.

This makes for a situation where you can "Scrub" across audio (waveform view) and find ALL of the edit points in a hurry. -- And avoid the embarrassment of a missed edit point.

In the old days, we would do this by running the reels past the heads to "Scrub" the audio. You could hear that tone pop out every time. Today, we can scrub to listen for it and also scroll through that graphics wave view and simply LOOK for them as the audio goes by.

Quote:

Noise is a problem too. Silence isn't silent. Not sure if PT has a noise eliminator. I used Audacity for it. Trouble with Audacity and the initial recording is that if you stop, it opens a new wav when you resume.




Audacity has a setting somewhere in the Edit ->Preferences to stop that, depends on which version if you have it or not. But why bother? You have a better option in PT or RB.

Simply set up the PGDynamics plugin to work like a Gate. In this case, a Noise Gate. This is done by setting the Threshold For the Expander portion to just above the indicated noise level on the VU in that window.

It is sonically sweeter than the noise gate in Audacity, too. James Chandler Jr. makes great sounding plugins.


--Mac