Difference between revisions of "Talk:PulseAudio"

From ArchWiki
Jump to: navigation, search
m (Forgot to sign my edit.)
m (Proposed Corrections: Grammatical correction.)
Line 54: Line 54:
 
"PulseAudio now supports systemd's socket activation. There's support only for unix sockets, though; support for TCP sockets will come later. PulseAudio ships with a ready-made socket file for starting the user instance, but it's not generally advisable to enable it, because doing so will likely prevent PulseAudio from accessing the D-Bus session bus, crippling some features that depend on the session bus. It's expected that in the future, systems that use systemd will replace the session bus with a user bus, at which point the socket activation support in PulseAudio will become usable more widely."
 
"PulseAudio now supports systemd's socket activation. There's support only for unix sockets, though; support for TCP sockets will come later. PulseAudio ships with a ready-made socket file for starting the user instance, but it's not generally advisable to enable it, because doing so will likely prevent PulseAudio from accessing the D-Bus session bus, crippling some features that depend on the session bus. It's expected that in the future, systems that use systemd will replace the session bus with a user bus, at which point the socket activation support in PulseAudio will become usable more widely."
  
Furthermore, autospawn=yes it the default in /etc/pulse/client.conf.
+
Furthermore, autospawn=yes is the default in /etc/pulse/client.conf.
  
 
Finally, taking the default /etc/pulse/client.conf autospawn=yes into consideration, Pulseaudio's autospawn works out-of-the-box. I would like to propose the following replacement.
 
Finally, taking the default /etc/pulse/client.conf autospawn=yes into consideration, Pulseaudio's autospawn works out-of-the-box. I would like to propose the following replacement.

Revision as of 00:46, 7 September 2015

Configuration of the PulseAudio ALSA plugin

Can anybody give an example where to use the pcm.pulse setting? --BertiBoeller 12:33, 17 October 2009 (EDT)

Abandoned draft

PulseAudio/Configuration was initially created to discuss PA configuration; then its goal was changed to be a replacement for this whole article; then it was abandoned. Currently it's marked for merge in PulseAudio#Configuration: is there anything worth being merged from there? -- Kynikos (talk) 04:44, 30 November 2014 (UTC)

It seems to focus more on generic explanation/configuration, where the main article is mostly about troubleshooting (considering the size of that section, you'd consider moving it to PulseAudio/Troubleshooting ...) -- Alad (talk) 10:40, 30 November 2014 (UTC)
How much sense would it make to actually merge PulseAudio/Configuration#Easy_configuration and PulseAudio/Configuration#Advanced_configuration and then simply redirect PulseAudio/Configuration to PulseAudio#Configuration?
I'd agree with moving Troubleshooting to PulseAudio/Troubleshooting.
-- Kynikos (talk) 12:01, 2 December 2014 (UTC)
I do agree it makes sense to merge PulseAudio/Configuration#Easy_configuration and PulseAudio/Configuration#Advanced_configuration in PulseAudio/Configuration. I made an attempt in this way. Gabx (talk) 18:24, 28 December 2014 (UTC)
I like what I see so far, more extensive configuration in the main article also allows to cut back on PulseAudio/Troubleshooting. -- Alad (talk) 23:29, 28 December 2014 (UTC)

Restore package list

Why revert the list? I think Arch News is just a temp reminder. Arch Wiki should keep all needed info.--Fengchao (talk) 09:37, 1 August 2015 (UTC)

I'm not sure what the right policy is for this (hence my query in my edit summary) but I would just point out that the archive does stretch back to 2002 so I don't think it's unsafe to link to that material. -- Chazza (talk) 16:34, 1 August 2015 (UTC)
That's true, but the set of split packages can change in the future... -- Lahwaacz (talk) 18:37, 1 August 2015 (UTC)
Exactly, so at that time, the news page is out of date and only wiki page could be updated to keep up.--Fengchao (talk) 12:57, 19 August 2015 (UTC)
We should ask for a more extensive optdepends instead of maintaining this information here. -- Alad (talk) 19:03, 1 August 2015 (UTC)
Alternatively creating a pulseaudio-modules group should be equally simple for the packager, more comprehensible to the user and most naturally referenceable from the wiki. -- Lahwaacz (talk) 19:14, 1 August 2015 (UTC)
Then before a group is created, should we restore the package list?--Fengchao (talk) 12:57, 19 August 2015 (UTC)

DBus module

I get this error with pulseaudio-6.0-2 when module-dbus-protocol is to be loaded:

W: [pulseaudio] module-dbus-protocol.c: module-dbus-protocol is currently unsupported, and can sometimes cause PulseAudio crashes.
W: [pulseaudio] module-dbus-protocol.c: The most popular use cases for module-dbus-protocol are related to changing equalizer settings and LADSPA plugin parameters at runtime.
W: [pulseaudio] module-dbus-protocol.c: If you don't use such functionality, it's possible that you don't actually need this module.
W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.BadAddress: In D-Bus address, percent character was followed by characters other than hex digits
W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.BadAddress: In D-Bus address, percent character was followed by characters other than hex digits

This is needed for PulseAudio#Equalizer.

-- Lahwaacz (talk) 18:58, 23 August 2015 (UTC)

Proposed Corrections

Currently, the Running section has the following.

"Since version 6.0, PulseAudio relies on autospawn/socket activation. To use socket activation, enable pulseaudio.socket for the systemd/User instance. Alternatively, set autospawn=yes in either /etc/pulse/client.conf or ~/.pulse/client.conf in order to use autospawn activation."

The linked upstream documentation directly advises against enabling pulseaudio.socket.

"PulseAudio now supports systemd's socket activation. There's support only for unix sockets, though; support for TCP sockets will come later. PulseAudio ships with a ready-made socket file for starting the user instance, but it's not generally advisable to enable it, because doing so will likely prevent PulseAudio from accessing the D-Bus session bus, crippling some features that depend on the session bus. It's expected that in the future, systems that use systemd will replace the session bus with a user bus, at which point the socket activation support in PulseAudio will become usable more widely."

Furthermore, autospawn=yes is the default in /etc/pulse/client.conf.

Finally, taking the default /etc/pulse/client.conf autospawn=yes into consideration, Pulseaudio's autospawn works out-of-the-box. I would like to propose the following replacement.

"Pulseaudio relies on autospawn for socket activation. This is enabled by default in /etc/pulse/client.conf."

This would effectively be a removal of https://wiki.archlinux.org/index.php?title=PulseAudio&diff=next&oldid=362083.

Pid1 (talk) 00:42, 7 September 2015 (UTC)