FIXED:TimerCHOP - goTo(seconds) disables parallel timers

pointshader · March 31, 2019, 6:35pm

Hi there,

If you provide a dat Spec to a TimerCHOP, the parallel timers work just fine. However, if you call the op(‘timer’).goTo(seconds=1) method, only the first timer will go to the correct time, all other parallel timers go to a time of zero with ‘ready’ enabled.

Side note - using the scrubbar in Greg’s timebase component calls this method, so the entire timeline breaks after the scrub bar is used, until the timer is reinitialized and started from 0.0.

Win10 Pro, 2019.12330 (Experimental)

pointshader · March 31, 2019, 6:47pm

On closer inspection, it looks like the Cue behavior in the CHOP interface is broken as well - only affects the first timer but not any parallel timers.

rob · April 1, 2019, 3:53pm

Thanks for the example.
We’ve confirmed, and are working on a fix.
-Rob

pointshader · April 2, 2019, 4:17am

Thanks for looking into this, Rob!

rob · April 2, 2019, 1:25pm

No problem.
The fix will be in builds 2019.13110+ and later.
Cheers.

pointshader · April 3, 2019, 9:48pm

Thanks! Do you have a rough ETA on a new experimental roll out?

ben · April 4, 2019, 2:04pm

Early next week at the latest.

pointshader · April 9, 2019, 9:25pm

Thank you so much! My project based on TimeBase now works in experimental 2019.13330.