Ablteon Push 2 & Max


    Jan 04 2016 | 5:48 pm
    Hi! Today I went to a shop and wanted to finally take a look at the ableton Push. I was thinking about buying it for a long time, but actually to use it with max/Msx4Live only. I wanted to get rid of all default behavior inside ableton and just use it for my stuff, controll it via max. This seemed kind of possible from what I read about it, although there doesn't seem to be a nice 'programmers reference' as there is for the Launchpad.
    Today I learned there is the Push 2. Does anybody have any experience with it+Max? Can we write anything we want to the awesome new display? I guess it's more difficult now, because of the high resolution.. Can we deactivate the default behavior and controll it just via Max4Live?
    Thanks a lot! Cheers!

    • Jan 04 2016 | 5:57 pm
      Yes, and yes, with a few caveats. I use my Push with M4L, although I still use some of the default behavior, as I use Live for a lot of stuff other. As far as using it with Max alone, it's just like any other MIDI controller. All the buttons/switches/encoders send standard MIDI messages, and the display can be controlled via Sysex. Within Live, you can use M4L to overide the default behavior of all the controls, or any individual controls, and use the Live API to observe controls, and make changes to the device. There is also a 'User' mode, which turns it into a standard MIDI controller, and the same communication options are available to you (except the display, because Live doesn't do Sysex). A lot of the information is lying around the internet for you, so you don't have to totally start from scratch.
      Most of this holds true for the Push 2 as well, except everything about the display. The display isn't done with MIDI, Ableton have a separate application that handles rendering to the display. An intrepid developer has recently release an external that can render jitter matrices to the screen though, so its all good :) (google P2D). I've had good success using it within Max, but have had serious framerate issues when using it with M4L.
      I love using the Push to perform, and program audio processes that are integrated tightly with the device. It's pretty versatile once you get the hang of programming for it.
    • Jan 05 2016 | 2:19 pm
      @Evan : can you develop about the framerate using M4L devices within live ?
    • Jan 05 2016 | 3:34 pm
      I am referring to the fact that the framerate on the display is about 2 fps. I have been meaning to send an email to the developer to see if he has any advice. The device he provides has a much smoother framerate, so there must be some extra processes that need to be done in M4L to get things running smoothly.
      (I hope I understood your question).
    • Jan 05 2016 | 11:36 pm
      Thanks a lot for your response EVAN! I was pretty sure to hear problems about the new display and am very surprised that somebody already came up with a method of controlling it! Good to hear!
    • Jan 06 2016 | 12:02 am
      Looking at this (p2d) more closely, I'm a bit afraid that the whole screen seems a bit hack-ish, and if one encounters problems, it's closed source I guess..?
    • Jan 06 2016 | 5:21 am
      Yeah it does seem closed to me, its paid as well. Even some js files with the demo device are unformatted making them practically unreadable. I was hoping it would be a relatively smooth solution, but it still seems a ways off.
    • May 23 2016 | 7:42 pm
      Sorry to post it here but i was wondering i read the in and out of the post and tried to apply it or at least get a sense of what to do in my project. Thing is i can't find the sysex value in the k1m manual. They doesnt seems to exist :( http://www.kawaius-tsd.com/OM/K_SYNTH/K1_Synth.pdf
      I've found some infos on the tg33 manual tho so i may just start here Anyone know if there are some tutorials on sending sysex in max or m4l ? i googled without success http://www.synthzone.com/midi/yamaha/tg33/TG33E_2.pdf
      I know i'll probably have to convert some number but still can't find something close. So here i am
    • Jun 11 2016 | 5:09 pm
      Hi, wish you'd got in touch about the frame rate issue as I'd have been more than happy to help out...
      That release was fixed at 10fps in M4L due it causing audio dropouts under some circumstances... This has now been removed for the upcoming updates, as has the full screen requirement
    • Jun 12 2016 | 5:42 pm