secondlife / secondlife/viewer
Can only hear users for 1 second after turning on the voice.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Environment
OS Version: Pop!_OS 24.04 LTS
Kernel: Linux 6.18.7-76061807-generic x86_64
CPU: AMD Ryzen 7 5800X 8-Core Processor (16 threads)
RAM: 31 GiB
GPU: NVIDIA GeForce RTX 3090
Audio Server: PulseAudio (on PipeWire 1.5.85)
Playback Device: Yamaha MG-XU
Playback Device ID: alsa_output.usb-Yamaha_Corporation_MG-XU-00.analog-stereo
Input Device (mixer): Yamaha MG-XU
Mic Device: Anua Mic CM 900
Default Mic: alsa_input.usb-Anua_Mic_CM_900_Anua_Mic_CM_900-00.mono-fallback
Storage: multiple drives detected, including 1.8 TB + 223.6 GB + 223.6 GB
Description
From Discord
On my side (Linux user too), everyone can hear me, but I can hear them only 1 sec after turning on the voice. after it's silence (litterally 1 second !). The green indicators keep moving, but not like it shows the voice, but more "continung the last movement of sounds heared".
I'm on the last beta on firestorm, but I had the same at the last release.
I have tried many things (changing the "default" to the exact speaker, and going back to default, removing the gain control, echo etc, relogging, restarting...)
lucky for me, I can talk to my friends via discord, but it's a bit annoying sometimes.
From Roxie:
- Note, the user is using a mixer panel for input.
Reproduction steps
Using the Linux build with a multi-channel input, attempt voice.
This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting
/reward 100 (replace 100 with the amount).🕵️♂️ If someone starts working on this issue to earn the rewards, they can comment
/try to let everyone know!🙌 And when they open the PR, they can comment
/claim #5791 either in the PR description or in a PR's comment.🪙 Also, everyone can tip any user commenting
/tip 20 @roxanneskelly (replace 20 with the amount, and @roxanneskelly with the user to tip).📖 If you want to learn more, check out our documentation.
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
No source file, test, or entry point is named. Start by reproducing the issue in the Linux build with the Yamaha mixer and multi-channel input, then trace the voice playback path and compare it with the reported one-second cutoff; done means remote audio continues and the indicators reflect current sound.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100