Arch Linux

adnanalbeda

Member

Registered: 2024-05-28

Posts: 2

[SOLVED] Move PulseAudio configs to pipewire-pulse

I have Rog Strix G15, which is known for audio issues with Linux.

I followed the instructions here:

https://bbs.archlinux.org/viewtopic.php … 7#p2025677

And it is working great. I decided to move to pipewire, and now I'm having the problem of either 100% or mute.

The trick was in element master in pulseaudio

/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common

:

[Element Master]
switch = mute
volume = ignore

but I don't know how I can replicate this config in pipewire.

Last edited by adnanalbeda (2024-06-09 16:48:50)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,104

Re: [SOLVED] Move PulseAudio configs to pipewire-pulse

Pipewire generally uses the same exact logic here as pulseaudio, just in a slightly different path,so...

/usr/share/alsa-card-profile/alsa-mixer/paths/analog-output.conf.common -- note that in the current setup logistics that file will get overwritten on alsa-card-profile updates, might want to make a mental note of that, or add that path without the leading slash to NoUpdate in your /etc/pacman.conf

Last edited by V1del (2024-05-28 12:29:09)

adnanalbeda

Member

Registered: 2024-05-28

Posts: 2

Re: [SOLVED] Move PulseAudio configs to pipewire-pulse

Thx, it is working perfectly.

Just the 'alsa-mixer' folder is called 'mixer'.

May I ask how you learnt this? What kind of tutorials or docs could lead to this?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,104

Re: [SOLVED] Move PulseAudio configs to pipewire-pulse

ah whoops, but yeah.

As for how to learn this, I'm generally interested in most of the things I run and how and why they work the way they do (... that's what I primarily run FOSS software for, you don't have to guess how things work you can just check), if you followed pipewire's footsteps into audio (it originally was just intended for video/screensharing in sandboxed/flatpak environments) they were very keen on keeping things compatible with the existing solutions. So for the pulse compatibility layer/the profile logistics they copied the same code pulseaudio used as is, just with a different prefix path (there even was a short time, where pulseaudio's lookup path for profile and mixer info was also in alsa-card-profiles... I was partially the reason that got reverted, because pulseaudio had a much slower release schedule and some of the profile adjustments made for pipewire were not yet picked up by pulseaudio, leading to breakage if you were still using pulseaudio, which I ran into and subsequently reported, after which the lookup paths got split again).

For "tutorials" the closest is probably the general Migration page on the pipewire wiki: https://gitlab.freedesktop.org/pipewire … PulseAudio

In any case, please mark as [SOLVED] by editing the title in your first post.

Last edited by V1del (2024-05-28 15:53:07)