My understanding is that if you utilise available configs, they will overwrite ALL of the relevant settings for whatever element you use. So if you use (for Eg) a whole VSN1 config, everything will be overwritten, but if you use an encoder config, then EVERYTHING for that encoder will be overwritten.
How then can one manage keeping the parts of the config you’ve already used, but still utilise new configurations. Eg. I want to use the Universal MidiRx config, but don’t want to lose any of the set-ups I already have. How do I achieve that. I seem to keep losing the work I’ve done when I use new configs.
Thanks - that makes sense. I keep thinking of the pages as you would for other controllers where you would use configs on each of them for different uses (mappings), and switch between them on the fly. However, more and more that seems to not be how the devs intended these to be used…clunky switching of pages being a case in point. I do think it is a restrictive scope to apply to these units where it would be much more useful to utilise pages like I do other controllers - ie page 1, controls xyz synth, and page 2 abc synth with me switching between the pages driven either by a button on the device or externally…IMO
When you Save a Config, the only options are (for me) VSN1 Module, Button Element, or Snippet. Given what you said above about it being for a page, does that mean if I want to save the Config for my whole unit I need to save 4 of these, one for each page…seems a bit crazy!! Also it references the VSN1 Module, rather than the page…so very confusing!