Erez Blumestock

At first I was sure that it was problem with my patching, but then I discovered that it's just a problem with triggering samples in Max.

I upload a patch to compare between an internal loop inside groove~ to a loop triggered by metro, and notice how jumpy is the metro loop.

Maybe it is some basic thing that I should have known about controlling MSP samples with Max Messages, but I am pretty sure that I was doing this quite a lot in Max 6 and it was never that unstable.

It sounds the same by the way when I'm using Index~ with Count~ instead.

Please let me know if you notice the problem a well, and if you know why it's like that and what is a better way to synchronise samples together.

* I didn't update 7.05 to 7.06 yet if it matters.

metro-triggers-groove-is-unstable-from-some-reason

Metro (or any Max object) will never be "in time". You may get varying degrees of acceptability, and it's possible that your vector settings are different currently, but if you want it to be consistent it has to be locked to a signal clock (phasor~/groove~/play~/index~ etc...).

A very common way to do this is to have a single phasor~ driving multiple playback objects (play~), and all "transport" (stop/play) is handled with the phasor~.

Is timing acceptable for you with Scheduler in Overdrive & in Audio Interrupt?

Thank you Jean-Francois, I am always aware to overdrive, but I didn't know about Audio Interrupt and now it's flawless.

triggering Groove~ with metro is unstable