3 ms·
If you care about timing over Midi, use MTC not Midi Clock. Because receivers have to derive clock frequency by counting pulses, Midi clock is inherently unstab
by brudgers 6mo ago
If you care about timing over Midi, use MTC not Midi Clock. Because receivers have to derive clock frequency by counting pulses, Midi clock is inherently unstable.
Midi Time Code is SMPTE.
- embedding-shape 6mo agoFun, I do the opposite, explicitly use Midi Clock so everything is purposefully a tiny bit out of sync, seems to sound better to me, "Midi clock is inherently unstable" is the feature I like :)
- bitwize 6mo agoMIDI clock on the Atari ST was rock solid. It being "inherently unstable" is one of those accidental things, like Windows 9x users assuming "computers just crash all the time".
- brudgers 6mo agoNo matter how solid the source of Midi clock, the receiver has to interpolate it’s own clock from multiple midi clock messages. Those messages arrive after passing through a network with arbitrary reliability, latency, and jitter. The instability is at the protocol level. That is why Midi timecode exists.