About nan value in LagCHOP

[sndmtk]

I’m using LagCHOP to smooth sensor values received via OSC, but after leaving it running for a long time, LagCHOP stops updating and shows nan. Even after pressing Reset, nan remains.

Sorry I can’t explain it better — it’s hard to reproduce.

I found a similar case here, but I’m not sure if it’s the same issue.

Lag op keeps dying with "nan Chan1"

I’m using a lag CHOP to smooth some values from audio - works exactly how I would like. All in a network that is in a container. Quite often when surfacing out of the container, the effect applied via the lag stops. Going back into the container and all the lag ops are “frozen” with a msg “nan Chan1” - which seems like an error related to the JS “non a number” error? [Screenshot 2023-09-26 at 10.27.02 AM] Is this a bug?

Any idea what might be causing this?

OS: Windows 10
TouchDesigner version: 2023.12000

[Gallo]

Hi,

nan stands for “Not a Number”
No idea why it works until it’s not. There is still a chance it could be a bug.
You can try to cast the value when you receive it to force the conversion to a number. Use (int) or (float) as needed before the value in python.
Otherwise be sure you keep sending your osc value as a number.

[sndmtk]

Thanks for your reply!
To add more detail: the data received via OSC is cast to a float and written into a Table DAT. Then I use a DAT to CHOP to convert it to CHOP format, and pass that into a LagCHOP.