When you apply the mapping for parameter 1, do the following: Close the mapping assistant, close the rce, disable track (with super 8), re-enable track.
Let’s see if that makes it stick.
To put it in two simple rules:
In the video, you are doing both at the same time, that’s why it looks so inexplicable
thank you so much gg <3
I’ve actually tried again from scratch and all the mappings are there again.
Also the QC dilemma seems to be solved too.
Not super sure how but I’ll keep digging.
Thanks again pal 
To put it in simple terms:
The point is to decide on a basis of what’s really needed right now for your worklflow. And when a new need arises, build on what you already have.
that makes sense thanks
when I said “I’ll keep digging” I meant that I’m not 100% sure how I solved it and until I find out I might bump into unexpected results like this 
Not sure what I’m missing there but mapping Massive X isn’t doing the trick (headscratch on 3…2…1…go)
hang on, as you suggested up here, I disabled the track and re-enabled it and now it’s working wtf 
At this point I’m thinking that “Disable/Enable” the track is mandatory?
Cos is not specified anywhere (YT tuts nor in the manual afaik) but it seems to be uber critical in order to get mapping to work using the RCE?
Seems to be mandatory for this specific reason:
seems that “old” mapping is sort of “buffered” somewhere and still exist and will conflict with a “new” mapping
Seems that “Disable/Enable” resets that hypotetical “buffer”
I guess this (not applying the new RCE order) is down to the plug-in. Not every developer follows guidelines to the letter. Some plug-ins “refresh” the list of parameters as soon as you hit Apply in the RCE, but other plug-ins do not. Those that don’t keep the “new” RCE layout aside, and put it into effect the next time they are loaded.
(Rough guess, don’t really know. But it agrees with observation. Disable/Enable does the trick. It unloads the plug, and then reloads it. Before it wasn’t working, after loading it does. If you use a new instance of the plug in another slot, or another track, that counts too I believe. So the mapping must be somewhere in there when clicking apply.)
Anyway, I have made a habit of it now, to unload/reload each plug after making changes to the RCE, so that I don’t spend the 5-10 seconds in utter confusion before it dawns on me “ohhh right, forgot to “refresh” the plug-in itself”
Indeed rough guess, if we’re potentially getting into code-specifics and Steinberg’s VST guidelines requirements, then it can get obscure and out fo reach awfully quick.
Even tho’, in my head, I always assume (maybe wrong) that QA at Steinberg has come up with a validation roadblock to make sure each 3rd party dev must strictly comply to those guidelines.
At the same time, this particular case, feels pretty unique and, working in game dev, I’m aware that big architectures always have some dark spots here & there that cannot be “conceived” if not after years down the line
Let me add another clue: 2 days ago I replugged my Midi Fighter Twister I previously created a whole mapping for but eventually abandoned 1 month ago.
I plugged it in and the mapping was still there.
I mapped the “Reverb On/Off” of Super 8 to an encoder but then I remembered why I didn’t like the controller and plugged it off again.
I remapped the fader on my Keylab 88 to another function (Amp Attack) where the “ReverbOn/Off” was located in the RCE and then in the Mapping Assistant but anytime I moved the fader I would still get the “Reverb On/Off” function from that Midi Fighter Twister which was no longer plugged in.
I could see, once selected the function in the RCE, that MAssistant would show the function colored yellow instead of white and I sensed that yellow coloring meant a mapping was already there but couldn’t figure out why since in the RCE there was no trace of it.
Obvs without doing the disable/enable trick
Kinda confirms this existing “buffer” storing those old mappings somewhere.
also, thinking of “Not every developer follows guidelines to the letter.” I’ve found out that
Massive X can only be mapped as long as you assign a parameter to these macros
the RCE doesn’t detect any parameter you move unless is assigned to one of those 16 macros. Which means, to my understanding as of today, that Massive X can only have a max of 16 mapping.
Omnisphere seems to work differently too.
I’m yet to find a tut on YT that mentions any of what we’ve discussed here.
Maybe it’d be useful, once I’m 100% sure, to reorganize this post and make it available for the community
And thanks again GG, without your input, I’d still be faffing around and scratching my head up
