bugs I experienced in the course of using the machine for maybe 2-3 hours. May be worth saying but I test software (and more recently some hardware) for a living and am likely pickier than users here. I also work fairly fast on my devices, or aspire to.
Yeah but it´s mostly german. maybe you find some english stuff. first link is older and english
2 Likes
Have you updated to recent firmware? Looks like a bug in the video.
How would you like the synth parameters to be displayed? They are labelled the same as the parameters on pretty much any Synthesizer out there as far as I can tell.
I can understand the thing about sample import but it also transfer from computer over wifi which most other devices do not
Certainly the good news is that it includes Compute Element devices, which is what the Push uses. Currently they only go on about the 13th gen one in their glossy marketing material online, which is newer than the one in the Push, so we will still have to wait and see whether Ableton support this in future.
1 Like
Not on the beta but on the latest public release. I was hoping the synth parameters were exposed more similarly to eq8 etc, with a gui (even if modified). Right now its just many menus long with a value. The first page is what Ableton has chosen as the most used which is not intuitive to me all of the time but I’m new to push (after returning push2 when I first got Ableton because it was too much to learn at once)
I like the Collision synth so I’ll use that as my example. In Ableton theres a GUI showing you “Decay” and “Material” as a ball with an X/Y axis on the object you’ve chosen for resonance, that is missing from the Push although the screen real estate implies (to me) it would be there. Possibly nitpicking but you cannot read the LFO destinations because they are cut off - R1 Pipe Opening becomes “R1 P Op”. On Ableton you always know the ON/OFF status of Mallet, Noise, Resonator1, Resonator2, and the two LFOs. On the push you must menu dive to see each of these individually.
I understand some of this is maybe asking a lot, but in standalone I found myself wanting a better gui a lot of the time. As a controller I am sure this thing is fine but as a completely unhooked device where you never look at the originally designed GUI I find myself lost a lot even with a decent level of familiarity with the device I’m working with
edit re new firmware- after updating and coming back after a couple days things do feel smoother and i am understanding the appeal a little bit. cant completely untether you but it can get you started~
3 Likes
I think this is fairly realistic and reflects many of my thoughts along the way. I prefer it to any other ’standalone almost-Daw’ by a mile, though! 
2 Likes
Hey Earthangel,
where are your studio monitors connected to: Push or 18i20?
cheers
Ron
Can you elaborate a bit on this? By spectral you mean for example eq 8? Where do can I see “the added plugin frequency” in Push or Ableton Live?
I am using only 8 channels but I do have some instrument and effect racks on my master template so I wonder if that is what it’s adding all the noticeable latency.
It seems that Machine plus when would hit a cpu limit, you would hear it on the sound - crackles. The P3S seems to first makes everything slower in the UI, and then note input/ knob twisting latency, before it crackles. I don’t even remember on being able to push my p3 cpu to a point where it starts to affect the sound, which is great. The note input/knob twisting latency on the other hand is quite annoying, specially because it is not consistent. You start with a blank project with a certain buffer setting and its great, and then when you create a - what I consider to be - fairly simple project it adds that latency that you have no muscle memory of. This is specially noticeable when playing drums on the pads, not noticeable when twisting knobs.
It would be good if that could be optimised. It makes sense too, once you choose your buffer and latency settings to have that consistent throughout the project. Otherwise it does really feel like computer controller and not really an instrument.
Sometimes I feel that I have a different push from a lot of people here 
The experience that I have with Max for live is that most of the stuff that I try does not work in a way that can understand what it is doing, if working at all. I get very often the missing object message, and I just try to avoid M4L stuff now. I am guessing that what makes my experience difference from a lot of users here is that I have almost no experience with M4L, so I don’t know what instruments/fx do what. Im guessing that if you already have some experience you can make them work/understand what they are doing?
When I bought my push I only had the Ableton Live intro in it, and I upgraded later to the Suite version. Even though I think the suite version is great, I feel that it adds a lot of clutter to the Browser of push 3. When the intro version you go to the browser, select an instrument or fx and 99% works with P3. With the suite version there is a steep learning curve, because you need to understand what works and what doesn’t. I think what will help is using it simultaneously with the software version, but I haven’t had the patience to do that just yet.
What I do for now is avoiding all the stuff that might not work - aka max for live - and use the Ableton instruments/fx/midi fx. I’ve read that there is a lot more stuff that some instruments can do in the software version, but if you are not used to using them like that, you don’t miss those extra features as much, most of the times.
I love my p3 but on my 3rd month with it, what I can say is that I am still overwhelmed :).
Spectral effects. They have spectral in the plugin name. Not the eq.
You can see plugin latency when hovering over an effect/instrument or audio effect/instrument rack’s name.
2 Likes
Not every M4L plugin will work on push. Despite what has been said here a few times. Controls need to be made available on push by the m4L device’s developer for starters. Ableton has said that M4L will become more integrated down the road but for now only a select few devices work fully and have all controls available. If you’re unfamiliar with M4L and its capabilities I’d suggest focusing on the stock plug-ins first as that is already a huge amount of stuff that is available and powerful. There’s a dedicated topic in this forum where people list M4L devices that currently work.
Regarding UI sluggishness, you must be adding a lot of heavy audio effects racks or complex instrument racks for that to happen?. 
. Haven’t encountered any of that so far and I’m running push 3 at a buffer of 32 currently. Feels responsive as any device should. But again, I’m not really stress testing it nor am I trying a lot of diffeeent M4L devices yet as most simply don’t work fully yet :).
Maybe start a clean project and just start creating your own effect chains with intention :).
3 Likes
This is gold. I opened up a project and I had 6,48 of added latency of all plugins. Interestingly enough the fx I thought where heavier didn’t had any latency.
The plugins that added more latency where:
1 limiter - 2.7 ms (!!!)
1 compressor - 1 ms
colision- 1.3 ms
Thanx for this
2 Likes
Limiter due to look ‘look ahead’. This way it can catch all peaks (brick wall).
The spectral time plugin adds 120ms of plugin latency for example in ultra mode. Which is really a lot and unfortunately (though logical). I’m still contemplating if I’ll take that hit and leave live pad playing alone except for arpeggios. Or to leave that plugin alone. The effect is so cool though.
My monitors are connected to the 18i20.
Broadly speaking, my routing works like this:
Hardware stereo out -> 18i20 -> ADAT channels 9/10, 11/12, etc -> Push -> ADAT 9/10 -> 18i20 analog out -> Monitors.
I also have a hardware FX send / return loop that uses the Push analog i/o.
The Push is essentially being used as a mixer.
Is it possible to create macros for my fave vsts that normally wouldn’t work with push so I can get control of a few parameters?
If your tracks - I had 9 tracks running, and you want to Sidechain, selecting the input track while it’s playing will also cause it to lag. Yeah, annoying for a 2k machine.
Only for Push controller NOT when its in standalone, Have your plugin on a Ableton track, in the device title bar select configure, then select the parameter you want by moving it with mouse, once done, then select configure to turn it off, then you can save it as default state for that plugin, you can after that Instrument/Effect rack it, and setup macros as normal & save it.
1 Like
So how do I go about making the Push usable in User Mode? So far I only got to it doing a limited number of things, with the entire pad surface remaining dim.
I was hoping to build out a surface for the Syntakt and see how far I can make it behave like a Rytm. Mute pads, play pads, selecting different “tabs” for each machine so the encoders behave differently. Performance macro pads (e.g. open up the filter as I pressure a pad, etc)
Where do I start?
By arpeggios you mean using the “repeat” function? That is also an option that I have been using sometimes, also in drums. It’s great for fills and had variation to a pattern but also to play sequences, and it’s much easier to time it right, specially if the system has considerable latency.
I also had a mid/side mastering fx rack that was adding a lot of latency. For now I managed to do a base template with all my mappings and zero latency added. There are so many fx and options that one can easily skip the plugins that add latency and still have a very, very powerful machine with tons of options. It would just be good to have an easier way to figure out what adds latency.