日本語

DBR-1

MIDI clock timing — how it works, what we measured, how to sync

This page is for people who use DBR-1 as the MIDI clock master (CLOCK: SEND) to drive other gear. It explains how DBR-1 sends clock on Android, what we measured, and which connections and settings give the steadiest sync. The settings themselves are described in the user manual (MIDI chapter).

1. In short

2. How DBR-1 sends clock

Timing comes from the audio engine

MIDI clock carries no tempo number: the receiving device works out the tempo from the time between clocks (24 per quarter note). So every clock has to leave on time.

A sender that the screen cannot pause

The clock gets priority on the wire

3. What we measured

Method: the tablet (Lenovo Tab K11, Android 15) was connected to a Windows PC by USB in MIDI mode, and a small program on the PC logged the arrival time of every clock. We compared each clock with a perfectly straight tempo line. A dedicated hardware groovebox was measured the same way as a reference. USB carries MIDI in 1 ms frames, so differences finer than about 0.3 ms cannot be seen with this method.

Against dedicated hardware (134 BPM)

Median deviation90% withinOver 1 msOver 2 msLargestTempo std. dev. per beat
Dedicated hardware groovebox0.19 ms0.46 ms0.19%0%1.2 ms0.13 BPM
DBR-1 on Lenovo Tab K110.22 ms0.51 ms1.97%0.56%5.1 ms0.17 BPM

At different tempos

TempoMedian deviation90% withinTempo std. dev. per beat
84 BPM0.22 ms0.55 ms0.07 BPM
134 BPM0.21 ms0.53 ms0.22 BPM
174 BPM0.21 ms0.52 ms0.31 BPM
Why the tempo display moves more at fast tempos: the timing wobble is the same at every tempo. But a receiver computes the tempo from the time between a fixed number of clocks, and at a fast tempo that time is shorter, so the same wobble becomes a bigger tempo number (roughly with the square of the tempo). This is true for any clock source, not only DBR-1.

Inside the app

In an engine-only test across 84–174 BPM, with swing, odd pattern lengths and jittery audio callbacks, the scheduled clock times were off by at most one sample and the average tempo was within 0.0006 BPM. On the tablet, about 0.3% of clocks took more than 1 ms to hand over to Android; the rest of the late clocks seen on the PC happened after that point.

What did not help

4. Using DBR-1 as the master

Connections, steadiest first

  1. A MIDI-only USB device with USB DIRECT on: a MIDI interface, or a keyboard / controller with a MIDI OUT port (drive your gear from that port). This skips Android's MIDI service. While it is on, MIDI IN from that device is not available; after turning it off, re-plug the device.
  2. The normal path: an audio interface's MIDI OUT, a synth that also carries audio over USB, a computer. Accuracy as in section 3. Devices that carry audio are detected and always use this path.
  3. Bluetooth MIDI has more delay and wobble and is not suitable for clock. (DBR-1 does not support Bluetooth MIDI.)

Settings in MIDI…

Keep the MIDI port from getting crowded

The clock is never held back, but on a 5-pin port notes and CCs can arrive a few ms late when it is busy: chords on several channels, many pads with MIDI assigned at a fast tempo and lots of moving CCs add up. If the external device ignores a channel, set it to ignore that channel, or uncheck NOTES / CC in MIDI….

About the device

If the wobble bothers you, use a separate master (a dedicated MIDI clock, a DAW, a drum machine…) and run both DBR-1 (CLOCK: RECEIVE) and your other gear from it. DBR-1 keeps its own time and lines up smoothly with the incoming clock, so small wobble in the clock does not shake its rhythm. DBR-1's own sound is timed by the audio engine and is not affected by MIDI clock wobble in any case.

5. Known limits

← User manual · DBR-1