Updated UAD DelayComp crashes Live 2.03
Posted: Wed Mar 26, 2003 4:44 pm
I updated the UAD-plugins to 3.01 today. ableton Live now doesn't load Sets anymore wich have the earlier 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 registered within Live with UAD-versions prior to 3.01.
This is especially bad, since I can't open these Sets anymore, by no way.
I've been already asking over at UAD-forum if there is any information available regarding the registration of UAD DelayComp with its host, that I can hand over to the devs at ableton.
Regards
BV
- 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 registered within Live with UAD-versions prior to 3.01.
This is especially bad, since I can't open these Sets anymore, by no way.
I've been already asking over at UAD-forum if there is any information available regarding the registration of UAD DelayComp with its host, that I can hand over to the devs at ableton.
Regards
BV