Indeed. The latency does persist when you disable it, but it you open preferences and exit again it should reset (that's what happens here anyway) - so if you can get it to work to do what you want it to do, I would just freeze or bounce the track with the hum zapped and then move on with the mix from there...

Are you getting the standard 60 Hz hum or is a broader range of frequencies?  If it's the 60 Hz you can just do a very deep, very narrow Q cut at 60 Hz and the first couple harmonics at 120 Hz, 180 Hz, 240 Hz and see if that takes care of your problem without the need for an additional plug-in.

subtlearts
Indeed. The latency does persist when you disable it, but it you open preferences and exit again it should reset (that's what happens here anyway) - so if you can get it to work to do what you want it to do, I would just freeze or bounce the track with the hum zapped and then move on with the mix from there...

Excellent. I will try that. That is a much better method than exporting/importing/exporting into older versions. I did however go into Prefs (to check the reported latency) but I cannot recall at which stage. Also... well there was the hard crash. Still this is something to try and I thank you for checking.
 

SF_Green
Are you getting the standard 60 Hz hum or is a broader range of frequencies?  If it's the 60 Hz you can just do a very deep, very narrow Q cut at 60 Hz and the first couple harmonics at 120 Hz, 180 Hz, 240 Hz and see if that takes care of your problem without the need for an additional plug-in.

Awesome. I had tried the 60 hz notch with no joy but did not consider resonant freqs (nor am I experienced/educated enough to have hunted them down precisely). If that is the old school method for handling 60 cycle annoyances then I will definitely play with it and be sure to keep it in my technique toolkit. May not work for this (because I am not sure if it IS a 60 cycle issue) but this can confirm/troubleshoot the problem.
 
Just those three freqs or should I check for other spikes?
 
Thank you.

For what it's worth I just used r-mix in platinum last month and had no issues had to remove some vocals and used it last week to remove some bleed on a kick drum.
 
 
 
Platinum win8.1 vstudio100

Beepster

subtlearts
Indeed. The latency does persist when you disable it, but it you open preferences and exit again it should reset (that's what happens here anyway) - so if you can get it to work to do what you want it to do, I would just freeze or bounce the track with the hum zapped and then move on with the mix from there...

Excellent. I will try that. That is a much better method than exporting/importing/exporting into older versions. I did however go into Prefs (to check the reported latency) but I cannot recall at which stage. Also... well there was the hard crash. Still this is something to try and I thank you for checking.
 

SF_Green
Are you getting the standard 60 Hz hum or is a broader range of frequencies?  If it's the 60 Hz you can just do a very deep, very narrow Q cut at 60 Hz and the first couple harmonics at 120 Hz, 180 Hz, 240 Hz and see if that takes care of your problem without the need for an additional plug-in.

Awesome. I had tried the 60 hz notch with no joy but did not consider resonant freqs (nor am I experienced/educated enough to have hunted them down precisely). If that is the old school method for handling 60 cycle annoyances then I will definitely play with it and be sure to keep it in my technique toolkit. May not work for this (because I am not sure if it IS a 60 cycle issue) but this can confirm/troubleshoot the problem.
 
Just those three freqs or should I check for other spikes?
 
Thank you.

if memory serves sonitus has a preset already set up for you; with minor tweaking it might work. more often than not now a days it doesn't but maybe worth a look.

I think r-mix uses an extremely intensive algorithm that can get out of hand; I have made X3 crash with it before. 
 

Beepster
 
Just those three freqs or should I check for other spikes?
 

 
I would isolate a spot in your track where you can here just, or at least mostly, the hum and stick a spectrum/frequency analyze on it.  That should tell you how much harmonic action you're getting, and where to cut.

Beep,

One of the best denoiser I've heard was using this
http://www.meldaproductio...p?id=MSpectralDynamics

I created a clone of the original track, flipped polarity, then removed all significant sound from the track. Then I used volume automation to bring the phase flipped track that was only the noise up and down during the song to optimally suppress our cancel the noise.

Bit has a great article he wrote on the plug. If you want to send me the track and the mix for context, I'll give it a shot for you.

If you haven't already demo'd Melda, it might be time.

I have Audition 4 (from CS5.5), and the NR algorithms in it are quite excellent - from a simple noise capture/removal all the way to removals that allow you to EQ sculpt and hear only what you are removing. For what you are doing, I simply capture an extra second of "only noise" at the beginning and end of each take. For consistent background noise it gets used on every audio track before mixing (but is not free, although OEM copies of version 4 are still around in places).

Agreed, Audition's algorithms are very good. However I jumped off Audition when the subscription thing happened. Fortunately I have Sound Forge and iZotope RX, both of which do the "noise subtraction" thing very well. But ultimately, my solution for guitar has been using humbuckers and the CA-X amps because that deals with the problem at the source.
 
Anyone check out the free Reaper plug-in? How does it work?