1 |
On Sat, Nov 28, 2009 at 2:07 PM, Florian Philipp |
2 |
<lists@f_philipp.fastmail.net> wrote: |
3 |
> Alan McKinnon schrieb: |
4 |
>> On Saturday 28 November 2009 13:58:42 Florian Philipp wrote: |
5 |
>>> Hi list! |
6 |
>>> |
7 |
>>> I recently updated one of my systems to KDE4. Now I have the problem |
8 |
>>> that only one application can access the audio output at a time. If I |
9 |
>>> start a second app (for example playing a video with Kaffeine while |
10 |
>>> Amarok runs but is idle) the second application reports that the device |
11 |
>>> "does not work". |
12 |
>>> |
13 |
>>> Is this normal behavior? How can I fix it? |
14 |
>>> |
15 |
>>> Maybe it's an issue with ALSA but before I investigate this option, I'd |
16 |
>>> like to hear a "works for me" from other users. |
17 |
>> |
18 |
>> Works for me. Also works for most other folks, as no-one else is complaining. |
19 |
>> |
20 |
>> What are your relevant configs? |
21 |
>> |
22 |
>> Are you in any way using (god forbid...) arts? esd? pulseaudio? Any sound |
23 |
>> daemon other than ALSA? |
24 |
>> |
25 |
>> |
26 |
> |
27 |
> Nah, I think ALSA is just misconfigured and doesn't enable HW/SW mixing. |
28 |
> I'll look into it and come back if I don't find it on my own. |
29 |
> |
30 |
> Thanks so far! |
31 |
> |
32 |
> |
33 |
|
34 |
When I was first messing around with Linux, I think I was using |
35 |
Mandrake (back when it was called Mandrake) and this issue crept up on |
36 |
me. Back then, if I understand correctly, it was accepted behaviour |
37 |
for hardware to be accessible by one program at a time. There was a |
38 |
fix back then that involved running some sort of daemon, but its been |
39 |
a while since I messed with KDE or Mandrake. |