Forums > MaxMSP

problems with a metro: order of @autostart vs. @transport

Dec 02 2008 | 8:23 am

I was having some difficulty getting an abstraction for Max 5’s ITM metro features to work correctly, due to some constraints on the order of the @autostart and @transport attributes. This patch should explain everything.

In the subpatcher, because of the default attribute values and some issues with the order of things coming out of [patcherargs], things didn’t "just work". I have a solution using [deferlow] to make the @autostart attribute get delayed slightly while the subpatcher initializes the other attributes. I found I have to do this with @autostartime too.

Is this a bug in [metro]? If not, I’d request that switching the @transport of a metro will maintain the current attribute values like @autostart and @autostarttime.

— Pasted Max Patch, click to expand. —
Dec 02 2008 | 2:55 pm

This is all fixed in 5.06, coming soon.


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

Forums > MaxMSP