Aha! Andrew:
Sure, just use Input instead of InputQueue
Would be interesting if that makes a difference for MIDI-clock, if it’s not already implemented that way in the Core MIDI module.
Tried it yesterday … but I am a shitty c++ programmer so my first Module did ABSOLUTELLY NOTHING.
Well at least it did build 
No, has nothing to do with it. The issue you’re describing is because midi::Message does not contain a timestamp, so MIDI modules do not attempt to correlate MIDI timestamps with the engine frame number.
@Vortico sorry to bother again, but …
is this on rtmidi.cpp side or generally? Or is this regarding the midi::message from vcv?
Would it be possible (or would it be of interrest) to include or set a TIMESTAMP in the midi::message for the special case of 0xF message in Rack v2.x.x.?
Ooohhh, now all we need is a module for sending (and receiving maybe also) MIDI program change 
I don’t address feature requests on this forum. See the forum rules.
Sorry … moved to https://github.com/VCVRack/Rack/issues/1654
for all topic readers =>
Yeah, sounds great!
You might find my write-up from today relevant, with good results using Rack as master sync: