timeslicing.... advise, guidelines?

I think I’m getting into a mess with chops timeslicing by default and
others not timeslicing, as I don’t see triggers at the right frame (or
not at all, that’s another matter, I have a ball bouncing on the screen
that’s suppose to trigger when it goes out 0 1 space, but sometimes if
it’s too fast the trigger doesn’t trigger…!).

In theory - unless I’m using a keyframe chop, I think everything should
be timesliced - or not…

do you guys have any guidelines/lessons learned to deal with timeslicing?

I’ve also noticed that converting a dat to a chop generates two frames, not one as I would expect. Since they must all be the same I’m just trimming the result
but definetly timeslicing - or the lack of it - is something that needs to be watched chop by chop with a lot of attention.

I’d like to read guidelines from Derivative on how/when to use timeslicing.

tx
d

Essentially you want everything that isn’t a static frame range (like a keyframe or a animation clip) to be timesliced. This will ensure triggers always go off (and you get smooth data)

But it’s perfectly legitimate and accurate to send a Constant CHOP (where you twiddle the slider) or a MIDI device (MIDI In CHOPs always at frame 1), or a Mouse CHOP into a time sliced CHOP like Filter or Trigger.