User changes to configurations persisting through updates
As I learn more and more about pipewire and how to set it up for my needs, I'm wanting to create some more changes than just going into pipewire.conf and altering default.clock.min-quantum from 1024 to 4096 (this change is so that way YouTube, Spotify and other consumer audio applications use very little CPU usage and don't occasionally stutter when I have the CPU governor set to powersave). To that end, I have a question: Is there a way to create persistence for user changes between updates - possibly pulling the rules out of the individual media-session.d configuration files and into their own folder , i.e. /home/username/.pipewire folder? That particular option has several benefits
- It creates persistence between updates for user modifications?
- It makes it so that if a user alters configuration files so severely it causes the pipewire daemon to crash, it's a matter of recreating the user, rather than a whole reinstall? (Have yet to see how this would be possible, but you never know what people/applications people make will do).
- It makes it so if a system has multiple users, that each can be configured to the users' needs - i.e. in my case, I answer phones all day logged into my work user, and would be perfectly happy with the default configuration for my work user, but my proaudio user I want some custom configurations for.