I’m using a subdivide SOP here to drop frames. Almost every time frames drop, the Bind CHOP is outputting some ghost value. As far as I understand, the Bind CHOP should only change value when one of its inputs changes value. Toe attached.
TD 2022.25370 Win 10
bindGlitch.toe (5.1 KB)
Thanks for the example, we’re having a look.
This will be fixed in upcoming builds 2022.26280 and later.
It had to do with different lengths in the connected inputs.
As a workaround, you could trim the second input to make sure it’s always the same length as the first one:
Cheers.
Thanks Rob. So just to make sure I’m understanding correctly, even though the two input chops in the example are 1 sample long each, dropped frames make the Bind CHOP think they’re different lengths? But as a workaround, I would only need to trim the second input, not the first?
I’ve had this issue in a few places, and used trimCHOP as workaround. make sure its set to absolute
No, the first input is usually one sample long, but if frames are dropped, it will grow accordingly (since it’s timesliced). So those cooks may be a few samples long.
The constant CHOP however, is always one sample long in your setup.
The workaround is to make sure the constant CHOP is always as long as the timer CHOP.
The Bind CHOP was incorrectly assuming all lengths were equal to the first input.
