Max 6 & Max4live Transport Issue


    Jul 17 2012 | 8:39 pm
    Hi All,
    I recently switched from using Max 5 to Max 6 with Max4live. I know that Max 6 isn't officially supported by Live yet, but I've stumbled across a potential bug in the way that Max 6 observes Live's transport.
    I'm a big fan of the Max4Live Api devices (CtrlEnvelope, CtrlGridSeq) and I've noticed that these are not reset correctly when I stop and restart my sequence. When using Max 5 'CtrlGridSeq' is reset to step 1 whenever transport is stopped, whereas with Max 6 it simply stops and restarts from it's current position.
    I haven't investigated the issue in any depth, so I'm not sure whether this is a bug (with the 'transport' object?) or some change in Max 6 which renders the current API devices incompatible.
    Has anyone else experienced this?
    Many thanks
    P.S. Is there any news on when we can expect official support for Max 6 in Live.

    • Jul 17 2012 | 10:00 pm
      Max6 is fully supported as the Max for Live editor for all full Max 6 license holders.
      Looks like the transport object is not reporting stop/start state correctly. We'll investigate this.
      Thanks for the report and sorry for the inconvenience.
      In the meantime , you could use the first outlet of the plugsync~ object in place of the transport object in that patch to do the same thing
      Cheers
      Andrew
    • Jul 18 2012 | 12:54 am
      I appreciate the clarification regarding Max 6 support (something I read (or misread) on Ableton's site led me to believe otherwise).
      Thanks for looking into the transport issue. I'll use plugsync~ for the time being.
      cheers Andrew.