Closed nofoto closed 1 month ago
Thanks for the report. I can reproduce. If the same effect is loaded into slots 2 and 3, they generate (and listen) to the same OSC addresses, which is obviously wrong.
Considering that touching a parameter of an effect in slot 3 generates such a message:
[..b] /2/mx/insert/1/mx-para/insert/2/rodel/til 1
_
slot 3 is the culprit.
@nofoto The issue is fixed in main branch
If you add the same effect to channels 2 and 3 of an 'mx-para' (counting the parallel channels alongside the main one as 1,2,3) then the system confuses the two instances of the effect and the slider for one of them will move the same on both etc