Push 3 Users Thread

Looks like it uses Mackie Control so a no go for now

I’ve had this happen before. I’m 99% sure I was doing something wrong in the cases this happened, but it could actually be a bug. I don’t remember which.

Figured I’d post this here. This is from Jesse at Ableton (don’t remember exactly his title - a community manager, maybe?). Context: people unhappy/ uncertain about the development of Push 3 Standalone on the Centercode beta forums:

Hi,
I’m sorry to hear the sentiment on this thread. The challenge to giving a roadmap is managing expectations - I could tell you today what I think is coming next, and we could find out that is not true, and it takes longer. Dates are a constantly shifting negotiation for updates and betas. What is one user’s top feature is not the same for the many different user types who own Push. Traditionally we don’t publicly speak about roadmaps as you never know how long certain features will take to make. I want to rethink this though.

I can say we have a relatively large team working on Push, who have had to focus on stability, features and technical debt after release, as well as support for Live 12. We always have to balance supporting new Live features as well as features Push doesn’t have yet, along with technical work that is unseen. The team is now deep into a feature rich update. Let me think a bit about what I can and can’t communicate, I could easily tell you the themes, but I think you are looking for specifics and I get it.

16 Likes

I have this bug all the time. Already reported it to Ableton. Please, if you have bugs, report them. The more data they have the easier it is to fix!

3 Likes

Glad to hear it’s not just me. I absolutely do report them! I hope others are doing the same.

I totally report my bugs, and send off crash reports—which is super easy to do with Ableton.

This is great to hear. I love new features, but I love not ever losing work even more.

2 Likes

Thank you for posting this message from Ableton. I have come back to Push 3S after a somewhat brief hiatus and, after updating it to Live 12, I am having very weird issues that have made me question its reliability.

Often, projects that I have started on P3 will not load properly, one day to the next, even though I always save my work. On start up I will see an error message and be asked if I would like to recover my work.

Projects often take a VERY long time to load. These projects are very simple – less than 5 tracks.

I will often see the “Live is showing a dialogue that needs your attention prompt.” While in Standalone mode. :woman_facepalming:

My future is with Push 3S, but I hope they can nail things down while improving the device.

1 Like

If you own/played both Push 3 and Launchpad Pro Mk3, how different is their touch sensitivity(in note mode) ? Thanks!

I do own both. I always preferred the Launchpad Pro over the Push 2. It was way way more sensitive and pleasant to use.

But now I prefer the Push 3. The sensitivity is perfect for me, plus there’s the MPE. The Launchpad is almost as good. If you weren’t testing them side-by-side you probably wouldn’t notice the difference.

1 Like

I think Jesse replies to the post I did at the Ableton Beta forum yesterday about the post he wrote in the Push 3 Standalone owner group on Facebook . It’s good news that he is willing to rethink the ‘not speaking about roadmaps.’ We really need this.

btw…Jesse Terry is a product owner of Ableton, co-creator of the Push

6 Likes

I desperately want a roadmap, but they are a trap for manufacturers/instrument makers.

I would much rather they get things done than tell us something, maybe, is possibly on the way at some point, using vague themes.

Just do it, Ableton! :muscle:

4 Likes

I’m having the same bug! I tried with both Meld and Wavetable and there was no way of adding to the matrix.

I just submitted a report.

I tryd both in control and standalone mode. Sometimes it is working and sometimes not. Thats really fucked up behavior. What if i want to do a Liveset tomorrow evening or so? I hope they will find a solution for that fast.

1 Like

I got a response, that confirmed, that it is in deed a bug, they can reproduce it, and added it to the list of issues they have to work on.

7 Likes

Thank you for confirming - I’m still on Push3SA 2.0 / Ableton live suite 12.0.1 / FW 1.4.0.

I have the notification “an update to push 2.0.2 is available” - but I’m going to hold off on it. Just feels like a lot of new issues were introduced without nothing being fixed - do people agree that it’s sensible for me to hold off on this update?

Sorry a separate question from me:

Renaming/deleting sets.

When scrolling my set library (in SA mode), if I bump the jog wheel to the right on any of them, I don’t get the “Delete/Rename” dialog box. Nothing happens.
Accordingly I can’t delete or rename anything within push, and have to do this via the laptop.

Question: does the “jog wheel to the right” to rename/delete sets work for anyone else?

Question 2: are there any other functions for “jog wheel to the right” that I can test, to make sure that “jog to the right” part of my jog wheel isn’t faulty?
The jog wheel works perfectly for me for everything else, except this

Is there a better way of mapping plugin controls to Push 3? Let me explain what I am trying to do. I was hoping to use P3 to program a Toraiz AS-1 as the built-in AS-1 UI is less than ideal. I purchased the CodeKnobs AS-1 editor and used the Configure option in the Ableton device title bar to add all the parameters in the editor. These do show up on Push in pages listed as Bank 1, Bank 2 etc. Is it possible to rename these. For example “oscillators”, “filter” etc.? As it stands, it is worse than using the AS-1 interface itself! Also, less than ideal is the fact that oscillator pitch shows the note value in Ableton, but 0-1.0 on Push. Toggle buttons are worse - on/off in Ableton, continuously variable from 0 to 1.0 on Push. Maybe this is only possible by writing a custom M4L patch?

Has anyone tried one of these covers for the Push 3 from ebay?

Considering buying one because the decksaver doesn’t suit the stand I am using.

Haven’t seen those covers yet, bought the Decksaver version.

Which stand are you using if I may ask.

1 Like

So I haven’t made it out to one of the stores yet to pick one up and try this, but IKEA recently came out with something that looks like it would be an unexpectedly great fit for the Push.

In a coincidence that’s up there with IKEA’s 19” rack bedside table, this 15.25” x13.5" lid is almost a perfect fit for the Push 3 dimensions of 14.96” x 12.52”, although I’m not sure yet how it will work with the cables in back. In any case, it’s a bit cheaper than a Decksaver, at… $1.

4 Likes