Currently, when using a remote controller, all remote knobs are relative to the page you are on.
Like in this use case:
And that works really well.
But what if the E1 would also accept other incoming MIDI commands, besides those 36 predefined remote knobs?
Imagine that any (noteless) command (CC, pitch bend, mono after touch, program change), sent out from the same Port and MIDI channel as the remote knobs, would leave the E1 with the same message type and value, but altered for port and MIDI channel to the âdefaultâ device of the preset.
The other way round (from synth via E1 to the remote controller) should not be foreseen. Since the E1 would not know what other MIDI data is to be interpreted by the remote controller, it could bungle up the remote knob values, with weird consequences (unless we would mention explicitly the messages that should be forwarded towards the remote controller, without being assigned to specific remote knobs).
That would allow the remote controller to send out standard MIDI messages, which follow the MIDI 1.0 standard (such as CC120 âall sonds offâ, CC64 âholdâ, CC01 âmodwheelâ, program change, pitchbend), and that are not assigned as one of the 36 remote knobs to control âthe defaultâ synth of the preset, regardless on which page the preset is at.
Why: have fixed MIDI panic, MIDI sustain, MIDI modwheel faders or buttons on a remote controller that always act the same, regardless of the preset, the current page and the synth. For it to work, weâd need to indicate which Device of a preset is to be considered as the 'default â one. That should ideally be an additional setting then in the editor. As long as the setting does not exist, we could set it to the device, controlled by the control with the lowest reference number (usually ref #1, if not assigned to a group). Since a lot of presets are single device only, it would allready cover a lot of cases.