Yeah, I got a discount code too… Just when I settled and decided to keep using Push 2, now I’m reconsidering it…
€1900 vs €1520 is a significant difference…
But, I still don’t know: does it sync well to an external clock with the latest beta?
How well does it send midi to external devices? How much jitter is there?
I’m wary of these things, because regular DAWs are not the best in these things, and since this is actually a computer with a DAW inside (although without the Windows shell around it), I’m afraid it might suffer from the same issues as a regular computer with a DAW…
Also, I guess the external instrument device works exactly the same as in the DAW, with hardware latency compensation etc?
That’s what… No I think it’s kind of proportionate to what you get. Look at a Linnstrument. Look at a DAW controller. Mash ’em together, and I argue you have something roughly the size of a Push.
The way the sample navigation works now is that it remembers where you were last when you press the hot swap button. You can tap different pads while that is open so if you wanted another snare you could tap the existing snare, hit hot swap, hit another pad, pick the snare for that pad, then close hot swap for example.
Everyone I’ve heard says they were much better at the start, perfectly consistent feel, and thats been my experience too. I think I’ve seen one person recently who says theirs have got worse over time, but I wont place weight on that unless others start to see it too.
Mine feel fine. They’re not great for super precise adjustments - the dead zone is surprisingly large when turning them slowly - but there aren’t any physical problems.
There is a program changer m4l device with controls mapped to Push, so maybe that works?
Thanks for this link, this device works. But I’m having a little difficulty automating the program change parameter. Ableton will allow me to change a parameter while the note is active, but it reverts to the device’s default value as soon as the note is off.
Creating a note that extends for the entire duration of the clip doesn’t work either, it changes back to the default value for just a split second at the end of the clip’s loop.
Anyone have ideas on how to automate a device parameter value in a way that sticks?
UPDATE: I decided to use clip settings to send the program changes and it’s working. I don’t like the idea of having to bounce them to desktop to configure each pattern change during the composition process so I just set up a series of 16 scenes that I can trigger at will.
This may end up opening up the workflow that I’ve been after.