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?
P.S. Is there any news on when we can expect official support for Max 6 in Live.