FIXED: Parameter Pulse not being triggered

Bugs
1

Hello, I have encountered strange problem where data driven by TCP/IP aren’t triggering pulses on parameters as expected. I guess this is some cook order related issue as it could be solved by requesting cook() on certain nodes. Nevertheless it seemed like it shouldn’t be happening by default, so I thought I might post it here. Please take a look at attached video showing the problem (left is server.1.toe and right is client.1.toe). Trail on the right doesn’t respond to pulses once timers in server are synchronized.

Win10, 2021.14360
server.1.toe (4.4 KB)
client.1.toe (4.4 KB)
demo_hap.zip (1.8 MB)

2

Hey @monty_python

Thanks for the report and example files.

After playing around in your file, it looks like you cannot call .pulse() on two different parameters on the same frame in the TCP callback… or something related.

I have logged an issue for a developer to look into it.

Best,
Michel

1 Like
3

Hello,
I have revisited this after a long time and there are some problems happening, so I thought I might bring attention here. I am attaching screencast from 2022.32660. In the first part there are no pulses being triggered, while in the second part is only one of two messages being processed in network.
demo.zip (1.7 MB)

1 Like
4

Hi I found your question because i had problem with sending pulse() to two different parameters using one python script. To resolve this i used run() to delay second pulse for 1 frame:

op(‘operatorName’).par.parName1.pulse()
start = ‘’‘op(‘operatorName’).par.parName2.pulse()’‘’
run(start, delayFrames = 1)

5

This will be fixed in the next experimental build we post.

2023.11162+

Best,
Michel

1 Like