bug in timepoint?

Nov 15, 2011 at 9:30pm

bug in timepoint?

Please look at the posted patch.
I’m wondering if this is a bug in the timepoint object or if this is the expected behaviour.

(Posted to the Dev Forum because it directly concerns the development of my external).

– Pasted Max Patch, click to expand. –
Nov 15, 2011 at 10:24pm

I don’t know that I’d call it a bug. You’re essentially feeding its output back into its inlet in the same tick of the scheduler, trying to reset the value of the timepoint object to time Y in the same scheduler tick as it’s responding to a different point in time, time X. Just insert a “defer” object somewhere in that loopback between the outlet of timepoint and the inlet of the same timepoint, and it should work fine.

Nov 15, 2011 at 11:23pm

Thanks Christopher,

inserting a defer object indeed “fixes” it (at least in Overdrive mode).

I’m trying to understand how several things work in the ITM stuff of the SDK and this was a question that raised.
It will make it clearer.



You must be logged in to reply to this topic.