Win10 2020.24520 - timeslice and trailchop weirdness

Hello,

See

If I use a timer as the input for a lookup, trailing the result will sometimes jump at 0 for no reason.
Funnily it doesn’t seem to affect a chopexec which doesn’t register these changes.
So I’m not sure what that means?

One way of fixing it is to use a trimChop so the input to the lookup is not timesliced anymore.
The other way is to put an extendchop hold/hold before the lookup for the input curve.

None of it make a ton of sense.
Thank you!

2020_07_15_trail_timeslice_weirdness.toe (4.6 KB)