You're doing it correctly. Do it to the individual tracks first before you mix. This will give you extra head room in the mixes and also reduce the noise floor, because DC offset causes a hum sound and mixing them together therefore increases the hum noise level. DC offset is really nothing more than a Low Pass filter with a steep slope with the start frequency somewhere around 3Hz.

Cool,
I processed all the individual tracks. Most of them came up 0, and didn't need any adjustment. The ones that were off were only off slightly. I don't hear any difference in the sound after running the DC Offset plug...but my monitors aren't the best.

jp

I don't know what you're recording, but some sources/sounds just aren't balanced over the zero crossing and will always have a DC offset. Mainly synthesized sounds. Check silent portions of a recording for DC offset.

TeeCee

I've been following the whole DCOffset threads for a while. I read one in which Rednroll said that the latest release fixed the 'one channel only' DCOffset problem, although after having read the entire release note posted by SoFo, I don't see anything relating to DCOffset at all. Also, lately, I've been finding that at times, the sound of the wav after DCOffset runs totally sux. Whereas before running it the sound was clear and tight, after running it it sounds muddy and awful. On those files I just un-did the effect and saved the file with the DCOffset still there. I tried EAC to use that program's DCOffset utility, but that began to be a P.I.T.A. I'm still using 6.0 build 132 because I tried an earlier 'update' and ended up with more problems than it was worth trying to deal with. Maybe if 6.0e has finally gotten the bugs worked out, I'll give that a shot.

sk

Sonically, I can't say for sure if it's doing a good job or not. I don't have any DC offset issues in my current studio setup. I did test SF 6.0E by adding DC offset and then using the DC offset remover and varified that it removed it in both channels and verifying 6.0d didn't do the same. All previous versions of Sound Forge v6.0 only removed it from one channel. I know they acknowledge the problem and said they would fix it. I'm sure they didn't post it in the bug fixes, because this is a major oversight that makes you feel uncomfortable and wondering, Is both channels being processed for every other process? Additionally they didn't post it, because users have been using this for 4 releases now and would highly doubt the intergrity of the program if they've been giving clients bad audio unknowingly relying on the program to do what it is SUPPOSE to do. This is a lack of software validation by Sonic Foundry on it's core functionality....which is probably root caused by a lack of resources. I'm only a Vegas beta tester, so I won't take any of the blame for bugs missed in Sound Forge. I found 8 bugs on the initial release of Sound Forge, when they include me on the beta Sound Forge team, I can help narrow that number down. Until then, I'll just keep everyone posted to help avoid problems. :-)