Device management

Devices can be connected directly to an Arthoff project and then controlled from cues. This includes lighting consoles, audio systems, cameras, effect machines, and devices controlled through OSC, MIDI, or HTTP.

Connecting a device to a project

Testing a connection

Use test mode before relying on a device during a rehearsal or live event.

Using a device in a cue

Lighting cue

Create a Lighting cue, select the lighting device, and define values such as:

1:255, 2:128, 3:0

You can also choose a group or preset and set a fade time before saving the cue.

Audio cue

For an Audio cue, choose the mixer or playback device and configure the source, for example a URL or line input, together with volume, pan, fades, and playback mode.

Camera cue

For a Camera cue, choose a PTZ camera and configure values such as Pan, Tilt, Zoom, or a saved preset. The transition may use Cut, Fade, or Wipe, with an optional duration.

Custom OSC, MIDI, or HTTP cue

For a custom device command, select the protocol and provide its address or command. Examples include:

/light/1/intensity
CC 10, channel 3
http://device.local/api/relay/1

Set the command value and its data type when required by the protocol.

Device groups and presets

Groups make it possible to control several devices as one logical unit.

Lighting presets can also be saved from a console. When creating a cue, select the preset, optionally configure a fade time, and save it.

Dry run without sending commands

Use dry-run mode when you want to verify the show flow without controlling real hardware.

Troubleshooting

The device does not connect

Check that the device is powered on and reachable on the network, then verify the selected protocol, port, and remote-control/API settings. A simple ping can help confirm network reachability. Also check host and network firewalls.

The cue runs, but the device does not react

First verify the same values in the device test panel. Make sure the device is not configured as preview only, and verify that command values are within the expected range, for example DMX 0–255 or MIDI CC 0–127. For lighting consoles, also check direct output and patch configuration.

Commands arrive with noticeable latency

A healthy local stage network should normally have low latency. Check whether ping times stay below roughly 30 ms, prefer wired Ethernet over Wi-Fi, and inspect buffering on USB MIDI interfaces. Arthoff may poll some device states periodically; the default interval is 500 ms and should only be reduced when the device and network can handle the extra traffic.

Example configurations

Theatre: conventional lighting through Art-Net

Connect an ETC EOS-class console through Art-Net, create a group for four front lights, configure DMX values and fades in lighting cues, and verify everything in test mode before rehearsal.

Conference: Yamaha CL5 over MIDI

Connect the console through USB MIDI, use the appropriate MIDI channel, create an Audio cue that switches the required line input and gain, and use a Custom MIDI cue for additional commands such as reverb changes.

Concert: moving heads and smoke

Use Art-Net for moving heads and OSC-controlled relays for stage effects. Group fixtures where useful and trigger a custom command such as /relay/2 1, followed by /relay/2 0 when the effect should stop. Test the sequence in dry-run mode first.

Corporate event: PTZ camera and recording API

Connect a PTZ camera through VISCA over IP or NDI and control a recording system through HTTP. Camera cues can recall PTZ presets, while custom HTTP cues can call endpoints such as POST /api/recording/start and the corresponding stop endpoint.

FAQ