Idle plugins (repackaged q.)

Geoff_Wood wrote on 1/12/2003, 2:08 PM
1 - Is a plugin with default (nonactive) settings equivalent in CPU terms to not having it running, the same as having active settings in it, or somewhere in between ?

2 - If the 'active' tick-box is cleared, is the CPU load equivalent to removing the plug, the same as with it active, or again somewhere in between ?

3 - What I'm getting at I guess, is if I have WaveHammers sitting there with default (inactive) settings, is this going to significantly affect my CPU-strain more than the equivalent instances of Track Compressor ?

geoff

Comments

pwppch wrote on 1/12/2003, 2:28 PM
1 - Is a plugin with default (nonactive) settings equivalent in CPU terms to not having it running, the same as having active settings in it, or somewhere in between ?
Depends on the plugin. Our track optimized FX are "doing nothing" when the default setting is used. Others - like our Chorus - actually process data.

2 - If the 'active' tick-box is cleared, is the CPU load equivalent to removing the plug, the same as with it active, or again somewhere in between ?
No. In order to permit simple a/b testing, audio is still streamed through the plugin when marked inactive.

3 - What I'm getting at I guess, is if I have WaveHammers sitting there with default (inactive) settings, is this going to significantly affect my CPU-strain more than the equivalent instances of Track Compressor ?
I don't know about WaveHammer. I will check.
PipelineAudio wrote on 1/12/2003, 6:52 PM
on a related note, any hope of ever " archiving "tracks cakewalk style, and being able to hide them? For now I gotta delete tracks that I MAY not use as they take up stability and performance, maybe theres a way to hide them till you want to bring them back up, but totally out of the way, not even being drawn ?