Tutorial: Concert with complex lighting control

Build a complete concert project in Arthoff with lighting, audio, stage effects, team roles, live operation, dry runs, and device synchronization.

This tutorial presents a concert workflow focused on synchronized lighting, audio, and visual effects. The example is a multi-act festival stage operated by a technical team.

Step 1: Create the project

Create a new project named "Summer Festival 2026 – Main Stage".

Use a description such as "Two-day music festival – Main Stage", set the event date to 22 July 2026, and optionally assign an orange project color.

Tip

For larger festivals, separate projects per stage or per day can make access control, scripts, and device configuration easier to manage.

Step 2: Add the technical team

Add the production and technical crew with permissions appropriate to their work. Example accounts include:

Account	Role
`prod@festival.pl`	Administrator
`lighting@festival.pl`	Lighting operator
`moving@festival.pl`	Moving-head operator
`sound@festival.pl`	Sound operator
`fx@festival.pl`	Effects operator
`stage@festival.pl`	Stage team

Step 3: Connect lighting and effect devices

Main lighting console

Configure the main Art-Net console using values such as:

IP: 192.168.1.100
Port: 6454
Protocol: UDP / Art-Net
Universe: 1
Name: Main Console – PAR Fixtures

Use additional universes for other fixture groups, for example universe 2 for moving heads and universe 3 for rear lighting and effects.

Network layout

A separate Art-Net interface may be used if the lighting network is isolated from the computer running Arthoff.

Effect machine through OSC

An effect controller can be configured with an address such as:

IP: 192.168.1.150
Port: 8000
OSC address: /fx/smoke

Step 4: Create the concert script

Create a script named "Main Stage – Full Day" and choose the Concert type.

Step 5: Divide the day into sections

A sample structure:

12:00 – Opening / Warm-up DJ
13:30 – Rock Band A
15:00 – Technical break
15:30 – Electronic Artist B
17:00 – Headliner
19:00 – Lighting / laser show
20:30 – Closing DJ / afterparty
22:00 – End

Step 6: Add lighting cues

Opening wash

Create a Lighting cue for the initial stage look. Example values:

The first channels can represent a red rear wash, while the following channels provide white front light. Use a fade such as 3 s for a smooth opening.

For a rhythmic cue, set the relevant intensity or effect channel, for example channel 4:128, and use a short fade such as 0.2 s. The operator can trigger the cue manually in time with the music when required.

Transition / fade out

Create a transition cue that brings the required channels to 0 or to a low ambient level. A 2 s fade gives the stage a controlled transition between acts.

Step 7: Add audio cues

Explosion before a chorus

Create an Audio cue using the FOH playback or mixer device. Configure the sample, volume around 80%, pan 0, and short fade-in/fade-out values such as 0.1 s. Set playback to one-shot and choose either manual or automatic triggering according to the performance.

Background audio during a technical break

Create a looping background cue at a lower level, for example 30%, with a 2 s fade. Stop or replace it when the next act begins.

Step 8: Add stage-effect cues

Stage-effect devices such as smoke, confetti, or lasers can be controlled with dedicated or Custom cues. For OSC-controlled hardware, a cue may send an address such as /fx/smoke with an activation value, followed later by a deactivation command.

Safety

Treat automated effect cues as real device commands. Confirm local safety procedures and test them with hardware output disabled before using them during a live event.

Step 9: Add comments and team notes

Use Comment cues for operational notes that should appear in the running order without controlling a device. They are useful for reminders about artist entrances, stage resets, cabling changes, or operator hand-offs.

Step 10: Prepare the lighting operator's live view

During preparation, the lighting operator can work from the editor together with device previews. During the live event, use the dedicated presenter or view-only workflow so accidental editing is less likely while the running order remains visible.

Step 11: Perform a dry run

Open the presenter and enable test mode.

Run the complete order of cues without sending commands to real devices.

Verify DMX values, OSC messages, audio transitions, and trigger order.

Correct cue values or timing before reconnecting real outputs.

Step 12: Concert day

Verify all devices and network connections before doors open.

Confirm that each operator has the correct project permissions and view.

Load the live script and begin from the opening section.

Advance manual cues with the presenter while automatic and external triggers run according to their configuration.

Use comments and section boundaries to coordinate artist changes and technical breaks.

If a cue must be skipped or repeated, use the presenter jump controls rather than editing the running script during the performance.

FAQ

Should every lighting change be automatic?

No. Keep musically sensitive or safety-critical moments manual when an operator needs to judge the exact timing. Automation is most useful for deterministic transitions and synchronized technical sequences.

Can different fixture groups use different Art-Net universes?

Yes. Separate universes can be assigned to different fixture groups as long as the console, network, and Arthoff device configuration use the same mapping.

How should I test smoke, confetti, or other effects?

Validate the cue sequence in dry-run mode first. Physical testing should then be done according to the venue's technical and safety procedures with authorized operators present.