alsa and pulseaudio problem
 

hi all,

I have a problem here that I have not encountered before in a Slackware install WITHOUT Dropline GNOME installed (and I have it installed now) and it installed pulseaudio so I am going to assume that this is the culprit.

my problem:
no audio in games. (specifically darkplaces quake, yamagi-quake2 and ioquake3. I own these games so I kinda figure that I want them installed and functioning properly on my system so any help here would be appreciated. everything was working with alsa and gstreamer before I installed dropline and it's pulseaudio package. I have since un-installed the dropline pulseaudio package and replaced it with the updated version from slackbuilds hoping that recompiling pulseaudio would solve the problem but it did not. also, I cannot run alsamixer in the terminal so something is up and it's probably an easy fix. here's the output of that command:

I'm not an idiot, but I need a little help. thanks.

The shared library you are apparently missing is part of alsa-plugins

You (or something) have alsa configured to use pulseaudio for audio output. Since it can't load the plugin, it can't do anything with the sound it gets and hence your games (and other apps using alsa directly) are silent.

excellent !!!
 

thanks bro...

I fired up pkgtool and checked the versions of some packages dropline GNOME overwrote. so far I have removed some packages and:

with the PULSEAUDIO=yes option
and now I have sound in my games and a master out for alsamixer. THANK-YOU

not only do I have sound in my games but I have sound in chromium when I am browsing http://youtube.com ... a problem I had posted on LQ previously but nobody was able to solve. so kudos to you, my friend... you aced this one.

scarrz, so you installed ffmpeg and alsa-plugins from sbo.org ?
what else did you change ?

This will help in updating dropline gnome to address this issue.

FWIW, ffmpeg should have no impact here. ffmpeg's pulseaudio support entails that it can transcode audio from pulseaudio input to another format, so potentially for use cases like screen recording, or recording skype conversations. But for being able to hear audio in games, it would hardly be relevant.

So the only reason for ffmpeg here would be alsa-plugin's optional dependency on it, but I'm not sure what that would do. I doubt it would be relevant either.

yep...
 

after installing those packages everything was fine. I JUST installed slackware-current and am going thru the motions of getting this set up again. alsa-plugins didn't build with the dropline version of ffmpeg and that's why I installed it. As far as my other changes... I had to find a slackbuild for audacious-plugins and install libcue to get my favorite audio player working with .cue support... (not dropline related) and I removed totem and replaced it with the sbo version because the interface is a little easier to use and it adds gst-plugins-bad and ugly to the build for dvd support and whatnot; and since vlc is no longer available on sbo totem is my replacement. I do not want to use AlienBob's vlc package as I prefer to use software form sbo first and foremost before anything and totem seems to run a bit better anyways.

So far my dropline GNOME pet is proving to be quite a challenge but I am not giving up! It works... it's just really slow and font rendering is buggy with the nVIDIA proprietary driver.

pulseaudio on slackware-current
 

hello again...

recently migrated to slackware64-current and am getting dropline GNOME set up again and am doing ALOT of tweaking. seems pulseaudio will not run as a normal user but runs fine as root. (ie: I can hear sound in games and YouTube and pulseaudio plugins in my favorite multimedia apps like audacious and totem) I have uninstalled the pulseaudio package from the gnome install as well as alsa-plugins and ffmpeg and all the gst1 plugins and replaced them with the SBo versions.this is what happens when I:
so I:
and:
and I get:
and I am scratching my head because this exact same setup worked in Slackware64 14.1 as a normal user.

I seem to remember jack audio needing special permissions to start it's own server... and at install pulseaudio was suppose to do that but I am wondering if it didn't. doing homework, any help would be much appreciated.

etc/pulse/default.pa
the output your reading is just that. If pavucontrol stops working. Then you need to restart the xorg or reboot.
this can be handled with outher edits to your default.pa. But we want alsa to control pulse in slackware.
And if using KDE we want the default devices chosen in kmix multimedida settings. To be used.

really does not do that ok. pulseaudio -k
but if your /etc/pulse/client.conf is
It will just restart.

re-solved...
 

heads up...
I must have had left my old settings in my home dir. removing ~/.config/pulse and logging out/in solved my problem. thanks again for your help.