Jason Priebe

I'm working on a M4L device that uses live.step. I have intermittent problems with live.step.

Sometimes when you add the device to a track and press "play", the live.step doesn't start advancing.

Sometimes it will self-correct after 8-10 bars. Other times, it never seems to self-correct. I have found that if I manually toggle the track activator (basically, mute the track, and unmute it), the live.step starts working.

I know this isn't a lot to go on, but maybe somebody else has seen these issues and has some workaround ideas? I'm using Live 11 on an M1 MBP, if that matters.

Maybe I'm not driving the live.step properly? I'm using metro and transport like I've seen in examples online. Or maybe I need to initialize it with a special message?

I'm working on a M4L device that uses live.step.  I have intermittent problems with live.step.

Sometimes when you add the device to a track and press "play", the live.step doesn't start advancing.

Sometimes it will self-correct after 8-10 bars.  Other times, it never seems to self-correct.  I have found that if I manually toggle the track activator (basically, mute the track, and unmute it), the live.step starts working.

I know this isn't a lot to go on, but maybe somebody else has seen these issues and has some workaround ideas?  I'm using Live 11 on an M1 MBP, if that matters.

Maybe I'm not driving the live.step properly?  I'm using metro and transport like I've seen in examples online.  Or maybe I need to initialize it with a special message?

I'm working on a M4L device that uses live.step.  I have intermittent problems with live.step.
Sometimes when you add the device to a track 

Buggy behavior from live.step