Found an update option to 1.1.1 in the license panel.
1.1.1 seems to save, but only after I save a separate data file.
I really love SV as a tool, but that behavior I feel is less than ideal for a VSTi plugin. Other plugins with built-in TL editors, such as Melodyne or Vocaloid (the plugin, not the built-in editor) save just fine with VSTi.
I believe that in the VST SDK it is expected for a plugin to fully serialize and deserialize its state to the host. This is described here: https://steinbergmedia.github.io/vst3_doc/vstinterfaces/index.html#Persistence
It should not be necessary to first save the state. Is there any chance for that to get fixed?
Thanks so much! I can’t wait for more english-language content for SV2, I know I will buy it immediately - but please fix the VSTi saving.
Even better would be support for ARA2: That would make it possible to support clips in the timeline instead of just linear tracks. For my workflow that would be simply amazing. ARA is supported by most common plugin hosts as well as Melodyne and Vocalign - plugins that do similar things to Synthesizer V in terms of editor and track management. More info here: https://www.celemony.com/en/service1/about-celemony/technologies