Steve A wrote: > hello, > > This happens in all versions, I think. > > I have a PCI soundcard + onboard soundcard. On startup, the system > will allocate randomly which card becomes /dev/dsp and which becomes > /dev/dsp1. > > This causes problems with Jack not starting because the device locked > into jack's config is no-longer the intended one. > > Also,in 1.3.7 I have seen my Edirol midi keyboard controller (ID'd as > "PCR") become the output device for jack ! (Jack did not start > unsuprisingly) > > Now I know what is happening, the random and mysterious "jack won't > start" messages make sense. > > Same problem occurs with /dev/*midi* allocations. This causes > problems where the /dev/*midi* device is hard-coded in the config , > such as with a synth called beatrix. > > I've read this is UDEV behaviour by design and can be overcome by > hard-mapping device hardware ID's to specific /dev/ nodes. > > Can anyone confirm that udev is the cause and the solution? > > May be worth writing this up in the FAQ? I'll document the udev > changes I have to make. >
I'll second the FAQ entry. You will not believe on how many forums I used to ask this question. Unfortunately it is considered to be an "Annoying Noob Question" and I never got any replies. In the end it was as simple as adding the following lines to the end of my /*/etc/modprobe.d/alsa-base*/ file alias snd-card-0 snd-emu10k1 options snd-emul10k1 index=0 alias snd-card-1 snd-rme9652 options snd-rme9652 index=1 alias snd-card-2 snd-usb-audio options snd-usb-audio index=2 This fixes my Audigy to card0 for normal playback, puts my Hammerfall in 1 (for jack) and the optional USB midi connector at card2. Obviously you have to add your cards details in the above... Now it works every time, without having to reconfigure the device in qjackctrl EVERY TIME... Cheers, Quentin _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
