Send commands to a destination.
DeviceJockey → Destination
Commands from items send their MIDI messages to the selected Core MIDI destination.
- Destination
- The endpoint that receives MIDI from DeviceJockey
- Used by
- MIDI commands
DeviceJockey Interfaces
MIDI Interface
Send MIDI commands to a destination and receive MIDI events from a source.
Core MIDI connections
Choose a direction for each interface.
DeviceJockey separates outgoing and incoming MIDI into two interface types. Each interface selects one Core MIDI endpoint. The endpoint can come from connected hardware, software on the same device, a virtual MIDI connection, or an established Bluetooth MIDI connection.
Receive events from a source.
Source → DeviceJockey
DeviceJockey listens to the selected Core MIDI source and passes received messages to matching events.
- Source
- The endpoint that sends MIDI into DeviceJockey
- Used by
- MIDI events and MIDI Clock
Use both directions when required.
Add separate MIDI out and MIDI in interfaces when a device or application should receive commands and return its current state.
Setup
Add and configure the required direction.
1
Make the endpoint available
Connect the MIDI hardware or establish the software or Bluetooth MIDI connection.
2
Add MIDI out or MIDI in
Choose the direction required by the commands or events in your scene.
3
Select the endpoint
Open the interface settings and choose the destination for MIDI out or the source for MIDI in.
4
Add commands or events
Assign the configured interface to the controls that should send or receive MIDI.
MIDI out
Send values, ranges, notes, and NRPN messages.
A MIDI out interface points to one available destination. Commands assigned to this interface send their messages to that destination.
Send a configured MIDI message with a fixed value.
Map an item value to a configured minimum and maximum MIDI range.
Forward note interaction from the Piano item on the selected MIDI channel.
Send Note On followed by Note Off after the configured duration.
Send a fixed Non Registered Parameter Number message.
Map an item value to a configured NRPN range.
Use Panic when notes remain active.
The MIDI out settings provide a Panic function that sends Note Off messages to stop hanging notes.
MIDI in
Turn received MIDI into item events.
A MIDI in interface listens to one available source. Events can filter incoming messages and use them to update an item or execute matching commands through Remote Options.
Listen to incoming MIDI on a selected channel.
React to a selected MIDI message type and channel.
React when an incoming value matches the configured message.
Map received MIDI values to a continuous item range.
Interpret configured messages as relative changes.
Receive fixed or ranged NRPN values.
Configurable MIDI messages include notes, Control Change, Program Change, Pitch Bend, polyphonic aftertouch, and channel pressure. The choices shown depend on the item and the event being configured.
MIDI Clock
React to transport and timing.
MIDI in can process MIDI Clock information such as Start, Stop, Continue, bar, beat, and BPM. Select the time signature in the MIDI in settings so bar and beat calculations match the sending system.
MIDI ClockUse timing values with ranges and supported item states.
MIDI Clock LabelDisplay selected clock or transport information in a label.
MIDI Clock ToggleReact to supported clock states with a toggle.
Wireless transport
Use Bluetooth MIDI endpoints.
Bluetooth MIDI establishes a Core MIDI connection between an iPhone, iPad, or Mac. Once connected, its source and destination can be selected in the MIDI in and MIDI out interface settings like other MIDI endpoints.
Connection first. Interface selection second.
Establish Bluetooth MIDI before selecting the new source or destination in the interface settings.
If an endpoint is missing
Rescan the Core MIDI connections.
Check the transport.
Confirm that the cable, application, virtual port, or Bluetooth MIDI connection is available.
Open the interface settings.
Check the destination list for MIDI out or the source list for MIDI in.
Restart the MIDI scan.
Use Restart to ask Core MIDI to rescan its connected endpoints.
Select the endpoint again.
Choose the detected source or destination and confirm the interface settings.