Solution
An AV control system you can configure instead of program
Cueva Control is an AV control system built on open protocols. Draw the logic, deploy it to the RELO IO8, and run meeting rooms and venues without a programmer.
Why AV control usually means a programmer
The established control systems are capable and proven. They are also closed. The processor, the touch panels, the configuration software and often the programmer all come from the same channel, and every change to a room goes back through it.
For a large campus with a dedicated AV team that can be the right trade. For a meeting room, a museum gallery or a bar with three screens and a projector, it is a lot of system for a short list of jobs.
How Cueva Control does it
The RELO IO8 is the controller. It has eight relays and eight inputs for the things that need a contact, and it talks TCP, UDP, HTTP, OSC, Art-Net and RTP MIDI to everything else on the network. The logic is a flow you draw in Cueva Desktop and deploy to the device, where it runs on its own.
- One button press: screen down, projector on, lights to a scene, DSP preset recalled
- Schedules: rooms that power down at night without anyone remembering
- Feedback: read device state back into the flow and act on it
- Remote: check every room from Cueva Horizon, without a VPN
Open protocols, no lock-in
Everything the RELO IO8 sends and receives is a documented, open protocol. It works with the displays, DSPs, lighting consoles and media servers you already specify, and with Bitfocus Companion and a Stream Deck when an operator wants buttons.
A meeting room touch panel on any iPad
Cueva Interface Builder, coming soon to Cueva Desktop, lets you design the room's touch panel yourself: buttons, faders and live feedback, laid out for a tablet and a phone. You upload it to the RELO IO8, and any iPad, iPhone or Android device on the same network runs it in the Cueva Interface app.
Behind every button is a relay or a flow, so the panel reaches the projector, the DSP and the lights through the same logic as the wall button.
Wiring schedule
Meeting room AV, port by port.
One button drops the screen, powers the projector, sets the lights and tells the DSP which preset to load.
| Port | Connected to | Behaviour |
|---|---|---|
| Input 1 | Wall panel button | Dry contact, press |
| Relay 1 | Screen controller input | Toggle |
| Relay 2 | Projector contact input | Pulse 500 ms |
| HTTP | DSP | POST /preset/meeting |
Questions
Common questions.
No. Flows are built by wiring nodes on a canvas: a trigger, optional conditions and timing, and actions. If you can read a wiring schedule you can build one.
For rooms where the job is switching, sequencing and sending IP commands, often yes. For large systems that rely on a vendor's own touch panels, video switching and certified ecosystem, it is better as an addition than a replacement.
With a wall button or keypad on the inputs, a Stream Deck through Bitfocus Companion, any device that sends TCP, UDP, HTTP or OSC, or a schedule. A touch panel designer is coming in Cueva Interface Builder.
The flow keeps running on the controller. Physical inputs and relays work without a network, and the unit has two power inputs so a single supply failure does not take it down.
Start with one. Scale when you need to.
Order the RELO IO8 from our store, or talk to us about your project.