Send control to the mixer.
Item → DeviceJockey → Mixer
Move a fader, toggle a mute, select a source, change an EQ parameter, recall a path, or send several values from a Script.
DeviceJockey
Interfaces
Behringer and Midas mixer control
Turn an iPhone or iPad into the focused mixer surface your production actually needs, with discovery, ready-made OSC templates, live feedback, and metering.
Direct mixer connection
Control only what matters and always see the console state.
DeviceJockey connects directly to the mixers using their OSC protocol. Commands change parameters on the console. Events receive the console’s answers and parameter changes so Items can follow faders, mutes, names, colors, and meter values.
Follow the confirmed mixer state.
Mixer → DeviceJockey → Item
Update a Slider or Rotary, show a name or value, match a console color, light a button, trigger an action, or display a meter.
Use the XR/MR model family for X Air and M Air mixers.
Use the X32/M32 model family for full-size and rack consoles.
Build a production surface, not a copy of the console.
One panel can hold presenter mics, playback level, stream bus, and emergency mute, even when those controls live in different places on the mixer.
Supported mixer families
One workflow for compact stageboxes and large consoles.
Create controls for XR12, XR16, and XR18 mixers using the XR model family and its matching path templates.
Use the same XR/MR protocol family for compatible M Air mixers, including MR12 and MR18.
Address channels, buses, DCAs, FX returns, main LR/mono, routing, processing, and meters through the X32 family.
Use the X32/M32 family for compatible M32 consoles and the corresponding OSC paths.
Select the family before choosing the mixer.
The selected family determines how DeviceJockey searches for the mixer and which templates are available. Switch families and restart the search if the mixer does not appear.
Network discovery
Let DeviceJockey find mixers on the local network.
1
Join the mixer network
Connect the iPhone or iPad to a network that can reach the mixer. Allow DeviceJockey access to the local network when iOS asks.
2
Add the interface
Add a Behringer/Midas interface to the active Scene and open its settings.
3
Select the family
Choose XR/MR for X Air and M Air, or X32/M32 for X32 and M32 consoles.
4
Select a discovered mixer
DeviceJockey broadcasts an /xinfo request. Tap a result to copy its network address into Host.
5
Enable interfaces
Turn on interface connections and confirm that the connection indicator becomes active.
Each discovered entry includes IP address, network name, console model, and firmware version reported by the mixer.
If broadcasts cannot cross the network, enter the console’s IP address directly. A fixed address or DHCP reservation is useful for show systems.
Restart after changing the model family, network, or Info Request. Selecting a result updates Host immediately.
After connecting, DeviceJockey renews the remote subscription regularly so parameter updates continue to arrive.
Discovery uses local UDP broadcast.
Guest Wi-Fi, client isolation, VLAN boundaries, VPNs, and some managed access points can hide a mixer even when its address works as a manual Host.
Built-in path templates
Choose mixer functions instead of memorizing OSC paths.
The Command and Event editors provide model-specific templates. Pick a functional area, select its channel, bus, DCA, FX return, or other index, and DeviceJockey builds the correct path. Templates also supply suitable value types, ranges, options, and formatting where the mixer protocol defines them.
Name, color, source, gain, trim, 48 V, polarity, low cut, fader, pan, mute, solo, LR assignment, gate, dynamics, and EQ.
Build bus masters, channel sends, main LR controls, mono/center controls, routing assignments, processing, and mix feedback.
Control DCA groups, aux inputs, FX sends and returns, insert assignments, effect types, and effect parameters supported by the selected family.
Select the mixer’s meter streams for Item labels and visual level feedback without manually decoding the returned OSC blob.
Templates stay synchronized.
When you choose a known template, DeviceJockey can keep the Command and matching Event aligned around the same mixer function. You can still enter a raw OSC path for an uncommon parameter.
Commands →
Send fixed, variable, prompted, or scripted control.
Send one typed value to a mixer path. Use it for mute, solo, color, source, 48 V, channel names, or another fixed setting. A Swap or the Item title can provide dynamic content.
Map a Slider, Rotary, or Toggle value to the required mixer range. This is the standard Command for faders, pan, gain, EQ, dynamics, and sends.
Send an OSC address without arguments. Use it for mixer functions triggered by the path itself or for explicit requests.
Ask the operator for a value when the Command runs, then send that entry to the chosen path, for example a channel name or exact number.
Use sendOSC(path, values) to calculate values, apply conditions, or send several related mixer messages from one Item action.
Use the template’s value specification.
A mute may use the opposite numeric meaning from a simple On/Off switch, while faders use normalized values. Templates select and format these values for the chosen mixer function.
← Events and feedback
Make every control reflect what the mixer reports.
Move a Slider or Rotary to the value received for a path. Match it with a BX Range Command for bidirectional control.
Show a channel name, parameter value, or formatted option on a Label or the label area of supported controls.
Translate the mixer’s channel color into the color of a supported Item, keeping the custom panel visually aligned with the console.
Read a selected value from the mixer’s meter data and display it on supported Slider, Rotary, or Label Items.
Switch a Radio Button on, control an Item light, or tap a Buzzer when a matching value arrives, for example when a channel becomes muted.
Evaluate incoming OSC data with a Script when a single value comparison is not enough, then perform the Item’s configured action.
Commands request; Events confirm.
Pair important show controls with feedback. The Item then follows changes made from the console, another tablet, automation, or a second DeviceJockey panel.
Command and Event examples
Three useful bidirectional controls.
Command: Add BX Value and choose Channel → Channel 1 → Mute. Select the template’s mute value for the button state.
Event: Add the matching value Event to the Item’s switch or light action. The button now follows the mute state reported by the mixer.
/ch/01/mix/on
Command: Add BX Range to a Slider and choose Channel → Channel 1 → Fader. Apply the range offered by the template.
Event: Add BX Range to the same Slider’s feedback action with the identical template. Moving the console fader moves the Item.
/ch/01/mix/fader
Name: Add a BX Label Event with Channel → Channel 1 → Name so the panel follows console naming.
Color: Add a BX Color Event with Channel → Channel 1 → Color. The Item can now identify the channel just like the mixer.
/ch/01/config/name/ch/01/config/color
Mixer mute paths describe “channel on.”
The templates account for the inverted meaning: a channel is muted when its mix-on value is off. Prefer the supplied Mute template over guessing the raw number.
Panel ideas
Start from the operator’s task.
Presenter and guest faders, mute feedback, playback level, stream bus master, and a guarded emergency mute.
One musician’s bus sends, talkback, master level, and clear source labels without exposing the rest of the console.
Place only parameters that still need manual adjustment next to buttons that trigger the surrounding show workflow.
Names, colors, meters, mute states, DCA masters, bus masters, and selected processing values on one status page.
1
Choose the role
Define who operates the panel and which mistakes the layout should prevent.
2
Add control
Use a template-backed Command for every value that must change.
3
Add feedback
Pair it with the matching Event and reuse the same family, path, channel, and range.
4
Test from both sides
Operate the Item, then change the same parameter at the console and confirm that the Item follows.
Troubleshooting
If discovery, control, or feedback does not work.
Confirm the model family.
Select XR/MR for X Air and M Air mixers or X32/M32 for X32 and M32 consoles. The wrong family also shows the wrong templates.
Check local network permission.
Device discovery and mixer control require iOS permission to access devices on the local network.
Enter the Host manually.
If the mixer is reachable but broadcast discovery is blocked, use its current IP address directly.
Remove network isolation.
Disable guest/client isolation and verify that Wi-Fi, VLAN, VPN, and firewall rules allow UDP traffic between the Apple device and mixer.
Check the connection switch.
The interface must belong to the active Scene, be enabled, and have global interface connections switched on.
Verify the exact path.
Use the template for the selected family. Similar parameters can use different paths or channel ranges on XR/MR and X32/M32.
Match the value type.
Check whether the template expects an integer, float, string, option, or normalized range. Pay special attention to inverted mute values.
Test feedback separately.
If control works but the Item does not update, compare the Event path and range with the Command and change the parameter directly at the mixer.
Use the interface log.
Inspect outgoing Commands and incoming OSC messages to confirm the path and value exchanged with the mixer.