Audio filtering for static, etc?

In FCP you can try one of the lowpass filters, which allows the low frequencies to pass through while sloping off some of the highs, or you could even try the vocal de-esser, which also gets rid of some of those high frequencies that come with static and clothing sounds. However, since I don't know exactly what the unwanted sounds are like, you'll have to play around. My best suggestion would be (failing re-recording, which it sounds like you can't do) using a 3-band EQ and trying to isolate the bad frequencies as much as possible and notch them out without affecting the voice too much.

Also, if you can get your audio into Soundtrack Pro or Pro Tools, you'll have much more control over it than you would within FCP, and then you can just import it back in.

You won't be able to remove the extraneous BG sounds completely, but you can certainly dampen them with enough tweaking of filters. As far as the music track muffling them, that depends on what kind of track you're using. Certain types of music might make them sound worse, depending on conflicting frequencies, but if you choose the right one it could help out a little bit as a bandaid.

If you can record this statement again if at all possible, that would be the absolute best way to go. Of course I understand that might not be an option.

Hope this helps,
Joni

What Joni said - if it was a consistent noise, like a hum, I'd use the noise print and remove noise in Sound Track Pro. That's saved a few shots for me...

Patrick

You can play around looking for magic bullets all you want, but in my opinion you are still going to end up diving into the waveform and manually editing out the offending noises. So you might as well steel yourself to the inevitable and just get on with it.

The fact that you are going to use a background music track is a real help. It means that you don't need to make up a loop of ambient noise from the wild sound in your recordings to use to mask the chunks of silence left by slicing out or potting down the offending noises.

That's what my experience usually ends up being on these things. I usually waste a day looking for an automated answer, and then still end up having to spend a few hours manually massaging the track.

Better to avoid the first and just get on with the second. Save the time and frustration.

Think of how proud you will feel every time you hear a section of the finished program that used to have an annoying crinkle or crack in it, but because of your efforts, that section is now blissfully annoyance-free. "I did that!" you will proudly say. Your self-esteem will soar. You will be happy you did this by hand.

So the sooner you get to that manual waveform editing the better, right?

Looks like you're fairly new to the forum. It's a good idea to go back in to your post once your question has been resolved and mark it Answered. You can also mark certain posts "Helpful" and "Solved" in order to give points to the folks who helped out. Keeps things neat and tidy, and your post will appear with a green "Answered" star next to it in the thread list, which helps other users when searching for information.

Just letting you know (in case you didn't already). I'm also blatantly trying to get some points because I'm so close to getting that second little blue bar. One blue bar says nothing of me. But 2, now that would mean something.

Joni