timerCHOP cook problem 32120

Bugs
1

binding or referencing a parent customPar from a timerCHOP in 32120 from the length() par doesn’t update the child value. Can get around it by forcing a cook with a parexec.

Here’s an example in a clean session:
timerCook.tox (1.8 KB)

2

Hey @drmbt

Thanks for the report.

I was able to reproduce and logged this as an issue for a developer to look into it.

Best,
Michel

1 Like
3

I’m also noticing in some feedback loops, pulsing the feedback bound to a parent customPar does nothing if I’m in the same network, but once I exit the network it behaves as expected. I think there may be some other cook issues lurking in this build

4

The length() par issue will be fixed in the next release. Do you have a file we can reproduce the parameter pulse issue with?