stefanha
The MIDI Beat Clock is not related to network latency. MIDI is only local to your computer. jammr does not transfer MIDI over the network.Another way of explaining the current clock drift behavior is that jammr knows the right time at which to emit a MIDI Beat Clock message, but the MIDI message is sent at an arbitrary point in time afterwards. The precise timing currently depends on your computer or you could say it's left up to chance. Adding a timestamp will ensure that the receiver knows exactly when the MIDI Beat Clock message is supposed to happen, regardless of when it was actually sent and received. This should significantly reduce drift.Don't worry, I will get to this if no one else does before me. At the moment it's looking like 3 weeks.
Thanks for the response, really appreciate it.
One thing to consider, why is it that a VST drum machine can stay in sync without the same issues as MIDI clock? Maybe there's a fix there?