20 Feb
2010
20 Feb
'10
3:36 p.m.
Paul Davis wrote:
On Sat, Feb 20, 2010 at 11:03 AM, Ralf Mardorf
<ralf.mardorf(a)alice-dsl.net> wrote:
My bad, I made this error in reasoning once before. Now I do remember.
If Linux apps would use JACK transport the coders
only would have to
take care to handle this. Just having on app doing sync among JACK and
eternal MIDI would reduce the risk of trouble. Btw. MTC should be part
of such an app too ... I didn't read the whole thread, perhaps this was
mentioned before.
this isn't true.
one of the most deliberate and conspicuous design decisions of the
JACK transport API is that there is no support for varispeed.
sync requires knowing two things: where we are, and how fast we are
going. JACK transport has only 2 answers the the second question
(stopped, rolling). this isn't adequate to fully capture the notion of
sync.