|
Page 1 of 1
|
[ 8 posts ] |
|
WebRTC voice isn't working for me
Author |
Message |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 250
|
I'm not sure whether I should report this here or with LL. When I try to use WebRTC voice in LL's four testing regions, theoretically the viewer connects, because I get a dot. If I click on the "talk" button, I get green waves around the dot, however it's not real. Pavucontrol shows no device using the microphone or playing sound. I tried changing the device from the viewer's picker, the viewer seems to understand it but the problem persists. (Shouldn't it be set to Default anyway, so the operating system can choose?) But I tried picking my headset as both incoming and outgoing anyway, but it didn't help. I am enclosing a log, hoping you can shed some light. (I did enable the DebugWebRTCVoice debug setting.) I do have voice on Discord, out of the box, which also uses WebRTC. Thank you.
|
2025-09-01 15:44:00 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6059
|
The WebRTC client is not using Pulseausio but ALSA.
You need to set the volume using the ALSA mixer.
|
2025-09-01 17:06:24 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6059
|
Also, in your log, you can see: So, this seems to point to an ALSA configuration issue on your system or a bad device configured in the viewer (try another ?).
|
2025-09-01 18:30:08 |
|
 |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 250
|
I think I fixed that, by deleting ~./asoundrc , which must had been old because I haven't fiddled with ALSA in years (it's all Pipewire now). Anyway, now the device list never loads.  It looks similar to this. Should I report to LL? Also I don't have the plasmatic waves around my dot. Changing volumes in input channels in Alsamixer changes them in Pavucontrol too, but it seems to make no difference with regards to SL WebRTC voice.
|
2025-09-02 10:19:17 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6059
|
This is a system miss-configuration... I'm afraid I cannot help "from afar" and I would need to get my dirty hands in your system to solve this issue (which is not actionable on the viewer coding side of things). Sadly, Linux audio configuration is (and has always been) a total mess and a genuine PITA (for example I spent a full week fiddling with my first Zen 4 on an ASUS motherboard, due to the latter only exposing the USB audio interface, and had to write a non-trivial ALSA configuration file to get the audio playing both on the loud speakers and the headphone)...  Your best bet is to ask in your distro's support group/forums for help with WebRTC/ALSA configuration. The ~/.asoundrc file should hold: Which the cool_vl_viewer wrapper script will add when missing. Else, WebRTC cannot get the device names.
|
2025-09-02 12:15:00 |
|
 |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 250
|
I understand. Thank you, Henri, I shall research more. Indeed, and it doesn't help that new protocols keep getting added to the existing ones. Between Alsa, Pulseaudio and Pipewire, perhaps something gets lost.
|
2025-09-02 17:04:17 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6059
|
I just found out during the voice meeting with Philip today that my old "VoiceWebRTCAutoTuneDuration" workaround (for WebRTC loosing voice when crossing parcels on different voice channels) is not working properly any more, and under Linux it causes WebRTC to loose the audio devices (does not seem to be the case under Windows)...
This may be why it did not work for you. Simply set this debug setting to 0.0 (this will be the default for next release if I can't find a better solution). When you loose voice on parcel/channel crossing, simply stop and restart voice instead.
|
2025-10-01 20:41:10 |
|
 |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 250
|
Thank you for the trick, Henri, but I'm afraid that didn't work either.  I don't understand what is going on. Sometimes, the viewer will let me choose devices, but when I speak on the microphone, it never "fills the boxes" according to the volume. (Firestorm does, sometimes.) In either case, sometimes, when I click on "speak", the voice dot will produce waves (which, sometimes will correspond to my actual speaking, other times they are entirely fake), but other people won't see them and they will never go through. I don't think the viewer (or Firestorm, for that matter) actually connects to the voice system. Since it does for you, it must be something within my system, but I don't know if it's the Alsa/Pulseaudio/Pipewire mess (which otherwise works fine) or something else. Vivox, on the other hand, which always caused problems, works annoyingly well under Wine. I'm attaching another log, for what it's worth.
|
2025-10-02 09:23:27 |
|
|
|
Page 1 of 1
|
[ 8 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 2 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|