The plugin preset management is up to the host, if the Plugin doesn't provide an internal preset management
...wich is what I call generic.
But it does save your presets you use into a song.
... well, as I wrote, it does *not* with Waldorf D-pole.
FYI: Another,
more important thing occured today, as I updated the UAD-plugins to 3.01. Live doesn't load Sets anymore wich have the
UAD DelayComp loaded in one or more tracks:
- Load a set in 2.03 wich includes UAD DelayComp inserted before updating the UAD-plugins
-> First message is about 'Path\to\my\VSTfolder\...\UAD DelayComp could not be loaded' (more messages come up depending on the number of DelayComps used - Note: UAD DelayComp actually is in the path)
-> Second message is the Application-Error-Message, wich recommends to save work under a different name, and to restart the application...
-> Latter message can not be quitted, since it kind of reoccurs in an endless loop
-> Have to kill the process to quit the application (can reproduce this anytime)
Compare with UAD DelayComp not in the path:
-> Same results as above
Compare with newly inserted DelayComp:
- Insert the very same updated UAD DelayComp in some already existing and one new Set
- Close the Sets and reopen
-> Everything runs as usual
Since the DelayComp *does* run when newly inserted, there must be some trouble causing change in the way its presence was saved within Live with UAD-versions prior to 3.01.
This is especially bad, since I can't open these Sets anymore, by no way.