Ableton Forum

In session view, I place a VSTi (Triangle II) in a track and create a new clip. I add some notes and loop the clip. Now I want to automate the filter cutoff in this clip. The cutoff in the preset is set about halfway between its min and max value. I draw in some automation and play the clip again. Up to this point all is fine.
I save the set and close Live. When I return to this set, the preset for the VSTi has been saved with a cutoff set at whatever the last automation value sent to it was. As the automation values work as x% of the original value, this is going to be less than the original value. When I play this clip now the automation produces lower cutoff values than I wanted. If I continue saving and re-loading the set, the cutoff in the preset eventually moves towards its minimum setting and the automation has very little effect.

Surely the x% should be applied to the whole range of the VSTi parameter, not just its current value?

Every time I open this set I have to set all the parameters that I have automated back to what they were originally, or I have to reload a saved version of the preset. Doing this for every VSTi and every preset that I have automated for every set that I open is going to be REALLY tedious.

You explained it sooooo much better than I did

I have this exact same problem and it is definitely giving me headaches. I've got tons of automation! This is going to be a tough one to fix for a myriad of reasons.

Yes, something similar happened to me:
http://www.ableton.com/forum/viewtopic.php?t=11276

jammen..? it happen on my rig as well..i'm REALLY looking forward to the next update!!! - hope it's bug-FREE this time..

regs,
jo

Anyone from Ableton have anything to say on this problem?

Sorry for not answering earlier. I had to look into the problem first and many more problems in the row.

You are right. This is not convenient. We are thinking what we can do about it.

Frank

Thanks Frank!

Yes, this is an odd problem indeed. Its more a problem of figuring out the best way to go about it. I'm thinking as well...I'll post here if I come up with any ideas.

Anyone else know how they'd like to handle it? You have to take into consideration that you might want to globally nudge a parameter for the song. Very difficult.

/drez

EverReaL wrote: Surely the x% should be applied to the whole range of the VSTi parameter, not just its current value?

Is this not how it should be? It is in all other VSTi software I have used. (mainly Cubase).
Then, it wouldnt matter what value was stored in the preset as the automation would set it to the values you actually want anyway.

Regards, EverReaL

EverReaL, other sequencing applications like cubase don't have something like Clip Envelopes. Clipe Envelopes are much more than simple automations.

Frank

Frank Hoffmann wrote: ...You are right. This is not convenient. We are thinking what we can do about it.

I'm at work right now so can't d/l and try 4.0.2 but this problem does not appear on the list of fixed bugs. Is there any update on a resolution to this problem - it's driving me crazy!

EverReaL

EverReal, try the update. It has some improvements in this section. But we were not able to resolve every single issue.

Frank

Frank, have tried the update and this problem seems to have improved greatly but hasn't completely gone away. I guess thats becuase the saved set has the wrong values anyway.

Unfortunately the problem with multiple outs from plugins has totally screwed everything else for me. 4.0.3 soon please.

EverReaL