Page 1 of 1

vst fx settings lost on opening (sorry if this has come up)

Posted: Tue Mar 11, 2003 11:35 am
by Mark Henning
sorry if this has come up before, but....

is it me, or are VST FX settings lost each time you shut/open Live???

Thanks.

if someone could point me to the right thread if this issue has come up previously... :)

Posted: Tue Mar 11, 2003 11:42 am
by Mbazzy
Mmm, when I insert VST efx [win2000-Live 2.0.3 ] My last saved settings are still there ...

Posted: Tue Mar 11, 2003 2:17 pm
by Frank Hoffmann
Can you specify which plugin(s) loose(s) the VST settings?

Frank

Posted: Tue Mar 11, 2003 6:15 pm
by Mark Henning
frh wrote:Can you specify which plugin(s) loose(s) the VST settings?

Frank
the DiscoDSP ThrillMe plugin....

thanks :)

Posted: Fri Mar 14, 2003 12:00 pm
by Frank Hoffmann
Mark, sorry. I think i didn't get first time what you ment. Do you mean that you edit a VST plugin setting in Live and the preset is not changed after quitting Live? That is true and a limitation we intend to change in the future. You can only save the settings of your VST plugin with a song for now. Many plugins provide their own interface for preset handling, but not the ThrillMe plugin.

Frank

Re: vst fx settings lost on opening (sorry if this has come up)

Posted: Sat Mar 15, 2003 8:58 am
by DCools
Yes, I have the same problem.

See my topic http://www.ableton.com/forum/viewtopic.php?t=2677

Regards,
Diederick F.M. Cools.

Posted: Wed Mar 26, 2003 11:38 am
by atom_b
You can only save the settings of your VST plugin with a song for now. Many plugins provide their own interface for preset handling, but not the ThrillMe plugin.
There seems to be some limitation with generic save/load-mechanisms from Live too, wich can be very annoying:

I haven't been using my UAD-plugins as well as D-Pole lately in Live. Now I must learn that I can't load or save any banks or presets anymore, since the built-in generic load/save-mechanism is disabled by Live.

While this is bad with UAD-plugins (I have some very helpful presets I can't load anymore), after all Live remembers the settings I actually made ina set(though I can't store them anymore, anywhere).

But it is absolutely inacceptable within D-Pole, where the generic save/load-mechanism is disabled by Live as well as it is *not* remembering the changes I made when I reopen the set. If you know what a pain it can be to restore settings in D-Pole just from what you remember, you'll know that this is not workable at all.

Am I wrong that until 1.5 this all was still possible and it vanished with 2.0x?

Oh you magnificent Abletons, please try to fix this with the next distro!

Posted: Wed Mar 26, 2003 2:36 pm
by Frank Hoffmann
Live doesn't disable anything. The plugin preset management is up to the host, if the Plugin doesn't provide an internal preset management. Live doesn't support loading and saving of preset banks in Live with versions up to 2.0.3. But it does save your presets you use into a song. We are aware on this limitation and working on a solutions.

Frank

Posted: Wed Mar 26, 2003 4:30 pm
by atom_b
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.

Worked around it...

Posted: Thu Mar 27, 2003 6:04 pm
by atom_b