I agree but I feel pretty confident it will be added. But it might take some time. I think this has been a huge undertaking for them.
Hmmm, dont agree but I think that it depends on what areas youre comparing, it most likely does some details better 
But just look at the P3s SSD, ability to play huge samples, and warp them with amazingly sounding algos, great sounding FX, chopping a sample to 64 pads, MPE pads/instruments etc. The list goes on
I’m on the Beta Releases page that lists the four downloads for Live 11, Push 3 v1, Live 12, and Push 3 v2, but there are no keys listed on the page. Looking around my Centercode account, I don’t find any keys either. I see serial numbers in my regular Ableton account, but obviously those aren’t for the betas.
You did receive a e-mail with the activation code of Live 12 beta?
No, how it seems to work now is that you go to Ableton Centercode, from the menu go to Beta Releases page, choose the Push 2.0b25 beta release: the page displays a Live 12 BETA serial (for Push standalone betas) above the link to Push beta firmware.
You’re right, that’s the way to activate the Push 23 Live 20 beta.
Would that I had the time… 
Thanks for the heads up!
Well, maybe I will reach out anyway and see if there is room for someone in my circumstances… . 
Interesting to see that the Hybrid users, are questioning their investment in the standalone unit. Not totally unexpected though. I´m also questioning my investment - that I had to make - on Ableton Live suite 
As others said already a few times, Push is not Ableton and Ableton is not push. Push is a groove box that communicates perfectly with Ableton, but it’s 2 different interfaces, so you will be pushed to make music a certain way using one or the other. Micro editing? Ableton Live. Knob twisting? Push. Arrangement? A.L. Step sequencer? Push. and so on.
And what about controller being the best of both worlds? I think so, if you want to make music that requires elements that are very difficult to make on a hardware machine. If you are really efficient on Ableton Live you will definitely hit a lot of dead ends when using push. It’s just not the interface for that.
To me the appeal of a groove box is to make music completely independently. It’s ok to setup some stuff wired to a computer, but not desirable. Having to learn 2 different ways of say, make a lead on the Wavetable synth just seems contraproductive. I’ve been an Ableton (and other daws) user in the past and I don´t want to reactivate that way of making music just because I love playing with hardware. And I also think my music on hardware sounds more loose and less overproduced and I like that.
WIth this I am trying to say that I think that is very difficult for Ableton (and other software/hardware makers) to make a perfect integration DAW-Hardware-DAW, and by not doing so ends up creating some confusion and disappointment in a lot of users.
But love my Push. I’m just not liking Ableton. And I´m afraid of starting to like Ableton because I might end up disliking Push .
Is there anybody out there that make the biggest chunk of their tracks on Push and just does the arrangement (more like multitrack midi/audio recording)/mixing and mastering in Ableton? Are you guys finding it efficient? Have you found the perfect balance Push/Ableton integration?
I don’t regret my purchase of the standalone unit. It’s nice for me to have the choice. It’s also nice to just fire the Push up and not launch Ableton if I have an idea.
Luxury choices versus necessities
I have no record of a separate email when I signed up at Centercode on January 1. The only serial showing in my Ableton account is for Live 11.
That link takes me to the “My Projects” page at Centercode, which lists “Ableton HS in test” and “Live 11.” The first link displays download links for Live 12.0b25, Push 2.0b25, Push 1.1.20b7, and Live 11.3.20b7. No serial numbers or other information are listed. The second link leads to a download link for Live 11.3.20b7, also without listing any serial numbers. I’ve clicked all around Centercode, and I never see any serial numbers there.
For the Ableton Live 12 beta you must receive a activation serial code that you must add to your Ableton account. With this you can active Live 12 beta.
For the Push 3 activation you need a serial that is provided in Center Code.
Not regretting Standalone at all. It’s so much easier preparing a gig than with any other setup. Love it.
You’re saying, then, that we only receive Live 12 beta serials sometime down the line when Ableton emails it to us? I guess I’m one of the people awaiting that notification. It’s not a big deal since I’ve pre-purchased Live 12 and I’m pretty much spending all my Ableton time these days learning Push, while refreshing my minimal knowledge of Ableton.
I was simply going to wait until the Live 12 release, but then I updated my Push to the Push 3 v2 beta, which says it’s for Live 12. Will I run into some odd behavior if I leave my Push on Live 12 while my Live stays on 11 beta? If not, with Live 12 releasing imminently, I can live without the Live 12 beta.
If you have Push 3 SA then you automatically get a Live 12 beta license through centercode. I don’t have a Live 12 invite yet but I still got the license. I assume they do this because they want SA users to be able to test the newest betas for Live 12.
The serial that I was able to add to my account on Ableton.com, and then use to authorize live 12 beta on my push AND my mac, is listed under “Push 2.0b25” on centrecode.
You don’t have a serial there?
Maybe people did explain this before, but I see the serial only now, thanks.
Under the four betas listed at Centercode (two Push, two Live), only the Push v2 supplies a serial, and that serial is for Live, so looking under the Live beta link was a mistake. when I downloaded the Push beta v2, I surely saw this serial, but I guess I didn’t take note of it.
Now that I have the serial for the Live 12 Beta, I enter it into my Ableton account via “Register a product,” it appears in my Ableton account’s list of serials, and my beta authenticates properly on my laptop. The most misleading factor in all this was how the authentication process was reporting in the Firefox part that the serial found and authentication was successful while the app itself was saying no serial found.
Yeah, this was confusing as heck, I stumbled as well…
I tried to be as clear as possible, sorry.
But it’s true that Ableton could have helped by putting Live beta serial on the Live beta firmware rather than Push beta firmware.
No doubt you were reasonably clear. It’s just a surprisingly ambiguous situation when described only in words to newbies. Getting used to Ableton’s methods is a necessity, I think, because apparently the best strategy is to stay permanently on the beta tracks for Push and Live. From what people say, I glean that the betas are so hefty with bug fixes that they’re not appreciably less reliable than the release versions. Tell me if I’m wrong. In any case, it’s worth getting gotcha’ed by feature changes to get the bug fixes, not to mention try out new features early.
