5.1.0 – timepoint behavior changed/bugged

Dec 2, 2009 at 1:41pm

5.1.0 – timepoint behavior changed/bugged

Using Max/MSP v.5.1.0, timepoint behavior has changed or is bugged.

It seems that a newly specified time will not become active until either the transport is stopped and started several times, or until the transport runs long enough to fire a previously specified time.

In 5.0.7, a newly specified time takes effect immediately.

Below is a patch to demonstrate.

Many thanks,
Jim C

– Pasted Max Patch, click to expand. –
Dec 2, 2009 at 3:05pm

Hi – Thanks for the patch, We’ll definitely take a look at it.



Dec 2, 2009 at 3:25pm

Confirmed on 5.1.0 on Mac.

Dec 4, 2009 at 9:00am

Yikes! I’ve gone a little timepoint crazy in some of my recent patches, which i have not yet opened in 5.1

Is there a workaround? Can you rapid fire a bunch of silent timepoints to wiggle the handle?


You must be logged in to reply to this topic.