Q-SYS programming
for hire.
We write and fix the software layer for AV systems other people installed. Q-SYS, QLab, Bitfocus Companion. The call usually comes from an integrator or an end-user with a system that boots fine and breaks on show day.
The code, not
the cabling.
You have the hardware. We write the part that makes it usable: the plugins, the UCI, the cues, and the routing that holds when the staff turns over.
Custom Q-SYS Lua components for behavior the stock blocks can't do. Written to be read and maintained, not just to work once.
A control surface built for the operator who actually runs the room, not the installer who set it up. Fewer taps, fewer ways to break it live.
QLab cue stacks, Bitfocus Companion surfaces, OSC and MIDI between the consoles, switchers, and lights that should already be talking to each other.
We document an existing install, then fix what's brittle. Signal routing that survives staff turnover and a patch you can actually read.
You already know
the symptoms.
Fifty taps to do what should be one button.
A UCI built for the installer, not the person running the show.
Cues that fall apart on the third rehearsal.
An install nobody documented and nobody can safely touch.
How it works,
and what it costs.
Yes. Most of our programming work is on systems someone else installed. We audit the design file, document what's there, and rewrite the parts that break under pressure.
It depends on the system and how much is broken. A small UCI cleanup is a fixed half-day. A full control-layer rewrite is scoped per system. Send the design file and we'll quote it.
Yes. Custom Lua components, UCIs built for the operator who runs the room, and signal routing documented well enough that the next person can follow it.
A lot of it, yes. Design-file work, plugin development, and UCI builds happen remotely. Commissioning and anything that needs ears in the room, we do on site in LA and Orange County.
Send the
design file.
We'll tell you what's wrong with it and what the fix costs. No standard intake form.