jcroson@earthlink.net

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.

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

5-1-0-timepoint-behavior-changedbugged

Hi - Thanks for the patch, We'll definitely take a look at it.

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?

5.1.0 - timepoint behavior changed/bugged