PipeWire - Revision history

Prabuanand: added wikilink

2026-04-15T10:47:04Z

added wikilink

← Older revision		Revision as of 10:47, 15 April 2026
Line 128:		Line 128:
	==== Without PAM ====		==== Without PAM ====

	If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. If this is the case, add your user to the {{Ic\|rtkit}} group. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.		If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. If this is the case, [[Setting_up_a_new_user#Group_management\|add your user]] to the {{Ic\|rtkit}} group. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.

	==== Using PAM ====		==== Using PAM ====

	Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included which applies to sessions started via PAM for members of the {{Ic\|pipewire}} group. If this is the case, add your user to the {{Ic\|pipewire}} group.		Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included which applies to sessions started via PAM for members of the {{Ic\|pipewire}} group. If this is the case, [[Setting_up_a_new_user#Group_management\|add your user]] to the {{Ic\|pipewire}} group.

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.

Prabuanand: added the instruction to add users to the group

2026-04-15T02:47:32Z

added the instruction to add users to the group

← Older revision		Revision as of 02:47, 15 April 2026
Line 132:		Line 132:
	==== Using PAM ====		==== Using PAM ====

	Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included~~. This configuration~~ applies to sessions started via PAM for members of the {{Ic\|pipewire}} group.		Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included which applies to sessions started via PAM for members of the {{Ic\|pipewire}} group. If this is the case, add your user to the {{Ic\|pipewire}} group.

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.

Prabuanand: added back the instruction to add users to the group

2026-04-15T02:44:13Z

added back the instruction to add users to the group

← Older revision		Revision as of 02:44, 15 April 2026
Line 128:		Line 128:
	==== Without PAM ====		==== Without PAM ====

	If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.		If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. If this is the case, add your user to the {{Ic\|rtkit}} group. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.

	==== Using PAM ====		==== Using PAM ====

WhyNotHugo: /* Realtime scheduling */ The details for configuring limits apply to the PAM configuration, not the rtkit configuration.

2026-04-14T16:50:14Z

Realtime scheduling: The details for configuring limits apply to the PAM configuration, not the rtkit configuration.

← Older revision		Revision as of 16:50, 14 April 2026
Line 124:		Line 124:
	Realtime scheduling will increase certain threads priorities to assist with low latency audio processing. By default, PipeWire tries to enable realtime scheduling with the [https://docs.pipewire.org/page_module_rt.html rt module].		Realtime scheduling will increase certain threads priorities to assist with low latency audio processing. By default, PipeWire tries to enable realtime scheduling with the [https://docs.pipewire.org/page_module_rt.html rt module].

	~~==== Option1 ====~~		This can be done in one of two ways: via {{Pkg\|rtkit}} or via PAM.

	~~Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], when you have a [[~~PAM~~]] login session, you should add your user to the {{Ic\|pipewire}} group.~~		==== Without PAM ====

	~~==== option2 ====~~		If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.

	~~If you don't have [[~~PAM~~]] but [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}; if this is the case, add your user to the {{Ic\|rtkit}} group.~~		==== Using PAM ====

			Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included. This configuration applies to sessions started via PAM for members of the {{Ic\|pipewire}} group.

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. ~~You may want to adjust settings for parameters like~~ <var>rt.prio</var>~~, if required~~. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.

	{{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [		{{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [

WhyNotHugo: /* Prerequisites */ XDG_RUNTIME_DIR

2026-02-11T20:32:40Z

Prerequisites: XDG_RUNTIME_DIR

← Older revision		Revision as of 20:32, 11 February 2026
Line 4:		Line 4:
	== Prerequisites ==		== Prerequisites ==

	* ~~PipeWire requires~~ [[D-Bus#D-Bus_session_bus\|D-Bus session bus]] ~~for most of its functionality~~.		* [[XDG_RUNTIME_DIR]] must be set in the running environment.
	* ~~Ensure that your~~ [[Setting_up_a_new_user#Creating_a_new_user\|~~non~~-root user ~~account~~]] ~~has~~ appropriate [[Setting_up_a_new_user#Groups_for_desktop_usage\|groups for desktop usage]].		* [[D-Bus#D-Bus_session_bus\|D-Bus session bus]] must be running.
			* [[Setting_up_a_new_user#Creating_a_new_user\|Non-root user accounts]] require appropriate [[Setting_up_a_new_user#Groups_for_desktop_usage\|groups for desktop usage]].
	* WirePlumber requires [[eudev]] for ALSA device discovery.		* WirePlumber requires [[eudev]] for ALSA device discovery.

Prabuanand: updated wiki based on message by invoked on 2026-02-08 16:49:14 in https://irclogs.alpinelinux.org/%23alpine-linux-2026-02.log

2026-02-09T05:58:25Z

updated wiki based on message by invoked on 2026-02-08 16:49:14 in https://irclogs.alpinelinux.org/%23alpine-linux-2026-02.log

← Older revision		Revision as of 05:58, 9 February 2026
Line 57:		Line 57:

	* Ensure the [[OpenRC#Prerequisites\|OpenRC User service Prerequisites]] are met and [[OpenRC#Configure environment variables\|environment variables are configured]].		* Ensure the [[OpenRC#Prerequisites\|OpenRC User service Prerequisites]] are met and [[OpenRC#Configure environment variables\|environment variables are configured]].
			* PipeWire will fail to start, if [[#Realtime scheduling\|realtime scheduling]] is not configured.
	* Issue the command {{ic\|$ rc-status -Ur}} to view and verify the current user runlevel as '''gui''' and '''default''' for Wayland and Xorg respectively.		* Issue the command {{ic\|$ rc-status -Ur}} to view and verify the current user runlevel as '''gui''' and '''default''' for Wayland and Xorg respectively.

Line 120:		Line 121:
	=== Realtime scheduling ===		=== Realtime scheduling ===

	Realtime scheduling will increase certain threads priorities to assist with low latency audio processing. By default, PipeWire tries to enable realtime scheduling with the [https://docs.pipewire.org/page_module_rt.html rt module].		Realtime scheduling will increase certain threads priorities to assist with low latency audio processing. By default, PipeWire tries to enable realtime scheduling with the [https://docs.pipewire.org/page_module_rt.html rt module].

			==== Option1 ====

	Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], when you have a [[PAM]] login session, you should add your user to the {{Ic\|pipewire}} group.		Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], when you have a [[PAM]] login session, you should add your user to the {{Ic\|pipewire}} group.

			==== option2 ====

			If you don't have [[PAM]] but [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}; if this is the case, add your user to the {{Ic\|rtkit}} group.


	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. You may want to adjust settings for parameters like <var>rt.prio</var>, if required. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. You may want to adjust settings for parameters like <var>rt.prio</var>, if required. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.
Line 135:		Line 143:
	}		}
	]</nowiki>}}		]</nowiki>}}

	~~If you don't have [[PAM]] but [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}; if this is the case, add your user to the {{Ic\|rtkit}} group.~~

	== Testing ==		== Testing ==

Encode: /* Realtime scheduling */ Rewording

2025-11-18T20:06:46Z

Realtime scheduling: Rewording

← Older revision		Revision as of 20:06, 18 November 2025
Line 120:		Line 120:
	=== Realtime scheduling ===		=== Realtime scheduling ===

	~~For glitch-free audio performance and~~ to assist with low latency audio processing, ~~the rt modules in~~ PipeWire ~~give real-time priorities~~ to ~~processing threads~~. ~~since PipeWire 0~~.3.~~66, if you have a [[PAM]~~] ~~login session,, you can add yourself to the <code>pipewire</code> group to use realtime scheduling~~.		Realtime scheduling will increase certain threads priorities to assist with low latency audio processing. By default, PipeWire tries to enable realtime scheduling with the [https://docs.pipewire.org/page_module_rt.html rt module].

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. You ~~way~~ may want to adjust settings for parameters like <var>~~rtprio~~</var> ~~in the above file~~, if required. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits. {{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [		Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], when you have a [[PAM]] login session, you should add your user to the {{Ic\|pipewire}} group.

			The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. You may want to adjust settings for parameters like <var>rt.prio</var>, if required. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.

			{{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [
	{ name = libpipewire-module-rt		{ name = libpipewire-module-rt
	args = {		args = {
Line 132:		Line 136:
	]</nowiki>}}		]</nowiki>}}

	~~Alternately~~, {{Pkg\|rtkit}} ~~package can be used and in that~~ case, ~~remember to~~ add your user to the ~~<code>~~rtkit~~</code>~~ group.		If you don't have [[PAM]] but [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}; if this is the case, add your user to the {{Ic\|rtkit}} group.

	== Testing ==		== Testing ==

Prabuanand: Accuracy tag removed as suggested changes are vali and hence corrections made..

2025-11-18T16:03:11Z

Accuracy tag removed as suggested changes are vali and hence corrections made..

← Older revision		Revision as of 16:03, 18 November 2025
Line 120:		Line 120:
	=== Realtime scheduling ===		=== Realtime scheduling ===

	~~{{Accuracy\|Is rtkit still recommended?\|section=Is rtkit still recommended for Realtime scheduling?}}~~
	For glitch-free audio performance and to assist with low latency audio processing, the rt modules in PipeWire give real-time priorities to processing threads. since PipeWire 0.3.66, if you have a [[PAM]] login session,, you can add yourself to the <code>pipewire</code> group to use realtime scheduling.		For glitch-free audio performance and to assist with low latency audio processing, the rt modules in PipeWire give real-time priorities to processing threads. since PipeWire 0.3.66, if you have a [[PAM]] login session,, you can add yourself to the <code>pipewire</code> group to use realtime scheduling.

Prabuanand: added and organised links

2025-11-18T05:09:05Z

added and organised links

← Older revision		Revision as of 05:09, 18 November 2025
Line 123:		Line 123:
	For glitch-free audio performance and to assist with low latency audio processing, the rt modules in PipeWire give real-time priorities to processing threads. since PipeWire 0.3.66, if you have a [[PAM]] login session,, you can add yourself to the <code>pipewire</code> group to use realtime scheduling.		For glitch-free audio performance and to assist with low latency audio processing, the rt modules in PipeWire give real-time priorities to processing threads. since PipeWire 0.3.66, if you have a [[PAM]] login session,, you can add yourself to the <code>pipewire</code> group to use realtime scheduling.

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. You way may want to adjust settings for parameters like <var>rtprio</var> in the above file, if required. Alternatively, it can be set at user level within the ceiling set by the system's rlimits. {{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. You way may want to adjust settings for parameters like <var>rtprio</var> in the above file, if required. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits. {{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [
	{ name = libpipewire-module-rt		{ name = libpipewire-module-rt
	args = {		args = {
Line 224:		Line 224:
	mod.rt ../src/modules/module-rt.c:1005:do_rtkit_setup: RTKit does not give us RTTimeUSecMax, using -1		mod.rt ../src/modules/module-rt.c:1005:do_rtkit_setup: RTKit does not give us RTTimeUSecMax, using -1

	~~Installing the {{pkg\|rtkit}} package as mentioned in~~ [[#Realtime scheduling\|Realtime scheduling]] section ~~resolves~~ the above error message.		Follow [[#Realtime scheduling\|Realtime scheduling]] section to resolve the above error message.

	== See also ==		== See also ==

	* [[Bluetooth]]		* [[Bluetooth]]
	* [https://gitlab.freedesktop.org/pipewire/pipewire ~~PipeWire source repository~~]		* Official PipeWire links
	* [https://gitlab.freedesktop.org/pipewire/pipewire~~/-/wikis/home PipeWire Wiki~~]		** [https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home Wiki]
			** [https://docs.pipewire.org Documentation site]
			** [https://gitlab.freedesktop.org/pipewire/pipewire Source repository]
	* [https://wiki.archlinux.org/index.php/PipeWire PipeWire on the ArchWiki]		* [https://wiki.archlinux.org/index.php/PipeWire PipeWire on the ArchWiki]
	* [https://wiki.gentoo.org/wiki/PipeWire PipeWire on the Gentoo Wiki]		* [https://wiki.gentoo.org/wiki/PipeWire PipeWire on the Gentoo Wiki]

	[[Category:Sound]]		[[Category:Sound]]

Prabuanand: changed the section based on https://docs.pipewire.org/page_module_rt.html and earlier text

2025-11-17T17:15:36Z

changed the section based on https://docs.pipewire.org/page_module_rt.html and earlier text

← Older revision		Revision as of 17:15, 17 November 2025
Line 121:		Line 121:

	{{Accuracy\|Is rtkit still recommended?\|section=Is rtkit still recommended for Realtime scheduling?}}		{{Accuracy\|Is rtkit still recommended?\|section=Is rtkit still recommended for Realtime scheduling?}}
			For glitch-free audio performance and to assist with low latency audio processing, the rt modules in PipeWire give real-time priorities to processing threads. since PipeWire 0.3.66, if you have a [[PAM]] login session,, you can add yourself to the <code>pipewire</code> group to use realtime scheduling.

	~~For realtime scheduling, it is recommended to use~~ {{~~Pkg~~\|~~rtkit~~}} ~~package~~. ~~Add your~~ user to the <~~code~~>~~rtkit~~</~~code~~> ~~group.~~		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. You way may want to adjust settings for parameters like <var>rtprio</var> in the above file, if required. Alternatively, it can be set at user level within the ceiling set by the system's rlimits. {{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [
			{ name = libpipewire-module-rt
			args = {
			#nice.level = 20
			#rt.prio = 88
			}
			flags = [ ifexists nofail ]
			}
			]</nowiki>}}

	~~Alternatively~~, ~~ensure~~ your user ~~has the right ulimit permissions. Since PipeWire 0.3.66, you can add yourself~~ to the <code>~~pipewire~~</code> group~~. You generally need (e.g. in {{Path\|/etc/security/limits.conf}}):~~		Alternately, {{Pkg\|rtkit}} package can be used and in that case, remember to add your user to the <code>rtkit</code> group.

	~~<pre>~~
	~~@pipewire - memlock 4194304~~
	~~@pipewire - nice -19~~
	~~@pipewire - rtprio 95~~
	~~</pre>~~

	This allows a member of the pipewire group to have the right permissions for PipeWire to use realtime scheduling without rtkit. This same snippet comes with PipeWire since 0.3.66, so if you have a [[PAM]] login session and add yourself to the pipewire group, you don't have to do anything else. Note that the above {{Path\|/etc/security/limits.conf}} will only work if your session is using [[PAM]].

	== Testing ==		== Testing ==