DeviceJockey Interfaces
Combine MIDI with Logic Pro’s control-surface OSC protocol to build a responsive custom controller.
The Logic Pro Toolbox contains prepared Panels and Items for the predefined OSC controls supplied by the DeviceJockey MIDI Device Profile. Import the Scene, test its controls and feedback, then copy useful Items into your own Panels.
Download the DJX file and import it into DeviceJockey as a Scene.
Install the MIDI Device Profile, connect the included Logic Pro interface, and try the prepared controls and feedback.
Copy working Items into your own Scene so their predefined Command and Event paths are preserved.
Two control paths
DeviceJockey can control Logic Pro through standard MIDI and through the dedicated Logic Pro interface. The dedicated interface exchanges OSC messages with Logic Pro and requires the DeviceJockey MIDI Device Profile on the Mac.
Add MIDI out and MIDI in interfaces and select the endpoints connected to the Mac.
Install the profile, add a Logic Pro interface, and accept the control-surface connection in Logic.
It defines DeviceJockey as a supported control surface and supplies the predefined OSC controls understood by Logic Pro.
Required download
Download version 43 of the DeviceJockey Profile Installer, unzip it, and open the installer application on the Mac running Logic Pro. The installer application is signed and notarized for macOS.
Quit Logic Pro completely before installing again or when the new profile does not appear in the control-surface list.
Verify the profile
claussen. The result must show manufacturer Claussen and model DeviceJockey.
DeviceJockey setup
The dedicated interface advertises and discovers the OSC services automatically. Keep the iPhone or iPad and Mac on the same local network, and make sure the global interface switch is on.
First connection
Logic Pro displays a connection request after it discovers DeviceJockey. Accept the request. DeviceJockey is then added to Control Surface Setup with its profile and OSC port.
The DeviceJockey surface should appear with the DeviceJockey logo and the port used by the interface.
OSC controls
Logic Pro’s control-surface OSC implementation does not accept arbitrary custom controls. Commands and events must use one of the OSC paths predefined by the installed DeviceJockey profile.
Open the Logic Pro Controller Assignments window.
Choose the surface shown as DJ with its port, normally DJ (8000).
Choose the required entry from the Control or Parameter list.
Read the path from OSC Message Paths, Value, and use that exact path in DeviceJockey.
Commands →
Send a fixed value or an OSC message without arguments to a predefined Logic Pro path.
Map an item position between a configured minimum and maximum and send the result to a predefined Logic Pro path.
Both Commands support Swaps in their configuration. Logic Pro Value can also use the Item title as its sent value when that matches the selected profile control. Neither option is required for a basic setup.
← Events and feedback
React when a message on the configured OSC path contains the expected value.
Map a received value into a slider, rotary control, light range, or another supported item property.
Display the value received on a selected Logic Pro OSC path as an item label.
Apply the color value reported by Logic Pro to a supported item.
Interpret step-up and step-down values as relative item movement.
Allow or protect supported item interaction based on Logic Pro feedback.
Save a named item state when the configured OSC message is received.
Recall a named item state, optionally with supported animation settings.
Supported events can use buffered Logic Pro messages during a status check so the panel can restore the latest received state.
Troubleshooting
On the iPhone or iPad, open Settings → Privacy & Security → Local Network and make sure DeviceJockey is enabled. Without this permission, the app cannot discover Logic Pro on the LAN.
Apple: Local Network privacy →Logic Pro’s OSC implementation supports UDP over IPv4 only. An IPv6-only network will not work. Both devices should be on the same local network and must be able to reach each other directly.
Apple: OSC Message Paths →Open Logic Pro’s Control Surfaces menu. If Bypass All Control Surfaces is enabled, connected surfaces are deliberately silenced; turn it off before testing.
Apple: Control Surface settings →After updating Logic Pro or macOS, verify that DeviceJockey still appears in the installation list. If it is missing, quit Logic Pro, reinstall the current MIDI Device Profile, and restart the Mac.
Apple: Logic Pro troubleshooting →In Control Surfaces, Setup, New, Install, search for Claussen and confirm that DeviceJockey appears.
Quit it completely after profile installation or reinstallation.
Logic Pro must be allowed to detect and add the DeviceJockey surface.
On the iPhone or iPad, enable DeviceJockey under Settings, Privacy & Security, Local Network.
When this Logic Pro menu option is active, the surface can appear correctly but still provide no control or feedback.
The interface port and the port associated with the Logic Pro surface must match.
Logic Pro cannot complete the first connection until the control-surface request is accepted.
Copy a predefined path from Controller Assignments. Logic Pro ignores arbitrary paths not included in the profile.
Logic Pro requires IPv4 and UDP for OSC. Allow Logic Pro through the macOS firewall and avoid guest networks that isolate devices from each other.
When troubleshooting, confirm whether the affected item uses MIDI in or out, or the dedicated Logic Pro interface.
Apple recommends moving ~/Library/Preferences/com.apple.logic.pro.cs into a backup folder, restarting the Mac, and opening Logic Pro again. This recreates the control-surface settings and means that DeviceJockey and other surfaces may need to be added again. Do this only after preserving the file and documenting any custom control-surface setup. Read Apple’s complete reset procedure →