mc.input versus custom message
How does mc.input actually differ from a custom made abstraction ?
Here I am using a multislider , unpacking each value , and a tuple of setvalue index + freq
The only difference is the mc.input only needs one cable out , and the custom approach needs several messages ( for each index )

So I ran into an issue
when I am using the multislider and unpack , the mc.input always outputs target 1 when doing a mousesweep , probably the unpack that sends all values >
