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