Posted by: foksadure
« on: November 07, 2023, 04:05:52 PM »It is much more interesting to test MIDI Clock and note timing with an external device.
MidiGAL is great for that, with its dedicated Clock generator or testing firmware (MIDIPal compatible):
https://midisizer.com/midigal/midiclk/
https://midisizer.com/midigal/midiclock-tester/
It's good for real-time measurements, and to confirm one's feeling about the MIDI tightness of a specific hardware/software combination.
On Windows 9x, Cubase 2.83/3.05 with legacy serial/parallel MIDI interfaces were my champion, until I got a Midex8 which unlocked the power of the LTB protocol included in VST5.
Actually, I've yet to test a software or hardware sequencer that's more accurate with MIDI clock than MIDI note events. Which makes sense, even though clock is supposed to have the highest priority in the MIDI norm.
MidiGAL is just missing a way to externally record data logs, to automatically import datas generated by longer stints into a spreadsheet.
MidiGAL is great for that, with its dedicated Clock generator or testing firmware (MIDIPal compatible):
https://midisizer.com/midigal/midiclk/
https://midisizer.com/midigal/midiclock-tester/
It's good for real-time measurements, and to confirm one's feeling about the MIDI tightness of a specific hardware/software combination.
On Windows 9x, Cubase 2.83/3.05 with legacy serial/parallel MIDI interfaces were my champion, until I got a Midex8 which unlocked the power of the LTB protocol included in VST5.
Actually, I've yet to test a software or hardware sequencer that's more accurate with MIDI clock than MIDI note events. Which makes sense, even though clock is supposed to have the highest priority in the MIDI norm.
MidiGAL is just missing a way to externally record data logs, to automatically import datas generated by longer stints into a spreadsheet.