I've updated the description with more details about the issues this causes so we can evaluate better a solution.
Steve, any official news? ** Description changed: Steps to reproduce: Run both of these at the same time: gst-launch-0.10 audiotestsrc ! pulsesink gst-launch-0.10 audiotestsrc ! alsasink If your default sound device does not support hardware mixing, the second command will fail. ALSA cannot use the device while PulseAudio is using it, and this affects a lot of applications. Note that if you run the commands the other way around, alsalib will use dmix, and then so will pulseaudio, so there is not as much of a problem this way around (except for the fact that dmix and PA are doing the same job, and you can not control the ALSA-using apps' volumes and routing with PA.) Resolution: Follow http://pulseaudio.org/wiki/PerfectSetup#ALSAApplications i.e. install /etc/asound.conf with: pcm.pulse { type pulse } ctl.pulse { type pulse } pcm.!default { type pulse } ctl.!default { type pulse } - Note, too, that there are some applications that fail with ALSA->Pulse, - in particular, SDL seems to hang with Neverball. These bugs can be - addressed seperately in due course. + Note, too, that there are some applications that fail with ALSA->Pulse: + + SDL seems to hang with neverball, but that is fixed by installing the PulseAudio backend for SDL (libsdl1.2debian-pulseaudio), which will replace the default ALSA backend. + WINE has its own issues with regards to device selection, which I don't know a remedy for. + Skype also has its own problems, but these aren't fixable by us and should not block us, though should be given some consideraton. -- Default ALSA device must use PulseAudio, otherwise ALSA applications may fail https://bugs.launchpad.net/bugs/198453 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
