Forums > MaxMSP

not using global transport?


seanzshow
Mar 23 2011 | 1:42 pm

Hi,

It seems like a pretty basic question but i’ve bin through the timing tutorials in max 5 and they all seem to involve syncing to the global transport. I cant find anything that tells me how to sync a phasor to a different named transport.

Sorry if its staring me in the face, its bin a long day! Any help would be great.

Cheers


Charles Baker
Mar 23 2011 | 3:51 pm

copied from the transport object’s documentation:
Attributes

Name Type Description
name symbol There can be multiple named transports running simultaneously. By default, a transport will be associated with Max’s global transport. If a name is provided then a new transport is created with that name and can be referenced using this attribute.

tempo float Sets the tempo in beats-per-minute for this transport.

this might help…
cfb aka j2k


Graham Dunne
Feb 04 2013 | 11:51 pm

Hi,
I’ve just encountered the same problem. The problem seems to be that unlike the metro object with the @name attribute, a phasor object can’t accept the @name attribute, thereby rendering syncing to a named transport impossible.

Just one of those things…

Viewing 3 posts - 1 through 3 (of 3 total)
Forums > MaxMSP