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

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

#1
>> MIDI Clock:
>>  * if not running, but prepared to run by "Start" or "Continue" then
>>  start running

#2
>> 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".


These two statements are different.   In #1 You say (and your code change
reflected this) that on a midi clock message, it "prepares to start ... then
start(s) running"...      But the spec you pasted in #2 says that the slave
should ignore the clock messages until it's actually running...  (which
makes a lot more sense in practice, from observing what devices do, and
thinking about what they could do incorrectly)...

Your code breaks continue support.  I verified this by testing with a yamaha
rm1x.
start/stop worked.
I didn't have a device that spams clock messages to see what happens in the
case of STOP then CLOCKs with your code, but from reading the code, I don't
know that what you have would be desireable (to start the sequencer on a
CLOCK message while STOPped...)

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


On Fri, Jun 26, 2009 at 11:29 AM, Guido Scholz
<gui...@ba...>wrote:

> Am Thu, 25. Jun 2009 um 18:37:43 -0700 schrieb Alex:
>
> Hi Alex,
>
> > > 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.
>
> Sorry, my description was too short. The current implementation does
> something like this:
>
> MIDI Clock:
>   * if not running, but prepared to run by "Start" or "Continue" then
>    start running
>
> This should comply to the text below (as far as I understand):
>
> > "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. "
>
>
> > MIDI sync in for seq24, awesome!
>
> Are you able to run tests of the current code with your hardware?
>
> Guido
>
> --
> http://www.bayernline.de/~gscholz/ <http://www.bayernline.de/%7Egscholz/>
> http://www.lug-burghausen.org/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKRPdPk6cKJms5yBsRAgx7AJ4y2V+VR/9SzTagYMWF+yr/Q9cWCwCfUlwq
> 3gjrKWhG9r4hDU3biWSgsKQ=
> =q1/X
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> seq24-users mailing list
> seq...@li...
> https://lists.sourceforge.net/lists/listinfo/seq24-users
>
>