mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Audio outputting to all channels in multichannel configuration #457
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#457
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 @RaspyAU on GitHub (Feb 7, 2015).
Hi guys.
Running Windows 8.1 and Mumble 1.2.8 client and I've always had an issue where Mumble outputs voice to all available channels. So in a 5.1 configuration, I get voice output from left, right, center and rear speakers. Its very loud as a result and makes using it rather difficult.
Previously I would get around this by using headphones but its just reached a point where its just too frustrating.
Would it be possible to implement a channel output override?
@MonkeyCrumpets commented on GitHub (Feb 7, 2015):
Seconded. Not only is the loud volume irritating but having the sound come from all speakers at once in a 5.1 system makes it seem like the sound is coming from inside your head which is very distracting and fatiguing. It would be nice to be able to manually set which speaker(s) to use (eg. centre or left and right fronts only) or failing that, the number of output channels (eg. mono, stereo, 5.1 etc).
@RaspyAU commented on GitHub (Mar 22, 2015):
Can we get an update/acknowledgement on this issue?
@MoonSha commented on GitHub (Apr 6, 2015):
Hey RaspyAU, I've been annoyed no end by this so I found a hacky workaround, create a file called avrt.dll and put it in your mumble directory. It breaks the WASAPI sound system from loading so it falls back to directsound which doesn't have this issue, you may have trouble getting your mic to work but I was able to use ASIO on mine.
@RaspyAU commented on GitHub (Apr 6, 2015):
Excellent. Much obliged MoonSha! I will give that a try.
@MoonSha commented on GitHub (Apr 9, 2015):
So I quickly discovered that the avrt.dll trick broke the volume suppression, so I checked the console log and found that mumble was trying to open a 2 channel audio "stream" but the driver was rejecting it. Based on that I updated my x-fi drivers to Daniel_K unofficial drivers and fingers crossed the problem seems to have stopped, the log no longer reports that it's failing to open a 2 channel stream.
@mfasse commented on GitHub (Sep 4, 2015):
There is a similar issue from 2013 on sf.net and not a word about it since then :/
@MoonSha commented on GitHub (Sep 4, 2015):
I haven't had a problem since changing audio drivers so I think it's safe to say the issue is caused by some miscommunication between mumble and the soundcard.
@mfasse commented on GitHub (Sep 4, 2015):
Tried all drivers available for my sound card and no other audio application seems to have this problem.
@brokenhands commented on GitHub (Sep 24, 2015):
As another 5.1 user I'd love this feature. The all-around sound breaks the point of having a surround system for gaming.