Re: [seq24-users] Midi Clock Sync patch (slave seq24 to external sequencers)

[Kevin M. <ke...@su...>]

true, I didn't notice this part.   some devices send clocks all the time...
so you only want to act on them if you got a start...

midi sync works already, Alex.  though like guido points out, it may be
lacking some checks.   Another person verified it maybe a month ago as
well...
I've tested x0xb0x -> seq24 as well as  seq24 -> seq24

---
kevin meinert | http://www.subatomicglue.com


On Thu, Jun 25, 2009 at 8:37 PM, Alex <x37...@gm...> wrote:

> > MIDI Clock:
> >  * if not running, start running
> >
>
> This is incorrect.  Masters may send clock messages even if slaves
> shouldn't be syncing... before a start or continue message is sent or
> after a stop message is sent.
>
> "A master stops the slave simultaneously by sending a MIDI Stop
> message. The master may then continue to send MIDI Clocks at the rate
> of its tempo, but the slave should ignore these, and not advance its
> "song position". Of course, the slave may use these continuing MIDI
> Clocks to ascertain what the master's tempo is at all times. "
>
> The clock ticks are simply for syncing, the start/stop/continue are
> what you use to initiate or end playback.
>
> MIDI sync in for seq24, awesome!
>
> -Alex
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>