Midi Clip Automation, Next Scene, Retain Previous State?

[JohnnyIndia]

I can't figure out how to do the following:

I need to have a scene that uses clip automation to set certain parameters (soft synth parameters, chain activator states, etc.) and then those parameters remain when I trigger the next scene in the session view....currently, it seems the only way to do this is to redraw the automation on the following scene...this is incredibly time consuming. Otherwise, when I go to the next scene, those parameters that I set revert back to different parameters.

To explain with an example: I may have 5 scenes for a song. I want to be able to set the parameters on a plugin, or ableton function in the first scene using clip envelope automation/modulation (I.e. Set LFO to 1/2 rate, / set chain activator to "ON / set fader volume") and have that state carry over into the following scenes without having to redraw in the clip envelope....currently when I do this, and click next scene, the settings revert back to a previous state....redrawing the automation/modulation for each scene is tedious, and I'd rather draw it in once at the first scene of a song, and then have the next 5 scenes follow those state changes.

Is this possible? If not, is it possible to copy and paste all the clip envelope automation from one scene to the next? This would be less time consuming than drawing in the automation for every parameter on every scene in a song...

To get more specific, let's say Scene 1 is a midi clip for an instance of Xfer Serum...I write in automation on the first scene clip that tells Serum to change the LFO rate to 1/2....what I want then is for the LFO to stay at 1/2 when I click "Next Scene". What instead happens, is the LFO then reverts to some previous state...ideally, I want every following scene to be 1/2 LFO without having to redraw that automation in the next 4 scenes/clips....then let's say in scene 5 I want the LFO rate to change to 1/4....I would then want to write in automation in scene 5 to change the LFO rate to 1/4, and then keep it at 1/4 when I go to scene 6, 7 , etc. until otherwise automated again....what happens instead is LFO rate will revert back to 1/2 in scene 6, 7 etc. rather than retain the state of scene 5.

Same goes for ableton functions. Let's say I want scene 1 to turn the chain activator on a track ON...when I go to scene 2 I want that activator to remain on....but if the chain activator was in the off state before triggerin scene 1, it will revert back to the off state when I click next scene and trigger the clip in scene 2....I want it to follow the state I set in scene 1 somehow.

I hope this makes sense so that someone can point me in the right direction for a solution. If I can't have the next scene retain the previous states set by the previous clip, then at least a way to copy all the automation/modulation envelopes from a clip and paste it onto a new clip would be the next best thing.

[gerundio]

I have the same problem. I can't believe there's no solution... Anyone?

[fortsound]

I am having the exact same issue it is really slowing me down. I do a lot of automation during my live shows and I am basically remixing tracks on the fly. At the beginning of every song [the first scene] I wipe all used automation back to defaults but it then jumps to some setting - for example a send that I used to end the previous song. Now in scene2 of the new song it comes back to haunt me. This behaviour does not make any sense. It also happens with track volumes. It is impossible to keep copying all the automation over to each scene also because it does not copy automation for multiple clips when those clips have different lengths [and with me they always do because they are musically sensible parts of my song - not simple 4 or 8 bar loops]. I want to be able to to tell Ableton to leave any automation on the last clip's state when the next clip does not have any new automation to overwrite the previous setting. Now it jumps back to where the controller left it off, not taking account the NEWER automation data. Serious bummer, there must be more people experiencing this.