DeviceJockey controls Companion.
DeviceJockey to Companion
Send button presses, text, and colors from flexible DeviceJockey Panels and Items to Companion’s actions, feedbacks, and devices.
Control Companion from DeviceJockey
Expand your Companion control panel with DeviceJockey.
Design a DeviceJockey panel around your Companion workflow. Make important buttons bigger, group related controls, add sliders, labels, colors, and images, and arrange everything the way you want.
The best of both worlds
Companion runs the actions. DeviceJockey provides the controls.
Keep Companion’s connections, actions, feedbacks, and variables. DeviceJockey remotely triggers them through Companion’s documented OSC interface. The panels can be as large, visual, contextual, and changeable as your workflow needs.
Any layoutMix buttons, sliders, labels, navigation, and changing Item states on one touch surface.
Every Companion pageAddress buttons directly by page, row, and column. This also works when that page is not visible on dedicated button hardware.
Two-way workflowsSend commands to Companion and let Companion return meaningful OSC events to DeviceJockey.
Two directions. One workflow.
Use one OSC connection in each direction.
Companion reports to DeviceJockey.
Companion to DeviceJockey
Send events, values, and status from Companion to DeviceJockey Panels, Items, and states.
The two connections do different jobs.
Companion’s built-in OSC listener receives remote-control paths from DeviceJockey. Optionally, a Generic OSC connection in Companion can send your own event paths back to DeviceJockey. This is not a Companion surface or module connection.
Setup
Connect both directions in a few minutes.
Enable Companion’s OSC listener
- In Companion, open Settings, Protocols, OSC.
- Enable the OSC Listener and note its port. The default is
12321. - In your DeviceJockey Scene, add an OSC out interface.
- Enter the computer’s IP address and Companion’s OSC listen port.
Add an outgoing OSC connection
- In DeviceJockey, add an OSC in interface and choose a free local port.
- In Companion, add a Generic OSC connection.
- Use the iPhone or iPad IP address as the target and enter the same port.
- Add a Generic OSC action to any Companion button that should report an event.
Same network, two destination ports.
Both devices must be reachable over the local network. Each sender targets the IP address and listening port of the other device.
From DeviceJockey to Companion.
Choose a Companion Template instead of typing the path.
The OSC out interface provides prepared Companion Commands through Templates. In the OSC Command settings, select the Template button 
and choose the required Companion function. The selected Template builds the required OSC path and prepares the matching values.
Path TemplateCompanion Button Tap
Page 1Row 0Column 5
/location/1/0/5/pressCompanion identifies a control by page, row, and column. When DeviceJockey sends the generated path, Companion performs everything configured on that button.
1
Add the matching OSC Command
Use OSC Path for button actions, OSC Value for text or CSS colors, and OSC Three Values for RGB colors.
2
Open Path Templates
Select the Template button beside the OSC path and choose a function beginning with Companion.
3
Choose location and value
Set Page, Row, and Column in the prepared controls. For text, color, or variables, enter the value DeviceJockey should send.
Button Tap, Button Press, Button Release, Rotation Trigger Left, Rotation Trigger Right, and Rescan.
Button Text, Text Color CSS, Background Color CSS, and Set Value of Custom Variable.
Button Text Color RGB and Button Background Color RGB with prepared red, green, and blue arguments.
Templates cover the common Companion messages.
Build semantic paths for feedback.
Paths such as /program/camera/2 remain understandable when a Companion button later moves to another page or position.
The Template remains editable.
It creates a valid Companion path and suitable value configuration. You can still change the generated path or values afterward.
From Companion to DeviceJockey.
Send events that describe intent, not grid positions.
In Companion, add a Generic OSC action to a button and choose a clear path such as /show/live or/camera/preview. In DeviceJockey, configure an OSC Event with the same path. The Event can light up an Item, load a state, change a label, or perform a Command.
Other OSC Event options.
Use an OSC Path Event for a simple trigger such as /show/go.
Use OSC Range to map an incoming numeric value to a Slider or Rotary control.
Why it becomes powerful
Flexible surface
Arrange buttons, sliders, labels, and images in a layout built around your workflow instead of a fixed button grid.
Contextual controls
Use states and visibility to show only the controls needed for the current scene, device, or production step.
Readable feedback
Turn Companion events into large labels, color changes, and status indicators that operators can understand at a glance.
Troubleshooting
If nothing happens, trace one direction at a time.
Check the destination address.
Each OSC out sender must use the receiver’s IP address, not its own.
Match the ports.
DeviceJockey’s outgoing port must match Companion’s OSC listen port. Companion’s Generic OSC target port must match DeviceJockey’s OSC in port.
Check every path segment.
OSC paths are exact. Compare slashes, page, row, column, spelling, and capitalization.
Check the argument type.
Strings, integers, floats, and booleans are different OSC value types, even when their values look similar.
Test one simple message.
Start with a fixed /location/1/0/0/press path or a value-free return event before adding more logic.