Forums > MaxMSP

timepoint rewire problem…

March 24, 2009 | 5:47 pm

I am experiencing a problem with timepoint and rewire.
I have a global transport that is synced to rewire. I have
two time points, one at timepoint 0, the other at timepoint 4000.

When ever I start my rewire app (Sonar), time point 0 never
triggers. Timepoint 4000 seems to always work. Any idea what the
problem might be?

– Pasted Max Patch, click to expand. –

March 25, 2009 | 3:02 pm

When Sonar starts, it looks like there is a slight delay
before Max starts the global transport. Instead of staring
at 0, it starts at 10 ticks.


March 27, 2009 | 1:41 am

Okay, I am still having problems with timepoints triggering
when using rewire. The following patch demonstrates things better…

It has 8 timepoints, all should trigger on the beat. The
first one at 0 ticks does not fire. I assume it is because
there is a delay from where Sonar starts and then Max.
Ticks 480, 960 fire, but 1440, 1920, 2400, 2880, and 3360
do not. All of these should definitely be firing. Have I discovered a bug here?

– Pasted Max Patch, click to expand. –

March 27, 2009 | 2:54 pm

Can someone please give this a try…


March 28, 2009 | 3:29 pm

*bump*

Can someone please give this a try…


March 28, 2009 | 5:47 pm

I can confirm, only mine is slightly different.

When using rewire and Logic 8.0.2 I’m only getting timepoints to fire at 0, 960 and 1920.

I modified the patch slightly for testing. Nothing exciting but you may want to use it.

– Pasted Max Patch, click to expand. –

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