Blog

How to investigate MIDI clock drift on a USB-C adapter

Learn how to tell whether MIDI clock drift comes from a USB-C adapter, the source, or the receiving device, with repeatable checks and a browser MIDI test.

Daniel HayesHardware tests Tests 6 min read

A sequencer starts in time, then its notes or loops gradually move ahead of or behind the beat. If you use a USB-C MIDI adapter, it is tempting to blame the adapter, but the clock source, receiving device, cable, or software can cause similar symptoms.

Check whether clock messages reach your computer, then change one part of the setup at a time. TooLab's MIDI Test can help confirm that MIDI data is reaching the browser. It is not a precision clock analyzer, so use it as one check rather than proof that timing is perfect.

Check the MIDI clock path

  1. Open the MIDI Test in Chrome or Edge on a computer. MIDI Test does not work in Safari. If the browser asks for MIDI access, allow it.
  2. Connect the clock source to the adapter's MIDI input, if it has one, and connect the adapter to the computer. If the source sends MIDI over USB directly, connect that device instead. Make sure the cable is in the source's MIDI OUT and the adapter's MIDI IN.
  3. Start the clock source and watch the test for incoming messages. If the test offers a device list, choose the input connected to the source. MIDI Clock uses repeated real-time messages, often identified as clock or as the MIDI byte F8. The test may show messages without labeling their precise arrival times.
  4. Repeat the same setup while changing only one part: use a different USB-C port, remove a hub, or swap the MIDI cable. Note whether the receiving device's drift changes, and whether the test continues to receive messages.

For a useful comparison, keep the same tempo, source, receiving device, and test duration. If you can, compare the adapter with a second known-working MIDI interface. Don't change several connections or settings at once, or you won't know which change mattered.

What the result means

No MIDI messages appear

The browser is not receiving MIDI data from the selected input. This does not prove the adapter is faulty: the source might not be sending clock, the cable could be reversed, the wrong input could be selected, or the browser may not have access. First confirm that another kind of MIDI message, such as a key press, reaches the test. If no messages arrive at all, investigate the connection before diagnosing clock timing.

Messages arrive, but the receiving device drifts

The computer sees MIDI data, but that alone does not prove it is receiving every clock tick at an even interval. MIDI Clock sends 24 pulses per quarter note. At 120 beats per minute, that is one pulse about every 20.8 milliseconds. A browser message display is not a calibrated timing instrument, so use a DAW's MIDI monitor or the receiving device's timing display for a closer check.

Drift changes when you bypass the adapter

The adapter, its cable, its driver, or the USB connection becomes a stronger suspect if the same source and receiver behave reliably when connected another way. If bypassing it makes no difference, check the source and receiver settings next.

The timing jumps around but does not steadily drift

Short, irregular timing changes are usually described as jitter. Gradual movement that builds over several bars is drift. Busy software, USB connection interruptions, or a receiver that does not follow external clock consistently can cause different patterns, so note whether the problem is gradual or sudden.

How to narrow down the cause

  1. Confirm which device is the clock master. Set one device to send MIDI Clock and the other to follow external MIDI Clock. If both generate their own clock, they can disagree. If neither is master, the receiver may free-run at its own tempo.
  2. Check the sync type. MIDI Clock is a stream of tempo pulses. MIDI Time Code is a different way to communicate timing and position. Make sure the source and receiver are set to the same kind of sync rather than expecting one to follow the other.
  3. Connect the adapter directly. Remove the USB hub or dock for a test and use another USB-C port. A direct connection helps rule out a flaky hub, loose connector, or shared connection problem.
  4. Try a known-good data cable. Some USB-C cables are made for charging and may not carry data reliably. Replace the cable for a comparison, and check that MIDI DIN cables run from source OUT to adapter IN.
  5. Check that the computer recognizes the interface. On Windows 11, right-click Start and open Device Manager. Look under Sound, video and game controllers or Universal Serial Bus controllers for the interface, and check for a warning icon. On macOS, open Applications › Utilities › Audio MIDI Setup, then choose Window › Show MIDI Studio. Seeing the device listed confirms recognition, not accurate clock timing.
  6. Close other MIDI software and reconnect. Quit DAWs and MIDI utilities, disconnect the adapter, reconnect it, and test again. An application may be holding or routing the input in a way that changes what another program receives.
  7. Check the manufacturer's driver or firmware. If the adapter works inconsistently on one computer, look for an official driver or firmware update for its exact model. Restart after installation, then repeat the same test.
  8. Compare another source or receiver. Keep the adapter in place and change only the clock source, then repeat with another receiver if available. If the problem follows one device, focus on that device's sync settings or hardware.

When the adapter may be faulty

Suspect the adapter when the same clock source and receiver work reliably with another interface, but drift or interruptions return with this adapter across multiple cables and USB ports. Check for a loose USB-C plug, bent MIDI pins, or a connection that drops when the cable moves. Avoid repeatedly flexing a damaged connector while it is powered.

If the adapter is under warranty, contact its manufacturer or seller with the model, computer, operating system, cables tested, and a short description of how the timing changes. For an inexpensive adapter that fails across multiple setups, replacement may be more practical than repair.

Why the browser test has limits

A browser can request MIDI access and display incoming messages, but it is not a dedicated hardware timing analyzer. Browser scheduling, the operating system, and the USB connection can affect when a message appears on screen. A visible stream confirms that messages are arriving, but it cannot certify that every pulse arrives at the correct interval.

For a drift measurement, use a DAW or hardware monitor that can show clock timing, and compare repeated runs with the same tempo and devices. The browser test is most useful for the simpler question: does MIDI data reach this computer at all?

More articles