Art-net port binding issue

philbearman · September 27, 2025 at 5:26 PM

Hi guys,

I'm trying to run a piece of software which is controlled via Art-net on the same computer as DMXC3. It appears that DMXC3 is already binding to port 6454 for input even though I'm only actually using DMXC3 for output, which means my other piece of software can't bind/listen for the Art-net output from DMXC3.

Is there any way of disabling Art-net DMX input in DMXC3 so that the port is available for my other software to bind to?

I have two Art-net interface instances configured, each one outputting a different universe. DMX-In is not enabled on either interface.

My knowledge of how Art-net works is a bit limited, so please excuse me if I've misunderstood how this works!

On the same topic, is there any documentation available for the latest Art-net plugin?

In particular, I'm interested in what the "Force broadcast" and "Additional Send to IP (optional)" fields in the interface are for?

Any help much appreciated,
Phil

**Qasi** · September 27, 2025 at 11:27 PM

Even you only Output ArtNet, under the hood Artnet is talking bidirectional with the Nodes.
This is nesseccery to fina all Nodes and send only the Universe each node needs as Unicast.
This behavior is required as Spec.

"Force broadcast" and "Additional Send to IP (optional)" is only nesseccery if you have stupid, old or buggy Nodes which are not using ArtNet4 Spec.
But "Force broadcast" is dangerus because shity Nodes are not capable of extensiv messages with Data they dont need due to missing RAM, but have to parse the Data to evaluate if the data is intended for him self

philbearman · September 28, 2025 at 10:13 AM

Ah ok, thanks for that information.

We proudly present: The release of DMXControl 3.3.3!