Ableton Push 3 - standalone MPE controller

[elxsound]

One thing is for sure, Ableton takes time to do stuff but they are not in a hurry to keep releasing stuff just for "growth", it took them 8 years for version 3 and it has some upgradability so I will expect it to be the main focus at least for 5 years and they can do a lot in that time.

I strongly doubt they’re interested in growth at the moment. Growth requires more employees and it comes with more problems. They likely have their hands full?

I’m guessing they’ll be working on issues for now before addressing new features that might attract a growing user base.

[machinesworking]

They obviously weren’t set up to handle the amount of returns they’re dealing with

Curious to know more about this - is there a news article or something? Couldn’t see anything in KVR.

Me too, I can't find any info on 'the amount of returns'. Probably all in his/her head...

There are plenty of threads on the Ableton forums addressing this, with employees of Ableton chiming in to apologize for the delay. It's a backlog, they admit it, nothing is "in my head".

[elxsound]

They obviously weren’t set up to handle the amount of returns they’re dealing with

Curious to know more about this - is there a news article or something? Couldn’t see anything in KVR.

Me too, I can't find any info on 'the amount of returns'. Probably all in his/her head...

There are plenty of threads on the Ableton forums addressing this, with employees of Ableton chiming in to apologize for the delay. It's a backlog, they admit it, nothing is "in my head".

Backlog in support, nothing to indicate its a backlog in returns. Feel free to show me otherwise, but I checked the Ableton forum and nothing specified it was due to returns.

[machinesworking]

They obviously weren’t set up to handle the amount of returns they’re dealing with

Curious to know more about this - is there a news article or something? Couldn’t see anything in KVR.

Me too, I can't find any info on 'the amount of returns'. Probably all in his/her head...

There are plenty of threads on the Ableton forums addressing this, with employees of Ableton chiming in to apologize for the delay. It's a backlog, they admit it, nothing is "in my head".

Backlog in support, nothing to indicate its a backlog in returns. Feel free to show me otherwise, but I checked the Ableton forum and nothing specified it was due to returns.

I'm not going to impress you with links, especially since none of this is hard to find and you "didn't find it". You would attempt to downplay it anyway. You bought it, you don't need or want to think other people aren't happy with it, and you have spent a few threads defending it. These are our roles, I'm the critic, you're the loyalist.

[elxsound]

They obviously weren’t set up to handle the amount of returns they’re dealing with

Curious to know more about this - is there a news article or something? Couldn’t see anything in KVR.

Me too, I can't find any info on 'the amount of returns'. Probably all in his/her head...

There are plenty of threads on the Ableton forums addressing this, with employees of Ableton chiming in to apologize for the delay. It's a backlog, they admit it, nothing is "in my head".

Backlog in support, nothing to indicate its a backlog in returns. Feel free to show me otherwise, but I checked the Ableton forum and nothing specified it was due to returns.

I'm not going to impress you with links, especially since none of this is hard to find and you "didn't find it". You would attempt to downplay it anyway. You bought it, you don't need or want to think other people aren't happy with it, and you have spent a few threads defending it. These are our roles, I'm the critic, you're the loyalist.

You’re not impressing anyone because you’re just saying anything you feel you want to, and because it’s not based on facts, it doesn’t stop you from sharing it.

I haven’t been defending Ableton or Push. Not just here but on Elektron forum too where we’ve confirmed bugs, found missing parameters and looked for workarounds where possible.

See that’s the difference between bashing something endlessly and being critical. I can enjoy something while simultaneously be critical of its flaws. I am actively looking for the flaws because I want it to get better since I’m keeping this.

It serves me no purpose to shut things down for any reason you perceive, but if you haven’t noticed… you’ve been harping on the same thing for pages now. So yeah, we get what you don’t like about it. It gets old especially when there’s no argument that what isn’t there, actually isn’t there.

[machinesworking]

You’re not impressing anyone because you’re just saying anything you feel you want to, and because it’s not based on facts, it doesn’t stop you from sharing it.

I haven’t been defending Ableton or Push. Not just here but on Elektron forum too where we’ve confirmed bugs, found missing parameters and looked for workarounds where possible.

See that’s the difference between bashing something endlessly and being critical. I can enjoy something while simultaneously be critical of its flaws. I am actively looking for the flaws because I want it to get better since I’m keeping this.

It serves me no purpose to shut things down for any reason you perceive, but if you haven’t noticed… you’ve been harping on the same thing for pages now. So yeah, we get what you don’t like about it. It gets old especially when there’s no argument that what isn’t there, actually isn’t there.

Honestly, I don't care what you think. You came at me with ridiculous nonsense out of the blue when I first posted that Push 3 standalone cannot do more than one time signature that had me baffled because I had never known you to be rude or condescending. Then I find out you bought it, and are blithely defending it, yet needed to make some inane accusation at me instead of just saying you bought it and are comfortable with it's shortcomings.

There's a backlog of returns. That's not an arguable point, people are not able to get a reply on returning their units. I'm not sure how there being other support requests related mostly to bugs that slows the process down makes that better? Erm chimes in, I mention flashbacks to 8 and Tarekith agrees.
https://forum.ableton.com/viewtopic.php?t=247726

Again, I think Ableton will pull it all together but for the foreseeable future finishing compositions on standalone is really limited, and they have some bugs to iron out. What is the argument there?

Your take on this is just weird, I said one thing that got quoted and commented on

They obviously weren’t set up to handle the amount of returns they’re dealing with

That isn't a lie, doesn't matter if it's because of bugs in standalone, people being clueless, or people being unsatisfied with standalone and returning it, they are backlogged support wise and people are not able to get their returns processed.

[JamminFool]

someone on the internet is wrong.jpg

[pottering]

They obviously weren’t set up to handle the amount of returns they’re dealing with

Curious to know more about this - is there a news article or something? Couldn’t see anything in KVR.

Me too, I can't find any info on 'the amount of returns'. Probably all in his/her head...

There are plenty of threads on the Ableton forums addressing this, with employees of Ableton chiming in to apologize for the delay. It's a backlog, they admit it, nothing is "in my head".

Employees of Ableton chimed in to say support was "backed up with various requests", not "amount of returns".

[elxsound]

You’re not impressing anyone because you’re just saying anything you feel you want to, and because it’s not based on facts, it doesn’t stop you from sharing it.

I haven’t been defending Ableton or Push. Not just here but on Elektron forum too where we’ve confirmed bugs, found missing parameters and looked for workarounds where possible.

See that’s the difference between bashing something endlessly and being critical. I can enjoy something while simultaneously be critical of its flaws. I am actively looking for the flaws because I want it to get better since I’m keeping this.

It serves me no purpose to shut things down for any reason you perceive, but if you haven’t noticed… you’ve been harping on the same thing for pages now. So yeah, we get what you don’t like about it. It gets old especially when there’s no argument that what isn’t there, actually isn’t there.

Honestly, I don't care what you think. You came at me with ridiculous nonsense out of the blue when I first posted that Push 3 standalone cannot do more than one time signature that had me baffled because I had never known you to be rude or condescending. Then I find out you bought it, and are blithely defending it, yet needed to make some inane accusation at me instead of just saying you bought it and are comfortable with it's shortcomings.

There's a backlog of returns. That's not an arguable point, people are not able to get a reply on returning their units. I'm not sure how there being other support requests related mostly to bugs that slows the process down makes that better? Erm chimes in, I mention flashbacks to 8 and Tarekith agrees.
https://forum.ableton.com/viewtopic.php?t=247726

Again, I think Ableton will pull it all together but for the foreseeable future finishing compositions on standalone is really limited, and they have some bugs to iron out. What is the argument there?

Your take on this is just weird, I said one thing that got quoted and commented on

They obviously weren’t set up to handle the amount of returns they’re dealing with

That isn't a lie, doesn't matter if it's because of bugs in standalone, people being clueless, or people being unsatisfied with standalone and returning it, they are backlogged support wise and people are not able to get their returns processed.

I don’t even know where to begin with you. Your perception of things and the reality of it are not aligned.

I obviously can’t control how you interpret what you read in these post exchanges, but it’s exhausting needing to constantly provide defense for things that are not necessary in any shape or form.

If you want a different type of exchange, then try starting interacting differently. Have actual conversations about the subject and quit trying dismiss people as loyalists, which is really ironic to need to tell you since the thing that triggered you in the first place was because you felt I dismissed you just by saying you weren’t the only one. That was all it took if for you to be enraged and now apparently stuck on it too. But f**k that, on a planet with this many people we’re all unlikely to be the only one at anything, so not much get hung up on. If that’s dismissive too, then so be it.

Yes I own it. Yes I can use it as is and I’m happy about that, but it’s not perfect and I have no problem discussing failures, omissions, bugs or even speculating about things. I’m saying this on repeat already, hopefully, but I’m guessing pointlessly, as a way to move on from your baseless accusations because I can actually prove I’ve discussed the very things you say I won’t acknowledge. Not sure how many times I wrote that same similar thing.

Now, as for your comment… you clearly say “amount” which triggered a different question, one which you couldn’t possibly know and there is clearly nothing to substantiate any amount of returns anywhere online. That’s a fact.

The backlog in support is well established. There’s no argument there. It’s been said from support themselves.

And for anyone reading this popcorn inducing BS…

If this doesn’t settle up soon. I’m okay being done with the thread. There’s nothing to gain here in this thread despite being plenty to actually discuss. There are other places online where people can discuss Push 3 including shortcomings and if you’re interested check the Elektron boards. There’s 3 different threads, 1 for actual users, the original speculative one, and another comparing Push 2 to Push 3 controller version for people undecided about switching. It’s actually civil with none of the ego BS.

[elxsound]

someone on the internet is wrong.jpg

Unfortunately, this BS happens.

[liquidsound]

someone on the internet is wrong.jpg

Unfortunately, this BS happens.

It happened before (often). It’s beyond repair.

[drez]

They obviously weren’t set up to handle the amount of returns they’re dealing with

Curious to know more about this - is there a news article or something? Couldn’t see anything in KVR.

Me too, I can't find any info on 'the amount of returns'. Probably all in his/her head...

There are plenty of threads on the Ableton forums addressing this, with employees of Ableton chiming in to apologize for the delay. It's a backlog, they admit it, nothing is "in my head".

Employees of Ableton chimed in to say support was "backed up with various requests", not "amount of returns".

Yeah, I searched through there as well and came up with the same conclusion @pottering . The only repeating theme I saw was the same resequenced guy posting about his return in threads that had nothing to do with returns Troll.

There are others that talk about wanting to return it, but it's a handful. It seemed like the majority of frustration was not understanding that not all that could be done with Push in controller mode could be done yet on Push standalone via the Push Standalone UI, but that you could do it in a project within the desktop Ableton Live, move it to Push standalone and those functions do work. Or how to get CV to work...or how to get Audio Interfacing to work. The amount of people that couldn't grasp those concepts would appear to be swamping the support staff, and I can see why. This is the first Push that has the new I/O capabilities and that's been a lot of support needs. Plus, for sure, there's been bugs, but support has two public beta's out in the first month, so that's promising to get them knocked out pretty quickly.

The good news is that, since those features of a project that work on desktop and still work when the project gets moved to Push Standalone with no UI mean the feature is actually implemented, there's just no UI built out around those functions yet, such as follow actions, selecting side chain I/O's on M4L plugins and various included native devices, clip launch settings, etc. Those things work, Ableton just needs to sort out the UI work to be able to do it natively on the Push standalone itself. That's encouraging, to me.

[elxsound]

They obviously weren’t set up to handle the amount of returns they’re dealing with

Curious to know more about this - is there a news article or something? Couldn’t see anything in KVR.

Me too, I can't find any info on 'the amount of returns'. Probably all in his/her head...

There are plenty of threads on the Ableton forums addressing this, with employees of Ableton chiming in to apologize for the delay. It's a backlog, they admit it, nothing is "in my head".

Employees of Ableton chimed in to say support was "backed up with various requests", not "amount of returns".

Yeah, I searched through there as well and came up with the same conclusion @pottering . The only repeating theme I saw was the same resequenced guy posting about his return in threads that had nothing to do with returns Troll.

There are others that talk about wanting to return it, but it's a handful. It seemed like the majority of frustration was not understanding that not all that could be done with Push in controller mode could be done yet on Push standalone via the Push Standalone UI, but that you could do it in a project within the desktop Ableton Live, move it to Push standalone and those functions do work. Or how to get CV to work...or how to get Audio Interfacing to work. The amount of people that couldn't grasp those concepts would appear to be swamping the support staff, and I can see why. This is the first Push that has the new I/O capabilities and that's been a lot of support needs. Plus, for sure, there's been bugs, but support has two public beta's out in the first month, so that's promising to get them knocked out pretty quickly.

The good news is that, since those features of a project that work on desktop and still work when the project gets moved to Push Standalone with no UI mean the feature is actually implemented, there's just no UI built out around those functions yet, such as follow actions, selecting side chain I/O's on M4L plugins and various included native devices. Those things work, Ableton just needs to sort out the UI work to be able to do it natively on the Push standalone itself. That's encouraging, to me.

One thing we found that didn’t move over (yet) to Push after transferring was with the Drum Racks, setting it to “receive all” in the Drum Racks I/O. This allows for using it with external instruments. If you enable this in Live, then transfer it, the feature disappears.

The workaround is just sending midi from the Drum Rack track, to another midi track with the external instrument.

I’m sure there’s more like this, and I’m hoping to find them and report them.

[drez]

One thing we found that didn’t move over (yet) to Push after transferring was with the Drum Racks, setting it to “receive all” in the Drum Racks I/O. This allows for using it with external instruments. If you enable this in Live, then transfer it, the feature disappears.

The workaround is just sending midi from the Drum Rack track, to another midi track with the external instrument.

I’m sure there’s more like this, and I’m hoping to find them and report them.

Ah yeah, I did see that. But that definitely seems like a bug in that it disappeared. My guess is that they fix the bug and then add the UI element later.

[elxsound]

One thing we found that didn’t move over (yet) to Push after transferring was with the Drum Racks, setting it to “receive all” in the Drum Racks I/O. This allows for using it with external instruments. If you enable this in Live, then transfer it, the feature disappears.

The workaround is just sending midi from the Drum Rack track, to another midi track with the external instrument.

I’m sure there’s more like this, and I’m hoping to find them and report them.

Ah yeah, I did see that. But that definitely seems like a bug in that it disappeared. My guess is that they fix the bug and then add the UI element later.

I’m hoping, but I am a bit worried that it might not appear for a while. I’m thinking along the lines that it’s not there because the routing might have caused other problems, but I guess nothing else to do but wait. At least there’s the workaround, so it’s still flexible.