4 ms·

Thanks for all your work getting this PR merged! I've been trying it out for a while now (streaming to a self-hosted broadcast-box), and almost everyone who vi

Thanks for all your work getting this PR merged! I've been trying it out for a while now (streaming to a self-hosted broadcast-box), and almost everyone who views the stream says that the video will freeze for 1 to 2 seconds every now and again (every few minutes). Audio is uninterrupted. Any hints about how I can debug this?

doctorpangloss 3y ago
In my opinion, moderate your expectations of non-libwebrtc implementations like the one used in this feature. Here's some speculation: Most users will experience non-libwebrtc WebRTC bugs (like OBS users). 1% of users who experience bugs in OBS WebRTC will report enough telemetry to fix the bug. But 99% of all of OBS's userbase uses Chrome, Edge or Safari, and maybe 50% of those (more than enough) report telemetry. So if their WebRTC bug was hardware / network specific - the bugs that matter - libwebrtc will have observed it and by now, probably fixed it. Despite telemetry from hundreds of millions of users every day, it still took years for libwebrtc to reach truly robust, flawless stability on all the platforms it deploys on. It's a complex technology.
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 ago
  Thanks for your hint about chrome://webrtc-internals -- I'll see what that tells me!
wisdow 3y ago
Been experiencing the same issue. I tried to figure what causes this but without success. If you have any idea i'm down to discuss about it.

doctorpangloss 3y ago

In my opinion, moderate your expectations of non-libwebrtc implementations like the one used in this feature. Here's some speculation: Most users will experience non-libwebrtc WebRTC bugs (like OBS users). 1% of users who experience bugs in OBS WebRTC will report enough telemetry to fix the bug. But 99% of all of OBS's userbase uses Chrome, Edge or Safari, and maybe 50% of those (more than enough) report telemetry. So if their WebRTC bug was hardware / network specific - the bugs that matter - libwebrtc will have observed it and by now, probably fixed it. Despite telemetry from hundreds of millions of users every day, it still took years for libwebrtc to reach truly robust, flawless stability on all the platforms it deploys on. It's a complex technology.

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 ago
Thanks for your hint about chrome://webrtc-internals -- I'll see what that tells me!

wisdow 3y ago

Been experiencing the same issue. I tried to figure what causes this but without success. If you have any idea i'm down to discuss about it.