6 Jan
2005
6 Jan
'05
10:04 p.m.
OK, so now I want to make Ardour master over Jackd,
right? So, I go into
"Options" and there I find that timing sync says "Master" suggesting
"Ardour" is master. Below, two options are checked "Jack something
(can't
remember)" and "Jack transport sync" or something like it (currently away
from my beloved Linux box).
In the "Sync" tab, you set "Positional Sync" to "Sync to
JACK".
The other options are "Internal", which means Ardour controls its own
transport with no involvement of any other systems, or "Slave to MTC"
which means that MTC will control the transport position (and its
implied that MMC will control transport operation).
The Jack Time Master option is orthogonal to all of these (which is
why it is a separate option), and simply determines whether its Ardour
that sets the JACK transport time.
Once you have selected "Sync to JACK", Ardour's transport control gets
"proxied" through JACK, and Ardour responds to JACK. When you press
"Play" on any application that is sending transport controls to JACK,
Ardour will start rolling, etc.
It is entirely possible that 0.9cvs041014 is taken from CVS at a time
when this functionality was broken while major changes to slaving were
going on to get MTC slaving to work.
In addition I tried recording something and as soon as
I press record and
play on an audio track I get:
"CRITICAL: UI request POOL OUT OF MEMORY - RECOMPILE WITH LARGER SIZE!!!"
And then... crash.
I am using Mdk 10.0 (Thac's rpms) stuff (ardour-0.9cvs041014). I also tried
10.1 (ardour beta22) on a different 10.1 Mdk machine and I got the same
errors...
This is an old bug that has not been reported in some time. I am very
puzzled that 0.9beta22 could generate the same error.
--p