[Win10 64 2019.10000 builds] parameter CHOP pulse issue

Not sure whether this is an issue with the Parameter CHOP, null CHOP or CHOP viewers themselves but I have some pretty odd cooking behaviour going on in a network that I’ve used a bunch in the past.

Seems likely to be the same thing as dage023 is reporting here
[url][Win10 64; 099 17550] ParameterCHOP and CountCHOP - Bugs - TouchDesigner forum

I often have a CHOP chain similar to this for sending one shot MIDI note cues.

In all 2019.10000 builds that I’ve tested the lag CHOP sometimes catches the pulse, and sometimes doesn’t. The issue is not present in 2018.27910 or 2018.28120

It seems to be unpredictable but mostly catch it when outside the network, but is hugely less reliable when inside with the CHOP viewers on.

Oddly it also seems to predictably miss it every time if there is a null after it set to ‘Always’ or ‘Selective’ cook type.

Simple example attached
pulseChopCooking.tox (758 Bytes)