Supported Sound Mixers and Channel Addressing

This guide documents the sound mixer drivers present in Falcon Play 0.10.0, what each driver actually controls, and exactly what to enter in the Sound Mixer Faderinput field. It distinguishes working drivers from experimental drivers and placeholders that are visible in Settings but are not operational.

The short answer

Most Falcon Play sound mixer drivers control input-channel faders only.
Yamaha's current DM3 reference manual documents 6 mute groups and no DCA groups. Do not enter DCA1 for a DM3; the current Falcon driver accepts the text because of an implementation error, but it is not a supported DM3 object.
Yamaha DM7 input and DCA control is implemented. Enter DCA1, DCA2, and so on; the current Falcon Play driver automatically discovers only DCA 1-12.
Ardour can address tracks, audio buses, MIDI buses, foldback buses, and VCAs by numeric SSID. The current automatic /strip/list parser does not match Ardour's documented reply order, so source discovery must not be relied on until the driver is corrected.
vMix can control normal inputs and Master. Use __master__ for Master.
Generic OSC can target channels, buses, groups, or DCAs only when its OSC address templates are configured for that object type. Faderinput itself must still be numeric.
Behringer X32, Midas M32, Behringer X-Air, and Yamaha QL/CL currently control input channels only. Values such as DCA1, BUS1, or AUX1 do not select those object types in these drivers.
The Type field on a Falcon Play fader input is only an operator classification such as microphone or server. It does not select channel, group, bus, DCA, or VCA addressing.

Driver status meanings

Status	Meaning
Supported	The driver sends real level and mute commands and is intended for operational use. Hardware and network validation is still required before a production.
Experimental	The driver sends protocol-level commands, but the implementation is explicitly marked as a skeleton or lacks normal discovery and feedback. Validate it with the exact mixer model and firmware before use.
Placeholder or unavailable	Selecting the entry does not provide working mixer control in the current build.

Supported drivers

Mixer	Default port	Controllable objects	Enter in `Faderinput`	Level and mute	Discovery and feedback
Blackmagic ATEM Fairlight	ATEM connection	Fairlight sources attached to ATEM inputs	Select the discovered source. The stored input can look like `1` or `1401`; Falcon Play stores the Fairlight source key separately.	Level, mute, unmute	Source discovery, level/mute feedback, labels, and meters
vMix	`8088`	vMix inputs and Master	Input number such as `1`; use `__master__` for Master	Level, mute, unmute	Input discovery; no live fader feedback
Behringer X32	`10023` UDP	Input channels 1-32 only	`1` through `32`	Level, mute, unmute	Channel-name discovery, level/mute feedback, and meters
Midas M32	`10023` UDP	Input channels 1-32 only	`1` through `32`	Level, mute, unmute	Same implementation as X32
Behringer X-Air	`10024` UDP	Input channels 1-16 only	`1` through `16`	Level, mute, unmute	Channel-name discovery, level/mute feedback, and meters
Yamaha QL/CL	`50000` control; `49280` discovery	Input channels only	Numeric channel such as `1`	Level, mute, unmute	Input-name discovery, level/mute feedback
Yamaha DM7	`49280`	Input channels and DCA groups	Input: `1`; DCA: `DCA1` through `DCA12` in the current verified Falcon scope	Level, mute, unmute	Input/DCA discovery, level/mute feedback, input meters. The physical DM7 has 24 DCAs, but the current driver probes only 12.
Reaper	`8000` UDP	Reaper tracks 1-64; a track used as a bus is still addressed as a track	Numeric track number such as `12`	Level, mute, unmute	Track-name discovery, level/mute feedback, and meters
Generic OSC	`9000` UDP	Any single numeric namespace described by the configured OSC templates	Numeric object number such as `1`	Level, mute, unmute	No discovery or feedback

Experimental drivers

Mixer	Default port	Current scope	Enter in `Faderinput`	Important limitation
Blackmagic Fairlight Live	`9990`	An `Input` plus optional `Source` using the implemented ASCII protocol	Mixer-specific input value; source must be supplied as a source key	Driver is marked as a skeleton. It has no source discovery; validate native fade, mute, and feedback on real hardware.
Yamaha DM3	`49280` in the current Falcon driver	The code attempts input and DCA level/mute control using Yamaha SCP-style paths	Numeric input such as `1` is test-only; do not enter `DCA1`	Yamaha documents OSC over Ethernet and MIDI over USB for general remote control, 6 mute groups, and 0 DCA groups in the OSC specification. No official DM3 SCP reference was found. Treat the entire DM3 driver as experimental; its DCA path is an unsupported implementation error, not a testable DM3 feature.
Ardour	`3819` UDP	Audio tracks, MIDI tracks, audio buses, MIDI buses, foldback buses, and VCAs	Numeric Ardour SSID such as `12`	Level, mute, and unmute commands are implemented, but the current `/strip/list` parser expects `type, SSID, name`; Ardour documents `type, name, inputs, outputs, mute, solo, SSID`. The dropdown may therefore be empty or incorrect. Enter a verified SSID manually and treat feedback as unverified until the parser is fixed.
Studer Vista	`8081`	Numeric mono channels	Positive channel number such as `1`	Driver is marked as a raw-TCP skeleton. Level, mute, and unmute packets exist, but there is no discovery or feedback.
Studer OnAir 3000	`8081`	Channels 1-24	`1` through `24`	Fader level only. Mute and unmute are not implemented. Driver is marked as a skeleton.
SSL System T	`23`	Numeric channels	Positive channel number such as `1`	Driver is marked as a custom-TCP skeleton. It has level/mute packets but no discovery or feedback.

Experimental drivers should not be described as generally supported until they have been tested with the target hardware, protocol version, and firmware.

Why DM3 DCA control is unsupported

Yamaha's current DM3 reference manual documents 6 mute groups and contains no DCA feature. The Danish/English DM3 product overview and the full specification do not list DCA groups, while Yamaha's published DM3 OSC Specification explicitly lists DCA Group 0.

One localized Yamaha Portugal overview contains a conflicting bullet that says ?8 DCA Roll-out groups.? That isolated marketing-page line is not repeated in Yamaha's current reference manual, OSC specification, Danish/English overview, or full specification and is therefore not used as evidence of DM3 DCA support.

Falcon Play currently shares an SCP-style TCP driver between DM3 and DM7 and attempts to send DM3 DCA commands to MIXER:Current/DCA/... on port 49280. The driver accepting identifiers such as DCA1 is an implementation defect. Do not configure DM3 DCA fader inputs. DM3's 6 mute groups are also not addressed by the current Falcon driver.

Placeholder or unavailable entries

Settings entry	Current state	What happens
Lawo Ruby	Placeholder	Opens an Ember+ TCP connection, but level and mute operations only log ?not implemented?; no control packet is sent.
Lawo MC2	Placeholder	Opens an Ember+ TCP connection, but channel/group level and mute operations are not implemented.
Lawo Relay VRX4	Placeholder	Opens an Ember+ TCP connection, but output gain and mute operations are not implemented.
Generic MIDI	Placeholder	No MIDI backend is bundled. Commands are logged and ignored, and status remains offline.
Falcon	Unavailable	The Settings entry exists, but the referenced `falcon.js` sound mixer driver is absent, so the driver cannot load.

Do not use these entries for live production control in the current build.

VCA, DCA, group, bus, and Master support

Mixer or driver	Input faders	DCA or VCA	Groups	Mix, AUX, or audio buses	Master
ATEM Fairlight	Yes	No	No	No	No
vMix	Yes	No	No	No	Yes, as `__master__`
X32 and M32	Yes, channels 1-32	No	No	No	No
X-Air	Yes, channels 1-16	No	No	No	No
Yamaha QL/CL	Yes	No	No	No	No
Yamaha DM3	Experimental	No documented DCA support	6 mute groups on the console; no Falcon group addressing	No	No
Yamaha DM7	Yes	Yes, DCA 1-12 in the current Falcon discovery scope; physical mixer has 24	No separate group addressing	No	No
Reaper	Yes, tracks	No dedicated VCA addressing	No separate group addressing	A track used as a bus can be controlled by its track number	No
Ardour	Yes, by SSID	Yes, VCA strips by SSID	Groups are not separate strips	Yes, audio/MIDI/foldback bus strips by SSID	Not included by the current strip filter
Generic OSC	Depends on template	Depends on template	Depends on template	Depends on template	Depends on template

This table describes Falcon Play's current drivers, not the full feature set of the physical mixer.

Configure a mixer and fader input

Open Settings > Device Config > Sound Mixer.
Add a sound mixer.
Enter a unique Name, enable Active, choose the mixer Type, and enter its IP and Port.
Add one Fader Input for every channel, DCA, VCA, bus, track, input, or Master object Falcon Play must control.
Select the correct Mixer when more than one mixer is configured.
Enter a clear Description such as Host Mic, Video A, Audience DCA, or Program Master.
Choose the Falcon Play fader Type: microphone, server, extern, or soundplayer. Remember that this is classification only.
Select or enter Faderinput using the driver-specific values in this guide.
Set setDb, Fade time (ms), and Delay (ms).
Save the configuration, reopen Falcon Audio Mixer, and test level, mute, feedback, and automation before production.

What each Falcon Play input field means

Field	Meaning	Example
Mixer	Chooses the configured mixer driver that owns this fader.	`Studio DM7`
Description	Operator-facing label in Falcon Audio Mixer and selection lists.	`Host Mic`
Type	Falcon Play classification only; it does not change mixer addressing.	`microphone`
Faderinput	Driver-specific channel, strip, DCA, input, track, or Master identifier.	`12`, `DCA1`, or `__master__`
Source key	Sub-source identifier used primarily by Blackmagic Fairlight sources. It is normally stored automatically by the dropdown.	`-256`
setDb	Target level when the source is opened by PGM or rundown automation.	`0` or `-12`
Fade time	Transition time in milliseconds. Falcon Play ramps non-native drivers in software; Fairlight Live declares native fade.	`500`
Delay	Wait in milliseconds before the level or mute command is sent.	`120`

Use levels from approximately -90 dB to +10 dB. Falcon Play uses its internal closed state to send a fully closed level; users normally enter a numeric target in setDb.

Exact addressing examples

Goal	Mixer	`Faderinput`	Source key	Notes
Open input channel 7	X32, M32, X-Air, Yamaha, Studer, SSL	`7`	Empty	Only if channel 7 is within that driver's supported range.
Control DCA 1	Yamaha DM7	`DCA1`	Empty	`DCA 1` and `DCA_1` are also accepted, but `DCA1` is the recommended form. Automatic discovery currently covers DCA 1-12.
Test input channel 1 during DM3 driver validation	Yamaha DM3	`1`	Empty	The entire current DM3 SCP-style driver is experimental. `DCA1` is not supported, and DM3 mute-group addressing is not implemented.
Control an Ardour VCA	Ardour	Enter the VCA's numeric SSID, for example `12`	Empty	Do not enter `VCA1`. Verify the current SSID in Ardour; the current Falcon Play discovery parser cannot be relied on.
Control an Ardour audio bus	Ardour	Enter the bus's numeric SSID, for example `8`	Empty	Do not enter `BUS1`. The SSID can change with session/surface layout.
Control vMix Master	vMix	`__master__`	Empty	`master` is also accepted; the dropdown stores `__master__`.
Control ATEM input 1401 left source	ATEM Fairlight	`1401`	Select Left/Ch1; source key is stored automatically	Do not guess the numeric source key when the dropdown is available.
Control ATEM input 1401 right source	ATEM Fairlight	`1401`	Select Right/Ch2; source key is stored automatically	Left and right can have the same `Faderinput` but different source keys.
Control OSC DCA 3	Generic OSC configured with `/dca/{ch}/fader`	`3`	Empty	The object type comes from the address template, not from `Faderinput`.

Generic OSC advanced configuration

Generic OSC accepts these mixer configuration keys:

Key	Default	Purpose
`addressFader`	`/ch/{ch}/fader`	OSC address template used for level commands
`addressMute`	`/ch/{ch}/mute`	OSC address template used for mute commands
`faderType`	`f`	OSC argument type: `f`, `i`, or `s`
`faderUnit`	`db`	Use `db` for direct dB values or `normalized` for a 0-1 fader value

The current Settings form does not add these advanced keys to a newly created mixer. They must already exist in the mixer configuration. Faderinput is parsed as a positive integer, so use a template such as /dca/{ch}/fader with Faderinput 3; do not enter DCA3 in the field. Configure separate Generic OSC mixer entries when channels, buses, and DCAs use different OSC namespaces.

Function action channel values

Sound Mixer function actions choose from the fader inputs already configured for the selected mixer. Configure the fader input in Settings first, then select it in the Function action.

For sources without a source key, the stored action value is the Faderinput, sometimes displayed internally with a trailing colon, for example DCA1:. For Blackmagic Fairlight, the action stores input:sourceKey, for example 1401:-256. Prefer the dropdown because it preserves the exact source key.

Unsupported input forms

DCA1, VCA1, BUS1, AUX1, or GROUP1 do not work on X32, M32, X-Air, Yamaha QL/CL, Studer, SSL, Reaper, or Generic OSC unless this guide explicitly lists that form.
DCA1 is parsed by the Yamaha DM3 driver because DM3 and DM7 currently share an implementation. Yamaha's DM3 documentation specifies no DCA groups, so this is an implementation defect and must not be used.
The fader Type dropdown cannot turn a normal channel number into a bus, group, DCA, or VCA.
A physical mixer supporting a feature does not mean the current Falcon Play driver exposes that feature.
A green network status alone does not prove that a placeholder or experimental driver can control the mixer.

Production validation checklist

Confirm the mixer-specific dropdown discovers the expected source when discovery is supported.
Move the Falcon Audio Mixer fader and verify the exact physical channel, DCA, VCA, bus, track, input, or Master moves.
Test mute and unmute separately.
Move the physical fader and confirm Falcon Audio Mixer follows when feedback is listed as supported.
Test the configured fade time and delay.
Trigger the same fader through a rundown input and a Sound Mixer function action.
Verify that no similarly numbered channel on another configured mixer changes.
Repeat the test after restarting Falcon Play and the mixer.

Troubleshooting

Symptom	Likely cause	What to check
A DCA, VCA, bus, or group does not move	The selected driver only implements input channels, or the wrong identifier form was used.	Check the capability and addressing tables above.
A configured DM3 DCA does not move	Yamaha's DM3 documentation specifies no DCA groups; the current shared driver incorrectly accepts the identifier.	Remove the DM3 `DCA1` mapping. DM3 mute groups are a different feature and are not implemented in the current Falcon driver.
The wrong ATEM channel moves	The input is correct but the source key is wrong or missing.	Re-select Left/Ch1 or Right/Ch2 from the discovered source list.
Ardour dropdown is empty or controls the wrong strip	The current `/strip/list` parser does not match Ardour's documented reply order, or the stored SSID changed with the session layout.	Determine the current strip SSID in Ardour and enter it manually. Treat Ardour as experimental until the parser is corrected and tested.
Generic OSC sends to a channel instead of a DCA or bus	The address template still uses the channel namespace.	Set the correct `addressFader` and `addressMute` templates in configuration.
Mixer shows online but nothing changes	The driver is experimental, a placeholder, or uses the wrong protocol/port.	Check the status table, server log, mixer remote-control settings, and network path.
Fade is not smooth	The driver uses Falcon Play's 50 ms software ramp or the first state is unknown.	Test a longer fade and verify repeated commands on the same configured fader.