On Thu, 2010-05-13 at 06:56 +0000, Frank Kober wrote:
PA or not, this is somewhat getting back to the
original question: how
can we get a reliable index assignment on startup with several
soundcards.
I'm not using PA, but mostly because I noticed that it uses (much)
more CPU with many desktop applications, due to resampling I was told.
I have an internal HDA, an nvidia graphics chip, a nanokontrol and a
UA-25.
The latter both use snd-usb, though one obviously cannot produce
sound.
The nvidia chip seems to expose an audio device (?) handled by a
snd-hda-intel module, as does the snd-hda-intel soundchip. Although
the first one cannot produce sound.
So I would like the following order to be maintained to have desktop
applications adress a working soundcard and to have the UA-25 always
at the same index for JACK.
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfbff8000 irq 32
1 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfde7c000 irq 16
2 [UA25 ]: USB-Audio - UA-25
EDIROL UA-25 at usb-0000:00:1d.0-1, full speed
3 [nanoKONTROL ]: USB-Audio - nanoKONTROL
KORG INC. nanoKONTROL at usb-0000:00:1d.0-2,
full speed
But why is index important to you? hw:Intel, hw:NVidia, hw:UA25 and
hw:nanoKONTROL are the predictable device names ALSA gives you.
A basic .asoundrc would be something like below, although you'd probably
want dmix too.
pcm.!default {
type hw
card NVidia
}
--
Peter