Automation recording jumps back to previous value

[Glint_Eye]

Hey Everyone,

couldn't find this one in the Forum.

I'm on Push 1 and Live 9.5 and got the following strange behaviour. When i am recording automation with Push on a Track which already had automation written on it, the automation lane jumps back to the point of the previous automation recording, when i let go of the encoder.

I've already tried to use a simple absolute midi controller like a knob or fader. Works fine... The automation stays wherever i let go.
I also tried to use a Push encoder in User Mode, midi mapped to a parameter. Works fine as well.

Only in the native Push Script i get this weird behaviour, which of course screws up every real time automation recording...

The really weird thing is it only happens the second time i touch and let go of the encoder. Like: I'm starting to record automation then i move the encoder around, let go of the encoder and the parameter stays where it is. Then i touch and move around the encoder a second time, let go of it and the automation lane jumps back immediately to the point of the previously done automation.

Can anybody confirm this or has an idea whats going on here?

Cheers.

[Stromkraft]

Can anybody confirm this or has an idea whats going on here?

Is this with the previous automation recording not getting played when the new recording stops? Because if it exists in the track after the out point then the jump is hardly surprising as Live is reading what data there is in the track.

If not and if the automation override button is lit when this occurs, it could be a bug Ableton is currently tracking.

[Glint_Eye]

Is this with the previous automation recording not getting played when the new recording stops?

Hey.

No, it jumps back to the previously recorded automation value while recording is still running.

[Stromkraft]

Is this with the previous automation recording not getting played when the new recording stops?

Hey.

No, it jumps back to the previously recorded automation value while recording is still running.

Hmm, this sounds very strange. Is this repeatable every time or just in a specific project?

[Stromkraft]

Can anybody confirm this or has an idea whats going on here?

I can confirm this doesn't happen in 9.6.1. I don't have 9.5 anymore.

What I did in Push 1 was this:

• Recorded a clip with automation with high values
• Stopped recording
• Deleted the automation
• Overdubbed automation with low values

The last recorded material plays. No jump backs as expected.

I think you need to be more detailed on what you do, what you expect and what does indeed happen.

[johnnyPB]

This problem persists with my Push 2 running Ableton 10.1.41.
First off there is a written/recorded value (for example a Utility plug) of 0 db through the whole track, this does not happen without previously recorded automation. Not being able to skip in a track and record further automations, or even edit with the input of my Push 2 would be really contra-productive.

I start recording with overdub and automation arm activated and the track lights up red (as in currently recording and overwriting automation). I keep my hand on the dial and it reacts to my input as i lower the value to -4db. If i let go of the dial at this point and don't manipulate it; it stays put.
However if I touch the dial again and try to manipulate the value further the Push 2-display will snap back and display 0db whilist still recording the value -4db. If I let go or touch the dial at this point the recording snaps to 0db and will do so every time i manipulate it further until i stop recording.

I found a workaround of having "Re-enable Automation" lit up before pressing record, but that will only work for the one dial i initially start manipulating/have greyed out. If i were to touch or attempt to try anything with a dial i haven't touched prior to pressing record; it will snap back as above.

[imDug]

Hey! I know this post is a bit old but by chance have you found a solution to this issue you have been experiencing? I am having the exact same problem and it is SUPER annoying. I am currently using a Push 2 with live 11 and this problem is non-stop with many projects. I was hoping to find any magical tricks to fix this issue.

[imDug]

This problem persists with my Push 2 running Ableton 10.1.41.
First off there is a written/recorded value (for example a Utility plug) of 0 db through the whole track, this does not happen without previously recorded automation. Not being able to skip in a track and record further automations, or even edit with the input of my Push 2 would be really contra-productive.

I start recording with overdub and automation arm activated and the track lights up red (as in currently recording and overwriting automation). I keep my hand on the dial and it reacts to my input as i lower the value to -4db. If i let go of the dial at this point and don't manipulate it; it stays put.
However if I touch the dial again and try to manipulate the value further the Push 2-display will snap back and display 0db whilist still recording the value -4db. If I let go or touch the dial at this point the recording snaps to 0db and will do so every time i manipulate it further until i stop recording.

I found a workaround of having "Re-enable Automation" lit up before pressing record, but that will only work for the one dial i initially start manipulating/have greyed out. If i were to touch or attempt to try anything with a dial i haven't touched prior to pressing record; it will snap back as above.

Hey! I know this post is a bit old but by chance have you found a solution to this issue you have been experiencing? I am having the exact same problem and it is SUPER annoying. I am currently using a Push 2 with live 11 and this problem is non-stop with many projects. I was hoping to find any magical tricks to fix this issue.

[xenum]

Hi!
Has anyone found a solution to this?

Same problem here with Push 2 and Live 12.