so you have some response woo game on :-)
the benefit of the RemoteSL (Zero, here) is that you get a text display at the top
and 40 'pages'/templates to work with, if you want to do big mappings, and link templates and have a navigation system.
QY70/100/700, RM1x, are all 'XG' and the main parameters are all accessible via midiCC.
other functions are accessible via Sysex - eg: effects parameter edit, sequencer section select.
and then all the mentioned 'main parameters' are also accessible via Sysex, but in a different context:
- when you CHANGE with midiCC, it resets when you restart the Song (/¨Pattern?)
- when you SET with Sysex, these are Song/Pattern parameter values
the trouble with the Remote, and all controllers to date, is that they can't change lists dynamically, as you can with a script-driven object.
if every effect you call up has different parameters and value ranges, a regular controller box, or even a sophisticated one such as the RemoteSL, cannot do it.
you could do it in Ctrlr, with Lua, and then map up physical controls to onscreen ones with MIDI Learn ?
but you can still do it 'blind' with Eric's templates, and it improves the overall 'soundstaging' a lot.
not long after that, i got a RM1x, and that took my attention away from the QY, because it's essentially an oversized QY, with 16-section 'styles' and the same sound engine, but no arranger stuff, but with much longer patterns, and some realtime midi controls
- Ctrlr would be a solution.
