I working with [transport] deeply for the first time.

I'm dealing with a complex patch with several named [transport] that never restart in sync.

I can't understand why they don't stay in sync when stopped and restarted.

And finally I wonder if is it a good idea to have multiple named [transport] to drive the patcher events …

Some explanation about [transport] would be appreciated.

I working with [transport] deeply for the first time.
I'm dealing with a complex patch with several named [transport] that never restart in sync.
I can't understand why they don't stay in sync when stopped and restarted.
And finally I wonder if is it a good idea to have multiple named [transport] to drive the patcher events …

Some explanation about [transport] would be appreciated.
Below a simple patch.


transport-metro-sync

having said that, I much prefer to have a central Transport, and then subdivide the ticks down as needed around the patch. That way, you're not only getting "bangs" at the right time, you're getting the actual position in the piece/performance.

Thanks for the tip. I haven't found much examples about [transport], and with the increasing complexity of Max I hope the V7 has a good documentation …

Thanks for the tip. I haven't found much examples about [transport], and with the increasing complexity of Max I hope the V7 has a good documentation …
Thanks again Wetterberg.


You might find some useful information in examples 42-48 here:

http://music.arts.uci.edu/dobrian/IAP2010/examples.htm#Ex42

http://music.arts.uci.edu/dobrian/IAP2012/examples.htm#Ex11

http://music.arts.uci.edu/dobrian/Music215/S13/examples.htm#Ex25

You might find some useful information in examples 42-48 here:http://music.arts.uci.edu/dobrian/IAP2010/examples.htm#Ex42

http://music.arts.uci.edu/dobrian/Music215/S13/examples.htm#Ex25


@wetterberg In your example 99% of the metro bangs are suppressed by the [change] object, so you're causing Max to do a ton of unnecessary work. How about this? 

[transport] & [metro] sync