[SOLVED] disabling PulseAudio

Alien Bob · 01-13-2016, 07:54 AM

And this page is informative as well: http://proaudio.tuxfamily.org/wiki/?title=PulseAudio

cgorac · 01-13-2016, 11:52 AM

@ReaperX7: I still don't get point of your posts - adding nothing of substance to the topic, but just keep trying to patronize instead.

Spinlock · 01-13-2016, 11:58 AM

Quote:

Originally Posted by cgorac

@ReaperX7: I still don't get point of your posts - adding nothing of substance to the topic, but just keep trying to patronize instead.

You've pretty much summed it up. ReaperX7 likes exactly two things in this world: To hear himself talk, and to troll people into engaging with him. I'd recommend just ignoring him.

dugan · 01-13-2016, 12:16 PM

cgorac: I'm going to point out another obvious fact. The forum supports ignore lists. If you put a user in your ignore list, then that user's posts will be hidden until you choose to click on them. It's exactly like code-folding in a text editor, if you've ever used that.

Soderlund · 01-13-2016, 12:53 PM

Can't you just not install L/pulseaudio? It will use ALSA then, right?

dugan · 01-13-2016, 12:55 PM

Quote:

Originally Posted by Soderlund

Can't you just not install L/pulseaudio? It will use ALSA then, right?

No. There's now a configuration file in the alsa-lib package that redirects ALSA's audio input to Pulseaudio. That file is the asound.conf file that I mentioned.

orbea · 01-13-2016, 01:01 PM

Its a bit more involved than that, alsa-lib brings in /etc/asound.conf which needs to be removed, additionally aolib, sox, mpg123 and some other stuff is built against pulse now.
And if you want to be complete you also not install the various new packages related to pulseaudio and remove the pulse user and group brought in by the updated etc package.

dugan · 01-13-2016, 01:03 PM

Yeah, I don't see it being realistic to not have Pulseaudio installed in Slackware 14.2.

Not having it running should still work fine.

orbea · 01-13-2016, 01:09 PM

My system is working perfectly without pulse, it wasn't as much effort as I imagined it would be too. It is a bit annoying to have to blacklist alsa-lib and etc so I can manually update them instead though.

GazL · 01-13-2016, 01:21 PM

Guys, where do I set default volume slider values for my card in pulse? it keeps changing the ones I'd set using alsamixer/alsactl store?

volkerdi · 01-13-2016, 01:22 PM

Quote:

Originally Posted by orbea

My system is working perfectly without pulse, it wasn't as much effort as I imagined it would be too. It is a bit annoying to have to blacklist alsa-lib and etc so I can manually update them instead though.

The pulse user/group in the etc package aren't going to do anything, so there should be no reason to blacklist them. As for alsa-lib, if you create an empty asound.conf then alsa-lib updates will not mess with your existing config file.

While pulseaudio is working fine here, disabling it on Slackware (and having it not try to turn back on) should be reasonably easy.

cathartes · 01-13-2016, 01:31 PM

Quote:

Originally Posted by Alien Bob

In my blog article about -current and pulseaudio I pointed to this Arch Wiki article which shows how you can keep ALSA as the boss and allow pulse-enabled apps to fire up a pulseaudio server "on-demand" to pipe sound into ALSA:
https://wiki.archlinux.org/index.php...b_pipe_to_ALSA

What was the rationale for not making the "dumb pipe" approach the Slackware default?

elcore · 01-13-2016, 02:19 PM

Quote:

Originally Posted by Soderlund

Can't you just not install L/pulseaudio? It will use ALSA then, right?

KDE won't start without, and is now linked to pulse.

volkerdi · 01-13-2016, 03:00 PM

Quote:

Originally Posted by cathartes

What was the rationale for not making the "dumb pipe" approach the Slackware default?

http://www.freedesktop.org/wiki/Soft...ithSystemWide/

Upstream says even having the rc.pulseaudio script that gives you a choice is "stupid" (but taking away choice is usually more stupid).

qunying · 01-13-2016, 03:38 PM

Quote:

Originally Posted by cgorac

my scripts for ACPI toggle-mute/volume-up/volume-down events (based on simple commands like "amixer set Master toggle" for muting/unmuting, and alike) aren't working any more

Actually I was at the same boat with you, but PV won't left us without control. Add the new package pamixer:

Code:

pamixer 
Allowed options:
  -h [ --help ]         help message
  --sink arg            choose a different sink than the default
  --source arg          choose a different source than the default
  --default-source      select the default source
  --get-volume          get the current volume
  --set-volume arg      set the volume
  -i [ --increase ] arg increase the volume
  -d [ --decrease ] arg decrease the volume
  -t [ --toggle-mute ]  switch between mute and unmute
  -m [ --mute ]         set mute
  --allow-boost         allow volume to go above 100%
  --gamma arg (=1)      increase/decrease using gamma correction e.g. 2.2
  -u [ --unmute ]       unset mute
  --get-mute            display true if the volume is mute, false otherwise
  --list-sinks          list the sinks
  --list-sources        list the sources

Use pamixer -i/d/t to do increase decrease and toggle command.