Q-SYS Matrix Control Router

[2.5.0] - 2026-08-13

Added

• OutputNone pin — per-output "no source" feedback and clear: A new bidirectional pin per output reads True whenever that output carries no source, and clears the output when written True. It gives a UCI None/Off button both halves of its behavior in a single binding — lit when nothing is routed, clears the route when pressed. Like the Single Press grid buttons it does not toggle off: pressing it while already lit re-asserts, since "un-clearing" has no meaning. In Named Component mode with Component Feedback enabled it also tracks routes cleared externally, so every panel bound to the same mixer/router agrees.

Changed

• OutputSource now reports 0 instead of "None" when an output is unrouted. The pin is a text control, so its string is what downstream logic reads; "None" forced every consumer to special-case it before converting to a number. Reading back a bare 0 means tonumber() works unconditionally. The human-readable "None" is unchanged on OutputSourceName, which is the pin intended for operator-facing display. Migration: anything binding OutputSource directly to a UCI text label will now show 0 rather than None on an unrouted output — point those labels at OutputSourceName instead. Writing 0, "None", or an empty string to the pin still clears, unchanged.

Fixed

• Writing "None" to OutputSource re-routed the previous source instead of clearing. The handler fell through to the control's numeric .Value when the string would not parse, and that value still held the previous input number — so a clear command re-commanded the route it was meant to remove. The written string is now resolved first, and empty/whitespace strings clear as documented.
• Indicator refresh no longer re-commands routes. UpdateOutputSources() writes OutputSource, which is itself a writable pin; its handler fired on the plugin's own refresh and re-issued a route from stale state. The refresh now runs behind a re-entry guard, so the indicators report routing without also driving it.
• SetCrosspoint() now suppresses the crosspoint's own EventHandler while writing. Every caller applies gains and refreshes indicators itself, so the handler's work was redundant — and in Single Press / Dual Press modes its "no toggle-off from the grid" rule fought the clear paths, re-asserting buttons that had just been cleared.

[2.4.0] - 2026-07-24

Added

• Component Feedback (bidirectional sync) for Named Component mode: The plugin now subscribes to the linked Matrix Mixer/Router and reflects external routing changes back into its own grid. Several plugin instances (e.g. one per touch panel) can drive the same target and stay in sync — a route made on one panel appears on all of them, while each panel keeps its own independent arm state. On link, a feedback-enabled instance adopts the target's current routing instead of overwriting it. New Component Feedback property (Enabled/Disabled, default Enabled); set to Disabled for the classic one-way behavior where the plugin is the sole source of truth.

[2.3.0] - 2026-07-15

Added

• Arm multiple outputs (Dual Press, Output > Input): Each SelectOutput press now toggles that output into an armed set instead of replacing the previous arm. The next input press routes that input to every armed output at once. Pressing an armed output again removes just that one. ArmedOutput now reports a comma-separated list.
• Arm All Outputs button: New ArmAllOutputs control (Output > Input mode only) arms every output in one press so an input can be routed to all outputs at once; pressing again while all are armed clears the arm.

[2.1.0] - 2026-06-04

Fixed

• On Gain / Off Gain property keyboard entry: Changed both gain properties from integer to double type so negative values can be typed directly in Q-SYS Designer's property panel.

[2.0.0] - 2026-05-29

Major release: the plugin can now drive a Matrix Mixer or Router directly by name (no crosspoint wiring), and the grid can be oriented to match the built-in Matrix Mixer. Routing, gain, and fade behavior from the 1.x line are unchanged.

Added — Named Component linking (drive a Mixer/Router without wiring)

• Mixer Connection Mode property — Pin Wiring (default, the classic behavior) or Named Component. In Named Component mode the plugin drives the target directly via the Q-SYS component API and the XpointGain (and OutputFadeGain in exclusive-fade mode) output pins are omitted entirely — no wiring of dozens or thousands of crosspoint pins.
• Runtime target dropdown — in Named Component mode the integrator picks the target from the Mixer Target dropdown on the Router page, which is populated from the design's scriptable Mixer/Router components (with a Refresh button to re-scan after adding the target). An unselected dropdown shows a "Select Mixer / Router…" prompt.
• Matrix Mixer and Router targets, auto-detected — the plugin probes the selected component's controls to classify it. A Matrix Mixer is driven via crosspoint gains (input.<i>.output.<o>.gain) and output masters (output.<o>.gain); a Router is driven via per-output selectors (select.<o>, fallback output.<o>.select).
• Router/Toggle guardrail — a Router holds one input per output, so it is only valid in the exclusive-family modes. Selecting a Router while Routing Mode is Toggle is refused (red status) rather than mis-routing. Routers have no gain, so On/Off Gain and fade have no effect on them.
• MixerLinkStatus bar (full-width, Router page, Named Component mode) — colors green when linked (naming the kind, Mixer or Router), yellow when no target is selected, and red when the component is missing, isn't a Mixer/Router, is too small for the configured matrix, or is a Router in Toggle mode. Backed by the MixerTarget / MixerRefresh controls.
• Channel-name sync at link time (Matrix Mixer targets) — the mixer's input.<n>.name / output.<m>.name controls populate the plugin's InputLabel / OutputLabel defaults so the grid matches the mixer.

Added — Grid orientation

• Grid Orientation property — choose Outputs as Rows (matches the built-in Q-SYS Matrix Mixer: outputs down the left, inputs across the top) or Inputs as Rows (the original 1.x layout). Purely visual — crosspoint indexing and all routing/gain/fade behavior are identical either way. Every per-row/per-column control (labels, CLR, Route-to-All, dual-press arm, gain, source indicators) follows the chosen axis.

Changed

• New default grid orientation: Outputs as Rows. Because Grid Orientation is a new property, designs upgrading from 1.x adopt this default and their grid transposes (outputs become rows). The routing is unaffected; to keep the original look, set Grid Orientation to Inputs as Rows.

Notes

• Mixer Connection Mode and Grid Orientation are design-time properties; the Named Component target selection is made at runtime from the dropdown and persists with the design.
• Named Component sync is one-way (plugin → target); changes made directly on the mixer/router are not read back, so the plugin stays the source of truth.
• Named Component mode targets the standard Q-SYS Matrix Mixer and Router control naming; custom scripted components with other control names should use Pin Wiring mode.
• Pin Wiring mode behavior is unchanged; existing designs upgrade with no schematic edits.

[1.2.0] - 2026-05-27

Added

• Timed source fade: new Enable Crosspoint Fade property with a runtime Fade Time knob (FadeTime pin, Knob, 0–30 s, default 1 s; 0 = instant). Adds a snapshot-style fade when sources change.
  • Exclusive Per Output / Single Press / Dual Press: switching the source on an output ducks that output's master gain to silence, swaps the crosspoints instantly, then fades the master back up — the old source fades out, then the new one fades up, with only one audible at a time. The envelope is emitted on the new per-output OutputFadeGain pins (wire to the matrix mixer output masters); crosspoints switch instantly in these modes. Fade Time is the total switch time (the out and in legs each take half).
  • Toggle mode: each XpointGain ramps linearly in dB to its target (On Gain / Off Gain) as crosspoints are added/removed (per-crosspoint fade). Requires Enable XpointGain Outputs.
• OutputFadeGain control (Knob dB, per output): present only when fade is enabled in an exclusive-family mode; rests at unity (0 dB) and ducks to silence during a faded switch.

Notes

• The fade applies to bulk actions too (Clear All, Clear Input/Output, Route to All).
• Toggling XpointGainEnable and startup gain sync apply final values immediately (no ramp), finishing any in-flight fade first.

Added

• Larger matrices: maximum Input Count and Output Count raised from 16 to 48 (up to 2,304 crosspoints).
• Strict-direction Dual Press routing: in Dual Press (Input > Output) and Dual Press (Output > Input) modes, only the configured "from" side can begin a route. Pressing the wrong-direction ARM button first is silently ignored (button does not stay lit). This removes the previous symmetric-arm behavior in which either side could be pressed first.
• Dual Press From Arm Timeout (s) property (default 5, range 0–300): if the user arms a "from" but never presses "to", the from-arm auto-clears after this many seconds. 0 disables the timeout (from-arm stays until manually cancelled or fired).
• Dual Press To Clear Timeout (s) property (default 1, range 0–300): after a route fires, the "to" button clears immediately and the "from" arm stays lit for this many seconds as visual feedback before clearing. 0 clears the from-arm immediately.
• Per-core Licensing support.

Changed

• Dual Press fire behavior: the "to" button no longer stays in its toggled-on state after firing — it is cleared immediately. The "from" arm now persists briefly after firing (controlled by Dual Press To Clear Timeout (s)) instead of being cleared instantly.

Fixed

• Dual Press (Output > Input) mode previously allowed the user to start a route by pressing an Input first (and Dual Press (Input > Output) allowed starting with an Output). Both modes now strictly enforce the configured direction.