Should my automation behave like this?

[portrhombus]

Hello,

First off, I have tried doing a search for this but nothing came up, so either it's not been covered or I suck at searching. (Probably the last option.)

I have a (two part) question;

Does anybody else have this trouble with writing in automation into a clip? Let's say I create a clip and the sample start is at 10% for one of the samples. I then duplicate that clip and want to write in automation so the sample in this clip starts at 30%. Automation selected, record enabled, move the pot for sample start; automation begins recording, no problem. The problem occurs when I hold the same value throughout the length of the clip. When I stop recording, the automation deletes itself and simply sets 30% as the new base value, which both clip 1 and clip 2 read.

Am I being a moron or is this a problem/setting within the Push? It only happens when I want to set a particular value for the entire clip - which sometimes I really need/want - and it's INFURIATING me. If there are a few fluctuations within it, the automation will record in fine*. I feel like I'm being a moron.

* Following on from this, is there any way to let a parameter setting revert back to the value before I attached automation on it? Basically touch instead of latch. Because when I do record in automation on a parameter, when I launch an earlier clip that has no automation for that parameter, it never plays out at the original value, it has the value from the end of the automation. Of course with the problem above and not being able to write in a constant parameter value in automation means I'm at a loss as to how have clips which have different parameter values, especially where the clips contain constant values.

I can of course, just click with the mouse and add a single point within the clip envelope. But I bought the Push to use the mouse as little as possible and I'd rather utilise that because I use a fair amount of automation.

[Valiumdupeuple]

Your not doing anything wrong, and I agree, these are annoying things that need to be improved.

[portrhombus]

Hmmmm, to be fair to Ableton I think it might have been me, after a bit of discussion and trial and error with someone.

Basically when I hold a constant value it'll write that value as automation, but once it loops round back to the same value, the clip doesn't actually have any value notches written into it. Hence the automation 'disappears' when I let go. What I actually need to do is hold the value until it's been set for the duration of the clip and also wait for the clip to start looping again. At which point a notch gets created with that value right at the start of the clip. Then I can let go and I have a constant value for the clip.

So yeah. I was being a slight moron.

[TomViolenz]

Hmmmm, to be fair to Ableton I think it might have been me, after a bit of discussion and trial and error with someone.

Basically when I hold a constant value it'll write that value as automation, but once it loops round back to the same value, the clip doesn't actually have any value notches written into it. Hence the automation 'disappears' when I let go. What I actually need to do is hold the value until it's been set for the duration of the clip and also wait for the clip to start looping again. At which point a notch gets created with that value right at the start of the clip. Then I can let go and I have a constant value for the clip.

So yeah. I was being a slight moron.

What you do is, you give the knob a very slight nudge. That will create a break point. Then you should be able to let go of the encoder.