Ableton Forum

Relevant thread: https://www.reddit.com/r/ableton/commen ... /?sort=new

Basically since 12.4, my push2 seems to get itself into an annoyingly weird state between Session and Clip view where the pads will highlight both and its impossible to properly get into note layout without triggering clips, or visaversa.

I have also noticed (maybe related or separate) that the screen will have the classic half gradient fade at the bottom with no prompt text, and will never clear.

Im constantly getting this issue and it has literally made the push2 unusable which means I cant do any live performances

Does anyone else get this same issue? i've already tried re-installing Live to refresh the remote script but it still happens.

Are you using any M4L device, or any 3rd party script made to customise Push's behavior?

scruffyfox wrote: ↑

Fri Jun 05, 2026 9:10 pm

half gradient fade at the bottom with no prompt text, and will never clear.

That rings a bell. Sounds like it's related to where the Variations are displayed. Are you seeing this in every view/mode?

I do have a custom device that can take over the push's pads that could be interfering. never had this kind of issue before with it and it has a toggle to activate/deactivate. I will try a set without them to see if i encounter the issue

One possible cause is when having a Drum Rack on a track set to "16 pitches" layout and navigating to/from it, Live will severely lag and drop audio. This even happens on a completely blank set. The audio/lag is so bad that it causes the midi clock to go out of sync with all my devices and even causes my launch control XL to "reset" back to the factory template (like it just been reinitialised)

edit: i just noticed that it is literally resetting the playhead back to 1.1.1 when this happens

That rings a bell. Sounds like it's related to where the Variations are displayed. Are you seeing this in every view/mode?

Yeah it doesnt go away even if I try and force a new status update to refresh the disappear timer

scruffyfox wrote: ↑

Fri Jun 05, 2026 10:59 pm

I do have a custom device that can take over the push's pads that could be interfering. never had this kind of issue before

There's some relatively important changes in M4L with L12.4, so that could explain it.
Let us know once you tested without that device in your set.

I'm having the exact same problem. It seems to occur when I select 'clip view' which now displays the session in the preview window (new feature). After selecting this it seems to mess up switching between 'session' and 'note' layout.

In other words it gets stuck in session view or half and half session/note view (as described by scruffyfox) and I can't get back to playing in 'note' view. This is a bit of a problem! Especially since I have an album launch gig on Thursday! It seems like a bug in the firmware?

fishface wrote: ↑

Sun Jun 07, 2026 4:41 pm

I'm having the exact same problem. It seems to occur when I select 'clip view' which now displays the session in the preview window (new feature). After selecting this it seems to mess up switching between 'session' and 'note' layout.

In other words it gets stuck in session view or half and half session/note view (as described by scruffyfox) and I can't get back to playing in 'note' view. This is a bit of a problem! Especially since I have an album launch gig on Thursday! It seems like a bug in the firmware?

And are you seeing this all the time, or only with certain Sets?

I have the same problem since Live 12.4

Its so annoying

And did anyone report to Support yet?

No , but I will,

before I had to find out, what is causing it exactly.

But I think it happens when you play a scene in session mode with clip view or on push pads in session mode, while one or more track has played on arrangement mode before.

phil-ip beats wrote: ↑

Tue Jun 09, 2026 6:50 pm

But I think it happens when you play a scene in session mode with clip view or on push pads in session mode, while one or more track has played on arrangement mode before.

I'll try that and see if i can repro.

[jur] wrote: ↑

Sat Jun 06, 2026 8:06 pm

scruffyfox wrote: ↑

Fri Jun 05, 2026 10:59 pm

I do have a custom device that can take over the push's pads that could be interfering. never had this kind of issue before

There's some relatively important changes in M4L with L12.4, so that could explain it.
Let us know once you tested without that device in your set.

So I did another set without my custom device and I still ended up experiencing the issue. It's almost like it gets confused when using/cycling through different states too quickly like going between session/note view and the note layout views. I've not been able to identify or recreate an exact cause just that at some point in my set, the note button will just "stop" working, and sometimes, some combination of navigating around different tracks im able to get back into note view, but the button never works like it's supposed to after that.

phil-ip beats wrote: ↑

Tue Jun 09, 2026 6:50 pm

But I think it happens when you play a scene in session mode with clip view or on push pads in session mode, while one or more track has played on arrangement mode before.

I've just reproduced it. No Arrangement involved here.
When the pads are stuck in Session mode, pressing the Note (mode) button arms the currently selected track, just like if it was actually switching to Note mode, but the pads stay in Session. (To me, that sounds like it could be related to the new Auto Arm Tracks options in Push's Setup, but there's probably more to it.)
FYI, I followed the steps quoted above, but also made sure to have a drum rack using the 16 Pitches mode (no idea if this plays a role atm, though).

Can someone try this changing the color of a drum pad (hold Shift and press a pad)? It's getting stuck on the color palette here.

With both the color palette or the Session being stuck, the way to get out of it is to select another track... but that doesn't mean every randomly lit pad will turn off.

That'd be great if all of you could report to Support. I'm forwarding on my end too.

Did anyone report to Support already?

I have raised a support request

scruffyfox wrote: ↑

Mon Jun 22, 2026 8:48 pm

I have raised a support request