Lost transport sync when editing M4L device

[devotional]

Spent some time this weekend on a sequencer device in M4L. It's been fine all the way up to a little while ago, when suddenly the transport is out of sync when I open the device for editing. Same thing happens to Mono Sequencer so it seems related to M4L. The transport sync seems to be a little delayed, but the tempo seems correct.

I have tried restarting everything, but no improvement.

My setup is in the signature. I upgraded M4L to 7.2.3 earlier this weekend, but it has been running fine for hours with that version, so something else must have happened. One thing I have noticed is that the Max editor window indicates "TRIAL NOT STARTED - SAVING DISABLED". Not sure if that has been there before, but maybe it indicates some kind of problem between Live and Max? I am opening the devices using the edit button on the device in Live.

Anyone got any ideas? Kind of frustrating not to be able to continue.

[devotional]

Hmm, so I rebooted my laptop and that seem to have removed the TRIAL NOT STARTED message and the sync is better again. It is almost good, but since I am now checking the sync more closely (recording my sequence to audio and comparing) I see that there is some 25 ms extra delay when device is open for edit. Is this normal?

I am using phasor~ @lock 1 with snapshot~ 1 to drive my sequencer.

[[jur]]

I think this is "normal". AFAIK, M4L always had some extra latency when in edit mode.

[S4racen]

I'd concur, timing is generally unreliable in edit mode...

Cheers
D

[devotional]

Thanks for feedback.

I am now using phasor~ with delta, < and edge instead and it feels a little more stable than the snapshot.

Metro didn't work for me, because it fired late too often to be useful for a sequencer - but I wondering if there is something I am doing wrong since it looks as though Mono Sequencer is using metro?

[jonbenderr]

[metro @interval X ticks @quantize X ticks @active 1]

This works wonderfully for me. X equals the tick values equal to the note division you want.

Here's a good thread from the cycling74 forums discussing usage of metro vs. phasor~..

https://cycling74.com/forums/topic/vari ... 5iOCRImuMl

[devotional]

Hey, that was an excellent link! I thought had googled around everywhere, but apparently not. Thanks!

I will dive back into metro and give it another chance.

[metro @interval X ticks @quantize X ticks @active 1]

This works wonderfully for me. X equals the tick values equal to the note division you want.

Here's a good thread from the cycling74 forums discussing usage of metro vs. phasor~..

https://cycling74.com/forums/topic/vari ... 5iOCRImuMl

[devotional]

Well, I was doing something wrong before, because now I got metro synced like a dream. I believe I am using better post-processing after metro now to calculate sequence position, using when as a basis.

Thanks again.

Hey, that was an excellent link! I thought had googled around everywhere, but apparently not. Thanks!

I will dive back into metro and give it another chance.

[metro @interval X ticks @quantize X ticks @active 1]

This works wonderfully for me. X equals the tick values equal to the note division you want.

Here's a good thread from the cycling74 forums discussing usage of metro vs. phasor~..

https://cycling74.com/forums/topic/vari ... 5iOCRImuMl

[jonbenderr]

No problem! Glad I could help at all. Rare occurrence.