#743: Sound disappears when some app tries to access alsa
---------------------+------------------------------------------------------
Reporter: walmis | Owner: lennart
Type: defect | Status: new
Milestone: | Component: daemon
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment(by coling):
I presume the apps that trigger this disappearance are trying to access
the alsa h/w directly? Can you get a very basic test case using only
aplay? e.g. aplay -D hw:0,0? If pulse borks with this test case then this
is likely a problem at the alsa level (trying to open the device a second
time should really fail (for 90% of audio h/w) or be allowed due to
hardware mixing. I'm guessing that either a) Alsa is giving us some kind
of signal we don't handle properly (no idea if this is the what is
happening as I don't knwo this code in PA too well, but I suspect it's not
the case.) or b) Alsa level playback is somehow borked when opening things
twice.
Another interesting test woudl be to run:
1) Terminal 1: pasuspender cat
2) Terminal 2: aplay -D hw:0,0
3) Terminal 3: aplay -D hw:0,0 (again!)
If 3) causes the playback in 2) to get messed up then you know this is
definitely an alsa bug... (although if it works fine, it doesn't mean to
say it's not an alsa bug!).
Please note that there is a pulseaudio output module for wine which may
work around the problem...
Lennart, any ideas?
--
Ticket URL: <http://pulseaudio.org/ticket/743#comment:2>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
_______________________________________________
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
