Re: what's up with midi clock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, May 30, 2009 at 3:46 PM, Gabriel M. Beddingfield
<gabriel@xxxxxxxxxx> wrote:

> Does sooperlooper respond to Song Position Pointer (0xF2) and/or MIDI Continue
> (0xFB)?  You may be able to sync time using these instead of Song Start (0xFA).
>  Song Position Pointer sends a 14-bit song position, followed by a MIDI
> Continue which means ("start playing at that spot on the next clock tick").  The
> 14-bit song position is in "MIDI beats" since the beginning of the song.  6 MIDI
> Clocks == 1 MIDI beat.

SL does not respond to SPP, but it probably should.

> Also, I noticed that sooperlooper is determining tempo by some manner of rolling
> average calculation.  (Maybe it doesn't, but that's the way it *acts*.)  If so,
> that makes it even harder to get sooperlooper to sync to a downbeat.

It does indeed determine the displayed tempo by a rolling average, but
for sync purposes it responds immediately upon receipt of the relevant
clock ticks.

jlc
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user


[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux