Re: [sc-users] MIDISyncClock (happy new year!)

[jamshark70@xxxxxxxxx]

On Mon, Jan 7, 2019 at 9:46 PM <jmckernon@xxxxxxxxx> wrote:
> Oh, I see that its 'tempo' variable isn't really used for anything
> internally, it's just available for querying. So if it's already
> known, there isn't really any sense in passing it in and asking for it
> back again.So never mind that part! But the class still seems useful.

Hi,

It is used -- it's the relationship between beats and seconds. (There
are still a couple of issues with that conversion logic, which I'll
get to when I can.)

MIDISyncClock is the slave. The tempo comes from the external clock
source. So, you can't set the tempo on the clock object. Otherwise,
someone will set e.g. tempo = 2 while the external clock is sending
tempo 1.8, and then wonder why it's broken.

MIDI messages are subject to timing jitter, so the tempo is not 100%
exact and stable. You should consider it an estimate. (This means, for
example, after I rewrite beats2secs and secs2beats, they will still
not be reliable in the way that it's reliable for TempoClock --
because the tempo is always changing.)

The new help file recommends that, if you can arrange things so that
SC is the master (sending MIDI clock), that's likely to be better.

hjh

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/