linuxaudio.org

On 6/24/07, Chuckk Hubbard  wrote:
>

quoted text
> Hi Dave and everyone.  I am still wrestling with this.  I have the new ALSA

> driver that supports my card, finally, but under 64studio I still get

> 20-some xruns a second, and Audacity is unable to connect to jackd.

> PortAudio appears for a split second in the jack connection dialog, and

> disappears.  Some of you told me 64studio was preconfigured for low-latency

> audio out of the "box" and all the apps were tuned to the distro, but it

> doesn't seem to work that way for me.

> Anyone know an up-to-date guide to low-latency audio on Debian or Linux?

> There's still a lot of info out there that is obsolete, so I'm wary of

> Google.

> Just a note: I have been trying for several years to get low-latency audio

> working right on Linux.  This is a new machine, though, as of November 06,

> and I had to wait 7 months for my audio card and wireless (still not working

> right) to be nominally supported, so I haven't tried much for about 6

> months.  I'm still amazed at how everything just seems to work without

> tweaking for some folks, and I'm wondering if there's something fundamental

> I'm just not doing.  My problems have baffled some of the very developers

> who created drivers specifically for the hardware I have.  What could be

> wrong?

>

> -Chuckk

>

Chuck,

   Sorry for your problems. However there isn't enough information to

help debug the problem. We'll need hardware specifics, info on the

kernel and how it's configured, what audio card drivers are loaded &

how you are attempting to run Jack, just to start with. We'll start

with that and see where it leads.
   Please provide the output from the following commands:
uname -a

lspci

cat /proc/asound/cards

lsmod

cat /proc/interrupts
and whatever info you can provide on how you are starting Jack. If you

start it in a terminal then the command will be fin. If you use

qjackctl then you can find the command in the message window.
With that we can start to get an idea about what machine you are

working with and how you have attempted to set it up. From there

possibly we can find the mistake and get you going.
good luck,

Mark