Triggering mutes remotely is very useful, and in some ways I kind of like the current trigger-only mute option because I can overlay various triggers that mix and match things in fun ways..
The main problem is that right now my controllers need some context of the current mute state before knowing whether to send a trigger. This can also complicate things if for example A and B both go to C, but don't start with the same mute state.
This is cool sometimes, but if I always want C to begin with tracks[1...3] muted I can't really program it currently.
tldr; Current: Mute Toggles on cc:127
Desire: Mute on — cc: 127, Mute off — cc:0 If I missed another way to do this let me know :)
I have this on my list of requests too, it’s difficult to program the mutes from external sequencers like hapax and oxi one. Cc 127 on, 0 off is preferred for any toggle type control, like mute/follow/chord select etc
This is a sound suggestion and I could see how it would be useful. I've added it to the request list for a future update. Hopefully it should be easy enough to put in the V7 Update. (V6 is imminent and it's too late to fit this in, I'm afraid) I presume that you would want this behaviour to be control specific, not global? Perhaps, an additional option when assigning the CC control (Absolute, Incremental and "LIMITS?") I'd have to think about how to do it. It's on the list at least. What MIDI controller are you using, perhaps there's a solution there?