The Track FX are included by default, but are set up such that they
are bypassed with no CPU overhead. The Track FX are "smarter" and can
communicate that they are doing nothing and therefore we can detect
this "no-op" case and optimize for it.

Simple anwser:
Yes, the FX will still use the same CPU resources when it is
bypassed, but you wont hear it as part of the mix when bypassed.

Long boring answer:
The assignable FX chains behave differently. If you have an FX in a
chain it is always recieving data. If you bypass it still recieves
the data, but the processed data is not part of the mix. This is done
so that a/b'ing of the signal is more responsive. It also permits the
FX to be "wet" when it is brought back on line. (There are a other
technical details for this as well as audible reasons. If you want
the gory details, I will be happy to - with out giving away any of
our secrets.) Peter Brett Crockett wrote: >>Is there a way to set the default Track FX configuration >>for a project? For example, can I set Vegas so that when >>I start a new .veg project it doesn't automagically put >>Gate, EQ and Compression on each new track. >> >>Also, when I have a Track FX chain set up if I uncheck >>an effect in the chain am I just muting the output or >>am I removing it from the chain and saving CPU cycles? >>To conserve cycles do I need to complete remove it from >>the track or can I just uncheck it? >> >>Thanks! >>Brett