DMX and Art-Net often belong in the same lighting system. DMX carries control data along a serial line to fixtures. Art-Net carries DMX data across an Ethernet network, often to a node that converts it back into DMX.
For a local rig, direct DMX is a sensible choice when your controller has enough outputs and the cable routes work. An Art-Net backbone becomes useful when you need to send control to separate fixture groups or distribute several universes. The decision is about the route from controller to light, not how many people attend the show.
Start with your fixture modes, available outputs and physical layout. Then choose the connections that serve that plan.
DMX and Art-Net solve different parts of the connection
The key difference is how the data travels. A direct DMX setup sends serial data from a controller output along a DMX line. Art-Net packages that data for a network. At the receiving end, a compatible node selects a network universe and sends its values through a DMX output.
The official Art-Net introduction describes this conversion between network packets and DMX512. The node changes the transport, not the fixture's list of functions.
A universe contains up to 512 control channels, as defined in the Art-Net glossary. That is a channel limit, not a count of lights. Each fixture uses a channel footprint: the number of channels needed by its selected mode. Choose that mode before counting how much room the rig needs.
| Planning question | Direct DMX route | Art-Net-to-DMX route |
|---|---|---|
| How does data reach the fixture group? | From a serial DMX output | Across Ethernet, then through a node |
| What selects the local data stream? | The controller's output patch | The network universe assigned to the node output |
| What reaches a conventional DMX fixture? | Serial DMX | Serial DMX from the node |
| What extra settings need attention? | Output patch and fixture addresses | Network interface, IP settings and node mapping, as well as the DMX patch |
This is why “DMX vs Art-Net” can be a misleading either-or question. You may use Art-Net for the shared route to the stage and DMX for the final connection to each light. A fixture needs native Art-Net support only if you intend to connect it directly to the network.
For the broader channel-control basics, see how DMX works. Here, the next task is choosing where each type of connection belongs.
Choose by the rig, not the event size
Count the required control channels before deciding how to distribute them. A rig with many lights can still have modest channel needs in simple modes. A smaller fixture group can need more channels when its selected modes expose more functions. Check each model's channel chart rather than estimating from fixture count.
Next, separate capacity from location. Capacity asks how many universes the controller must produce. Location asks where those universes need to emerge as physical outputs. A control system can have enough channels but put its outputs in an awkward place.
Consider two hypothetical plans. In the first, a band has nearby fixture groups and a controller with enough local DMX outputs. Direct DMX meets the channel demand and follows practical cable routes. Adding nodes would introduce network settings without solving a clear routing problem.
In the second, a venue needs separate control at the stage and a distant fixture group. A network backbone with local nodes lets the designer place DMX outputs near each group. The Art-Net background guide describes this approach: Ethernet to the fixture area, then DMX locally. Its value here is distributed output, not a claim that Art-Net makes every rig faster.
Before choosing the second plan, check who will maintain it. Record the controller's supported protocols, enabled universe capacity and any software licensing limits. Check the node's output count and mapping options against your required branches. Include the switch and node power in the plan; these are working parts of the signal path.
When comparing DMX stage-lighting fixtures, choose useful operating modes first, then total their footprints. This order helps prevent buying a control system around a fixture count that hides the actual channel demand. Choose the simplest route that meets both the patch and the layout, with settings your team can document and test.
Follow the signal from console to fixture
Sketch the route before connecting equipment. These two paths show where conversion belongs:
- Direct DMX: Controller DMX output → DMX branch → fixtures.
- Hybrid System: Art-Net source → Ethernet switch → compatible Art-Net-to-DMX node → DMX branch → fixtures.
In the hybrid route, the source produces the network data and the switch carries it toward the node. The node receives the assigned universe and sends serial DMX from the chosen output. The downstream lights still use their DMX modes and addresses. Existing DMX fixtures can therefore remain on those branches when their requirements match the system.
Place the conversion point where a local DMX branch serves the layout. For example, a node near a fixture group gives that group a local output instead of requiring its serial feed to begin beside the console. Mark both the network universe and the output port on your drawing; “node on stage” is not a complete patch instruction.
A fixture with documented native Art-Net support offers another path: network data can reach that fixture without a separate conversion node. Confirm this in the exact model's manual. An RJ45 socket alone tells you too little. ETC's DMX wiring guidance notes that RJ45 connectors can also carry serial DMX. A passive adapter changes the connection, not the protocol.
Also distinguish a node from an ordinary DMX splitter. A splitter distributes a DMX signal into branches; extra sockets are not, by themselves, extra independently patched universes. Use suitable active distribution for branching rather than passive Y cables, and terminate each DMX line as the connected equipment requires.
Once the route is drawn, assign the data to it. A correctly connected node can still send the wrong universe through the right cable.
Map universes, ports and fixture addresses separately
A working network connection and a correct lighting patch solve different problems. The IP address identifies a network device. The Art-Net universe identifies a stream of lighting data. A node output selects the stream to send down a physical DMX branch. The fixture's start address tells it where its channel footprint begins within that universe.
Give each network device a unique IP address. For a simple local system, use compatible IP settings and subnet masks according to the equipment manuals. ENTTEC's network setup guide makes the unique-address requirement explicit. Record those settings separately from the lighting patch so that a universe label is never mistaken for an IP setting.
Universe labels also need checking. ETC's Eos configuration guide documents a setting where console universe 1 is sent as Art-Net universe 0. That offset is an example, not a rule for every console.
The following patch is fictional. It assumes three fixtures in a 16-channel mode, with console universe 1 deliberately mapped to Art-Net universe 0 and node output A.
| Fixture | Console universe | Configured Art-Net universe | Node output | Start address | Occupied channels |
|---|---|---|---|---|---|
| A | 1 | 0 | A | 1 | 1–16 |
| B | 1 | 0 | A | 17 | 17–32 |
| C | 1 | 0 | A | 33 | 33–48 |
The check is last occupied address = start address + footprint − 1. Fixture B therefore ends at 17 + 16 − 1 = 32, leaving 33 free for fixture C. These are sample values, not specifications for a SHEHDS product.
Match the console profile to the mode selected on the actual fixture. ETC's Hog patching instructions explain how mode affects footprint and address allocation. If you change a mode, check the occupied range again before assuming the next fixture still has room.
The same start address can serve different fixtures on different universes. Within one universe, reserve separate ranges when you want separate control. Once that map is correct, DMX controller programming becomes a separate task from making the data reach the right light.
Commission one layer at a time
Test a minimal route before building the whole system around it. The aim is to learn which layer works, so each next change has a clear meaning. This sequence combines the signal path with manufacturer setup and fault-finding guidance.
- Prove One Fixture: Select the intended mode and start address. Where a suitable DMX source is available, test the light with a known-good local cable before adding the network route. Check the fixture profile too.
- Check The Source: Enable Art-Net output on the intended network interface. Confirm that the controller is sending the required universe, not merely showing values inside the program.
- Check Network Settings: Compare the sender and receiver IP settings and subnet masks with the equipment manuals. Keep device addresses unique. For a simple local system, compatible settings must let the two endpoints communicate.
- Check The Node: Confirm its selected universe, physical output and port direction. Compare them with your written patch rather than relying on matching-looking numbers.
- Check The DMX Branch: Connect the tested fixture, verify its mode and address, and check cable and termination. Add the remaining fixtures and branches in controlled steps.
Read activity indicators through the node's manual. A data light can help show that something is arriving; it does not prove that the intended universe reaches the correct fixture functions. ENTTEC's network troubleshooting guide recommends a minimal chain and checks at the interface, subnet, universe and output layers.
Use the symptoms to choose the next check. If no fixtures respond, begin upstream with output and routing. If a fixture responds with the wrong functions, compare its mode and profile before changing network settings. If a known-good direct DMX test works but the network route fails, focus on the added parts. These are diagnostic starting points, not certain diagnoses.
Check delivery settings against the installed equipment version. The Art-Net specification, revision 1.4dp dated October 23, 2025, requires ArtDmx packets to be sent by unicast to subscribers. Here, unicast means sending to a specific receiver. Some implementations still expose broadcast controls, as the Eos guide documents. Follow the relevant manual instead of treating every Art-Net menu as identical.
Finally, rehearse the full route and retain the tested settings. ENTTEC's node setup guide recommends a dedicated lighting switch or planned VLAN to separate show traffic. Treat that as network planning, not a reliability guarantee. Record which branches depend on each switch and node so the next operator can trace the same path.
Frequently asked questions
Does adding a node unlock more controller channels?
Check the controller's output and license limits first. A node converts and distributes data that the source can send; its socket count is not proof that your software gains more usable universes. Before buying, compare the enabled source universes with the streams and outputs you intend to use. This avoids choosing a node for capacity that is unavailable upstream.
Should I replace working DMX fixtures when adding a network?
Start by checking whether those fixtures can remain on DMX branches fed by compatible nodes. If their modes and channel needs still fit the design, network transport alone is not a reason to replace them. Compare that route with native-network fixtures only when their documented features meet another need in the plan.
What should a seller confirm before I buy control hardware?
Ask for the exact manual and identify supported protocols, input and output directions, universe mapping and usable output capacity. For fixtures, request the mode and channel chart. A label such as “network extender” is a starting point for these questions, not an answer to them.
Write the control plan before buying
Choose direct DMX when the available outputs, channel capacity and cable routes already serve the rig. Choose an Art-Net backbone when placing network-fed outputs near fixture groups solves a real distribution need. In either case, the fixture patch remains part of the design.
Write down the fixture modes, occupied channel ranges, physical zones and available controller outputs. Add node ports and network settings if the route needs them. That short plan gives each cable and setting a purpose.
SHEHDS lists control and signal-distribution options in its DMX controller collection. Use the plan to compare the relevant options, then check the exact manuals against your required signal path. The useful purchase is the one that fills a documented role in the system.
