Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'm now using a Sound Blaster AE-5 and everything works wonderfully with it... except for Counter-Strike 2, obviously. I noticed recently that every time I shoot or get hit or anything that makes a sound, the first time it plays there's a 1/4 second to as much as a 2 second pause.
If I re-route sound through to HDMI using my AMD GPU's inherent ability to process sound, the hitching/pausing goes away.
Long story short: It ended up being a PIpewire setting. Behold...
I don't like making system-wide changes, so I first copied the contents of /usr/share/pipewire/ into a new directory in ~/.config/pipewire/ then I edited the pipewire.conf file in there.
I found the line:
default.clock.min-quantum = 16
That's WAY too low!
I changed it from 16 to 1024 and, like magic, no more sound-based hitching. I also haven't experienced any laggy sound, so I guess that's that.
I hope it helps someone else!