I get rid off pulseaudio. Xine, auadacious,xmms, ogg123 and others players are satisfied with alsa only, but mplayer does not even try to read command line options (terrible), it simply complains about missing libpulseaudio and exits. Do I have to recompile it or simply use VLC instead ?

Hello,

You can disable pulseaudio via the configure option --disable-pulse.

--
SeB

Uhm, yes?

Recompiling it is the more foolproof option (you know it's just a matter of downloading its directory from source/xap/MPlayer and running the SlackBuild there, right?). If you test VLC and find out that it also works, then you can you that instead.

Don't know what else you wanted to hear.

If you already uninstalled pulseaudio, the applications that linked to it will no longer run. Since you already uninstalled pulseaudio, just download the slackbuilds from the source directory of Slackware and just recompile the applications, since they cannot link to pulseaudio during compilation now. If you want to be a bit more future proof, add switches like --disable-pulse to the configure command. It was easy removing pulseaudio on my end, and there aren't too many apps that needed a recompile.

Why not? I think everyone enjoys compiling things (only if it compiles and does it for not so long).

Patrick made a statement not long ago that pulseaudio should be left installed.
It is possible to disable it through config changes.
http://www.linuxquestions.org/questi...6/#post5498703

For myself, all I did to get back on ALSA was the following:
1. remove /etc/asound.conf
2.adding following two lines to /etc/pulse/client.conf:
autospawn = no
daemon-binary = /bin/true

As for igadoter, have you simply tried making sure mplayer is using ALSA by
checking in /etc/mplayer/mplayer.conf for:
?

2 members found this post helpful.

Pulseaudio does not need to be installed if you recompile the affected applications.

Yes, but did you actually try that in practice? It seems that pulseaudio aware applications (some have runtime detection), can trigger the daemon to start. The only real option seems to be running a cron job to kill it every few minutes. Not only that, but pulseaudio manipulated my volume controls* without my asking. It had to be purged to stop this insanity.

*Yes, someone might mention there is an option for that too, but still, it did manipulate my volume levels in strange ways based on system events. I don't consider this user friendly program to take control of the mixer programmatically, since the programmer thinks he knows what you want, then have hunt for some chance for a gazillion new unfriendly switches to turn off these things, when I never needed them in the first place. It never was this arcane to use sound before.

2 members found this post helpful.

This is true, but that can be a lot of work, and depending on the person's skill level, may seem quite difficult.

pulseaudio just works™ for me. I've never had any issues from it. In the past, I've had issues with alsa that required some work to fix (wrong device as default, mixing up my channels (center channel was coming out the rear left speaker), audio card not supporting alsa's mute toggling -- so I had to instead make the volume zero in my script). I was able to fix them, but, so far, I've been problem free with pulseaudio (knock on wood). Sorry you've had trouble with it.

1 members found this post helpful.

He's not the only one. I've had nothing but trouble with audio since this PoS made its way into Slackware. Trouble with audio in Firefox, trouble with audio not obeying the KDE volume control.

My experience has been the same as bassmadrigal's, i.e., pulseaudio just works. Prior to it being added to Slackware I had to run a config file in /etc/modprobe.d/ to tell ALSA which audio card was to be use as the default. I also had low volume problems. With pulseaudio the config file is not needed and low volume is no longer an issue.

My post was not to discuss whether or not pulseaudio works for me. My point was that if you are removing pulseaudio, as what was asked, then editing /etc/pulse/client.conf and /etc/asound.conf does not fully disable it. Only removepkg and recompiling the packages you wish to keep is the only real solution to disable pulseaudio. This other discussion just muddies the topic (works for me / doesn't work for me). I don't care about whether alsa works for you.

But that was half your post.

Either way, the question has already been answered. mplayer will need to be recompiled to remove the pulseaudio dependencies. Any discussion beyond that (including what I posted) is off-topic.

1 members found this post helpful.

Again, you misunderstood my second half of the post. I mentioned something I thought would be questioned (use another pulseaudio config setting to resolve volume issues), so I explained it further. But this wasn't an issue with running a system with pulseaudio on. The second half was a continuation of the first part explaining further that even when "disabled" pulseaudio still caused unwanted effects. The goal is to eliminate the effects entirely. I have not seen an actual solution without removing and recompiling.

It is generally known why people remove pulseaudio, going into detail is unneeded and did nothing to further the discussion.

What would be nice is for the people who are having trouble with pulseaudio to create some posts for some diagnosing, so maybe those problems can get resolved rather than burying heads in the sand (by removing a major component that requires programs to be recompiled to work properly).

But, I digress, and I take leave of this topic to prevent me misunderstanding other posts and further veer this topic away from the subject.

1 members found this post helpful.

I have more pressing issues to resolve. As far as I'm concerned it's the developer of pulseaudio who should be spending valuable time debugging the PoS he imposed on us, not I.