<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Greetings, HamRadio.<br>
<blockquote
cite="mid:291cdeab0910250801l1e702ff0l77bd0a853236f082@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Anyone here have perhaps some more hints to get alsa route its output
to jackd?<br>
Thanks in advance for answering.<br>
</blockquote>
</div>
</blockquote>
I decided to try to figure out a good way, because my live performance
hardware is also my all-purpose PC :-) So far it seems to be working
very well, and because of some of the below, I think my latency has not
suffered. <br>
<br>
My first step was to identify the alphanumeric name (as opposed to the
number!) of the sound device I want to use for everything. This is
done thusly:<br>
<blockquote><tt>$ cat /proc/asound/cards</tt><br>
</blockquote>
I received the following from the above:<br>
<blockquote><tt> 0 [HD2 ]: Prodigy71HD2 - Audiotrak Prodigy
HD2<br>
Audiotrak Prodigy HD2 at 0xef80, irq 10<br>
<br>
</tt></blockquote>
You should have at least two items, because both your motherboard and
your Edirol are active. If not, your Edirol is not configured
completely to work with ALSA, and I'm afraid I cannot help :-) Anyway,
providing that both your motherboard sound and your Edirol are visible
as items in /proc/asound/cards, you will have one alphanumeric name per
sound system; the ones you want are in the square brackets []. So my
card's ALSA name is "HD2".<br>
<br>
My second step was to test Jack applications using this alphanumeric
name. In qjackctl setup, in the "Interface:" field, usually it reads
either <tt>(default)</tt> or a numeric device number, e.g., <tt>hw:0</tt>.
In my case, I set this field to read <tt>hw:HD2</tt>. Suddenly all
sound on the machine began behaving a bit better. I don't know
entirely why, but I suspect the numeric-to-alphanumeric translation in
ALSA either runs slow or gets confused or both. No matter;
alphanumeric is far better, the numerics do definitely get confused
when USB audio is plugged in et cetera. I ran in AVLinux just like
this for a while; AVLinux gives me an MPlayer which will do Jack, which
is nice, but some annoyances remained. <br>
<br>
My third step was to get the ALSA2Jack plugin in. This is a module for
ALSA, which permits it to send output to Jack. The idea is that I need
two audio data paths. The first is for general latency-irrelevant
applications, jack-incompatible, which will run
App-->ALSA-->Jack-->ALSAdevice. The second is for
latency-critical applications, which will run
App-->Jack--ALSAdevice. If we set up the ALSA2Jack plugin's virtual
device, as default audio device, and tell Jack to run all of its output
direct to the ALSA sound device of explicit choice, we should get the
best of both worlds.<br>
<br>
So. This being AVLinux (Debian), I had to install package
"libasound2-plugins", to get the ALSA2Jack plugin in.<br>
<br>
The last step was to vary Ray's .asoundrc a bit. I am using the
below. The only significant change, is the ALSA mixer is set to point
to the alphanumeric name of my ALSA sound device. Probably should
reboot after changing it, just in case. On the other hand I use it as
an /etc/asound.conf, which is just a bit different; I don't like the
idea of sound configs changing at login, I want them nailed to the wall
at boot :-)<br>
<br>
J.E.B.<br>
<br>
<tt>pcm.!default {<br>
type plug<br>
slave { pcm "jack" }<br>
}<br>
<br>
pcm.jack {<br>
type jack<br>
<br>
playback_ports {<br>
0 alsa_pcm:playback_1<br>
1 alsa_pcm:playback_2<br>
}<br>
<br>
capture_ports {<br>
0 alsa_pcm:capture_1<br>
1 alsa_pcm:capture_2<br>
}<br>
}<br>
<br>
ctl.mixer0 {<br>
type hw<br>
card HD2<br>
}<br>
<br>
<br>
</tt>
</body>
</html>