u/Complete_Flight8303

https://forums.opensuse.org/t/audio-in-games-cuts-out-after-several-seconds/185139/12

(I'm running Mint Cinnamon) I have been experiencing game audio stuttering or cutting out and found a solution that works, linked above. By entering pw-metadata -n settings 0 clock.force-quantum 512 into the terminal, my problem is solved, but it's not permanent and I have to do it every time I turn on my computer to play.

The user in the forum suggests the following:

I created a file in /etc/pipewire/pipewire.conf.d called 15-clock-quantum.conf. The contents are:

context.properties = {
    default.clock.quantum  =       512
}

That sets the clock buffer size to 512 by default. I double-checked it, after rebooting, by running:
“pw-metadata -n settings”.

I thought it was solved. Then I tested it, and it hadn’t fixed it. I’ll have to do more reading of the pipewire docs. I think that somehow, even though I set the default to 512, something is overriding that when the system boots, or when a game launches, or something. So I need to figure out how to lock that value. But like I said, I’m sure it’s in the docs somewhere. I have a few hours tomorrow to look into it. I will update when I have the solution. I created a file in /etc/pipewire/pipewire.conf.d called 15-clock-quantum.conf. The contents are:
context.properties = {
default.clock.quantum = 512
}

That sets the clock buffer size to 512 by default. I double-checked it, after rebooting, by running:

“pw-metadata -n settings”.
I thought it was solved. Then I tested it, and it hadn’t fixed it.
I’ll have to do more reading of the pipewire docs. I think that
somehow, even though I set the default to 512, something is overriding
that when the system boots, or when a game launches, or something. So I
need to figure out how to lock that value. But like I said, I’m sure
it’s in the docs somewhere. I have a few hours tomorrow to look into
it. I will update when I have the solution.

To which another user replies:

Maybe default.clock.min-quantum ? See man pipewire.conf.

___

My understanding is that he edited his original line to read:

context.properties = {
default.clock.min-quantum = 512
}

This appears to have worked for the original user but I've only been using Linux for about 48 hours and I don't understand how they are implementing this fix. I think they're creating a new .conf file in pipewire? I tried to do just that but it appears I don't have the correct permissions. Do I just need to give myself permission somehow or am I off base? If so, any help would be great.

Thanks!