Have to Press Record Button Twice-Sometimes But Not All the Time

[LemonEar]

Usually the set up is that I have the metronome playing to count myself in, I select my Fixed Length to record. Global Quantization is set to 1 bar, I press the Record button and sometimes it works as expected, and other times it doesn't. I have to press Record two times regularly.

The person who is teaching me live looping says it happens to him regularly too. He uses a piano style sustain pedal (I don't have one yet) and says very often he has to step on it twice in order to engage recording.

Any idea what could be causing this?

[vinnibald]

I am experiencing the same issue with Push 2. It is not dependent on Fixed Length.

Push 2:
Firmware 1.0 Build 69

Ableton:
10 Suite 10.1.18 Build

https://www.youtube.com/watch?v=uIM_2u83FEs

Just found out that when I manually arm or disarm any track, I need to press record twice afterwards, no matter which track I want to record.
(disarming/arming directly on push 2 - holding any track for 2 secs)

I guess its a bug. In "Note" view it should record no matter if its "darkred-armed" or just "push2-armed".

So get used to press it twice after arming/disarming any track on push 2.

Weird and annoying and confusing behaviour. Or I dont get why Push 2 behaves like this.

BTW I need to press twice to STOP recording when I armed/disarmed a track while recording, too.

Can someone explain further?

[[jur]]

That's a bug, good catch!
We're filling it.

For now, a workaround is to use the (hold)REC + Track Selector button to un/arm a track.

[vinnibald]

Many thanks for the quick feedback!

Can you estimate how long the fix will take, or is the extent of the necessary changes not yet calculable?

The workaround works like a charm. I didnt know you can arm tracks like this.
Its even faster, but you need two hands...

This bug is so essential, I experience it very often when I change some arming and then fail recording afterwards...

Is this a new bug since the last update or did nobody else really notice it?

[[jur]]

Can you estimate how long the fix will take, or is the extent of the necessary changes not yet calculable?

Is this a new bug since the last update or did nobody else really notice it?

It's actually not that new, but I have no idea when it'll be fixed, sorry.

[tonemalogne]

Hello, I am also having this issue and it is very frustrating! This forum post is almost two years old now, is there any chance you guys can bump this up on the priority list please?

I'm running Ableton 11 Live Suite 11.1.1, Push 2 Firmware 1.0 Build 71.

[spyinzedark]

Hi, anything new about this bug ?
It's very frustrating to me also...

[deluxe87]

It's 2023 and guess what? The bug still here. I have Live v11.2.
I just want to ask developers or whatever Ableton team: do you feel any shame by any chance? I would be for sure!

[[jur]]

It's 2023 and guess what? The bug still here. I have Live v11.2.
I just want to ask developers or whatever Ableton team: do you feel any shame by any chance? I would be for sure!

I haven't experienced it recently so I didn't notice it's still here.
Please send a bug report to Support !

[johnsimmons]

I haven't experienced it recently so I didn't notice it's still here.
Please send a bug report to Support !

Oh man, how was this forgotten about down at HQ? I've been dealing with this every Ableton session for so many years now. It's bittersweet finding this thread because, all along, I thought it was because my Push 2 Rec button was starting to wear out.

It's also nice to find out about the Rec button + Track Select button to arm select without this double-pushing bug. Somehow i missed this one.

But still, I learned the long press way to do it and it is ridiculous that it's still there! I'll send a report.

[desiggers]

This is indeed an ancient issue.
I have a suggestion however:
In options.txt check if you have "-EnableArmOnSelection" present.

I've used this as a solution for a long time (via Push Bible) to improve this behaviour.

Of late however it seems that it's actually making it worse.

I removed it and things got better immediately. Even when I put it back in, things were better.

Give it a try and see if it helps - curious to know if it does.

[whatisnotrue]

I was always confused about this behavior. Nice to see it reported 5 months ago.

[[jur]]

I was always confused about this behavior. Nice to see it reported 5 months ago.

Make sure to report it too, the more info for the devs the better; and the more reports the higher it goes into the priority list.

[chapelier fou]

I’ve reported it as well and it’s been logged.