I have (4) modules that I use assigned as a preset in PC.  I have the same preset on each channel.  Is there any difference in CPU usage between having the module off where it is not needed or removing it?
 
Thanks

Not being certain, I believe having it enabled adds to the load on your cpu.. Having it inserted in a strip, but not enabled removes it's cpu load.

That's my suspicion.  I do my work on a better computer and notice some delay on my weaker one.  I decided to look over the Pro Channel and did notice many modules were on, but I wasn't utilizing them.  Find out for sure tomorrow!
 
many thanks

I think I've read that having them only disabled does not reduce anything -  they are still processing things, only 'muted'... Just like a track that is muted per se.
 
The track has to be frozen - or effect removed - in order to really disable them from CPU usage.  When disabled only, they are 'on the ready' to come into play - hence always running in the background waiting to be enabled.
 
To be clear - I could be completely wrong - though from a programming logic, this makes sense to me.

That did appear to be the case today.  I had to substantially increase buffer size.  I'll try eliminating them and see what happens.
thanks
Willard

One thing I notice is it also increases load time. Watch the little blue box in the lower right as a project loads and you'll see Pro Chanel certainly taking up time. I noticed this and a few modules loading that I didn't think I was using. Checking a few tracks those modules were there but turned off.... but they seem to still use CPU. SO it would seem it's best to delete all unused modules from every track CPU wise. 

I believe that plug-ins in general remain connected to the CPU when bypassed, so that they can start up instantly when enabled. 

vst3 plugins support "no cpu usage when turned off" (assuming both plugin and host handle it) but prochannel is a vst2 hack (unless it's been updated and i missed that?) so unfortunately prochannel doesn't benefit from the vst3 stuff

One really strange issue I've seen with the pro channel (on my laptop running WASAPI), is a strange brick-wall limiter type effect when playing from bar 1. It's like a burst of volume that almost immediately settles down in a fraction of a second.
 
This happens when ProChannel is enabled regardless of whether any of the modules within the ProChannel are enabled or not.
 
Disabling the ProChannel makes it go away.
 
My usual workaround of leaving an empty bar at the beginning of the project fixes this, but it's strange that just having the ProChannel enabled causes this behaviour.