-
Notifications
You must be signed in to change notification settings - Fork 111
In Video Room, one participant can't be heard by the others #3176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Here is a log of the (non-video) private room call that went good for hours. Timestamps are UTC. The bad call was happening on matrix.org's SFU just in the ~15 minutes before (from 18:20-18:22 UTC, according to my Element Desktop). You should be able to get the log from there. We were the exact same set of participants. |
For the record, our video room has these hidden messages in the timeline for our "bad call", timestamps from 18:09 to 18:22 UTC. This is taken from Element Desktop from participant A, but this is from a session that didn't actually enter the call. It's just member of the room. (We then proceeded to our "good call" in the non-video room at 18:25 UTC, as you can see in the livekit log.)
|
Steps to reproduce
I was told to open this ticket on an issue I reported to the #webrtc matrix room.
We've got a video room, created at about the time when the Jitsi → Element Call migration happened. We used the room for months without serious problems. Until recently:
In that room, there were 3 participants in an actual call on 2025-04-07 from 18:20 to 18:22 UTC:
Participant B could not be heard by the others. Participants A and C could be heard by all others, including B.
And here is the kicker: I invited the same participants into a fresh (non-video) private room and started a call there, and it worked without hitches for 4 hours until we called it a day.
This issue is reproducible, we had it on multiple days and on different LiveKit SFUs (including matrix.org's). It happens with 2 or 3 participants. However, it only started a couple days ago. We were using that video room for months without serious issues, and also with the (now) affected participant. The issue started at around the time when Element Call was embedded into Element.
I told everyone to check for latest versions of clients. And at least from participant C I got confirmation he was running 1.11.96 (latest).
We never checked video, we're only using audio. The avatar image that is replacing the video was in general only showing a capital letter, despite us all having set up an image. I was told on #webrtc that this is a known limitation. **However, the avatar image of affected participant B was behaving strange, it was only shown as a "B&W YouTube" icon (see screenshot below) for quite a while before it finally was shown as a capital letter.
I will try to provide as many logs as I can.
Outcome
see above
Operating system
No response
Browser information
No response
URL for webapp
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: