Artnet problems build 2025.32280

Bugs
1

I had a show this weekend were in was sending artnet out to a lighting desk as i did plenty of times before. Somehow the refresh rate of the artnet that I was sending out was really low. I was sending to a lighting grid and sending a moving gradient wasn’t even possible. Some lights froze or had a delay etc.

I checked the connection and there was nothing wrong with that. Sending artnet via resolume was also smooth. I then downgraded to the 2025.32050 build and everything worked perfect again, without changing anything.

Did anything change between these two build regarding the artnet protocol?

Thanks in advance!

3

Are you using the DMX Out CHOP or POP? If CHOP, are you sending Packet Per Channel or Packet Per Sample mode?

There’s only been one change to Art-Net between those two builds, which was a fix to the sequence value on the ArtDmx packet. In 2025.32050 and earlier builds (regression/bug since 2023.12230) the value was always 0, which was causing issues with some receivers.

Is the packet_rate entry of the DMX Out’s Info DAT reporting what you would expect?

5

Hi Eric!

thanks for your response, for some reason i missed the notification.

i’m using the dmx out chop and i’m sendin packet per Channel.

in the 2025.32050 the packet rate is 1920 (and that is right, 32 channels 60 fps)

in the 2025.32280 it fluctuates a lot between 1770 and 1820 ish. (and i opend the exact same file)

6

Are you using ArtSync?

If you send me over your project (either in its entirety, or just the isolated DMX issue) then I can take a closer look into it.

7

hi Eric,

i tried both with and without artsync while testing at location.

here is the isolation dmx issue of the file.

touchdesigner dmx test.2.toe (4.2 KB)

I rather not send my whole file via this public forum because of tools that are in it that i’m still working on… if you can’t reacreate the problem i’m happy to send the whole file privatly.

Thanks in advance!

8

In that file, the column header channel is added as CHOP channel in the DAT to CHOP, and is included as one of the 32 channels for DMX output, but it is not actually routable through the routing table so only 31 channels are being sent. When I set the DAT to CHOP parameter First Row is to “Ignored”, then it correctly sends out 32 channels and I get a constant packet_rate of 1920.

However, you mentioned it works fine in 2025.32050 and this issue is present in both, so I imagine it’s not the source of the problem in your original post.