No- if I duplicate a serum instance, MPE remains enabled in both Serum & Ableton and works as expected. FWIW I also have ‘MPE Enabled by Default’ checked (as well as ‘Limit Polyphony to One of Any Note Number’ deselected) for Serum’s default settings. (and at one point, I’d clicked the save icon in global preferences after setting those settings.)
When I duplicate a Vital instance that has both ‘Enable MPE Mode’ checked in Ableton, and ‘MPE Enabled’ set on under ‘Tuning’ within Vital’s settings, the duplicated track will still say that both are checked- but MPE does not perform correctly until I toggle ‘MPE Enabled’ off and on in Vital.
Just thinking out loud here so this could work or not but try this. Open up a fresh instance of Vital not touching its default settings and make sure ‘MPE Enabled’ is working (so yeah, go through the toggle/re-toggle thing if necessary). Then right-click on the device and “Save as Default Preset”. Does that change anything when duplicating?
Unfortunately not- same behavior as before when duplicating, where ‘MPE Enabled’ will be checked in Ableton & ‘MPE Enabled’ in Vital, but MPE retuning won’t work until I toggle it off then on in Vital.
Also interesting is that creating a brand new instance of Vital after doing this does not actually keep ‘MPE Enabled’ on even after using ‘Save as Default Configuration’ in Ableton.
I think something about this particular parameter is not stored properly with the plugin state.
Probably the same issue. I’m on Mac OS Sonoma 14.3/Ableton 11.3.21 and getting this. Worth noting the exact same thing is happening to me with Arturia Pigments. I contacted Arturia support about it and they couldn’t reproduce it. Seems like a bug with Ableton + certain plugins, as some other MPE synths I have are working fine in Ableton.