Quote:
Originally Posted by nofish
Hm..I thought this is common VST(? not sure about other formats) behaviour.
E.g. I did this in Reaper, behaving exactly the same, or am I misunderstanding?
|
Hmm - this appears to be a difference between VST2 and VST3 that I never noticed before.
Also in Reaper I found:
1) VST2 - Changing settings after loading a preset saves the changes to the preset.
2) VST3 - changing settings after loading a preset does NOT save the changes to the preset.
Now, I couldn't test this difference in Ableton Live 10 because it appears it does not support VST3 "baked in" presets at all - only supported in VST2 versions. Wavelab 10 does not show VST3 hard-coded presets either (I reported that to PG at Steinberg and he said he would fix it in 10.0.30). Cubase 10 DOES support it. Go figure!