Timecode CHOP: locked to timeline frame calculation errors?

When using timecode CHOP in “Locked to Timeline” mode, it appears to be introducing some frame calculation errors that cause some frames to hold for two frames for no apparent reason, as evident when looking at its trail:

Notice the little random “steps” in the ramp. There appears to be no pattern and they appear randomly.

Just tested this on a fresh TD (2023.12230) project running at 60 fps with 0% dropped frames.
It happens even with project running at 30 fps:

Thanks for the report – I’m able to reproduce. We’ll take a look into it.

1 Like