| 1 |
hmmm. I've managed to focus the problem: Some programs try to access |
| 2 |
to sound device called "hw:0,0" and there for do not allow it to be |
| 3 |
shared. MPD was one of them, and when I changed the setting in |
| 4 |
mpd.conf to using "default" it works. The flash player, though, still |
| 5 |
tries to access the hardware directly. I'm not sure how to reconfigure |
| 6 |
it. I'm using the adobe player. |
| 7 |
Can anyone think of away of making all programs use "default" sound |
| 8 |
output rather than "hw:0,0"? |
| 9 |
Should I report that as a bug to the mpd package maintainer, that the |
| 10 |
default setting try to access the sound device directly? |
| 11 |
|
| 12 |
On Sat, Dec 5, 2009 at 6:12 AM, Joshua Murphy <poisonbl@×××××.com> wrote: |
| 13 |
> On Fri, Dec 4, 2009 at 4:43 PM, walt <w41ter@×××××.com> wrote: |
| 14 |
>> On 12/03/2009 09:08 PM, Joshua Murphy wrote: |
| 15 |
>> ... |
| 16 |
>>> |
| 17 |
>>> Lately, I've had zero issues with alsa pretty much configuring itself |
| 18 |
>>> properly, given I'm using the in kernel alsa drivers for my systems... |
| 19 |
>>> and it hasn't required any manual configuration of dmix or similar to |
| 20 |
>>> function properly. Last time I used a separate sound daemon (aside |
| 21 |
>>> from a short stent with Ubuntu on my netbook that, I think, had me |
| 22 |
>>> using pulseaudio), I was running esound to manage audio from a |
| 23 |
>>> headless box over my network... and ESD was playing nicely with other |
| 24 |
>>> straight alsa apps on the same box... |
| 25 |
>> |
| 26 |
>> I discovered a few weeks ago that I could completely delete all traces |
| 27 |
>> of arts, pulse, *and* esd, and still I can listen to a podcast from |
| 28 |
>> npr.org with firefox and play an mp3 using audacious at the same time. |
| 29 |
>> (Which drives me totally nuts, BTW, and I did it only as a test.) |
| 30 |
>> |
| 31 |
>> As you say, alsa seems to DTRT by itself these days. The only thing |
| 32 |
>> I'm not sure about is whether the gnome-panel volume/mixer applet is |
| 33 |
>> now doing what esound used to do. |
| 34 |
>> |
| 35 |
>> If you still have esound installed you can try it yourself. Just |
| 36 |
>> remove the arts, esd, and pulse USE flags first, then remove any/all |
| 37 |
>> of those packages from the machine and revdep-rebuild. It's amazing |
| 38 |
>> how many packages are linked against esound and AFAICT they no longer |
| 39 |
>> need to be. (This applies to gnome, of course.) |
| 40 |
>> |
| 41 |
>> OTOH, I haven't tested every sound-related app on my machine, so I |
| 42 |
>> might be missing some important exceptions. |
| 43 |
> |
| 44 |
> All Gnome's volume/mixer applet does, AFAIK, is the same as alsamixer, |
| 45 |
> on a less cli/ncurses interface... just volume control for the |
| 46 |
> channels the card tells the driver to tell the alsa subsystem it has |
| 47 |
> ;) ... it doesn't have anything more, really, to do with the actual |
| 48 |
> 'mixing' than that, and it works just as well without it, as evidenced |
| 49 |
> by my netbook with ratpoison, no arts, esd, pulseaudio, etc... |
| 50 |
> listening to a radio stream on one aterm that's running mplayer |
| 51 |
> (outputting to bare alsa) and getting prompt and proper alerts from |
| 52 |
> Skype at the same time. |
| 53 |
> |
| 54 |
> 'Course, all the anecdotal evidence in the world won't make the |
| 55 |
> problem the OP is seeing. |
| 56 |
> |
| 57 |
> -- |
| 58 |
> Poison [BLX] |
| 59 |
> Joshua M. Murphy |
| 60 |
> |
| 61 |
> |
Archives