FWIW and semi-related. Here are my findings of a Force's MIDI Out and Gate Out jitter. Recorded from the physical electrical TRS MIDI output, into a computer audio interface's audio input, as 44100 Hz audio WAV file on a computer, and differences between times of starts of consecutive MIDI messages i.e. timing jitter measured from the WAV file with a Python script. Python code included in the opening post.
viewtopic.php?f=49&t=214354 In my tests, maximum MIDI note-on jitter on a 120 bpm 4ppq pattern was close to 3 ms. Surprisingly, MIDI Clock seemed to jitter slightly more, even though it should be a "realtime" message with maximum priority.
Gate Out jitter was over 4 milliseconds, and it's either -4, 0, or +4 milliseconds all the time, looking like the gate signal is driven by a 240 Hz timer interrupt. Maybe the Force is worse in this regard than an MPC. I don't have a physical MPC I could test with.
Particularly the MIDI Clock jitter is much worse than what I compared it with, Arturia Keystep 37.
Whether any of this matters at all for person X, is completely up to person X to decide.
A surprising finding I made during this testing was that it takes 10 ms for a MIDI message to simply pass through the Force. Set a track to monitor a MIDI input, reroute to a MIDI output. A Note-On message sits waiting inside the Force for 10 milliseconds to be sent out.
I don't know how the older MPCs operate, but with the current generation, _internal_ MIDI timing, when the MPC or Force is the clock master and its own sequencer is triggering its own samples, then the timing is sample-accurate, and there's no jitter. Things start to go slightly downhill when sending MIDI messages between separate devices. This seems to be common with all DAWs, and MPC/Force is just a DAW in a box.