I haven’t seen the videobridge signaling pli/fir from the receiver at all (tried it with all rtcp strategies):
However the receiving side is sending them for sure (googPlisSent 415).
Also on jitsi-meet I can see this behaviour if you see onRemoveStream and later onAddStream being called, video is sometimes black for up to 100 seconds, also as expected because of chrome’s default key frame interval 3000. Means 3000f / 30fps = 100s.
2015-05-16 1:00 GMT+02:00 Philipp Hancke email@example.com:
Am 15.05.2015 um 15:13 schrieb Brian Baldino:
a=rtcp-fb:100 nack pli
here. Not sure what meet does these days but chrome has been explicitly signaling pli for about a year.
dev mailing list
Unsubscribe instructions and other list options:
Gave that a shot but still see the issue. From what I can tell, even in
working jitsi calls the same behavior (receive stream created before send
stream) seems to happen, so maybe this is an issue but something about the
way the jitsi meet client is written is working around it? Driving a key
frame in some other way, perhaps?
type: offer, sdp: v=0