Due Gnome requiring pulseaudio in the near future, I have switched to pulseaudio and, as I expected :S, it still has some problems. Looks like flashplayer is not yet fully compatible with pulseaudio and, while I am playing a flash video, it uses the sound and prevents any other gstreamer app (I guess mplayer is still working because it's not using pulse by default, but I am not sure) from working, they simply get stalled while I get messages like this in /var/log/messages: Nov 29 01:18:30 belkin4 pulseaudio[25370]: alsa-sink.c: Error opening PCM device front:0: Dispositivo o recurso ocupado I have googled a bit and looks like there are different solutions like using libflashsupport (but it looks to be indicated for older flash versions) or tweaking /etc/asound.conf As I don't know if http://pulseaudio.org/wiki/PerfectSetup information is updated enough, I prefer to ask here to flash and pulse maintainers for the proper solution, and also try to get things working by default instead of needing to manually need to tweak a lot of files for getting things working and preventing regressions over non-pulseaudio systems Thanks for your help Reproducible: Always
libflashsupport is definitely not a proper solution - it was something needed for flash 9, IIRC. I may not be 100% up to date with the info, but - at very least - you'll need alsa-plugins[pulseaudio]. I don't know about gstreamer, but i.e. audacious an firefox aren't in conflict here. An entry making pulse default device/control might still be needed in /etc/asound.conf. Exact version of both alsa-plugins *and* pulseaudio matters too - there were significant changes (sometimes even improvements) made for pulseaudio 1.0, that haven't left alsa-plugins repo yet (well, as far as the main tree goes, that is, I've been on the patched version for quite awhile).
You just need to follow this -- http://pulseaudio.org/wiki/PerfectSetup#ALSAApplications This does need alsa-plugins[pulseaudio]. Things work just fine for me with the packages in tree. I'm open to suggestions on how to make this easier for users. Should we have some sort of eselect alsa module?
(In reply to comment #2) > You just need to follow this -- > http://pulseaudio.org/wiki/PerfectSetup#ALSAApplications > > This does need alsa-plugins[pulseaudio]. Things work just fine for me with the > packages in tree. I'm open to suggestions on how to make this easier for users. > Should we have some sort of eselect alsa module? Thanks, will try it From my point of view: 1. adobe-flash with a new USE "pulseaudio" should RDEPEND on alsa-plugins[pulseaudio] to get them installed by default on that setups 2. We need to find a way to get that /etc/asound.conf autogenerated, maybe the eselect module could do that (the problem is that I don't know how eselect modules work :( )
(In reply to comment #3) > From my point of view: > 1. adobe-flash with a new USE "pulseaudio" should RDEPEND on > alsa-plugins[pulseaudio] to get them installed by default on that setups Maybe it should be the other way around, since alsa-plugins[pulseaudio] is not flash specific, but pulse specific. pulseaudio already has an IUSE="alsa" that lets it use alsa as a backend. Perhaps it should also make pulseaudio RDEPEND on alsa-plugins[pulseaudio]? > 2. We need to find a way to get that /etc/asound.conf autogenerated, maybe the > eselect module could do that (the problem is that I don't know how eselect > modules work :( ) A simple matter of programming ;) A quick google found this, which looks promising: http://www.gentoo.org/proj/en/eselect/dev-guide.xml
(In reply to comment #4) > (In reply to comment #3) > > From my point of view: > > 1. adobe-flash with a new USE "pulseaudio" should RDEPEND on > > alsa-plugins[pulseaudio] to get them installed by default on that setups > > Maybe it should be the other way around, since alsa-plugins[pulseaudio] is not > flash specific, but pulse specific. pulseaudio already has an IUSE="alsa" that > lets it use alsa as a backend. Perhaps it should also make pulseaudio RDEPEND > on alsa-plugins[pulseaudio]? > The problem is that, until seen flash having problems with pulse, I never installed alsa-plugins and, then, I think a lot of people won't have it installed on their systems even if adobe-flash needs it to work fine > > 2. We need to find a way to get that /etc/asound.conf autogenerated, maybe the > > eselect module could do that (the problem is that I don't know how eselect > > modules work :( ) > > A simple matter of programming ;) A quick google found this, which looks > promising: > http://www.gentoo.org/proj/en/eselect/dev-guide.xml Thanks for the link :)
I have seen Arch is simply providing a "pulseaudio-alsa" package to install needed /etc/asound.conf: https://wiki.archlinux.org/index.php/PulseAudio#ALSA http://projects.archlinux.org/svntogit/packages.git/tree/trunk/asound.conf?h=packages/pulseaudio-alsa Looks easier than eselect module, anyway, in case of needing to prepare an eselect module, what other config files should be handled for asound.conf apart of pulseaudio one?
my 2cents: The flash ebuild should have IUSE="pulseaudio" and then RDEPEND="pulseaudio? ( media-plugins/alsa-plugins[pulseaudio] )".
(In reply to comment #7) > my 2cents: The flash ebuild should have IUSE="pulseaudio" and then > RDEPEND="pulseaudio? ( media-plugins/alsa-plugins[pulseaudio] )". Yes, but we also need to let people to easily have proper /etc/asound.conf, otherwise it will still fail to work properly ;)
(In reply to comment #6) > I have seen Arch is simply providing a "pulseaudio-alsa" package to install > needed /etc/asound.conf: > https://wiki.archlinux.org/index.php/PulseAudio#ALSA > http://projects.archlinux.org/svntogit/packages.git/tree/trunk/asound.conf?h=packages/pulseaudio-alsa > > Looks easier than eselect module, anyway, in case of needing to prepare an > eselect module, what other config files should be handled for asound.conf apart > of pulseaudio one? What about this easier solution? :)
Other option: - Make alsa-plugins install that proper asound.conf file insider /usr and tell people to copy it to /etc if they want to route all alsa though pulseaudio
Updates: * alsa-plugins[pulseaudio] now sets up configuration to autoprobe for the presence of a PA daemon and route audio through it if this is the case * In the next PA release, I will make alsa-plugins[pulseaudio] an RDEPEND on pulseaudio[alsa], so effectively emerge'ing PA will effectively set things up to Just Work™.
In that case I guess that dep wouldn't be needed in adobe-flash ebuild then
(In reply to comment #12) > In that case I guess that dep wouldn't be needed in adobe-flash ebuild then Correct. The next PA bump should see all this fixed and working magically.
Reassigning this to myself since it's PA-related.
Tha AMD64 stable version media-sound/pulseaudio-1.1-r1 don't work out of the box, it just needs a emerge of media-plugins/alsa-plugins-1.0.25-r1. And as the stable version are a bit old i emerged the unstable media-sound/pulseaudio-2.1. As i don't use any voip to test webrtc-aec i emerged it without that use flag, it's also unstable (i suppose thats one reason that pulse-ausio is unstable. I don't have any problem with sound in flash now, so to stabilize pulseaudio-2.1 would solve this for stbale systems, I think
This is solved now with latest stable pulseaudio