Installation and First Start
Supported platform
CUE/IO is designed for Raspberry Pi 4 or Raspberry Pi 5 running a 64-bit system. Use a high-quality microSD card of at least 8 GB, a stable power supply, and a wired Ethernet connection for the initial configuration.
Raspberry Pi 3, Pi Zero, and 32-bit systems are not supported targets.
Writing the CUE/IO image
Use only the CUE/IO image supplied by CUE/IO and its accompanying SHA-256 checksum. If you cannot verify the image source or checksum, do not write it to the microSD card; contact info@cueio.app.
Before writing the card, compare the downloaded file with the SHA-256 value in your customer account. All 64 characters must match exactly:
macOS: shasum -a 256 CUEIO_FILE.img.xz
Windows PowerShell: Get-FileHash CUEIO_FILE.img.xz -Algorithm SHA256
Linux: sha256sum CUEIO_FILE.img.xz
- Install Raspberry Pi Imager.
- Insert the correct microSD card into your computer.
- Select Choose OS → Use custom and choose the supplied
.img.xzfile. - Select the microSD card and press Write.
- Do not use the Imager customizations for hostname, user, SSH, or Wi-Fi.
- Eject the card safely after verification.
Writing the image erases all existing content on the microSD card.
First start
- Insert the microSD card while the Pi is powered off.
- Connect Ethernet and the USB audio interface, if you will use one.
- Connect power and leave the device powered on for several minutes. The first start may take longer than a normal restart.
- Connect a phone or computer to the same local network.
- Open this address in a browser:
http://cueio.local/
You do not need to specify a port. If the .local address does not open, find
the IP address assigned to the Raspberry Pi in your router and open
http://PI_IP_ADDRESS/.
If an available Wi-Fi adapter supports AP mode, a clean CUE/IO image starts an
open CUE/IO Setup fallback network. It has no password initially; this is
an intentional local recovery path for setup. Open http://10.42.0.1/ or
http://cueio.local/, then use Settings → Network → Management access
to enable WPA2 and set your own password. For self-installation from an IMG
file, initial configuration over Ethernet is recommended. If the fallback
network is not active, the Network section explains whether a separate Wi-Fi
adapter is required.
Access and maintenance credentials
Everyday users do not need Linux or SSH access. Maintenance accounts, passwords, and administrator codes are not published in the public guide. Only an authorized administrator should retain the device-specific access details; never send them by email, include them in screenshots, or distribute them with the CUE/IO image.
If first start does not complete or the control page remains unreachable after the safe checks, contact info@cueio.app. Do not try to change system files or maintenance accounts yourself.
Initial configuration
Before the first real recording:
- Settings → Audio: select the input and output, then run the audio test.
- Settings → DMX: check the protocol and DMX playback offset.
- Settings → Network: check the Art-Net interface, IP/broadcast address,
global Art-Net unicast targets,
.localaddress, fallback Wi-Fi status, and that the Art-Net port is not also reserved for fallback Wi-Fi or internet access. - Status: check storage, diagnostics, audio, and network warnings.
- Monitor: confirm that DMX packets are arriving.
- Record and play a short test show.
- Test Timecode, GPIO, Scheduler, and RTC separately before combining them in one installation.
Global targets under Settings → Network → Art-Net unicast targets apply
only to shows whose type is not manual: at least one valid address replaces
broadcast, while an empty list or no valid address restores the configured
broadcast. For a Manual show—fixed scenes, an effect, or an imported Manual
show—open Manual show or Edit in the PLAYER list and save that show's
own Art-Net output. It is authoritative: both a single show-specific
Unicast IP and show-specific Broadcast ignore the global list. Show origin does
not select this behavior; the stored show type does.
Updates and backups
Before an update, download important shows to another device from the Files section. CUE/IO checks the server after startup and then every six hours; the user does not need to enter an update password or access code. An operator can install an available update under Settings → Updates. Writing a new CUE/IO IMG file completely overwrites the existing card.
The complete .img.xz file is for a clean installation or recovery and erases
the entire microSD card. An OTA update under Settings → Updates upgrades
an existing CUE/IO installation while preserving shows, configuration, the
licence, playlists, fixture profiles, and the service-event journal; it
requires no SSH or Linux account. Stop Record, Player, a playlist, Timecode,
preview, or a manual live test before pressing Install update. The
installer rejects new work while the update is running and, on failure, keeps
or restores the previous healthy application release.
Transferring a licence to another physical Raspberry Pi is a separate action. See the licence instructions or use the support option in your customer account.