mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #242] Surround sound is completely broken, with ringing, crazy volume spikes and ducking, 5.1 channels wrongly mapped, and some channels not mapped at all. 7.1 is not working at all. #164
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#164
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rkkoszewski on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/242
Hi, I've been testing the Surround Sound settings. Apparently that works in Wolf, but it doesn't seem to be working correctly.
Stereo works perfectly fine.
5.1: Has heavy distortions in audio. It seems that some volume normalization/ducking is going on, that ducks the audio at times, and at times it goes super loud, distorting the audio up to pure screeching white noise. I've also ran the Frauenhofer 5.1 surround test, and I noticed that the left speaker seems to be mapped to the right physical speaker, the center one is mapped correctly to the physical center, but the right speaker drives both physical speakers from the back. And the rest of the speakers don't work at all.
7.1: Doesn't work at all and produces silence.
Here are the logs for the 5.1 setup.
Wolf Logs:
WolfPulseAudio Logs:
Moonlight was running on Windows on a 5.1 card. But I did previous tests from an Android device, and there I could repro the same issues.
UPDATE:
I get the same artifacts as in this bug: #199
@ABeltramo commented on GitHub (Aug 13, 2025):
I knew there was already an issue about this, and I was trying all kind of queries on Discord. Thankfully, I've seen your edit; I'm going to close this as a duplicate of #199 it's definitely worth to keep the discussion there.
Can you try the proposed fixes in there and report back if that works for you too?