I have only encountered this in very rare cases, but sometimes the received video cannot be played.
Some of them are receiving multiple videos from the same source with the same Transport and are being received successfully at the same time.
Checking the status of inbound-rtp, I found that framesReceived remained at 0 and did not increase, and retransmittedBytesReceived and bytesReceived had the same value.
Does anyone have any advice on what I should look into next?
Isn’t it strange that the received numbers are growing rather smoothly while the rates are showing as 0? Something seems to be wrong in the calculations.
It is interesting to note that the server was outputting the following logs near the time of the problem.
[2024-01-18T00:04:06Z WARN mediasoup::worker] [id:0611cce4-c14c-4408-a957-086cc0f1933f] RTC::RtpStream::UpdateSeq() | bad sequence number, ignoring packet [ssrc:3004310925, seq:6982]
[2024-01-18T00:04:06Z WARN mediasoup::worker] [id:0611cce4-c14c-4408-a957-086cc0f1933f] RTC::RtpStreamRecv::ReceiveRtxPacket() | invalid RTX packet [ssrc:3004310925, seq:6982]
https://chromium.googlesource.com/external/webrtc/+/d440358ccaeb9aa5dc4a50c0c37638416a15cac5^!/
This may have been fixed in Chromium.
I have researched to work around this problem that only occurs in Chrome and found that I can work around it by enabling paused at consume and resuming after the Consumer is created on the browser side.
Hope this helps if anyone else is encountering the same problem.