From: Florian S. <mis...@gm...> - 2009-03-26 18:35:18
|
On Thursday 26 March 2009, david wrote: > D. Michael McIntyre wrote: > >> I was hoping to be able to link to an illustrative video about this, > >> but I can't find it any more. > > > > Ouch. I remember you telling us about this at the time. That kind of > > thing really is difficult for us to deal with too, because ALSA is too > > arbitrary about numbering things. Well, a very large case in point here, > > every time I reboot my computer, I have to reconfigure JACK to use the > > ice1712 soundcard. It's as random as my old TRS-80 Color Computer, where > > you had to keep hitting the reset button until the color on the screen > > randomly turned red instead of blue. I've tried to deal with this > > before, and nothing has worked. I have no way to know which card will > > come up hw:0 for any given boot. > > That happens to me all the time with the onboard sound on my laptop and > the external USB sound card I prefer to use. Sometimes the onboard sound > is hw:0, sometimes it's hw:1 or hw:2 (ALSA is stupid - it considers the > onboard Intel modem a sound device because it's controlled by the same > chipset!) Doesn't ALSA support aliases for devices? If so, maybe RG > could allow us to specify a device by alias? Hi, there's a simple fix for the numbering. Every ALSA sound card driver supports an "index" argument with which one can specify the hw number. Your distribution's documentation should have a section specifying how to set module options (on ubuntu for example /etc/modprobe.d/options is a place to specify these).. ALSA is not to blame, it's your distribution or you, depending on the point of view ;) Regards, Flo -- Palimm Palimm! http://tapas.affenbande.org |