"should not the clock be sent only between start and stop messages?"
No..
START | STOP | CONT events
serves only for preparation for the SLAVE !
Meaning:
after the Slave receives the above..
=
With the "Next Arriving/Incoming CLOCK event" I should start/stop/resume my possible sequence.
The CLOCK Event (24 events per quarter note) as such is required for the SLAVE to determine/calculate the tempo from MASTER.
It is basically even better to send the clock event permanently and not only between START|STOP or CONT|STOP.
The slave can thus calculate the upcoming TEMPO before START|CONT.
The slave has simply more time to calculate the correct MASTER TEMPO!
Otherwise with no
Continuous Clock event:
the Slave receive START or CONT so he should start with the next incoming clock event..
but with only one clock impulse he cant calculate = cant know the correct Tempo
So Continuous sending Clock events can prevents, for example, glitches / delays after START|CONT.
BTW.
Happy new year
-
the Option for Cont. sending Clock events is simply the last option which is missing for REAPERs native Master MIDI Clock.
EDIT
maybe for:if some guys don´t believe and or cant understand my horny english