5 Oct
2003
5 Oct
'03
4:48 p.m.
arg! I forgot to switch the thing again, and so i have to send this twice
in case it gets rejected - sorry if it's a duplicate...
Basically true. The main practical difference between
SMPTE timecode
and MTC is that the SMPTE timecode is encoded in an audio stream. If
digitized and fed to a JACK port, this becomes sample-synchronous,
which can potentially provide excellent timing. Synching to an
external SMPTE clock will be difficult for many JACK clients because
of clock drift. But generating SMPTE from within a JACK timebase
master client should be very solid, because then there's only one
clock source.
yes this sort of confirms what I said in another post, which is that it
would be really good to use jack as a master time code hub and have
everything (internal AND external) sync to that...
the other sample accurate sync (the one I've always trusted the most) is
ADAT sync
MIDI messages are generally not delivered with
accurate timing by
existing Linux interfaces. I believe this is why ardour has trouble
with it.
hmmm - I see