Documentation
Official user guide

Run your lighting show with confidence.

Plain-language instructions for installing, connecting, recording and operating CUE/IO. You do not need Linux knowledge for normal use.

No matching section found.
Try a shorter phrase such as “audio”, “IP”, “timecode” or “licence”.

Matching sections:

01 · Introduction

What CUE/IO does

CUE/IO turns a Raspberry Pi into a standalone Art-Net show recorder and player. It can capture lighting data with synchronized audio, then replay the result without keeping the lighting console connected.

RECORD

Capture Art-Net and optional audio with one shared timeline.

TIMECODE

Wait for a timecode signal and run the prepared show in sync.

PLAYER

Select, play, loop and control a recorded show.

Only one main mode is active at a time. When you change modes, CUE/IO stops the previous mode and releases its audio and network resources. Use the browser interface from a phone, tablet or computer connected to the same network.

Normal operation is localInternet is required for initial licence activation and selected online services. Recording and playback continue on the local network.

02 · First setup

Install and activate

Write the supplied CUE/IO image to a suitable microSD card or SSD, insert it into the supported Raspberry Pi and connect power only after all essential cables are attached.

Write the imageUse Raspberry Pi Imager or another trusted image writer. Select the supplied CUE/IO image and the correct storage device.
Connect hardwareConnect Ethernet, the supported USB audio device and optional RTC hardware. Then connect power.
Wait for the first bootThe first start may take several minutes. Do not remove power or the storage device during this time.
Open CUE/IOFrom the same network, open the local address shown in the Network section, or use the device IP address.
Activate onceOpen Licence, enter the one-time activation code from your customer account and let the Raspberry Pi reach the internet for activation.
Choose the storage device carefullyWriting an image erases the selected card or drive. Keep backups of important show exports on another device.

Before the first real show

  • Open Status and confirm the application, disk and network are healthy.
  • Open Settings → Audio and test input and output devices.
  • Open Settings → Network and select the Art-Net interface.
  • Run a short test recording before a live event.

03 · Access

Connect and open the interface

Connect your phone or computer to the same LAN or Wi-Fi as CUE/IO. In a browser, open the exact technical <hostname>.local address shown under Management access (the factory default is cueio.local) or the current IP address shown by your router or in CUE/IO network settings.

Recommended

Raspberry Pi connected by Ethernet to the Art-Net network; phone or computer on the same LAN or its Wi-Fi access point.

Fallback access

Use the optional rescue Wi-Fi access point when the normal network address is unknown or misconfigured.

No port number is normally neededOn the prepared production image, enter the local name or IP address directly. If your installation displays a specific address, always use the address shown on that device.

Art-Net connection

  1. Connect the lighting console, CUE/IO and Art-Net nodes to the correct network.
  2. Make sure their IP addresses and subnet mask belong to compatible networks.
  3. Select the intended interface in Settings → Network.
  4. Send Art-Net and verify activity in Monitor before recording.

04 · Inputs and outputs

Audio and DMX settings

Set up and test the physical inputs and outputs before relying on them in RECORD, TIMECODE or PLAYER mode.

Audio

  • Select the recording input and playback output.
  • Test each selected device before a real show.
  • Confirm the displayed sample rate and channel count match the equipment.
  • Stop the active mode before unplugging or changing an audio device.

DMX and playback

  • Select the interface physically connected to the Art-Net network.
  • Review broadcast or unicast output targets before playback.
  • Use Monitor to confirm incoming data and a short test show to confirm output.
  • Keep RECORD trigger settings in RECORD; they do not start TIMECODE or PLAYER.
  1. Stop recording, playback, timecode listening and Benchmark.
  2. Open Settings → Audio, Settings → DMX or Settings → Network.
  3. Select the device or interface, save, and wait for confirmation.
  4. Run the built-in audio test and verify live DMX in Monitor.

Authoritative Art-Net output routing

Routing is selected from the saved show metadata, not from how the file arrived. A show whose meta.type is manual—a Fixed Scenes show, an Effect Generator show or an imported Manual show—uses its own saved output. Recording, importing or generating a show does not by itself decide whether the show is Manual.

Saved show classAuthoritative output
Manual · UnicastThe show sends to its one saved Target IP address. Every global Art-Net unicast target is ignored.
Manual · BroadcastThe show ignores every global unicast target and sends to the device's currently configured Broadcast address.
Any non-Manual showCUE/IO uses all valid addresses in the global Art-Net unicast targets list. One or more valid targets means Unicast only—no duplicate Broadcast packet is sent. With zero valid targets, output falls back to the currently configured Broadcast address.

For a Manual show, open PLAYER → Manual show, or choose Edit on an existing Manual show, then use Art-Net output → Unicast to one IP address → Target IP address and press Save and generate show. For global routing, open Settings → Network → Art-Net unicast targets, enter one IPv4 address per line and press Save Ethernet and Art-Net. Leave that list empty to use only Settings → Network → Broadcast address.

Addresses are device configuration, not documentation constantsThe values displayed by your CUE/IO unit are authoritative. Any numeric address in an example, screenshot or public demo is explicitly sample or TEST-NET data and must not be treated as the device's current Broadcast address or unicast list.
A listed device is not automatically a working deviceA cable can be disconnected or another program can hold an audio interface. Always use the test and check Status before recording.

05 · Automatic operation

Automatic startup, Show Sequence and recovery

In Settings → Startup, choose exactly one action for the moment CUE/IO becomes ready after power-on or a restart.

Startup actionWhat happens
Do nothingCUE/IO remains idle until an operator selects a mode.
Show SequenceCUE/IO enters PLAYER mode and follows the saved startup sequence.
Wait for timecodeCUE/IO enters TIMECODE mode, prepares the configured audio path and listens for LTC.

Show Sequence

Power OnCUE/IO starts, checks readiness and prepares PLAYER resources.
WarmupOptionally play one warmup show before the main show.
WaitPause for the selected number of seconds after Power On or Warmup.
Main ShowPlay the required main show.
LoopOptionally repeat Main Show until an operator presses Stop or changes mode.
FinishClose PLAYER audio, Art-Net and files when the sequence ends or is stopped. This stage does not power off the Raspberry Pi.

Automatic Timecode startup

Before selecting Wait for timecode, enable the Timecode configuration, choose the LTC audio input, make sure every enabled cue refers to an available show, and select an audio output when any cue has audio. If CUE/IO starts after a cue has already begun, it waits for the next cue instead of jumping into the middle of a show.

After an unexpected restart

CUE/IO does not resume an incomplete recording. It preserves saved configuration and reports the previous reason and error in Status. Enabled Scheduler work and explicitly configured startup or Loop behaviour can continue only when the required show, licence, devices and network are ready.

Test unattended startup with the real equipmentPower-cycle only during a planned test, then confirm the selected mode, audio output, Art-Net interface, system time and next Scheduler action.

06 · Hardware controls

GPIO and device safety

Settings → Device contains disk safety limits and system controls. Settings → GPIO can assign physical Raspberry Pi buttons to supported show actions.

Storage and system

  • The minimum free-space limit blocks a new recording.
  • The critical limit safely stops an active recording.
  • Restart CUE/IO restarts the application only.
  • Restart or Shut down Raspberry Pi affects the whole device.

GPIO buttons

  • Use the correct BCM pin and HIGH or LOW active level.
  • Select the action and show, then set debounce to prevent repeated presses.
  • Use protection options when buttons must not interrupt recording or playback.
  • Test every mapping with a safe test show while all modes are stopped.
GPIO is 3.3 V hardwareUse only a correctly built Raspberry Pi button circuit. Shut down and remove power before adding or moving wires; never feed 5 V into a GPIO pin.

07 · Create shows

RECORD mode

RECORD mode captures lighting packets and, when enabled, audio in the same session. Timecode and Player remain stopped while recording.

Choose RECORDSelect the RECORD mode card and enter a clear show name.
Prepare inputsSelect the audio input, enable or disable audio, and select the Art-Net network interface.
Choose the start conditionStart immediately, wait for the first DMX packet, or use the configured DMX channel trigger.
Start recordingCUE/IO checks the device, interface and free disk space before it begins.
Watch the indicatorsConfirm duration, universes, packets per second, file size, free space and the audio waveform.
Stop safelyPress Stop Recording and wait for confirmation before changing mode or removing power.

DMX channel trigger

Choose one universe and channel, then set a start value and a lower stop value. The gap prevents rapid switching when the signal moves near the threshold. The live value monitor in the upper corner helps verify the chosen channel before use.

Audio enabled but unavailableThe recording will not start if audio is enabled and the selected input cannot be opened. Select a working input or turn audio recording off deliberately.

08 · Synchronisation

TIMECODE mode

Use TIMECODE when playback or recording must follow an external time reference. CUE/IO prepares and checks the audio device before it waits for timecode.

Open TimecodeSelect the input source, format and the show or recording action.
Check readinessAudio input, selected device and timecode signal status appear in the main Timecode section.
ArmPress Prepare/Arm. The status changes from Not armed to Waiting for timecode.
Send timecodeWhen a valid signal is detected, CUE/IO displays it and starts the configured operation.
Stop or cancelUse Cancel while waiting, or Stop while running. Changing mode also closes the listener safely.
StatusMeaning
Not armedNo timecode input is active.
Armed / WaitingInputs are ready; CUE/IO is waiting for a valid signal.
DetectedA valid signal and frame rate are visible.
Recording / PlayingThe configured operation is active.
ErrorOpen the visible message and Status details before retrying.
If timecode disappearsObserve the mode status instead of immediately restarting. The configured signal-loss behaviour determines whether the show waits, stops or resumes when the signal returns.

09 · Playback

PLAYER mode

PLAYER sends the recorded Art-Net data and synchronized audio to the selected outputs. It prevents two shows or audio players from running at the same time.

  1. Select PLAYER and choose a show from the list.
  2. Confirm duration, audio status and universe count.
  3. Set Loop, volume and Mute as needed, then press Play.
  4. Use the progress bar and position display to follow playback.
  5. Press Stop before disconnecting outputs or shutting down.

Selecting another show during playback safely stops the current show, closes its audio and Art-Net resources, then starts the selected show. Volume changes do not modify the original audio file and do not restart playback.

Pause availabilityPause is shown only when the active audio/output method supports it reliably. Stop is always available and releases the resources.

09A · Multi-show playback

Playlists

A playlist plays saved shows in a fixed order and repeats each show an exact number of times. For example, Show A × 10 → Show B × 5 always plays A ten times, then B five times. You choose whether to stop there or repeat the whole playlist.

CreateOpen PLAYER, switch the library from Shows to Playlists, choose New playlist and give it a clear name.
Add and orderAdd saved shows, set the repeat count for each row, and move rows up or down into the required running order.
Choose the endingAt the bottom, leave Repeat the whole playlist off to stop after the final show, or enable it to begin the complete sequence again from the first show.
Save and editSave the playlist. Reopen Edit whenever you need to change its name, shows, order or repeat counts.
Start and followPress Play on the playlist card. PLAYER shows the current show, its current repetition and overall playlist progress.
Stop safelyPress Stop playlist to finish the current Player session, close audio and Art-Net resources, and prevent the next item or complete playlist cycle from starting.
DeleteStop an active playlist first, then delete its saved definition from the playlist actions.
LimitAllowed value
Saved playlistsUp to 100
Playlist name1–100 characters
Rows in one playlist1–64 shows
Repeats for one row1–1,000
Total repetitionsUp to 10,000 per playlist

The normal Player Repeat button does not control playlists. The playlist's own whole-sequence switch is saved with its definition. Playlists remain after a CUE/IO update or Raspberry Pi restart, but playback is intentionally not resumed automatically after a restart: an operator must start it again.

Validation happens before playbackCUE/IO checks the complete playlist and every referenced show before starting. A missing, deleted or invalid show, an out-of-range repeat count or a conflicting active mode produces a clear error and does not interrupt an already running show. Stop recording, Timecode, Benchmark or other Player work before starting a playlist.

09B · Calibration

Audio and DMX synchronization

DMX playback offset (ms) is applied when a PLAYER playback session starts. Saving it does not require a Raspberry Pi or application restart. Stop the current playback and press Play again to use the new value.

ValueResult
0 msKeeps the recorded timing unchanged.
Positive, for example +100 msSends DMX 100 ms later than audio.
Negative, for example -350 msSends DMX 350 ms earlier than audio. Use this as a starting point if the light appears about 350 ms after the sound.

Calibrate the output

  1. Use a short test cue with an audible click and a clearly visible light flash.
  2. Stop playback, adjust the offset in 20–50 ms steps, then press Play again.
  3. Check several points in the show before keeping the value.

Latency can come from the audio interface and its ALSA buffer, a DAC or audio processor, the loudspeaker signal path, the Art-Net node or switch, fixture response, and the physical network path. Recalibrate after changing the audio interface, output device, Art-Net node, network equipment, or buffer settings.

Why file durations can differArt-Net duration is the timestamp of the last valid recorded Art-Net packet. It can be shorter than the audio when the console stops transmitting or holds its last value. This difference alone does not prove dropped packets or a synchronization fault. Also check the dropped-packet and sequence-error counters and verify real playback.

10 · Library

Show files, audio management, backup and trimming

The file manager shows each show’s name, creation date, duration, size, universes, audio availability and audio file name.

Organise

  • Rename or duplicate
  • Delete an unused show
  • Import or export a complete show

Download

  • Complete show archive
  • Art-Net data only
  • Audio only, when available

Add, replace or remove show audio

Open Manage audio in a show’s action menu to attach sound even when that show was originally recorded without audio, or to replace or remove its existing track. CUE/IO accepts ordinary local MP3, WAV, FLAC, M4A/AAC, OGG/Opus and AIFF files and creates a playback-ready WAV copy; the source file is not modified.

Start delay inserts silence before the sound. Match show length crops or pads the end with silence while preserving the existing timeline; Keep full audio retains the complete track and delay, so it may change the total show length. Neither mode changes speed or pitch. If no reliable DMX timeline is available, use Keep full audio.

CUE/IO creates a durable backup before every addition, replacement or removal, publishes the change atomically and leaves the show’s Art-Net data unchanged. A rejected upload or conversion failure leaves the previous show usable. Stop Record, Player and Timecode before processing audio.

Trim a show

Open the show action menu and choose Trim. Move the start and end handles, preview the selected section with lighting output and audio, then apply the trim only after you are satisfied. Art-Net and audio are trimmed to the same boundaries to keep synchronization.

A backup is created firstCUE/IO preserves a recoverable copy before rename, trim and other modifying operations. Still keep important exported shows outside the Raspberry Pi.
Do not edit active filesA show that is recording or playing cannot be deleted or modified. Stop the active operation first.

Edit a complete manual show

For a manual show, choose Edit to reopen the same complete builder used for creation. You can change the name, Broadcast or Unicast output, fixed scenes, duration, every Effect Generator parameter, palette, ordered fixture list, address and pattern, or convert between a fixed-scene show and an effect. Saving rebuilds the files safely while preserving the show ID, creation identity and playlist references. A title-only edit keeps the saved Basic or Effect builder, Art-Net output mode and target IP, fixture order, effect settings and audio choice unchanged.

To branch a Manual show without changing it, choose Duplicate (the copy icon) on its PLAYER card. The new independent show receives a new ID and a localized — copy title, numbered automatically if it collides, while retaining the complete Fixed Scenes or Effect Generator settings, audio, Broadcast/Unicast route and target, ordered fixture patch, addresses and fixed channels. The source and all existing playlist references stay unchanged; the copy is not inserted into a playlist automatically.

When a fixed-scene or Effect Generator show already contains audio, choose Keep, Replace or Remove. Keep reuses the stored audio; Replace requires a new file; Remove creates a silent show whose total duration comes from the duration field. The same choices remain intact when switching the editor between fixed scenes and effects.

Create and test a fixed-scene show

Open Files → New manual show → Manual show, enter the universe, FPS, start/middle/end channel values and timings, then either choose audio or enter the total silent duration in seconds. Start live test is available for both fixed-scene and effect forms before saving; it always tests DMX without audio and remains subject to the bounded live-output safety described below.

Busy errors include the safe next actionIf this same show is currently running, the error panel displays Stop show on its right so you can stop it without leaving the editor. That action appears only for a real runtime conflict; an edit already being saved reports that the builder is busy and does not offer a global Stop.

10A · Manual show creation

Effect Generator

Open Files → New manual show → Effect Generator to create a reusable Art-Net animation without recording a console.

Effects

  • Static — fixed palette colours.
  • Pulse — smoothly breathes brightness.
  • Chase — moves a lit head and tail.
  • Rainbow — flows palette colours with a selectable character.
  • Unique random — reshuffles pairwise different non-black RGB values across all fixtures.
  • Forest harmony — slowly drifts 1–4 selectable compatible saturated hue families, with a separate tone for every fixture.
  • Random — lights deterministic random-looking groups.
  • Rain — moves colour drops and tails.
  • Wave — creates flowing brightness and colour crests.

Controls

  • The built-in library contains only Generic RGB (3 channels) and RGBW (4 channels); choose a quantity to add multiple pixels at once, or add custom profiles one at a time.
  • Set the first DMX channel and choose among 15 ready-made palettes. The ten new cohesive presets are Sunset, Ocean, Neon Night, Aurora, Forest, Gold + Violet, Candy, Pastels, Fire + Ice and Tropical; they contain 3–10 colours. A custom palette supports 1–16 addable, removable and reorderable colours.
  • Shape the selected effect with Intensity, Speed, Amount, Spacing and Variation.
  • Pattern number makes random-looking output repeatable; New variation creates another pattern.
  • Generation uses a fixed 30 FPS. Uploaded audio determines the duration; a silent effect uses the entered 0.1-second to 1-hour duration.

Preview and save

  1. Select the effect, addressing, palette, intensity, speed, amount, spacing and variation, then upload audio or enter a silent duration.
  2. Use the visual preview to check the general movement and colour order.
  3. Add fixtures in their physical order, then open the DMX address report and verify every profile, mode, start/end address and absolute fixed-channel address.
  4. Use Start live test for a short physical check, then save the show.
Visual preview and live test are differentThe visual preview is a simplified browser-only animation and sends no Art-Net. Start live test uses the real Raspberry Pi output path and the selected Broadcast or Unicast destination for 0.1–30 seconds. It sends no audio, creates no show, never appears in Files, and Stop, normal completion or an error sends a blackout.
Audio is optionalAn uploaded audio file is converted to the canonical WAV format and its measured length becomes the effect and Art-Net duration, up to one hour. Without audio, enter the silent duration. When editing, audio can be kept, replaced or removed. Start live test deliberately remains audio-free.
Ready-made or customThe pure RGB palette remains exactly red #ff0000, green #00ff00 and blue #0000ff. The ten new presets provide harmonious 3–10-colour combinations, while Custom supports 1–16 colours.
Quick character variants are editable starting pointsEach effect offers three tailored variants that set only its meaningful Speed, Amount, Spacing, Variation and/or Pattern number values. Intensity, palette, fixtures, audio, output, Forest families and the separate Rainbow character stay unchanged. Moving an owned control afterwards changes the status to Custom settings. Static variants do not change unused Speed; Unique random variants change only Shuffle speed and Pattern number.
Choose how Rainbow flowsRainbow offers Classic, Flow, Reverse flow, Bounce and Mirror characters. New shows start with Flow; an older show without a saved character opens as Classic and retains the previous Rainbow bytes. For Flow, Reverse flow, Bounce and Mirror, Amount sets palette-repeat density, Colour transition length sets the fade window from a hard 0% change to a full 100% linear segment, and Gradient offset plus Pattern number selects a repeatable whole-gradient start. Flow, Reverse flow and Mirror speed is rotations per minute; Bounce speed is full outward-and-back journeys per minute. These characters require 2–100% intensity and create pairwise-distinct, non-black reconstructed 8-bit RGB triples in every transmitted frame. This is a DMX-data guarantee, not a promise of visibly different hues: black, duplicate or very similar palette entries can use small neighbouring DMX corrections that real fixtures may render alike.
Forest harmony supports one to four colour familiesSelect Canopy, Glow, Accent and/or Depth; CUE/IO keeps that canonical order and alternates the selected families through the physical fixtures. The legacy Canopy + Depth pair remains byte-identical and may start with either family according to Pattern number. The first chromatic palette colour is the anchor; later palette stops remain saved but are not interpolated, and an all-gray palette falls back to teal. Family contrast maps to a 100–135° safe arc from Canopy to Depth, with Glow and Accent at its one-third and two-thirds positions. Hue spread maps to a complete 12–32° spatial spread, and Organic drift to a slow 4–20° out-and-back movement. With one selected family, the requested Hue spread slider still spans 12–32°, but DMX allocation uses a 13.125° internal minimum solely to retain enough unique reconstructed RGB triples for up to 170 fixtures; the slider value itself does not change. Speed is 1–4 complete drifts per minute, Intensity is 10–100%, and Pattern number makes the anchor, orientation and fixture tones repeatable. Every transmitted frame gives each fixture its own saturated reconstructed RGB triple, and the generated duration closes at its starting drift position. In the integer-DMX additive RGB model, neither any two-fixture channel sum nor the full fixture-set sum has ΣR = ΣG = ΣB; no equivalent claim is made for arbitrary weighted mixtures or subsets. Real LED spectra, lenses, calibration and RGBW optics may render nearby tones alike or make some mixtures appear whitish.
Unique random never duplicates a fixture colourIt samples one colour per fixture evenly across the selected palette, adjusts any quantized collision to the nearest free non-black RGB value, then reshuffles that same unique set at the selected number of changes per minute. It uses Palette, Shuffle speed, Intensity and Pattern number; Amount, Spacing and Variation are hidden. Intensity starts at 2%, which provides enough different emitted RGB values for all 170 supported fixtures. A single-colour or duplicate palette still works, although nearby shades are added to preserve the guarantee.

Fixture profiles and fixed channels

The fixture library lets one effect combine different real DMX fixtures while keeping selected support channels at fixed values. For Generic RGB/RGBW, use −/+ to choose a pixel quantity and add the bounded group at once; custom profiles add one at a time. Add up to 170 fixtures in their physical order and move or remove rows as needed. Starting at the chosen first channel, CUE/IO assigns each profile's complete footprint contiguously and prevents a group from passing channel 512. The address report lists every fixture's order, profile, mode, universe, start/end address and absolute fixed-channel addresses.

A custom profile requires Red, Green and Blue mappings, may include a White mapping, and may add other non-colour channels with fixed values from 0 to 255. A colour channel and fixed channel cannot overlap. Select one of your profiles and press Edit to reopen every field; revision protection prevents an older browser tab from silently overwriting a newer change. Mixed RGB and RGBW rows are supported; fixed slots are written at their absolute assigned addresses in every generated frame.

Custom FOS F-7 exampleChannel mappingUse
3ch RGBCH1 Red, CH2 Green, CH3 BlueSmallest direct RGB mode
4ch RGBWCH1 Red, CH2 Green, CH3 Blue, CH4 WhiteSmallest direct RGBW mode
6ch RGBW — recommendedCH1 Shutter = 10, CH2 Master = 255, CH3 Red, CH4 Green, CH5 Blue, CH6 WhiteExplicitly opens the shutter and keeps the master dimmer at full

The mappings above follow the FOS F-7 manufacturer manual and can be entered as your own profile; FOS profiles are not built-in library choices. Always confirm that the fixture itself is set to the same DMX mode before testing.

  1. Choose Generic RGB/RGBW, or create a custom profile with its full channel footprint.
  2. Map Red, Green and Blue, optionally map White, then add only the fixed channels the fixture needs.
  3. Add one row per physical fixture in installation order. CUE/IO calculates contiguous addresses from the first DMX channel; confirm the complete address report before output.
  4. Run a brief live test or save and use PLAYER. Fixed values are output in every frame only while that output runs; Stop and normal end-of-file output a blackout, including those channels.
Saved shows keep every mappingCUE/IO stores each ordered profile and immutable channel-layout snapshot inside the generated show. Deleting or changing the library profile later does not break playback or full editing of that existing effect.
One complete 512-slot universe is writtenEvery frame contains all 512 channels; only the mapped RGB/RGBW and fixed profile channels are driven, and all other channels are set to zero. Use a dedicated universe unless deliberately blacking out every other channel in that universe is safe.

File operations

A generated effect can be fully edited, renamed, played, trimmed, duplicated, exported and imported like another CUE/IO show. Edit restores all generator controls, the ordered fixture layout and saved snapshots; its stable show ID keeps playlist references intact.

Validation opens the exact place to fixIf a required field is missing, CUE/IO switches to the correct builder tab or custom-fixture editor, highlights and focuses that field, and shows a translated explanation instead of the browser's generic “Please fill out this field.” message.

11 · Automation

Scheduler and DS3231 RTC

The Scheduler can play a show at a specific date, on chosen weekdays, daily, on workdays or on weekends. Select a start time, end time or duration, optional Loop, and enable the schedule.

  1. Open Scheduler and add a schedule.
  2. Select the show and recurrence rule.
  3. Set start and end conditions and choose Loop if needed.
  4. Save, enable it and verify the displayed next action.

Conflicting schedules should be resolved before activation. After a restart, enabled schedules remain available.

RTC

A supported DS3231 real-time clock lets the Raspberry Pi retain time without internet. CUE/IO displays RTC status. When reliable network time is available, the system can refresh the RTC; without RTC, the application still works but offline schedules may use an incorrect time after power loss.

Verify time before an unattended installationCheck the current time, time zone, RTC status and the Scheduler’s next action after installation or hardware service.

12 · Connectivity

Network, local address and rescue Wi-Fi

CUE/IO supports Ethernet, Wi-Fi and compatible USB Ethernet interfaces. You can use one Ethernet connection for Art-Net and internet, or separate Art-Net and internet traffic across different interfaces.

Device identity

Under Settings → Device → Device profile, give every unit an operator-friendly Device name and press that card's Save device name button. It appears in the browser title, desktop dashboard and sidebar, mobile header and local Licence card. The general Settings save button does not save a pending name. A factory or migrated value can initially match the hostname, so the operator—not CUE/IO—must assign distinct names when several units are used.

The Device name does not change the network address or immutable Device ID. The technical hostname and exact local URL remain separate read-only details in the profile card.

Local mDNS address

The .local address is a friendly name discovered inside the local network. It does not expose CUE/IO to the public internet. If the name is not found, use the current IP address instead.

To change the address, open Settings → Network → CUE/IO management access, enter a technical Local .local address name (hostname) and press Save access settings. That one management-access action saves the hostname and the complete adjacent fallback Wi-Fi configuration together. Open the clickable http://<hostname>.local/ address shown by CUE/IO. This does not change the human-readable Device name. Ethernet and Art-Net changes use the separate Save Ethernet and Art-Net action.

Rescue Wi-Fi access point

The optional rescue access point provides a local path to the web interface when the normal LAN address is unknown or a network change failed. It is for local setup and recovery, not a replacement for venue internet.

  1. Open Settings → Network → CUE/IO management access.
  2. Select an available Wi-Fi interface, enter an SSID and set a passphrase containing 8–63 characters.
  3. If that Wi-Fi interface already provides internet or Art-Net, use a separate compatible Wi-Fi adapter for the rescue access point.
  4. Apply the settings and confirm that the displayed rescue Wi-Fi status is Active. An enabled setting alone does not prove the access point is running.
  5. Write down the SSID and exact recovery URL shown by CUE/IO. The passphrase is write-only and is never displayed: write down a new passphrase before applying it. A blank WPA2 field preserves the configured passphrase, a new value replaces it, and selecting Open removes it.
  6. To recover access, join that SSID on the phone or computer and open the displayed URL. This Wi-Fi may have no internet connection; that is normal.
Apply network changes carefullyCUE/IO validates and saves the selected network settings immediately; there is no confirmation period or automatic rollback. Keep the browser open, then reconnect using the new IP or the exact <hostname>.local address shown under Management access. If that route is unavailable, use an already-active rescue Wi-Fi and its displayed recovery URL to correct the settings.

Static IP checklist

  • IP address is not already in use.
  • Subnet mask matches the Art-Net network.
  • Gateway and DNS are valid when internet is required.
  • Broadcast and optional unicast targets are correct.
  • You know both the local name and the assigned IP before leaving the site.

13 · Live data

Live DMX monitor

Use Monitor to confirm that Art-Net reaches CUE/IO before recording or playback. Select a universe to view channel values and live movement. The packet view helps identify the receiving interface, active universes and whether data is changing.

  • A moving graph confirms recent DMX changes.
  • A stable value is normal for a channel that is not changing.
  • No universes usually means the wrong interface, address, subnet or sender configuration.
  • The selected trigger channel can also be monitored directly in RECORD mode.
Monitor is a diagnostic viewDo not use it as the only acceptance test for a show. Always verify the physical fixtures and audio output.

14 · Capacity

Benchmark

Benchmark generates test Art-Net traffic, records or plays it, compares the data and measures load. Choose FPS, duration, audio on/off and the desired test type.

The levels test 1, 4, 8, 16, 32, 64 and 128 universes. The final screen reports Benchmark Complete, a recommended universe count and any higher level that exceeded safe limits.

Use the recommended valueA level is considered safe only when packet loss is zero, audio has no errors and CPU and temperature retain enough reserve.
A local benchmark has limitsA test generated inside one Raspberry Pi does not fully test physical Ethernet switches, cables, nodes or traffic from a real lighting console. Test the complete venue network before production.

15 · Health

Status and diagnostics

Status provides a low-overhead live overview of the system, Art-Net, audio and the application.

AreaWhat to check
SystemCPU, RAM, temperature, disk space and uptime.
Art-NetActive universes, packets per second, dropped or sequence errors and selected interface.
AudioInput/output device, sample rate, channels, underrun, overrun and synchronization offset.
ApplicationCurrent mode, show, last error, version and service health.

A short CPU spike when starting or stopping is normal. A steadily rising memory, thread or open-file count, repeated restarts, increasing dropped packets or audio errors require investigation.

Reporting a problemNote the exact local time, active mode, show name, what you pressed and the full visible error. Send this information to info@cueio.app.

16 · Maintenance

Safe online updates

  1. Export a backup of irreplaceable shows, then stop recording, Player, Timecode, playlists, Benchmark, any live test and every file operation.
  2. Open Settings → Updates, press Check again and review the installed and available versions.
  3. Press Install update once. Keep power and internet connected and wait for the final result; do not restart the application, reboot the Raspberry Pi, reload repeatedly or start another operation.
  4. After success, confirm the displayed version, Status health, important settings and one safe short playback test.

CUE/IO verifies the signed release information and downloaded package before activation, then checks the new release's health. If that check fails, it attempts to return to the previous working release and reports the result. Normal updates preserve shows, playlists, configuration, licence state, fixture profiles and the service event journal.

“Another update operation is already in progress”Do not press Install repeatedly or remove power. Leave the page open, wait for the current operation to finish, then press Check again. If it remains unchanged after the application has fully restarted, record the exact time and message for support.
An active live test also blocks installationStop the test and wait for its blackout and stopped state before installing. Never update while fixtures or audio are in an unsafe state.

17 · Interface language

Languages and adding a translation

Use the flag menu at the top of CUE/IO to search for and select a language. The choice is saved in that browser. Latvian and English are included.

Download the templateOpen the language menu and choose Download translation template. It contains every current text key.
Set the language detailsIn _meta, change the code, name, flag and text direction when needed. Use a code that is not already installed.
Translate values onlyKeep every JSON key and placeholders such as {count} or {name} unchanged. Save as UTF-8 JSON.
Add the translationChoose Add translation and upload the completed file. CUE/IO validates its format and required keys before installation.
Keep the template private until it is completeA translation file contains interface text, not licences or device configuration. Do not add passwords, activation codes, customer data or support diagnostics to it.

18 · Activation

Licence and device change

One CUE/IO device licence is activated for one Raspberry Pi. The device normally needs internet access only during activation and periodic licence reconciliation when it later reconnects.

Activate

  1. Sign in to the customer portal and open My licences.
  2. Reveal the current activation code. You can return to the account and view it again while it remains valid.
  3. Connect the Raspberry Pi to the internet.
  4. Open Licence, enter the activation code and confirm.
  5. After a successful result, CUE/IO can operate offline.

Replace a failed Raspberry Pi

In My licences, detach the licence from the previous device and create or reveal the fresh activation code, then activate the replacement device and import your show backups. If the self-service controls are unavailable, contact info@cueio.app with the licence identifier and purchase details.

Remove the local licence

Any operator with access to the local CUE/IO interface can use Settings → Licence → Remove local license…. Confirming always puts CUE/IO into Idle, so an active RECORD, TIMECODE or PLAYER operation is stopped. It removes only the local licence state: Device ID, local device key, Device name, shows and settings are preserved, and the portal licence is not released, revoked or moved.

Keep a local path before remote removalLocal licence removal closes this device's remote-access tunnel within about one second. If you are using the portal, arrange LAN or other local access before confirming; the closed remote session cannot be used for reactivation.

An already-used activation code can be entered again only on the same preserved Device ID and local device key while that server licence and its generation remain active. After a portal transfer, the old code is invalid and the new transfer-issued code is required. After a full revoke, that licence cannot be reactivated; use another active licence.

Do not clone an activated storage cardA copied card does not create a second valid licence. Device identity and licence reconciliation are designed to detect unsupported cloning.
Open customer licences

19 · Solutions

Troubleshooting

ProblemSafe checks
Page does not openCheck power and link lights, confirm the phone is on the same network, try the current IP address, then use rescue Wi-Fi if enabled.
No Art-Net dataCheck the selected interface, sender IP/subnet, cable and console output. Confirm at least one universe in Monitor.
Audio device unavailableStop the active mode, reconnect the USB device, refresh the list and select it again. Test before recording.
Recording cannot startCheck free disk space, audio readiness, network interface and that no other mode is active.
Timecode keeps waitingCheck source, input, signal level and timecode format. Cancel and arm again after correcting the source.
Playback has no sound or lightCheck show metadata, audio output, Mute/volume, Art-Net output interface and unicast targets.
Schedule starts at the wrong timeCheck system time, time zone, RTC status and the displayed next action.
Low disk spaceExport important shows, remove unwanted files and temporary data, then verify the free-space indicator.

If the error repeats, do not repeatedly remove power. Record the details from Status and contact info@cueio.app.

20 · Power

Safe shutdown

A Raspberry Pi writes configuration, logs and show data to storage. Removing power during a write can damage files.

Stop the active operationStop recording, Timecode waiting/recording or Player and wait for the stopped state.
Use ShutdownOpen the device/system controls and choose the safe Shutdown action.
WaitWait until the interface confirms shutdown and device activity has stopped before disconnecting power.
Never unplug during recording, update or file operationUnexpected power loss can leave the current show incomplete. A proper backup protects important installations.