M4L Device Transport issues
So I made this synth device that's basically a cv sequencer combined w a macro oscillator (Mutable Instruments Braids/Plaits). So far everything works great but lately, I've run into this strange issue since updating to the new Ableton/Max for Live version.
When you first load the device. Ableton CPU jumps to 400% and the playback on the sequencer goes wacky. Now if you adjust your tempo in Ableton the device starts behaving correctly and all is well.
I'm completely mystified. Any help would be greatly appreciated :)
How is your sequencer clocking and how is it listening for Live transport? I also make custom sequencers and have found that triggering off the plugsync~ object is the best way to go, in case you are not already doing that.
Ahh no, Im actually using a metro + transport combo for clocking. Will give that a shot!
Switched over to plugsync but still having the same issue. EDIT: the issue is coming from a snapshot~ object. Marking as resolved for now. Thank!
Snapshot is expensive if you poll fast and have lots of them!
To be clear, there is nothing wrong with clocking off the global transport - in Max for live this is locked in with Live's transport. The issue plugsync solves is that at the very beginning you get a lag for that first clock hit if you are listening via the API or some other possibilities, but with plugsync you get the starting gun at the right time. I have stuff locked in great with live by clocking in Scheme for Max off the global transport and using plugsync to kick things off.