Send commands to another system.
DeviceJockey → Receiver
DeviceJockey sends each configured OSC command to one network destination.
- Host
- IP address or host name of the receiver
- Port
- Port on which the receiver expects OSC messages
DeviceJockey Interfaces
OSC Interface
Send and receive flexible control messages using OSC paths and typed arguments.
Network connections
Choose a direction for each interface.
DeviceJockey separates outgoing and incoming OSC into two interface types. OSC messages use an address path such as /mixer/channel/1/fader and can carry one or more typed arguments. Supported values include integers, floating point numbers, booleans, and strings.
Receive events from another system.
Sender → DeviceJockey
DeviceJockey listens for incoming OSC messages and passes them to matching events.
- Host
- DeviceJockey IP address shown to the sender
- Port
- Local port configured in the OSC in interface
Use both directions when required.
Add separate OSC out and OSC in interfaces when an application should receive commands and return its current state.
Setup
Add and configure the required direction.
1
Check the network
Place both systems on a network where they can reach each other.
2
Add the direction
Add OSC out for commands, OSC in for events, or both.
3
Enter connection data
Configure the destination host and port or the local listening port.
4
Match the paths
Use the OSC paths expected by the receiving system in commands and events.
OSC out
Choose how a command builds its message.
Send a path with a configured value.
Send a path with three configured arguments in one message.
Send an OSC path without an argument.
Map an item value to a numeric minimum and maximum.
Map an item range and send the resulting value as text.
Ask for input and send the entered value with the configured OSC message.
Build and send one or more OSC messages from a script.
The available value editor can adapt to the selected argument type. Choose the type expected by the receiving application. A number sent as a string is different from the same number sent as an integer or float.
OSC in
Match incoming paths and interpret their arguments.
OSC events first compare the received address with their configured path. Depending on the item and event, DeviceJockey can then compare a value, map a range, apply a relative change, update a label, or evaluate the received arguments with a script.
React when a message with the configured path arrives, even when no argument is needed.
React to a path and a matching argument value.
Map an incoming numeric range to the value or state of an item.
Interpret configured values as relative upward or downward changes.
Use received content to update supported text or URL properties.
Evaluate all received arguments and derive the result used by the item.
The available events depend on the item.
A slider needs different OSC reactions than a button, label, or Web View. DeviceJockey shows the variants that fit the selected item event.
Paths and values
Both sides must agree on the message format.
A matching port is not enough. The OSC path, argument order, and argument types must match what the other application sends or expects. Consult that product’s OSC documentation when configuring a command or event.
Example
/light/level with the float argument 0.5 is not the same message as the path with the string argument "0.5".
Troubleshooting
If OSC messages do not arrive.
Verify the destination IP address.
For OSC out, use the address of the receiving system. For incoming messages, configure the sender with DeviceJockey’s current address.
Check both port numbers.
The sender must target the same port on which the receiver listens.
Compare the complete OSC path.
Check every slash, segment, number, and letter. OSC paths must match exactly.
Check the argument type.
Confirm that integer, float, boolean, or string matches the format expected by both sides.
Check network restrictions.
Make sure local network access and any firewall allow traffic between both systems.