For the complete documentation index, see llms.txt. This page is also available as Markdown.

Network DMX

Network DMX Input (ArtNet, sACN, CITP, Sig-Net)

The Network DMX tool group of the Logic Module provides four input objects that let Depence receive incoming DMX data from the network and feed it into the DMX buffer:

Object
Protocol
Typical use

Input DMX ArtNet

Art-Net 4

Receiving DMX from Art-Net nodes/consoles

Input DMX sACN

sACN (E1.31)

Receiving DMX via sACN/E1.31 (multicast)

Input DMX CITP

CITP/MSEX

Receiving DMX from visualizer/media server streams

Input DMX Sig-Net

Sig-Net (encrypted)

Receiving DMX via the encrypted Sig-Net protocol

All four objects follow the same basic principle: they receive DMX data for a freely selectable universe range and write it into the shared DMX buffer according to a configurable merge mode. This allows external controllers (lighting consoles, media servers, other visualizers) to be brought live into the 3D visualization.

These objects are inputs. They receive data from the network. For sending DMX out to the network there are separate output objects.


Common behavior

Universe range

Each object receives a contiguous range of DMX universes. This is defined by two properties:

  • Start by Universe – the first universe to receive.

  • Universe Count – the number of universes received starting from the start value.

The currently configured range is shown directly on the Logic Module node, for example:

Univ: 1 to 16

Status output

Each object has an output connector Status:

  • Value 1 as long as data was received for at least one universe of the range in the current frame.

  • Value 0 if no data was received.

This can be used, for example, to build a "signal present" indicator or to trigger logic as soon as an external console is sending.

DMX Merge Mode

The DMX merge Mode determines how the received values are merged with other DMX sources (cues, other network inputs, etc.) in the buffer:

Mode
Behavior

LTP (Latest Takes Precedence)

The most recently changed value wins. Default setting.

HTP (Highest Takes Precedence)

The highest value wins.

Overwrite

The network value overrides other sources with the highest priority.

LTP is the default setting and the right choice for most use cases. HTP is suitable, for example, for merging multiple dimmer sources. Overwrite forces the network source to take precedence.

Enabled

Enabled turns reception on or off:

  • Enabled: The object receives and processes data. For sACN and Sig-Net it additionally joins the corresponding multicast group.

  • Disabled: Reception is stopped and the associated buffer range is reset. For sACN and Sig-Net the multicast group is left again.


Input DMX ArtNet

Receives DMX data via Art-Net 4.

Properties

Property
Description
Range
Default

Enabled

Enable/disable reception

On / Off

Off

Start by Universe

First received Art-Net universe

0 – 32767

0

Universe Count

Number of received universes

1 – 1024

16

DMX merge Mode

Merging in the buffer

LTP / HTP / Overwrite

LTP

Art-Net counts universes 0-based. The first universe is therefore 0 by default.


Input DMX sACN

Receives DMX data via sACN (E1.31) using multicast.

Properties

Property
Description
Range
Default

Enabled

Enable/disable reception (incl. multicast join)

On / Off

Off

Start by Universe

First received sACN universe

1 – 32767

1

Universe Count

Number of received universes

1 – 1024

16

DMX merge Mode

Merging in the buffer

LTP / HTP / Overwrite

LTP

sACN uses multicast. When enabling, as well as when changing the start universe or universe count, Depence automatically joins or leaves the corresponding multicast groups. Make sure your network (switches/routers) properly supports multicast and IGMP.


Input DMX CITP

Receives DMX data via CITP/MSEX, typically from media servers or other visualizers.

Properties

Property
Description
Range
Default

Enabled

Enable/disable reception

On / Off

Off

Start by Universe

First received universe

1 – 255

1

Universe Count

Number of received universes

1 – 255

16

DMX merge Mode

Merging in the buffer

LTP / HTP / Overwrite

LTP

For CITP, the start universe and universe count are limited to the range 1–255.


Input DMX Sig-Net

Receives DMX data via the encrypted Sig-Net protocol using multicast. Unlike the other protocols, a passphrase is additionally required here.

Properties

Property
Description
Range
Default

Enabled

Enable/disable reception (incl. multicast join)

On / Off

Off

Start by Universe

First received Sig-Net universe

1 – 32767

1

Universe Count

Number of received universes

1 – 1024

16

Passphrase

Key for decrypting the Sig-Net stream

Text

(empty)

DMX merge Mode

Merging in the buffer

LTP / HTP / Overwrite

LTP

Sig-Net uses multicast and is 1-based (universe 1 corresponds to the first multicast address). When enabling, as well as when changing the start universe or universe count, the multicast join or leave happens automatically. The join is self-healing: if it was not yet possible when loading the project, it is performed automatically as soon as the connection is ready.


Step by step: setting up an input

  1. Drag the desired object from the Network DMX tool group into the Logic Module.

  2. Set Start by Universe and Universe Count to match your patched fixtures.

  3. Choose the DMX merge Mode (when in doubt, use LTP).

  4. For Sig-Net only: enter the sender's passphrase.

  5. Set Enabled to On.

  6. Check the Status output or the visualization to see whether data is arriving.


Troubleshooting

  • No data visible: Check whether Enabled is on and whether the configured universe range matches the universe numbers of your fixtures.

  • Wrong universe offset: Mind the different counting – Art-Net starts at 0, sACN/CITP/Sig-Net at 1.

  • sACN/Sig-Net receive nothing: Make sure multicast/IGMP works in the network and the correct network interface is used.

  • Sig-Net receives nothing: Verify that the passphrase matches the sender's exactly.

  • Values "flicker" or jump: Check whether multiple sources are driving the same universe, and choose an appropriate merge mode (e.g. Overwrite so the network source takes precedence).

Last updated