OK I have a repro path for the breaking MIDI controllers: Latest VEP7, latest Mac intel
Repro:
1. Launch VSL and create a new instance, with an instrument plugin of your choice
2. Connect to the instance from your DAW, and learn a MIDI controller (over there on the right column hidden behind Automation/Parameters) using your keyboard controller and a knob on the plugin
3. Turn the Instance's power off (so you won't have to wait to load it every time you open the server project) and disconnect from it.
4. Save the server project as "CC Test 1"
5. Quit and relaunch VEP7. Open CC Test 1 server project. Note that the CC controller is still properly mapped to the plugin knob, but don't power it back on
6. Save it as "CC Test 2"
7. Quit and relaunch VEP7. Open CC Test 2 server project.
=> THE MIDI CONTROLLER IS NOW BROKEN. It still knows the keyboard control, but it decided to stop saving the plugin control when it was powered off. That is now blank and has to be remapped.
While this may seem a rare path, it is a super-common path for me, as I am using a big template full of powered-off options, some with MIDI controllers mapped to them, that loads quickly but lets me choose which instances I want to work with on a project, and then save the server project as a specific version. I'm constantly forced to remap the MIDI controllers because of this bug, and what's worse, people not expecting this bug may silently have changes in their arrangement introduced by it, which will only be discovered later, potentially with a costly or dismaying result (imagine it is rendered as reference for a live recording, and the live players don't play vibrato because the rendering's vibrato quietly got broken by this bug!).
Don't say "ah it's good enough." ZERO of your customers feel that way about what they are being paid to produce. Whose music has bugs like these? And they are being paid less than you!