Groups were only reachable through the generic "Buss:" actions, whose
dropdown mixes all 25 busses, so users could not find group fader
control.
- New "Group:" and "Aux master:" mute, solo, set fader (with fade time)
and adjust fader actions; their dropdowns list only busses of that
type. Matching muted, solo, fader text/position, meter, signal and
peak feedbacks.
- The old buss_* actions and feedbacks keep working for existing
buttons and are now labelled "Any buss (aux or group)".
- Presets: "Busses" is split into "Groups" and "Aux masters", and the
bus meters into "Group meters" and "Aux meters". A bus that changes
type on the console moves section on the next rebuild.
npm test: 542 checks pass on Node 25 and on Companion's Node 22.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Found on the live S31 (read-only, plus meter subscriptions):
- Matrix inputs are named at /Matrix_Inputs/N/Channel_Input/name (an
address missing from DiGiCo's 2014 list). Their names now appear in
every matrix-send dropdown, preset and the new matrix_in_N_name
variables, falling back to "Matrix In N" when empty. Matrix inputs also
get trim and phase.
- Console names are space-padded where the surface wraps them; every name
is now trimmed and its whitespace runs collapsed ("LEAD V RESI").
- Meter values are inverted: 127 is silence and lower is louder, about
1 dB per step below full scale (silent channels read 127, the room mic
36-48). The module treated 127 as peak. Level meters now read dBFS
(approximate), gauges span -60..0 dBFS, signal and peak thresholds are
in dBFS; gain reduction reads dB of reduction, 127 meaning none.
- Bus and matrix outputs have meters (/Aux_Outputs, /Group_Outputs and
/Matrix_Outputs/N/Output/meter): new signal, peak, value and gauge
feedbacks and "Buss meters" / "Matrix meters" presets.
3002 presets, 2.7 MB. npm test: 425 checks pass on Node 25 and on
Companion's Node 22. Deployed and checked on the booth Companion 5.1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rewrite of the module around what the console itself reports:
- Settings cut to console address/ports, the iPad relay and debug logging;
nothing site-specific remains. An upgrade script carries v1 configs and
remaps v1 actions/feedbacks whose ids were reused.
- On connect the module reads every name, buss type (aux/group), stereo
mode, fader/mute/solo/pan and the snapshot list; entities that never
answer are hidden. Definitions rebuild (debounced, skipped when
identical) when names, buss types or snapshots change.
- Every entity option is a searchable dropdown of live names. 70 actions
cover inputs, aux sends, group assigns, busses, matrix outputs and sends,
control groups, graphic EQs, channel-strip switches, trim/gain/filters and
snapshots, each level with set and encoder-friendly adjust variants.
- Boolean, value and bar feedbacks for every state, input level and
gain-reduction meters via the console's meter subscription protocol, and
about 2800 presets including rotary knob presets with live level text.
- A write guard keeps fast encoder turns from being undone by delayed
echoes; feedbacks are re-checked per instance.
- Relay: the client table survives config changes, idle iPads are kept for
an hour by default (0 = forever), bind failures retry and show in status.
npm test: 326 checks pass on Node 25 and on Companion's Node 22.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
michaelandClaude Opus 5.5