Hi Steve / Others...
I've been looking further into some other options for storing values and for general workflow ideas (separate reasons) for my Qu16 mega-mix-2000 (is '2000' now "old-school"??)... and other project ideas... I've been searching around for an answer to this, but I'm probably using the wrong terminology:
Is there a way to ping/query an existing midi value of something? e.g. HP filter cutoff =120... Can I ping my Qu16 with some kind of 'query' message and then extract it's actual value (120)? Also - is there an increment/decrement message in midi that I'm not aware of? (I've watched the two increment / decrement encoder vids, but they seem to be specific to an encoder type / functionality)...
The types of things I'm hoping to do:
Use the save scene function on my Qu16 to store all current values for parameters (most of my qu16 setup is only controlling actual internal parameters)... Then I can save / recall all of my custom settings by simply saving/loading that scene. This would rely on MT Pro actually pinging these values after scene load to allow fader automation to present the actual values...
Use a fader as a +/- modifier (not absolute) like a modwheel. Use this to modify values on e.g. a synthesiser from their current value to max 127, min 0 (but I'd script to retain values beyond these limits to allow return to their original state)...
Use a non-automated fader to "do nothing until its value equals the actual value" (maybe + or - 1 to avoid skipped value issues)... So you can scan for the value manually without value jumps...
As always, I'm sorry if this is basic / part of every-day midi... I do try to search around before asking questions! I'm also sorry if this isn't actually possible, but that's a different kind of sorry :) haha...