when code component is consuming CPU?

[Perfect Human Interface]

So here's a (hopefully) related question:
In DSP components are there any effective "get out early" operations? Such as with bitmasking; does it save on CPU to get out of a conditional with a 0 boolean or is everything calculated out regardless?

It would be nice if there was a way to force DSP code blocks to skip over all the expensive stuff when you don't need it. I know I have one project I backburnered a while back that was at 25% CPU idle. I put a lot of work into that too.

[tulamide]

... it reminded me, that in the past I saw situations in which "disabled" code blocks - used CPU. And I started to wonder - what are the options.

I just experienced the same. I was playing around with the sync'd lfo, added a scope, asio out and watched it working. Then I removed the link to the asio out - but the lfo continued to work. Only after deleting the asio prim, it stopped. This behavior is inconsistent. If it only starts processing after linking it to the audio out, it should stop processing when links are removed.