Control Values

Control Values connect named controls on a QSC Q-SYS or Symetrix DSP core — audio levels, source selectors, mutes — to the DMX Core 100’s own control points. Once defined, a Control Value can be driven from a control surface knob, a custom menu slider, an input trigger, a timeline track, or a script — with the current DSP state reflected back everywhere.

A typical install: a wall fader (via input trigger), a Stream Deck knob, and a custom menu slider all bound to the same VOL1 Control Value, which maps to a Symetrix volume controller. Move any of them — or change the volume from the DSP side — and every surface updates.

Web UI

Control Values are managed under Control & Integrations > Control Values. The DSP connection itself is configured in the DSP plugin’s settings on the Plugins page — see Q-SYS & Symetrix.

Kinds

Kind	Holds	Example
Level	A continuous 0–100% value	Room volume
Selector	One choice from a list	Source select (Input A / Input B / …)
Toggle	On or off	Mute

Settings

Each Control Value has:

• Code / Short Name — the identifier used in menus, triggers, timelines, and scripts (e.g. VOL1)
• Kind — Level, Selector, or Toggle
• Plugin — Symetrix or Q-SYS
• Controller Number — the controller number assigned in SymNet Composer (or the named control in Q-SYS Designer)
• Status Controller (optional) — read state from a different controller than the one written to. Use when a trigger writes one control but the real state is reported by another (e.g. a relay or wall panel)
• Step Size — how far Up/Down operations move a Level (default 5%)
• Linked Mute Controller (optional) — a mute controller linked to this level, with an optional Unmute On Level Change behavior

Operations

Anything that targets a Control Value can perform:

• Set value — a level percentage, a selector choice, or on/off
• Up / Down — step a Level by its step size, or move a Selector through its choices
• Toggle — flip a Toggle kind (or a linked mute)

Value-mode input triggers feed their numeric payload straight into a Level — optionally shaped by a transform script for response curves and dead zones. Timed ramps fade a level smoothly to its target instead of jumping.

Triggering From the DSP

Control Values also work in the other direction: a Control Value input trigger watches a Control Value and fires an action when it changes on the DSP side — a wall panel button plays a cue, a source selector landing on “Party” starts a timeline, a level crossing a threshold brings up the lights. Changes made from the DMX Core 100 itself never fire these triggers, so bound sliders and schedules can share the same Control Value without feedback.

Live State Everywhere

The current value is shown in the Control Values list and is pushed to every bound surface: LED colors on keypads, knob displays on a Stream Deck, OSC feedback to TouchOSC layouts, highlight states on custom menu items, and dmx.controlValue.get()/status() in scripts.