Smells of audio drivers...

It has nothing to do with Audio drivers. I have seen this behavior on various systems, always related to the Channel Tools, insomuch that deleting it fixes it. Deleting all instances, saving, opening and then reinstantiating Channel Tools ALWAYS fixes it.

eikelbijter
It has nothing to do with Audio drivers. I have seen this behavior on various systems, always related to the Channel Tools, insomuch that deleting it fixes it. Deleting all instances, saving, opening and then reinstantiating Channel Tools ALWAYS fixes it.

Sadly this is the sort of typical confusion that normally happens when we post two different issues on the same thread. I was responding to SilkTone,  FX Chain > Vocals > BG Vocals 1 PX2 FX chain module does not contain Channel Tools. Unless I've missed something in which case somebody better relieve me of my confusion.... Cheers...

CakeAlexS

eikelbijter
It has nothing to do with Audio drivers. I have seen this behavior on various systems, always related to the Channel Tools, insomuch that deleting it fixes it. Deleting all instances, saving, opening and then reinstantiating Channel Tools ALWAYS fixes it.

Sadly this is the sort of typical confusion that normally happens when we post two different issues on the same thread. I was responding to SilkTone,  FX Chain > Vocals > BG Vocals 1 PX2 FX chain module does not contain Channel Tools. Unless I've missed something in which case somebody better relieve me of my confusion.... Cheers...

Well, a search showed this thread as the closest related issue. It could very well be that this is something to do with FX Chain modules (the container itself) since when you add any FX plugin (including Channel Tools) to a ProChannel module, an FX Chain module is automatically created. I'm very sure it has something to do with the FX Chain module container because I've never seen this behavior in a track's FX bin. I guess I can play around with FX bins and FX Chain modules and see if any pattern emerges.
 
Also I'm trying to figure out if the initial issue had any resolution so I can see if the same fix/workaround resolves it for me.

SilkTone
...It could very well be that this is something to do with FX Chain modules (the container itself) since when you add any FX plugin (including Channel Tools) to a ProChannel module, an FX Chain module is automatically created. I'm very sure it has something to do with the FX Chain module container because I've never seen this behavior in a track's FX bin.
 

FWIW, automatically adding an FX Chain is how the Pro Channel handles non-PC plugins since it doesn't have an FX Bin per se.  Going from memory, I believe this feature was added in X2.
 

SilkTone
 
 
Well, a search showed this thread as the closest related issue. It could very well be that this is something to do with FX Chain modules (the container itself) since when you add any FX plugin (including Channel Tools) to a ProChannel module, an FX Chain module is automatically created. I'm very sure it has something to do with the FX Chain module container because I've never seen this behavior in a track's FX bin. I guess I can play around with FX bins and FX Chain modules and see if any pattern emerges.
 
Also I'm trying to figure out if the initial issue had any resolution so I can see if the same fix/workaround resolves it for me.

Hi SilkTone,
I never did get a fix for the problem I was having. That said, I also never called support, so I haven't really tried all that hard.
 
Dean

eikelbijter
It has nothing to do with Audio drivers. I have seen this behavior on various systems, always related to the Channel Tools, insomuch that deleting it fixes it. Deleting all instances, saving, opening and then reinstantiating Channel Tools ALWAYS fixes it.

 

Razorwit
Hi SilkTone,
I never did get a fix for the problem I was having. That said, I also never called support, so I haven't really tried all that hard.
 
Dean

 
So Dean would you agree with eikelbijter?
Cheers...

Uh, not sure Alex. My solution so far has been to just replace instances of channel tools with Waves S1 and move along. I haven't really tried deleting and whatnot.

Dean

Like I said guys, I've had this a number of times, from when Channel Tools first came with Sonar. It's always been fixable by deleting all the instances, saving, and then reinserting them....
 
R