[LAD] midi beat clock

Rui Nuno Capela rncbc at rncbc.org
Sat Feb 20 01:49:37 UTC 2010

On 02/20/2010 01:00 AM, Tim E. Real wrote:
> On February 19, 2010 07:51:58 pm Rui Nuno Capela wrote:
>> On 02/20/2010 12:40 AM, m.wolkstein at gmx.de wrote:
>>> for more information's read here.
>>> http://en.wikipedia.org/wiki/MIDI_beat_clock
>>> my question, exist something like this for alas. i am interested to send
>>> midi beat clock signals from hydrogen to external hardware
>>> synthesisers/arpeggiators. and i am explicit not interested to sync them
>>> to any timecode. because the external machines have to run independent
>>> and in a randomly order. they only have to sync there beats.
>>> here the mbc specs.
>>> midi beat clock defines the following real time messages:
>>>     * clock (decimal 248, hex 0xF8)
>>>     * tick (decimal 249, hex 0xF9)
>>>     * start (decimal 250, hex 0xFA)
>>>     * continue (decimal 251, hex 0xFB)
>>>     * stop (decimal 252, hex 0xFC)
>> this is all about midi clock and song position pointer (spp) events.
>> question is: which devices, hw or sw, are there that sync to midi clock?
>> i'm afraid there's none.
>> but wait, there are some that respond to spp: ardour, qtractor,... maybe
>> many others ;)
> MusE-1 syncs to midi clock,


> and responds to start, stop, continue and spp.

well, i've made the cardinal sin to put "start", "stop" and "continue"
in the same bag as of "spp" ie. song position pointer. which all refer
to midi-clock aka midi-metronome time base, whatever

> It also transmits them. It also recognizes tick but doesn't use it.
> From what I understand, tick is nothing more than a periodic 'keep alive' 
> signal, not a sync signal. I could be wrong though...

this "tick" signal (0xf9) must be (is it?) some leftover from ancient
midi times, if ever used effectively. i fail to recognize its use but
being just, uh,... _undesirable_ noise:)

i'll turn off
rncbc aka Rui Nuno Capela
rncbc at rncbc.org

More information about the Linux-audio-dev mailing list