karma1959
Bump - any thoughts on below pls?
 
Did a quick test - it seems the FX button in the transport DOES disable ProChannel effects in one of my projects, but it DOES NOT in another project. 
 
Any ideas why this would be?

The FX button is not in the the Transport module. Its in the Mix module. 
 
 

John

karma1959
Bump - any thoughts on below pls?
 
Did a quick test - it seems the FX button in the transport DOES disable ProChannel effects in one of my projects, but it DOES NOT in another project. 
 
Any ideas why this would be?

The FX button is not in the the Transport module. Its in the Mix module. 
 
 

John - thanks.. yes.. that's the one I'm using.  I mistakenly referred to the entire top area as the transport..
It's odd it disables prochannel modules on some projects, but on others, it only disables the prochannel modules on busses, but not on tracks.  I'm baffled.  Maybe it's corruption in projects, but those projects function fine otherwise.

From memory (not at my DAW), pressing E (or clicking the Fx button) will bypass the entire Pro Channel but NOT the individual modules contained inside. Are you sure this is not what you're seeing?

Bristol_Jonesey
From memory (not at my DAW), pressing E (or clicking the Fx button) will bypass the entire Pro Channel but NOT the individual modules contained inside. Are you sure this is not what you're seeing?

I'm not in front of my DAW, but what I recall in some projects, it worked fine - clicking "FX" in the mix bar disabled all the prochannels by disabling the button at the top of each prochannel module on every track and bus.  To your point, I didn't open up the prochannel to examine each individual effect, but I suspect they correctly disabled, as my CPU usage and latency went way down when the master prochannel button was disabled on each track. 
 
However in other projects, when clicking the FX button in the mix bar, it only disabled the master Prochannel on/ off on busses, but not on individual tracks. 
 
I haven't tried the E keyboard shortcut, but will try that over the weekend to see if there's a difference in behavior.

http://forum.cakewalk.com/FindPost/3431891
The second part of the message is a reproducible sequence  to "decouple" ProChannel On/Off from global bypass.

I have a couple of projects with this issue as well Russ. I suspect that the link provided by Azslow could well describe the cause in my case. At some stage I bypassed all FX in the Mix module, then reactivated them one by one. I have not tried to reproduce the issue yet, but will when I get a chance.

azslow3
http://forum.cakewalk.com/FindPost/3431891
The second part of the message is a reproducible sequence  to "decouple" ProChannel On/Off from global bypass.

That's a good find.

Yes, that's probably what happened.  Seems odd behavior - I'd be surprised if this is an intentional design.  I'll send a bug report to CW this weekend for them to research further.  Thanks again for all your assistance - good to know I'm not completely losing my mind.  :)