| Summary: | Audio device selection in ALSA | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Matt Windsor <matt.windsor> |
| Component: | audio | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED ABANDONED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | enhancement | ||
| Priority: | P2 | CC: | dominik.frizel |
| Version: | 2.0.3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Attachments: | Allow device Selection Alsa | ||
|
Description
Matt Windsor
2015-02-09 21:00:47 UTC
Created attachment 2039 [details]
Allow device Selection Alsa
This patch allows the device selection for the ALSA system.
I did some basic tests (Mint Linux 17.1 - amd64), using alsa over the pulse plugin
A lot of devices show up
(In reply to Dominik Frizel from comment #1) > A lot of devices show up No kidding! PulseAudio shows me three devices (the on-board audio chip, the HDMI port in my Nvidia GPU, and a USB headset I have plugged in). ALSA shows me _fifty four_ devices for the same configuration (that's counting input and output, but still, that's a lot). I'm pretty sure Pulse uses ALSA to talk to actual hardware; does anyone know how it cuts down this list so ruthlessly (and correctly)?! --ryan. Well I know where to get the information cat /proc/asound/cards - but how to map that on the cards delivered by the alsa api call, I am not sure (yet). Also this is very Linux specific. (In reply to Dominik Frizel from comment #3) > Well I know where to get the information > cat /proc/asound/cards - but how to map that on the cards delivered by the > alsa api call, I am not sure (yet). Also this is very Linux specific. It looks like it uses udev, which is also pretty Linux specific. (but oh well, so is ALSA, in practice.) http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/module-udev-detect.c?id=85f5d93306888bd3ee09497056bfa1b1e32bd51f Still, that's some pretty complicated code. I'm inclined to just list everything here and be done with it. --ryan. (sorry if you get a lot of copies of this email, I'm marking several bugs at once) Marking bugs for the (mostly) final 2.0.4 TODO list. This means we're hoping to resolve this bug before 2.0.4 ships if possible. In a perfect world, the open bug count with the target-2.0.4 keyword is zero when we ship. (Note that closing a bug report as WONTFIX, INVALID or WORKSFORME might still happen.) --ryan. Hello, and sorry if you're getting dozens of copies of this message by email. We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc. Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report. So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues. (please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!) Thanks, --ryan. |