Re: [linux-audio-user] emu10k1 multichannel support

Lee Revell wrote:

>On Fri, 2005-01-21 at 15:44 +1100, Shayne O'Connor wrote:
>
>
>>when i run jackd using the hw:0 device and my usual command:
>>
>>"/usr/bin/jackd -T -v -R -P60 -dalsa -dhw:0 -r41000 -p512 -n2 -S -i2 -o2"
>>
>>
>>
>
>You can't run at 41000 (or 44100 which is what I think you meant to
>write). This only works at 48000Hz (just like kX ASIO, because it's a
>hardware restriction)
>
>Lee
>
>
>
oops - that is what i meant to write :)

but i probly should've been more clear - i tried my usual start-up
command on hw:0 (with the 44100 rate) in *addition* to trying it at
48000 ... same result (avalanche of x-runs).

i meant to say that i tried (pretty much) all settings (different sample
rates, buffer periods, memory lock/no memory lock) but nothing would get
rid of them x-runs on hw:0 - not even a sample-rate of 48000.

i've heard a lot of negative stuff about creative's native (?) 48000Hz
sampling rate - not being too technically adept, i'm wondering what is
really going on ... is *everything* put in through the ac97 codec
(that's the input port, no?) sampled at that rate? what does this mean
if i'm always setting jack (without the patched alsa) to record at
44100Hz? i know that things start sounding funny if you record at 48000
and then playback/downsample to a different rate .....

should i *always* be using 48000Hz when recording on an emu10k1 card? if
so, what's the best way to get a finished project down to CD-style
44100Hz without making it sound wierd?

shayne
Received on Sat Jan 22 00:15:17 2005