I’ve done stuff like this, using CV, and I don’t think it ate up 5-6% of CPU at all.
My experience has been CV connections and blocks don’t take much CPU. But if you have tried it and seen a jump, then possibly there are other ways to configure what you want which are less CPU intense.
Connecting one knob to multiple parameters is easy with CV and doesn’t seem to eat up much CPU. I do that all the time.
However I was not able to reliably have two knobs alter one parameter. The issue is probably that if each knob can change the same setting, when you switch pages, the knob needs to return to a ‘passthrough’ mode, but which of the multiple knobs would it listen to?
Each Control to CV is set to the same knob on different pages.
The sum output of the Slew Rate goes to the volume knob.
This will seem to work the first time around. One knob affects the sum output, and that connects to the volume. Switch pages, and then yup, it seems to work, the second assignment (same knob different page) also affects the sum output and controls the volume. But then it falls apart. At some point the knob stops working, and switching between pages does not help. I believe if you have Control to CV set at either extreme, they cancel each other out - not sure.
Possibly there is a way to expand on this, so that each input uses different ranges, and then this gets limited back down to what you want for the volume knob. Not ideal.
@jon Do you think this might ever be implemented? See my screenshot above, it seems like it would just be a matter of allowing non-exclusive assignments in the matrix. I could of course be overlooking something though.
In a DAW I’m able to assign multiple knobs to a single parameter with no ill side effects. That’s similar to what we’d be doing here.
Yeah, I just tried a slightly different CV method, but having one knob left at full when switching pages, meant that the second knob couldn’t ‘reduce’ the full signal from the abandoned page. I did some workaround, none were ideal.
I think it’s quite complicated to have two knobs control one setting, for a variety of reasons, so I hope an easier option, is just to allow a single knob assignment to appear on more than one page - same knob, but sticky like the volume knob is. Then there is nothing complex in the signal path at all.
Yes. But we don’t really know when. We already talked a bit about that, but what seems simple on the front end sometimes is not so easy to develop on the backend.
The issue here is on the structure of the assignment system.