Hello o/
My name is Max
Been using linux since May and sometimes (seemingly at random) in games, that some may call friend slop, my microphone input is constantly cutting out.
Ive tried many things to solve this issue but i cannot find anything that would help. It honestly can be my lack of knowledge about linux or pipewire in general.
After switching to Kubuntu (studio edition) where i thought that pipewire is preconfigured issue is now persistent and its now rare to have a game when my mic works.
Games i talk about in particular are PEAK and demo of YapYap. I suspect it is issue with any unity game but my steam library is not rich enough to test that out.
I think on unity specifically cus my Team Fortress 2 install works fine no matter the method (native or proton the win64bit version)
After searching around the web i tried these things:
configuring quantum and rates of pipewire
adding latency to pulse to launch arguments with PULSE_LATENCY_MSEC=[values from 60 to 100] %command%
changing around priority using rt-kit
Diagnostic wise I honestly dont know much so I would be open to give you folks all the info you may need relevant to this issue
Thank you in advance for any help
My name is Max
Been using linux since May and sometimes (seemingly at random) in games, that some may call friend slop, my microphone input is constantly cutting out.
Ive tried many things to solve this issue but i cannot find anything that would help. It honestly can be my lack of knowledge about linux or pipewire in general.
After switching to Kubuntu (studio edition) where i thought that pipewire is preconfigured issue is now persistent and its now rare to have a game when my mic works.
Games i talk about in particular are PEAK and demo of YapYap. I suspect it is issue with any unity game but my steam library is not rich enough to test that out.
I think on unity specifically cus my Team Fortress 2 install works fine no matter the method (native or proton the win64bit version)
After searching around the web i tried these things:
configuring quantum and rates of pipewire
adding latency to pulse to launch arguments with PULSE_LATENCY_MSEC=[values from 60 to 100] %command%
changing around priority using rt-kit
Diagnostic wise I honestly dont know much so I would be open to give you folks all the info you may need relevant to this issue
Thank you in advance for any help