BrainModular

Good morning.

In which cases makes it the most sense to use Quick Links instead of regular cables
in terms of saving CPU Cycles?


Thanks in advance,

tL.

Nobody uses Quick Links?

The thing is they add latency like buses do, and for that reason I avoid them.

Simon.

well, there are places where a bloc of latency doesn't matter. Anything involving updating the display--opening a popup window, changing the name or visibility of a control, etc. Don't send audio or midi through them, unless it's just setting the midi channel or resetting the cc number of a control or something like that....

But they can clean up your patches! And if you have a big wkp with a lot of busses, they will reduce your CPU.

Be aware, they work only within a patch, not between patches, even if they are in the same rack.

woodslanding wrote:Anything involving updating the display--opening a popup window, changing the name or visibility of a control, etc. Don't send audio or midi through them, unless it's just setting the midi channel or resetting the cc number of a control or something like that....

Thanks for clarification.

woodslanding wrote:And if you have a big wkp with a lot of busses, they will reduce your CPU.

Perfect, that's what I wanted to know before I spend a lot of time optimizing my racks (quite a lot of them)
because I usually have pretty big wkp's and I was hoping that these help with the CPU strain.

woodslanding wrote:Be aware, they work only within a patch, not between patches, even if they are in the same rack.

Thanks again, I knew this one though..

Best,

tL.