> On Mon, 2007-02-26 at 19:42 +0100, prg@email-addr-hidden wrote:
>> Am Montag, den 26.02.2007, 19:23 +0100 schrieb e:
>>> When I start Ardour it always comes up in 48k,even when I start jack in 44100.
>>
>> Ardour doesn't "start" with a specific sample rate. Rather, it uses the
>> sample rate of the current session (which it deduces form the source
>> samples used). Then, it tries to connect to jack, which -- of course
>> will be only successfull, if there is a jackd with the correct sample
>> rate currently running).
>
> this is not correct. ardour has no concept of "session sample rate" at
> all. it connects to JACK at whatever rate JACK is running at.
>
>> PS: under some circumstances, Ardour is (was?) able to start up a
>> jack demon on its own. You will see this on the output of the terminal
>> you used to launch Ardour. Often this ist not what one would expect
>> and want....
>
> this capability exists in all JACK clients and is controlled by the JACK
> environment variable JACK_NO_START_SERVER
And at least in Debian, it is (unfortunately) possible to install two
jackd's. One into /usr with normal package management, and one to
/usr/local if you build it manually. So if you built jackd and ardour but
you still have the Debian version of jackd running, ardour will try to use
the /usr/local one.
Things might have changed now, but at least I have experienced this at
some point.
Tommi
Received on Tue Feb 27 20:15:02 2007
This archive was generated by hypermail 2.1.8 : Tue Feb 27 2007 - 20:15:03 EET