Besides L and V can we get M or P not to repeat unnecessary pages

Question

I was successful to repurpose the midi channel variable "L" to control one of the  26 individual drums in JD-XI via SysEx , so one set of controls (60-100) with one Super  control and two hidden ones  can repurpose the 60 controls to one of the 26 drums. Thus having 26x60 controls on ONE PAGE. Well 60 + 1 controls.   The same concept can be adapted to partials which rolland has a lot. So you'd need to ceate Layout for ONLY one partial and then have a selector (super control) that will choose with partial to edit.   

So I really don't care which letter of alphabet you'd use M or P but we'd have one page for multiple midi channels and multiple partials, Somehow this could be applied to LFOs, ADSRs with more than 2.

Since I sense that Dan might implement SysEx feedback (get state from a device) this could complicate the implementation but the same applies to request as soon as selector changes it would trigger Sysex request state so that controls would set values from device properly.

Answer 1

1.  SysEx feedback is a special case of sending specific SysEx messages from MDP2 output to input, where they can be processed with StreamByter rules.  This is implemented.

2. Get state from a device is possible in several ways.

3.  Additional SysEx variables have previously been requested, but is a low priority right now.  With StreamByter and SysEx feedback, you can configure as many additional SysEx variables as you need, and the two existing variable cover the preponderance of use cases. https://mididesigner.com/support/requests/   The Roland Jupiter X(m) has the similar Roland architecture, and it is possible to edit everything with the previous MDP2 SysEx capabilities.  (I have not updated my Roland layouts to take advantage of more current MDP2 capabilities.

Comments

I will try and work up an example of adding additional SysEx variables with StreamByter.  Stay tuned.

Answer 2

1.  SysEx feedback is a special case of sending specific SysEx messages from MDP2 output to input, where they can be processed with StreamByter rules.  This is implemented.

2. Get state from a device is possible in several ways.

3.  Additional SysEx variables have previously been requested, but is a low priority right now.  With StreamByter and SysEx feedback, you can configure as many additional SysEx variables as you need, and the two existing variable cover the preponderance of use cases. https://mididesigner.com/support/requests/   The Roland Jupiter X(m) has the similar Roland architecture, and it is possible to edit everything with the previous MDP2 SysEx capabilities.  (I have not updated my Roland layouts to take advantage of more current MDP2 capabilities.