WebRTC: Unable to hear voice, but others can hear me
under review
Lou Netizen
I am on macOS Sequoia, and audio runs through a multi-channel audio interface. Microphone input is on channel 1 at 44.1Khz; output is to main 1-2.
Since the changeover to WebRTC voice, I have been unable to hear voice from any other users. Others report they can hear me clearly, and when they speak the green "signal" indicators appear above their heads, but I hear no audio. I have confirmed my voice input/output settings are correct (and unchanged since Vivox). I can hear other sounds from Second Life (inworld audio played from inventory, played from script, media streams, etc.) as normal. As of 10-Jun I hear no "echo" in Voice Echo Canyon. Again, I can hear non-voice sounds just fine.
I'm happy to provide any additional information that would be helpful.
Log In
Maestro Linden
marked this post as
under review
Maestro Linden
marked this post as
needs info
Maestro Linden
Hi Lou Netizen, I have a few questions:
- What is the hardware model of your multi-channel audio interface?
- If you open Preferences -> Sound & Media -> Voice Input/Output devices, what is the current output device setting?
- If you open Utilities -> 'Audio Midi Setup.app' in MacOS, what is the value of "Format" for the audio output device that is in use by the viewer's voice output (either explicitly or if set by default)?
- If you have speakers that aren't connected to the audio interface (such as built-in speakers or headphones plugged directly into your mac's 3.5mm port) and change the voice output device to that device, can you hear voice audio in that configuration?
- For this thing, note that all voice audio output is muted while the 'Voice Input/Output devices' panel is open. You need to click "OK" to apply the preference update and (hopefully) start hearing voice audio.
It would also be helpful to get a viewer log from a voice-connected session that had this issue (incoming voice audio inaudible). A short-lived viewer session should be fine.
To send a viewer log file, the instructions are:
- Log out
- Zip up your viewer logs folder. This page tells you where to find the logs folder: https://community.secondlife.com/knowledgebase/english/how-to-report-a-bug-r224/ Note that for Firestorm sessions, the directory and log filename pattern is the same but with "Firestorm" substituted for "SecondLife".
- Email the zip file to bug-attachments@lindenlab.com and reference the issue name in the email subject line.
- Leave a comment on this canny issue once that's done so we can take a look at the logs.
With this information, we can compare the server logs to the viewer log and hopefully see what triggered the failure.
The "Voice Echo Canyon" region you've already been testing in should be good for testing voice audio output, including when toggling between different output devices. If you want to test with other users' voices, there are usually several people talking in these regions:
Lou Netizen
Maestro Linden I've sent two sets of logs, one demonstrating the reported issue, and another of a hard viewer crash when attempting to switch voice output as recommended above.
Hardware is presently a MOTU 828x connected via Thunderbolt/USB-C. The MOTU 828x is set as the default audio interface on the Mac, for both input and output.
When I open Voice Input/Output devices, the current device output setting is MOTU 828x. If I attempt to change that when logged into SL the viewer experiences a hard crash (see second set of logs, above). However, if I change the setting to the Mac's built-in speaker PRIOR to logging in, quit the viewer, relaunch the viewer, and then go to Voice Echo Canyon, I
can
hear my voice echoed on the built-in speaker. All other
sounds from SL play through the MOTU 828x. If I try to change the voice output at that point, same hard crash.If there's any other info I can provide, still happy to do so. Thank you!
Maestro Linden
Hi Lou Netizen, thanks for the details in your email. I don't see the actual attached files in the email - could you double check if they show up as attached on your end?
Also, while I'm bugging you, I had updated my questions just before (or maybe just after) you had replied in the canny issue. I added 1 more question;
> If you open Utilities -> 'Audio Midi Setup.app' in MacOS, what is the value of "Format" for the audio output device that is in use by the viewer's voice output (either explicitly or if set by default)?
I'm curious about that because I wasn't sure if your MOTU 828x is using something exotic. WebRTC voice operates at 48kHz 2ch natively, and the OS should be able to handle output conversion to other sampling rates (at least it does on my Mac's built-in speakers when I customize them to use 44.1, 88.4, or 96kHz sampling rates) , but I thought it would be worth checking just in case.
Lou Netizen
Maestro Linden I sent two ZIP archives of log files. On attempting to resend, I got this:
<bug-attachments@lindenlab.com>: host aspmx.l.google.com[142.251.188.27] said:
550-5.7.1 [[REDACTED IP] 12] Gmail has detected that this message is
likely 550-5.7.1 unsolicited mail. To reduce the amount of spam sent to
Gmail, this 550-5.7.1 message has been blocked. For more information, go to
550 5.7.1 https://support.google.com/mail/?p=UnsolicitedMessageError
d9443c01a7336-2c433b2a14esi13578475ad.187 - gsmtp (in reply to end of DATA
command)
Audio MIDI Setup reports 48KHz, 2ch, 24-bit for audio output, which matches the MOTU configuration. However, I've been able to reproduce the same problems with setting it to 44.1Khz/16-bit.