nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Switching off to save cpu

TravOsc

Is there really no way to save cpu on chains not being used? If say an osc, filter or fx are not being used why are they eating CPU? Makes it hard to have a lot of options when everything is being processed and only 10% is actually being used at any given time.

I’m just working in primary for now. If anyone has a solution or link to something to help me out here be very appreciated.

Find more posts tagged with

Accepted answers

colB

In primary, if you use switches, any elements that are switched to a route that is not active will not use cpu, unless they are switched to 'always active', or contain components switched to 'always active'.

See this example, the pro 52 is switched on, you can see that the lamp at the bottom right of the ladder filter macro is off, that tells you it is not using cpu

All comments

colB

https://community.native-instruments.com/discussion/51546/switching-off-to-save-cpu

What do you mean by "not being used"?

TravOsc

For example if I have 6 filters available and 2 auxiliaries with 8 fx units each - that’s 22 units eating cpu all the time. But I only ever run a path through 3 at a time - all the rest are just currently unused options to choose from.

I’d like to effectively “mute” the other units currently not being used - I highly doubt there was some way to actually mute the unit, but you know, however something like that would work.

colB

See this example, the pro 52 is switched on, you can see that the lamp at the bottom right of the ladder filter macro is off, that tells you it is not using cpu

colB

I prefer to avoid primary switches, because they can cause other issues, but I would be doing this in core where there is a completely different equally effective approach to controlling cpu activity.

TravOsc

Thanks, it seemed my issue was around placement. I could do something like put a switch on the outside of a vector micro and kill the audio but all modules inside of it we’re still running. I checked but couldn’t find anything always active within it. Where as if I put the switch just on the other side of the oscillator selector (within the vector) it does turn off all the modules before the oscillators as well.
Thanks for helping a newbie out, much appreciated!

Quick links

Unanswered questions