I’ve encountered a bug with the DMX out chop node - or at least I think so! Please let me know if there are other things I should try, or if I’ve overlooked a similar post on the forum!
When sending to Art-net no DMX data leaves TD upon reboot and launch of program. I have this issue with multiple projects relying on DMX out (context is kinetic winch installations)
Hardware is a SHOWTEC net2/3 pocket node connected directly via ethernet-cable
Hardware connection I can verified in terminal (ping).
I tried to recreate new IP for both local and node address
Also tried fresh td file sending DMX data from constant chop to the DMX out
I have also tried with different art-net hardware (Ode MKII), same issue.
By coincidence, I noticed that connecting the machine to a Wifi access point is the fix, and DMX data flows from TD to the art-net node immediately. I can also turn Wifi off again, data still flows. Rebooting the machine requires a new wifi-connection, before DMX data is pushed to art-net from TD.
I got used to connecting wifi at this point, but sometimes the machine runs turn-key in installations outside reach – so not a huge issue, but inconvenient. I am unsure how to verify if this is an issue with TD or the machine, besides the fact that I can connect to all the node-hardware by other means (browser/terminal), while TD is not forwarding DMX data.
I realize now I’m on a slightly old build, as I’m holding off updates until end of a running project. Will verify if the issue is still there in newest build and macOS asap!
Mac mini 2024 M4 16GB macOS Sequoia 15.2. TD 2023.12370
Are you selecting the correct network interface via the local address parameter? If left blank, then the DMX packets will be sent out on the default network interface (which is determined by the OS but is typically the first enumerated interface in the menu), which could be the incorrect one for your output case.
Good point! I have set the IP directly to the address on the node, and the local address as per set up in network settings on the machine… I have also tried changing these to new addresses for both, and “all” configurations of subnet mask (255.0.0.0, 255.255.0.0, 255.255.255.0, 255.255.255.255) without luck
The local address parameter only accepts the local network IP as a value, not subnet masks. If you click > on the right side of the parameter you will get a full list of all available network interfaces on the system.
Ah sorry I confused the settings here, indeed subnet mask I only tinkered with in the machine settings.
Oddly, the drop down menu does not show anything when I click it. But when I manually type my local address, and the address of the node, everything runs fine. Granted the machine has had a wifi connection, prior…
The network interfaces are only enumerated once on TouchDesigner start-up, so if any network interface system changes are made while TouchDesigner is running, they will not be reflected in the menu until TouchDesigner is restarted. However, you will still be able to manually enter them and use them like you’ve mentioned here, provided you do know the local IP you want to use. If you’re certain you’re using the correct local IP then this may not be the issue.
Are you unicasting to the device or are you broadcasting? If trying via unicast, does changing to global broadcast 255.255.255.255 yield results?
Are you using a custom network port or the default port (ie. 6454)? Is the device visible/routable to TD when using the Art-Net DAT? The Art-Net DAT will broadcast an ArtPoll packet and listen for any ArtPollReply’s from devices. Note: you will want to use the same local address value on the Art-Net DAT as on the DMX Out CHOP.
The next thing to try would be to directly inspect traffic on your network interface using something like Wireshark. That way, you can see whether the ArtDmx, ArtPoll, etc. packets are being sent out correctly and on the correct network interface.
Hi Eric!
Thanks for the suggestions! I tried switching between direct and unicast in a fresh TD-file with no luck, the art-net dat showed nothing either when polled; but I could still “ping” the interface in terminal successfully…
I connected to Wifi to install Wireshark in order to monitor if any packets was indeed leaving TD as you suggested. But now I cannot recreate the issue whatsoever - which in practice Is great; everything is working, even when starting up without network connection. But would be nice to pin down an issue, or what I did wrong…
In any case - thanks for your time, I will keep monitoring and keep an eye on the forum if anyone else encounters this!
