Closed danstiner closed 3 years ago
Tested locally on edge and ingest nodes. I see about 0.6% dropped frames and I'm not sure why. Will test if I see the same an older commit but I suspect I will. (webrtc-internals says 0 nacks, but 30+ picture loss indicators so it might even be an issue on the decoding side)
Tested locally on edge and ingest nodes. I see about 0.6% dropped frames and I'm not sure why. Will test if I see the same an older commit but I suspect I will. (webrtc-internals says 0 nacks, but 30+ picture loss indicators so it might even be an issue on the decoding side)
Possible you're running into #101? If you're only seeing freezes and not actual packet loss.
Going back and doing ebefe001a1f6a42cac2c1c8f7cf59db18fe50897 the right way this time.
This shortens the path for RTP packets to only require a single lock at the stream level.