QSC Q-SYS — Networked AV Platform Overview
Q-SYS is QSC's software-defined audio, video, and control platform. Unlike traditional AV systems where DSP, control processor, video switcher, and conferencing codec are separate boxes from different vendors, Q-SYS consolidates these functions into a unified system built on standard IP networking. A Q-SYS Core processor handles audio DSP, room control logic, video processing, and conferencing endpoints simultaneously, all configured through a single software environment.
Q-SYS Core Processor Lineup
| Model | I/O | Max Channels | Target Use |
|---|---|---|---|
| Core Nano | 4 mic/line in, 4 out | 32 audio channels | Small rooms, single-room conferencing |
| Core 110f | 8 mic/line in, 8 out | 128 audio channels | Medium rooms, up to 2 Dante domains |
| Core 310f | 32 mic/line in, 16 out | 256 audio channels | Large spaces, multi-room systems |
| Core 510i | 64 mic/line in, 32 out | 512 audio channels | Campus-scale systems |
| Core 5200 | 128 mic/line in, 64 out | 1024 audio channels | Enterprise headquarters, large venues |
All Cores include Dante built in — no add-on card required. Dante inputs/outputs count toward the total channel budget. Cores also have AES3 I/O, analog I/O, and USB audio for direct computer connections.
Q-SYS Designer Software
Q-SYS Designer is the configuration, programming, and commissioning environment for Q-SYS. It runs on Windows and Mac and connects to Q-SYS Cores over the network in real time.
The design environment is graphical: audio processing components (EQ, compressor, AEC, matrix mixer, Dante I/O) are placed on a canvas and wired together with signal flow connections. Control components (UCI controllers, event scripts, external control triggers) are placed alongside audio components in the same design.
Emulation mode — Q-SYS Designer includes a full software emulator. Designs can be built and tested completely offline before touching hardware. Control scripts, UCI layouts, and audio processing chains all run in the emulator.
Deployment — Completed designs are pushed to the Core over the network. The Core stores the design and runs it on every boot. Design changes take effect in real time when pushed to a running system.
Dante-Native Audio
Every Q-SYS Core includes a full Dante implementation. Dante channels appear as components in the design canvas, allowing direct routing of Dante streams to/from any audio processing block. A Q-SYS system with 20 Dante-enabled microphones, amplifiers, and processors connects entirely over IP — no analog or AES3 wiring required between devices.
Q-SYS also supports AES67 mode for interoperability with non-Dante networked audio devices. See dante and aes67.
Plugin Ecosystem
Q-SYS has an extensive plugin library developed by QSC and third-party manufacturers. Plugins appear as components in Q-SYS Designer and handle communication with external devices via TCP/IP, RS-232, or IR.
Common plugin categories:
- Display control — Sony, Samsung, LG, Epson projectors (send power/input commands, read back status)
- Conferencing — Zoom Rooms, Teams Rooms, Cisco, Poly integration plugins
- Camera control — VISCA-over-IP PTZ control with pan/tilt/zoom feedback
- Lighting/shades — Lutron, Crestron Horizon, KNX
- Amplifier control — QSC amplifier monitoring and channel muting
- Security/access — Door contacts, card readers for occupied/unoccupied room modes
The Q-SYS plugin architecture means most device integrations require no custom code — the manufacturer-provided plugin handles the protocol.
Lua Scripting
For logic beyond what the graphical components provide, Q-SYS supports Lua scripting inside Script components. Lua scripts have full access to the Q-SYS API: reading and writing component properties, responding to events, making HTTP requests, parsing JSON/XML, setting timers, and sending TCP/UDP/RS-232 commands.
Common Lua uses:
- Parsing REST API responses from room booking systems (EMS, Robin, Condeco)
- Conditional logic ("if room is occupied AND camera detects motion AND no calendar booking, send alert")
- Custom TCP/IP protocol implementations for devices without published plugins
- Scheduled tasks (daily reboot, overnight preset recall)
Lua scripts in Q-SYS are relatively approachable for integrators familiar with other scripting languages. QSC provides a Lua API reference in Q-SYS Designer help.
Video Processing — NV-32-H
The NV-32-H is a Q-SYS network video card that adds HDMI video routing and encoding to Q-SYS systems. Installed in a Q-SYS Core chassis slot, it provides 4K HDMI I/O that routes through the Q-SYS backplane alongside audio.
NV-32-H handles basic video switching, display output, and HDMI/HDCP management — sufficient for small to medium rooms. For large-scale video distribution, Q-SYS connects to third-party AV-over-IP solutions (Crestron NVX, ZeeVee, SVSi) via TCP/IP control.
Q-SYS as a Control System
Q-SYS is increasingly used as the primary room control system — not just audio DSP. UCI (User Control Interface) components create touchscreen interfaces that display on:
- iPads and Android tablets via the Q-SYS UCI Viewer app
- Dedicated Q-SYS touchscreen hardware
- Chrome-based browser panels
A Q-SYS Core can eliminate the need for a separate Crestron or AMX control processor in audio-primary spaces. Many integrators deploy Q-SYS as a complete AV control solution for conference rooms, lecture halls, and boardrooms.
Q-SYS Soft Codec
Q-SYS Soft Codec runs Microsoft Teams or Zoom directly on a Q-SYS Core, eliminating the need for a separate PC or codec appliance. The Teams or Zoom client runs as a Q-SYS component, receiving audio from the DSP chain and displaying video on connected screens.
Soft Codec reduces rack footprint and cost: one Core handles DSP processing, control, and conferencing simultaneously. Available as a licensed add-on per Core.
Q-SYS Reflect Enterprise Manager
Q-SYS Reflect is QSC's cloud-based monitoring and management platform for Q-SYS deployments. It provides:
- Real-time status of all Cores in a deployment
- Remote design pushes and firmware updates
- Alert rules (send email/SMS when a device goes offline)
- Inventory and licensing management
Reflect is comparable to Crestron XiO Cloud in scope and is required for enterprise-scale Q-SYS deployments.
Common Pitfalls
- Core channel budget exhausted mid-project — Dante channels, analog I/O, and internal processing all count against the channel license. Audit channel requirements before specifying a Core model.
- Emulator passes, hardware fails — The emulator does not simulate network timing, PTP clock behavior, or hardware I/O latency. Always test on hardware before commissioning.
- Dante domain isolation — All Dante devices a Q-SYS Core communicates with must be on the same Dante domain/subnet. Multi-VLAN Dante deployments require Dante Domain Manager. See dante.
- Plugin version mismatches — Q-SYS Designer version and Core firmware version must be compatible. A design built in Designer 9.x may not upload to a Core running firmware 8.x. Always update firmware before commissioning.
- AEC reference not wired in design — The loudspeaker output must be explicitly routed to the AEC reference input in the Q-SYS design. Forgetting this is the most common AEC commissioning error. See aec.