|
Martin I suspect if you use 'dmesg' you can see all the USB ID numbers and that may answer your question. If you are using Pulse audio, I think you can have a simple script to set the default sound device. Probably Pipewire can do that also. Maybe I don't
understand what you are asking. See
From: Martin McCormick <martin.m@xxxxxxxxxxxxxx>
Sent: Tuesday, December 17, 2024 10:45 AM To: blinux-list@xxxxxxxxxx <blinux-list@xxxxxxxxxx> Subject: Re: My Sound-Cards Are out of Order Again I am not complaining, here, but I don't feel good about the
To unsubscribe from this group and stop receiving emails from it, send an email to blinux-list+unsubscribe@xxxxxxxxxx.following situation: I have 3 identical Behringer usb sound cards on a Raspberry Pi. Every identifying descriptor for each card is the same so udev rules may not work, here. There is an old usb 4-port hub that the 3 Behringers plug in to with the hub plugged in to the Pi. I discovered that if I plug the 3 sounds cards in to the first 3 slots on the hub, they always come up in the same order every time so far but I have done nothing with configuration files to force this situation. Am I just lucky that the order doesn't change or what? It always seemed to me that if one could control the activation sequence order of usb ports, a lot of weird trouble would just go away. The order problems are race conditions in which one device may register a few clock cycles before another so it is device0 right now and may be device1 or 2 later. If you could tell the system that Socket 1 should go live first, then 3, then 2 if that's what you hope for, then that would solve a lot of issues. Obviously, if one unplugs a device or the device disables itself for whatever reason, nothing guarantees it will get's old number back but that is a different sort of issue. If you leave your sound cards connected and they stay operational, they should keep their current indices indefinitely. Martin Geoff Shang <geoff@xxxxxxxxxxxxxxx> writes: > Hello, > > The card number is defined by the index parameter to the ALSA module. > > > So if you want to change it on the fly, you could remove the particular > ALSA module and reload it with the appropriate value for index. > > > For example: > > modprobe snd_ens1371 index=2 > > > To have them come up in the right order, you would edit whatever mechanism > loads them and add the appropriate index value. > > > > I'm running Debian Bookworm (version 12) and I can't figure out exactly > how > my sound driver is being loaded. To unsubscribe from this group and stop receiving emails from it, send an email to blinux-list+unsubscribe@xxxxxxxxxx. |