MIDI
Connect music software and audio equipment by cable or wirelessly with Bluetooth MIDI.
Open the MIDI guide →DeviceJockey Guide
Interfaces
Interfaces define how DeviceJockey communicates with a device, an application, or your local panel.
The connection layer
Every control starts with an interface.
Before an item can control a device or react to an application, DeviceJockey needs to know how to communicate with it. That is the role of an interface. You select the interface that matches your target and configure the required connection settings, such as an address, port, or login details.
You can add multiple interfaces to a scene. This makes it possible to combine devices and software from different areas on the same control surface.
Commands go outButtons, sliders, and other items send actions through an interface.
Events come inDevices and applications can update item values, labels, and states.
Scenes keep connections separateOnly the interfaces in the active scene are available to its items.
Universal connections
Use protocols supported by many products.
OSC
Exchange flexible control messages with a wide range of media, audio, and production applications.
Open the OSC guide →MQTT
Publish values and react to topic updates in automation, IoT, and custom control environments.
Open the MQTT guide →Dedicated integrations
Connect products with specialized requirements.
Some systems need more than a universal protocol. Dedicated interfaces provide commands, events, and connection options designed for the product you want to control.
Control OBS through its built-in WebSocket connection.
OBS guide →Combine OSC with the DeviceJockey MIDI Device Profile.
Logic Pro guide →Build bidirectional controls for X Air, M Air, X32, and M32 mixers.
Mixer guide →Control compatible camera systems through a CCS one or MCP 450.
Grass Valley guide →Switch destinations and work with named sources and destinations.
Videohub guide →Send DMX control data to lighting equipment on your network.
Art-Net guide →Inside DeviceJockey
The Local Interface
The Local Interface does not connect to an external product. It controls and monitors behavior inside DeviceJockey itself. Use it to update items, react to panel and connection states, or build navigation between panels.
Example
An event from the Local Interface can make an item light up when all interfaces are connected.
About system events →Getting started
From interface to working control.
1
Choose a target
Decide which device or application you want to control.
2
Add an interface
Select the matching universal or dedicated interface.
3
Configure it
Enter the connection settings required by your target.
4
Connect items
Add commands and events to the controls on your panel.