Serial Segmented TimerCHOP gradually (and infinitely) increasing cook time when locked to timeline

Win11 TD2023.12120

  • Take the “segments - serial” TimerCHOP snippet from OP Snippets for example
  • Set the Timer’s Time Control parameter to Locked to Timeline
  • Set the Timer’s On Done parameter to Re-Start or Re-start without Initializing
  • Set the project length to some higher number, for example 6000 frames
  • Optional: set the segment def table to only have one line with 1 second length for a quick effect
  • Let the timer run and monitor the Timer CHOP’s CPU cook time increase with each cycle, but also somehow dependent on where you are on the timeline

Here you see in the beginning of the timeline, the timer’s cook time increasing in the first 10 seconds (10 cycles of a single 1 second segment) to almost 4ms gradually, then I jumped on my timeline to 3600 frames and cook time immediately increased to 15ms!!! By the end of the 6000 frames cook time is up to 25ms!

File for testing:
segmented_timer_bug.toe (3.2 MB)

@snaut just bumping as this seems like a critical bug to me

Hi @function.store,

sorry for answering just now - confirmed and we are having a look.

cheers
Markus

1 Like

So the issue is that you’ve set ‘onDone’ behavior to restart.
Unfortunately this is incompatible when tied to the timeline, as every frame it then restarts the timer and advances to current frame causing it to be done again, resulting in the building cook time.

If you set ‘On Done’ to ‘Do Nothing’ it will automatically restart as the timeline wraps around.

We’ll change this in a future build to disable the ‘On Done’ menu in this case entirely.

Cheers,
Rob.

1 Like

hey @rob

Do Nothing results in a different behavior though where it does not repeat the segmented timer (if it’s shorter than the timeline).

The point of my exercise was that I could have a segmented but looping timer that is still synced to the timeline.

1 Like

Ah okay, thanks.
I’ll take another look.

1 Like