10 ms·
Sorry about that! chrome://webrtc-internals should tell you the exact reason. My guess is packet loss and then it recovers on the keyframe. In the next day or
by Sean-Der 3y ago
Sorry about that!
chrome://webrtc-internals should tell you the exact reason. My guess is packet loss and then it recovers on the keyframe.
In the next day or two I am gonna open a PR to set NACK buffer properly. Right now it is too small :/
Sorry you are hitting issues. Will try my best to fix it up! Email me sean@pion.ly and would love to make sure we get it working 100%. I bet other users are hitting the same issues and not sharing.
- eminence32 3y agoThanks for your hint about chrome://webrtc-internals -- I'll see what that tells me!