mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
No audio output and no push to talk possible in 1.5.634 on Windows #2829
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#2829
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 @Hartmnt on GitHub (May 20, 2024).
Discussed in https://github.com/mumble-voip/mumble/discussions/6418
Originally posted by smakibbfb May 20, 2024
After updating to the new version this morning I get no audio at all and the push to talk function is completely broken, even deleting the config and resetting the audio devices to default does nothing at all to help, if i revert back to the previous version though everything works perfectly again, is anyone able to point me in a direction as to why this might be happening?
Hi, Windows 11 Pro 23H2 Build 22631.3593 with a Soundblaster AE-5 Plus soundcard, no sound from the new version at all
@Hartmnt commented on GitHub (May 20, 2024):
@smakibbfb
Could you please send us the contents of the developer console when using the new version?
It may contain a clue as to what the problem is.
@smakibbfb commented on GitHub (May 21, 2024):
@Hartmnt commented on GitHub (May 21, 2024):
@davidebeatrici
@Krzmbrzl commented on GitHub (May 21, 2024):
This part seems to be the juicy bit:
@davidebeatrici commented on GitHub (May 21, 2024):
Precisely:
IsFormatSupported()returnsAUDCLNT_E_UNSUPPORTED_FORMATwhen the format is not supported in exclusive mode.See https://learn.microsoft.com/en-us/windows/win32/api/audioclient/nf-audioclient-iaudioclient-isformatsupported.
@Krzmbrzl commented on GitHub (May 21, 2024):
So the solution would be to turn off exclusive mode?
@davidebeatrici commented on GitHub (May 21, 2024):
Yes.
@smakibbfb commented on GitHub (May 22, 2024):
Only problem there is I have never had exclusive mode set.
@davidebeatrici commented on GitHub (May 22, 2024):
Interesting... could you provide brand and model of your sound card, please?
@smakibbfb commented on GitHub (May 23, 2024):
It's a Sound BlasterX AE-5 Plus, https://uk.creative.com/p/sound-blaster/sound-blasterx-ae-5-plus
Running the latest drivers and software
@davidebeatrici commented on GitHub (May 23, 2024):
Well... in that case the format we are requesting is not supported and the driver does not suggest a close one.
Could you provide a screenshot of the audio output device properties? Specifically, I'm interested in the format that is set.
@smakibbfb commented on GitHub (May 24, 2024):
Default is the above but I have tried a few others too, just want to be clear this has worked perfectly and still works perfectly on the previous version of Mumble
@davidebeatrici commented on GitHub (May 24, 2024):
Without any changes at all to the audio driver and/or settings?
@smakibbfb commented on GitHub (May 24, 2024):
Yep, previous version has worked fine since it was released with no changes between the two.
@Fuchs commented on GitHub (Jun 16, 2024):
Same effect here, and while I also do have a Sound BlasterX AE-5 in my machine, it's actually not used and not the default, in use and the default is a Sennheiser GSX 1200. Downgrading mumble to 1.4.287 resolves the issue, upgrading to 1.5.634 it doesn't work, with the exact same settings between the two versions.
@Krzmbrzl commented on GitHub (Aug 4, 2024):
@smakibbfb @Fuchs is anyone of you able to compile Mumble yourself in order to do a bisect to identify the root of this issue?
@github-actions[bot] commented on GitHub (Aug 18, 2024):
This issue has been marked as stale, because our request for more information has thus far not been fulfilled.
If no further action occurs, this issue will be closed within 7 days.