secondlife / secondlife/viewer
WebRTC Spatial voice sometimes cannot be heard from someone in an adjacent region
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Environment
Second Life Release 7.1.11.11074622243 (64bit) Release NotesYou are at 128.0, 128.0, 23.0 in webRTC1 located at simhost-07c23d76c83837d55.aditi
SLURL: secondlife://Aditi/secondlife/webRTC1/128/128/23
(global coordinates 259,968.0, 245,376.0, 23.0)
WebRTC-Voice 2024-09-30.11111372425
Release Notes
CPU: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (3491.91 MHz)
Memory: 32610 MB
OS Version: Microsoft Windows 10 64-bit (Build 19045.4894)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce GTX 1080/PCIe/SSE2
Windows Graphics Driver Version: 32.0.15.6590
OpenGL Version: 4.6.0 NVIDIA 565.90
Window size: 1712x1217
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.375
Render quality: 3
Texture memory: 8192MB
Disk cache: Max size 1638.4 MB (26.4% used)
J2C Decoder Version: KDU v7.10.4
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.23.1 / OpenAL Community / OpenAL Soft: OpenAL Soft
Dullahan: 1.14.0.202408091639
CEF: 118.4.1+g3dd6078+chromium-118.0.5993.54
Chromium: 118.0.5993.54
LibVLC Version: 3.0.21
Voice Server Version: Secondlife WebRTC Gateway
Packets Lost: 0/270 (0.0%)
October 11 2024 13:06:29
Description
Spatial voice does not work reliably for users that log into adjacent regions.
Reproduction steps
Repro: (this is not a reliable repro
- UserA (testerd5) logged into WebRTC1 on Aditi (Windows 10, 7.1.11.11074622243 ExtraFPS)
- UserB (testerd1) logged into WebRTC2 on Aditi (Windows 11, 7.1.11.11074622243 ExtraFPS)
- UserA and UserB cannot hear each other across the region boundary
- UserB crossed into WebRTC2
- UserB can see their own voice waves.
- UserB cannot hear or see voice waves from testerd5.
Viewer logs with debugging enabled:
UserA WebRTC1 SecondLife.log
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached UserA WebRTC1 SecondLife.log and UserB WebRTC2 to WebRTC1 SecondLife.log, then try the reported two-user scenario across the WebRTC1/WebRTC2 boundary. Done means adjacent-region users can reliably hear each other and see one another's spatial voice waves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- audio-video-rtc
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100