On Mon, 2007-02-26 at 23:48 +0100, e 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
>
> Thanx4dareplies,but it doesn't really help me out here.Of course I know Ardour
> uses the samplerate jack is started at,but as I stated in my initial post(do
> it all over again):no matter how I start jack,Ardour keeps using 48k.
many consumer audio interfaces only run a 48kHz. if JACK is using the
hw:N devices via ALSA (the default) this is the only rate it will ever
run at. you could tell JACK to use plughw:N instead but then you get
nasty ALSA resampling code between JACK and your speakers.
either get a new interface or learn to live with 48kHz or put up with
ALSA's resampling code or reimplement the latter. 4 options to choose
from. freedom! :)
--p
Received on Tue Feb 27 04:15:04 2007
This archive was generated by hypermail 2.1.8 : Tue Feb 27 2007 - 04:15:04 EET