Trying crackling cures in pipewire.conf

English Hardware
1

I have been trying to fix very annoying crackling in audio with bluetooth. The problem is more cutouts of the sound stream rather than crackling noise on top of continual sound stream. I use alsa, pipewire, bluetooth, and wire plumber. Installed per openSUSE instructions. Everything works but “crackles”.

I have been modifying parameters in user directory pipewire.conf as seen in several posts to try to find a right combination.

I just noticed that there are additional pipewire.confs in root in /etc/pipewire and /etc/alsa/conf.d

Should the root *.conf really the one be modified rather than the user pipewire.conf or should it be modified to be the same as the user configs or do I just continue to tinker with the user confs.

What is the relationship between root and user pipewire.conf? Which controls?

thanks, tom kosvic

2

User configs will override system-wide settings…

System-Wide Overrides: If you place a configuration file in /etc/pipewire, it will override the default settings in /usr/share/pipewire.

User-Specific Overrides: You can also place a configuration file in ~/.config/pipewire to override the default settings for your specific user.

3

Need further clarification. I have:

/home/tom/.config/pipewire/pipewire.conf
/etc/pipewire/pipewire.conf
/usr/share/pipewire/pipewire.conf
and
/etc/alsa/conf.d/50-pipewire.conf

In which one should I be tinkering with the settings to possibly control crackling?

thanks for any insights.

4

Any of the first three locations should be ok. If you only have one user configured, consider a user config (editable as user).

Refer man pipewire.conf for more information.

5

I should have looked up the man file. It is spelled out clearly there. I have been tinkering with the right file. But the tinkering is not working but that is another thread.

I do have only 1 user.

Somehow I thought man function only covered an executable app not a file. It never occurred to me to look at man.

thanks, tom kosvic

6

Logically, when one hears about man one could be tempted to use

man man

to learn about man.

And yes, there it is:

The table below shows the section numbers of the manual followed by the types of pages they contain.


0	Header files (usually found in /usr/include)
1	Executable programs or shell commands
2	System calls (functions provided by the kernel)
3	Library calls (functions within program libraries)
4	Special files (usually found in /dev )
5	File formats and conventions eg /etc/passwd
6	Games
7	Miscellaneous (including macro packages and conventions), e.g. man(7), groff(7)
8	System administration commands (usually only for root)
9	Kernel routines [ Non standard ]
7

Closing this topic out, and a link to your subsequent discussion: