Forums > MaxMSP

problems with groove~ and named transport

February 15, 2010 | 10:29 pm

Hello,

I have a problem when using a named transport with groove (@transport attribute) :
groove doesn’t seem to recognize it, but keeps being refered to the global transport: doesn’t apply tempo changes others than in global transport, nor timesig specifications.
Moreover, it seems like the beginning of the buffer is addressed at 0 0 0 (instead of 1 1 0). I think it’s the same with record~ though I didn’t verify all the features (ticks vs bbu)
strange behaviour too when passing in the inspector from bbu to ticks and vice versa…
Does somebody know something about that ?

thank you

A

a test patch:

– Pasted Max Patch, click to expand. –

May 9, 2010 | 1:32 am

Did you ever figure this out?


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