fix(janus): Set playoutDelayHint=0 for Chrome to fix 1 FPS slowlink issue #204
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the 1 FPS WebRTC H.264 streaming issue on Chrome/Blink browsers after the uStreamer 6.47 update.
Problem
After upgrading to v4.144, Chrome browsers experience:
Related issue: #1632
Root Cause
Chrome's H.264 decoder doesn't handle uStreamer 6.47's new FPS limiter frame pacing well, causing RTCP feedback delays that trigger Janus slowlink detection.
Solution
Set
playoutDelayHint=0on video receivers for Chrome/Blink browsers when adding video tracks. This is similar to the existing Firefox workaround for playout-delay issues.The
playoutDelayHintproperty was already used in a commented-out block (removed in the refactoring commitac0eee9f), but only for all browsers. This PR applies it specifically to Chrome/Blink where it's needed.Changes
playoutDelayHint=0on video receivers to reduce latency and fix frame timingTesting
This fix should: