[linux-audio-user] Is it possible to force a USB MIDI device to use a fixed ALSA client ID?
9 Sep
2005
9 Sep
'05
2:22 p.m.
I've been playing around with session saving and restoring using LASH
0.5.0pre0 - it works pretty well for restoring and connecting programs
that support LASH (such as a patched Zyn 2.2.1, Om from current CVS,
Dino 0.1.52 etc), but it doesn't work quite as well for connecting the
ALSA MIDI input ports to the output port of my USB keyboard, since the
keyboard can get a different ALSA client ID every time I turn it on.
If I could somehow tell ALSA that my USB keyboard should _always_ use
client ID 80 (for example) and never let any other client use that ID
the problem would be solved, since LASH would then find the keyboard at
the same client ID as last time and connect everything as it was. Is
there any way to do this?
--
Lars Luthman
PGP key: http://www.d.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
9 Sep
9 Sep
2:39 p.m.
New subject: [linux-audio-user] Is it possible to force a USB MIDI device to use a fixed ALSA client ID?
If I could somehow tell ALSA that my USB keyboard
should _always_ use
client ID 80 (for example) and never let any other client use that ID
the problem would be solved, since LASH would then find the keyboard
at the same client ID as last time and connect everything as it was.
Is there any way to do this?
I don't know any, but another solution could be that ALSA remembers a
device and reserves the ID for it. Worth a feature request?
Best regards
ce
2:47 p.m.
New subject: [linux-audio-user] Is it possible to force a USB MIDI device to use a fixed ALSA client ID?
Lars Luthman wrote:
the keyboard can get a different ALSA client ID every
time I turn
it on.
The client ID depends on the sound card number. ALSA drivers grab the
first free sound card number when they're loaded unless told
otherwise, so the client ID will change if drivers are loaded in a
different order.
In your /etc/modprobe.conf (or whatever your distribution uses), add
"index" options to your drivers to force them to always have the same
ID:
options snd-whatever index=0
options snd-usb-audio index=1
If a driver handles more than one card, use multiple index values like
this:
options snd-usb-audio index=1,2,5
HTH
Clemens
4:01 p.m.
New subject: [linux-audio-user] Is it possible to force a USB MIDI device to use a fixed ALSA client ID?
On Fri, 2005-09-09 at 18:47 +0200, Clemens Ladisch wrote:
Lars Luthman wrote:
Thanks! I added "options snd-usb-audio index=1" and ran depmod, and now
it looks like the keyboard gets client ID 72 every time I turn it on.
--ll
the keyboard can get a different ALSA client ID
every time I turn
it on.
The client ID depends on the sound card number. ALSA drivers grab the
first free sound card number when they're loaded unless told
otherwise, so the client ID will change if drivers are loaded in a
different order.
In your /etc/modprobe.conf (or whatever your distribution uses), add
"index" options to your drivers to force them to always have the same
ID:
options snd-whatever index=0
options snd-usb-audio index=1
7018
days inactive
7018
days old
linux-audio-user@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Christoph Eckert -
Clemens Ladisch -
Lars Luthman