Need for beat perfect tempo sync at core level

[khz]

But comes in the future, certainly slowly since the hen egg phenomenon also prevails here.

I would also find 14 bits useful.

Internal MIDI resolution in 14 bit?

Would it be possible in the mod to realize the internal MIDI resolution in 14 bit instead of the usual 7 bit? This would have an enormous added value IMHO. I know this from the C15 which runs with a Linux (audio/MIDI).

With what actually runs ModAudio jackd, raw or jackmidi? Raw MIDI is the most stable/most direct.

However, well known is as well, that jack-midi never was done for interact with “hardware synthesizers”. For hardware midi handling you indeed better use raw alsa.
That changed, when interaction with software midi devices steps up in the game.
jack-midi is handled in the realtime-audio thread of jack. Developers needs to be aware that anything not real-time save shouldn’t be done in the jack_process_callback, regardless if it is midi or audio. You may imagine that a couple of VSTi plugs ain’t have a clue about this.
jack-midi does exactly what jeff proposed, no timestamp, plain messages handled as they comes in.
I must admit that I use midi only as a controlling interface, so jitter ain’t matter for me, but, for my use case, jack-midi is the best, and painless choice for me and the users.

Source: Loading...

I find the internal clock on the DuoX quite stable.I think tick_double was useful.

Now, for the rationale behind the transport tick_double API update:
When using JACK transport to sync between clients with precise timing requirements (such as MIDI sequencers) rounding errors would accumulate and eventually make the separate clients out of sync.
This was observed in Carla and mod-host, which use audio plugins as JACK clients. Some MIDI plugins could miss notes due to rounding errors. This change has been deployed in MOD Devices for a couple of releases already and it is known to work (that is, it corrects the situation).
There were discussions on IRC about this potentially be unnecessary, that clients can just use bar_start_tick to store the non-integer part of the tick.
While the idea could work in theory, supporting it turns out to be non-trivial and from all applications that I have tested none implemented this part correctly.
Some applications do not set bar_start_tick at all, even though they can be run as transport master.

Source: JACK2 v1.9.19 release | JACK Audio Connection Kit

How it behaves in sync mode I have not checked. Random MIDI jitter is not really musical. IMHO