[LAU] Sync'ing a ProTools studio with a Linux studio

[Paul Davis]

On Thu, 2007-10-11 at 13:17 -0700, Ken Restivo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Thu, Oct 11, 2007 at 02:15:13PM -0400, Paul Davis wrote:
> > On Thu, 2007-10-11 at 10:46 -0700, Ken Restivo wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > > 
> > > On Thu, Oct 11, 2007 at 11:35:42AM +1000, Geoff Beasley wrote:
> > > > Hey Ken.
> > > > MTC in Ardour is the best you'll find. Just run Ardour as Jack time master 
> > > > with  MTC out enabled. Get the FPS right between Ardour and Pro-Tools. Have 
> > > > Pro-Tools slave to MTC ( i suppose you can do that...never used PT !) then 
> > > > set RG to slave to Jack sync and it will be slaved to Ardour and so will  PT.
> > > >  Control everything from Ardour's transport.
> > > > 
> > > > will work a treat,
> > > > 
> > > 
> > > Well, not really. I need to slave *my* studio to his, not the other way around.
> > 
> > ardour will slave to MTC and MMC from protools. it will lock and chase
> > better than almost any other system you could get your hands on.
> > 
> 
> Cool!
> 
> My next question is: while it is locking and chasing MTC, will it simultaneously be a JACK Transport master so as to control all my other sequencers, loopers, etc?
> 
> Cause that's what I need.

you can't do that with JACK, because we are not willing to require that
every JACK client can do varispeed. since MTC is inherently varispeed
(it may not run exactly in time with the sample clock), we can't slave
to MTC and export the result to the JACK transport system.

sequencers and loopers do not follow MTC anyway, and many don't
understand a linear timeline either.

--p