From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: WARNING: Latest Linphone on Arch breaks device access
Date: Wed, 07 Sep 2016 11:39:02 -0700 [thread overview]
Message-ID: <87twdrmu61.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160907173128.GC1838@opera.rednote.net> (Janina Sajka's message of "Wed, 7 Sep 2016 13:31:28 -0400")
Janina Sajka <janina@rednote.net> writes:
> It was a great suggestion, Chris. Unfortunately, it seems there's yet
> another bug in how alsa handles usb devices.
>
> I have 2 usb devices. No matter how I specify things, the card that gets
> invoked is the first of those two.
Oh interesting. So it looks like there's a name clash.
Last time I dealt with multiple USB audio devices, they had unique
human-friendly IDs by default. My Logitech USB headset was called
Headset, and my FM transmitter was called RocketFM.
Apparently I was just lucky.
Not sure how much you know about alsa, so I'll also mention that
you can see the human friendly IDs by looking for the symlinks in
/proc/asound. They're also listed in the output of aplay -l, but it's
sort of non-intuitive what they are.
> Now, if I were really clever, I suppose I'd know how to write udev rules
> to insure that the Sennheiser gets a lower card ID than the C-Media
> device.
Well if you send me the output of lsusb, I can probably write some udev rules
for you. Or alternatively have a look at http://alsa.opensrc.org/Udev for a
starting point.
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Chris Brannon
` Janina Sajka
` John Covici
` Janina Sajka
` Chris Brannon [this message]
` Janina Sajka
` Janina Sajka
` Janina Sajka
` Chris Brannon
` Janina Sajka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twdrmu61.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=speakup@linux-speakup.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).