How to Use MIDI-OX to Diagnose Latency and Routing Issues

How to Use MIDI-OX to Diagnose Latency and Routing Issues

1. Download and install

• Get MIDI-OX from the official site (search “MIDI-OX download”) and install the latest Windows-compatible version.

2. Open MIDI-OX and set ports

• Options → MIDI Devices: select your input and output devices (virtual ports, MIDI interfaces, USB controllers). Click OK.

3. Monitor incoming MIDI

• The main Event Window displays received messages in real time. Use this to confirm messages arrive from your controller.
• Tip: If nothing appears, verify cable/USB, drivers, and that the device is enabled in Windows MIDI settings.

4. Check routing and port mapping

• Options → MIDI Devices shows which physical and virtual ports MIDI-OX is using.
• Use View → Port Routing to map inputs to outputs. Ensure the intended input is routed to the correct output port.
• Test by sending notes from your controller and observing both the Event Window and the receiving device (instrument or DAW).

5. Measure latency visually

• MIDI-OX itself doesn’t display numerical latency, but you can infer delays:
  • Send a rapid, single MIDI note from controller; observe timestamped events in the Event Window. Large gaps between send and receive indicate latency.
  • Route the same input through MIDI-OX back to a synth and play while comparing audio response. Any audible lag indicates end-to-end latency (controller → MIDI-OX → synth/DAW → audio output).
• For precise measurement, use a loopback: route MIDI out of the synth back into MIDI-OX and compare timestamps of sent vs returned messages.

6. Use timing and logging for analysis

• Options → Timestamping: enable timestamps to see event times. Use the Event Logger (View → Log) to capture sessions.
• Save logs (File → Save Event Log) then inspect timestamps to calculate intervals between messages and locate delayed segments.

7. Apply filters and mappings to isolate issues

• Options → MIDI Filter: disable message types (e.g., SysEx, Active Sensing) to see whether specific messages cause delays or routing problems.
• Options → Data Mapping: temporarily remap channels/notes to test whether routing by channel is working as expected.

8. Test with and without background applications

• Close DAW, antivirus, Bluetooth apps, or other MIDI utilities to see if latency improves. USB hubs and cable quality can also introduce latency—test direct connection.

9. Diagnose common causes and fixes

• Wrong port routing: Reassign ports in Port Routing.
• Driver issues: Update MIDI interface drivers; try different USB ports.
• Buffering in DAW: Lower audio buffer size in DAW settings for lower audio latency; ensure MIDI-OX routing isn’t forcing extra buffering.
• High CPU/load: Close heavy apps or increase process priority for your audio/MIDI software.
• Sysex or excessive messages: Filter out high-volume messages to reduce congestion.

10. Final verification

• After changes, record another log and compare timestamps. Verify that note events appear promptly and are routed to the intended destination without unexpected duplicates or drops.

If you want, I can provide a concise checklist or step-by-step log example to copy into MIDI-OX.