we’re developing our own client on top of lib-jitsi-meet, JVB, etc.
What we’re seeing is that, if, for instance, you have clients A,B,C in a jitsi room, occasionally, A will freeze for B but not C. B also receives a track mute event in that case (the actual MediaTrack, not JitsiTrack). B will continue to receive C’s video with no issues
The track will usually emit an unmute event and resume after some time (anything from some milliseconds to more than a minute).
We’re trying to figure out what is causing this or how to mitigate it. Our understanding is that JVB sends the same media to all clients connected to the same room. Is this correct or is there a chance that JVB freezes a track if a client (B in this case) has low connectivity?
Also, is there a way to restart the remote stream for the receiving client, if the freeze goes on for too long? That is, without re-joining the room and so having to restart the incoming video from C.