top of page

Ideas and Feature Requests

Public·6 members

Mute Over CC Control (non-toggle option)

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 :)

30 Views
steve
Aug 12, 2024

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

Members

bottom of page