Signal-Desktop
Signal-Desktop copied to clipboard
signalapp
Microphone doesn't work in Signal desktop on Windows 11
- [x ] I have searched open and closed issues for duplicates
- [x ] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.
Bug Description
Microphone doesn't work in Signal desktop on Windows 11. Video works just fine. I've allowed access to microphone and camera in Signal settings as well as in Windows 11 Privacy->App permissions->Microphone->Allow desktop apps to use microphone.
In the Windows settings Signal doesn't show up as recently used.
Microphone works just fine for Zoom and apps from Microsoft Store.
Steps to Reproduce
- Open Signal Desktop
- Make an audio/video call
- Speak
Actual Result:
Other party can't hear me
Expected Result:
Other party can hear me
Platform Info
Signal Version: 5.29.0 production
Operating System:
Windows 11
Linked Device Version:
Android 12
Sorry about that. Could you give it one more try on your Windows machine and submit us a debug log using the menu (View -> Debug Log). Thanks!
Sorry about that. Could you give it one more try on your Windows machine and submit us a debug log using the menu (View -> Debug Log). Thanks!
========= System info =========
App version: 5.29.1
Environment: production
Node version: 16.9.1
OS version: Windows 10 Pro
Time: 1643292335905
User agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Signal/5.29.1 Chrome/96.0.4664.110 Electron/16.0.7 Safari/537.36
========= User info =========
conversationId: [REDACTED]07c
deviceId: 3
e164: +[REDACTED]223
pni: [REDACTED]e14
uuid: [REDACTED]98b
========= Capabilities =========
announcementGroup: true
changeNumber: false
gv1-migration: true
gv2: true
senderKey: true
========= Remote config =========
desktop.announcementGroup: enabled
desktop.calling.useWindowsAdm2: enabled
desktop.canResizeLeftPane.beta: enabled
desktop.canResizeLeftPane.production: enabled
desktop.cds: enabled
desktop.customizePreferredReactions: disabled
desktop.disableGV1: enabled
desktop.floatingDateHeaders.beta: enabled
desktop.floatingDateHeaders.production: disabled
desktop.groupCallOutboundRing: disabled
desktop.groupCalling: enabled
desktop.gv2: enabled
desktop.gv2Admin: disabled FALSE
desktop.internalUser: disabled
desktop.mandatoryProfileSharing: disabled FALSE
desktop.mediaQuality.levels: enabled 1:2,61:2,81:2,82:2,65:2,31:2,47:2,41:2,32:2,385:2,971:2,974:2,49:2,33:2,*:1
desktop.messageCleanup: disabled
desktop.messageRequests: enabled
desktop.retryReceiptLifespan: disabled 3600000
desktop.retryRespondMaxAge: disabled 1209600000
desktop.sendSenderKey2: disabled
desktop.sendSenderKey3: enabled
desktop.senderKey.retry: enabled
desktop.senderKey.send: enabled
desktop.showUserBadges: enabled
desktop.showUserBadges.beta: enabled
desktop.showUserBadges2: enabled
desktop.storage: enabled
desktop.storageWrite: disabled FALSE
desktop.storageWrite2: disabled FALSE
desktop.storageWrite3: enabled
desktop.usernames: disabled
desktop.worksAtSignal: disabled
global.calling.maxGroupCallRingSize: enabled 16
global.groupsv2.groupSizeHardLimit: enabled 1001
global.groupsv2.maxGroupSize: enabled 151
global.payments.disabledRegions: enabled 98,963,53,850,7 978,7 365,7 869,7 941
========= Statistics =========
conversationCount: at least 100
messageCount: at least 1000
senderKeyCount: at least 1
sessionCount: at least 10
========= Logs =========
INFO 2022-01-25T20:14:51.801Z background/shutdown
INFO 2022-01-25T20:14:51.801Z Flushing sql.Client.updateConversationBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete sql.Client.updateConversationBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing messageBatcher.updateMessageBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete messageBatcher.updateMessageBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing Whisper.deliveryReceiptBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete Whisper.deliveryReceiptBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing respondWithProfileKeyBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete respondWithProfileKeyBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing MessageReceiver.decryptAndCacheBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete MessageReceiver.decryptAndCacheBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing MessageReceiver.cacheRemoveBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete MessageReceiver.cacheRemoveBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing sql.Client.updateConversationBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete sql.Client.updateConversationBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing messageBatcher.updateMessageBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.801Z Flushing complete messageBatcher.updateMessageBatcher for batcher
INFO 2022-01-25T20:14:51.801Z Flushing Whisper.deliveryReceiptBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.802Z Flushing complete Whisper.deliveryReceiptBatcher for batcher
INFO 2022-01-25T20:14:51.802Z Flushing respondWithProfileKeyBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.802Z Flushing complete respondWithProfileKeyBatcher for batcher
INFO 2022-01-25T20:14:51.802Z Flushing MessageReceiver.decryptAndCacheBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.802Z Flushing complete MessageReceiver.decryptAndCacheBatcher for batcher
INFO 2022-01-25T20:14:51.802Z Flushing MessageReceiver.cacheRemoveBatcher batcher items.length=0
INFO 2022-01-25T20:14:51.802Z Flushing complete MessageReceiver.cacheRemoveBatcher for batcher
INFO 2022-01-25T20:14:51.802Z waitBatcher#waitForAllWaitBatchers
INFO 2022-01-25T20:14:51.802Z data.shutdown: shutdown requested. 0 jobs outstanding
@spogulis this is great, but I'm afraid it is only a top part of the log. Could you either save it to the file and attach it here (or send by email: [email protected] ), or click "Submit" and post here a link that will be copied to your clipboard once it is done. Thanks!
@spogulis this is great, but I'm afraid it is only a top part of the log. Could you either save it to the file and attach it here (or send by email: [email protected] ), or click "Submit" and post here a link that will be copied to your clipboard once it is done. Thanks!
Here is the full file: debuglog.txt
I'm having the same issue: Since switching to Windows 11, the mic does not work any more (the chat partners do not hear me).
@scottnonnenberg-signal it's a USB audio device: https://www.iconnectivity.com/audio4c
On my journey of a misbehaving microphone i stumbled across an issue when the windows privacy settings do not allow microphone access.
My symptoms where a bit different: nothing happened when i clicked on the mic symbol to record a voice message. no matter if "note to self" or to someone else. i havent tried a call, though.
"Settings > Privacy & security > Microphone" -> "Desktop App Web Viewer" requires microphone access. (needs to be ticket, blue highlighted)
I was unable to find any resources about this online so ill leave it here, maybe this will help some others. :)
EDIT: after some more tests its cant be an issue with the privacy settings. after a call the mic does generally not work anymore. not even for voice messages.
a restart of signal does not help. a entire system reboot is necessary to get crackling voice messages working again. another silent mute call later the same problem repeats and i have to reboot to record voice messages...
even though i thought i was only affected by #5215 it looks like im also affected by #5742...
Hi, I updated from Win10 to Win11, and since then, I have no sound from my mic only in Signal-desktop (Discord is fine, for example). Signal mic setting is OK. Same hardware and Signal on Linux works like a charm.
- Win11 privacy settings are allowing Desktop apps to use Mic, and shows that Signal asked Win for the mic (as opposed to OP).
- USB audio interface (Motu M2) with mono Mic.
Cheers :)
On windows 11 my microphone in windows settings -> system -> sound -> input device gets mutes. If I unmute it here deep in system it let me speak during the call. However it gets muted at some point (that I haven't pinpointed yet). So I have to unmute microphone before each call deep in system settings.
OK, so I end up having the final word in this frustrating issue on my side... because root cause is a window/system + application issue (which could be mitigated by Signal, see below).
TL:DR
Microphone is working again on Windows 11 with Signal. I switched input on my USB interface (see below for details) from 2R to 1L.
Details
My microphone and the input of the USB sound interface it is plugged in are MONO. There are 2 inputs on my audio interface: 1L and 2R.
BUT Windows thinks my mic/sound input is stereo (and nowhere to change this in windows, only at the application level like an audio software where you can force the mono mode of the mic, let's say audacity for example). My setup on Linux produce 2 separate mono audio inputs at the system level, which explain why I don't have this issue with Signal on Linux.
So everything ends up being "How do the software deals with a stereo input?".
Hopefully the good way:
- Application with no use for a stereo input: "Good way" to do this is to force mono mode on the microphone input by default and merge both stereo channels into one. It should apply to any video game or usual videoconferencing software (90% of what I've seen so far)
- Application that can use a stereo input: best to allow a mono fallback setting, but no issue here if stereo mode is still enabled, as at worst the mic will still works even if only on one of the stereo channels (will be heard by other people with stereo output on only "one ear").
Bad way for an application that has no use for a stereo input would be to pick one of the stereo channels and drop the other one instead of merging them. Which would mean that you can end up with a perfectly fine setup producing no sound at all in this app. If Signal does this, that would explain everything. I managed to come up with this explanation by trying to play R.E.P.O. (which shows input level live) this week end, which behaves like that.
So what now?
For the user
To to confirm you have a mono mic that is connected to a stereo source (and is recognized as such wy Windows). Then try to connect the mic to the other channel of the logical source associated with your USB audio interface (R->L or L->R).
For Signal
If you can confirm this behavior, and if you do work with mono voice signal anyway, please try to deal with stereo mics by converting them properly to mono by merging their channels, and not just picking one of the channel :)
@fdutheil We do rely on the format that windows tells us that the device is using, and have some code to convert multi-channel input to a single channel, which I believe it is picking one of the channels.
But we're also rolling out some major new changes soon (which includes specific logic to mix stereo channels to mono), which hopefully will also fix your issues. It would be useful to know if your client was using some of the new audio logic in the app or not, could provide a debuglog so we could take a look?
@fdutheil We do rely on the format that windows tells us that the device is using, and have some code to convert multi-channel input to a single channel, which I believe it is picking one of the channels.
That's my point, it is best not just "to pick one", but merge them into one, instead.
But we're also rolling out some major new changes soon (which includes specific logic to mix stereo channels to mono), which hopefully will also fix your issues. It would be useful to know if your client was using some of the new audio logic in the app or not, could provide a debuglog so we could take a look?
Noted. I uploaded logs as asked by Signal Support by then:
- my Win11 logs: https://debuglogs.org/desktop/7.42.0/b606d9a104148fe31fc9a88047cdd96f18e0b0bdd861088a2f8a4d8fc7262734.gz
- my Android logs: https://debuglogs.org/android/7.33.2/0c6f7aa26845b25d66f84cd415056df9126c5dcd9e3d6f679ee17831618abb75
- my relative's logs: https://debuglogs.org/ios/7.44.0/d529e43d535a023689797c9697b6f2d5a6bf54bd3d4df738d2b6ffd898870113.zip (after both calls).