You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both serialization and mappability are controlled by whether the param is bounded, so there is no obvious way to make a param mappable but not serialized.
Mapping a button with a 0-127 CC prevents that button from being used interactively; the 0 value from MIDI Map always overwrites the interactive control.
Not clear how pressed/held states work with mapping.
1 and 3 are probably resolvable by just allowing the params to be serialized, and removing the distinction between press and hold in param state. Hold can be implemented by just ignoring mouseup, it doesn't need to be a separate state.
Issue 2 can probably be resolved by keeping two sets of Rack parameter values, one for mapping, one for interactive control, and sending grid key presses when either one or the other is high.
The text was updated successfully, but these errors were encountered:
Issues preventing MIDI Map support:
0
value from MIDI Map always overwrites the interactive control.1 and 3 are probably resolvable by just allowing the params to be serialized, and removing the distinction between press and hold in param state. Hold can be implemented by just ignoring mouseup, it doesn't need to be a separate state.
Issue 2 can probably be resolved by keeping two sets of Rack parameter values, one for mapping, one for interactive control, and sending grid key presses when either one or the other is high.
The text was updated successfully, but these errors were encountered: