RESOLVED: timesliced inputs to script CHOP breaks scriptOp.numSamples = X

Bugs
1

Hi there, pretty easy bug(unless this is intended behavior) to reproduce, in a script chop in most scenarios I can set the .numSamples parameter just fine. However, if I have an animated, timesliced input to the script chop I lose all but what seems like the first sample in the script sop no matter what.

I should note, that if this is intended behavior, it’s not too obvious, but very easy to work around - all I need to do is put a trim chop down, and set to absolute before the script CHOP and this forces it out of timesliced mode effectively, and then the script CHOP works as intended.

I’ve attached a file for easy reference!

scriptChop_NumSamples_TimeSlice_Bug.1.toe (4.0 KB)

2

Hi Lucas, this is an old one but we got around to cleaning it up with warning that includes a tip on how to fix it.

warning
warning1159×398 11.1 KB

Next 40k build.

1 Like
3

This is awesome! Is the variable isTimeSlice only on the script chop and persistent? Or does anything cause it to reset?

4

Yeah, only Script CHOPs will be able to set isTimeSlice, similar to numSamples, and will persist once set.

1 Like