Forums > MaxMSP

why does this make the transport stop?

November 29, 2010 | 6:09 am


The objective of this patch is to have a metronome playing certain random rhythms in time, 16n, 8n, 32n, etc, and these rhythms are being allowed to pass only when a gate object lets them pass.

But for some reason I can’t figure out, when i start the transport it stops after awhile. Just curious if anyone has an idea as to why this is happening. Thank you in advance for any possible input.

… Nick

– Pasted Max Patch, click to expand. –

November 29, 2010 | 7:33 am

Hello nicnut,

it seems when setting the third [metro] with speed higher than 64n, it stops the second [metro] ; (on my macbook os X.4.11, max 5.1.6).

maybe it’s a bug ?

– Pasted Max Patch, click to expand. –

November 29, 2010 | 9:46 am

Actually if you look at the notevalues syntax, you’ll see that 64nt is not valid, so it’s converted to 0 ms. Which is probably something that you’d like to avoid ;-)

November 29, 2010 | 4:01 pm

wow, awesome. thank you for your reply Emmanuel, that fixed it.

… nick

November 29, 2010 | 4:48 pm

Hello Emmanuel Jourdan,

"… converted to 0 ms."

I am surprised that [metro] do that instead of ignoring bad values or just clipping them ; but i understand now why it freezed max after connected a [print] to the [metro] outlet ; only way was to kill max from the terminal ;-)

Viewing 5 posts - 1 through 5 (of 5 total)