Yes. All MIDI processing devices, not only zynthian, have some latency. You can’t process MIDI without adding some latency. Currently, zynthian with its default configuration has a latency of about 10ms. You can reduce this latency by using a smaller buffer size or increasing the sample frequency. We plan to add easy configuration of latency in a future version. Until then, you can adjust latency by modifying the jackd command line parameters, from webconf’s audio config screen. This has been explained several times in recent threads:
I didn’t say this. You can send MIDI clock from zynthian. I just fixed an issue that was causing the filtering of MIDI system messages, and it’s solved now. So please, update and try again. You must create a MIDI chain with no effects, what acts as a MIDI thru. Then select the MIDI input device sending the clock and the MIDI output devices that will receive it.
The same MIDI chain can be used for sending the internal MIDI clock if you select “Internal/Send” as “Clock Source”.
MIDI clock is 24 ppqn (pulses per quarter note). On every pass-thru device, this clock signal is delayed by a fixed offset, that is the MIDI-round-trip latency. Each device in the chain adds its own latency, so the last device see the clock delayed by the sum of delays accumulated. This is sub-optimal but can be enough, depending of how you use it.
Ideally you should route your master clock in a way that it’s received simultaneously by each device, If you are super-picky a star-topology with equal length cables is the best, but using physical MIDI thru is a very good option too, or a MIDI-network protocol like QMidiNet or RTPMidi with dedicated wire, if your devices support it.
The best!