Conversation
gwdp
marked this pull request as ready for review
September 17, 2026 18:21
gwdp
force-pushed
the
gwdp/webrtc-weak-link-tuning
branch
from
September 18, 2026 00:17
13da9c6 to
b45a5ea
Compare
gwdp
force-pushed
the
gwdp/h264-encode-level-cap
branch
2 times, most recently
from
September 21, 2026 18:04
f137306 to
f74215f
Compare
gwdp
force-pushed
the
gwdp/webrtc-weak-link-tuning
branch
from
September 21, 2026 18:04
b45a5ea to
a12d107
Compare
gwdp
force-pushed
the
gwdp/h264-encode-level-cap
branch
from
September 21, 2026 21:56
f74215f to
9af9441
Compare
gwdp
force-pushed
the
gwdp/webrtc-weak-link-tuning
branch
from
September 21, 2026 21:56
a12d107 to
09355e8
Compare
gwdp
force-pushed
the
gwdp/h264-encode-level-cap
branch
from
September 22, 2026 00:16
9af9441 to
4b43e82
Compare
gwdp
force-pushed
the
gwdp/webrtc-weak-link-tuning
branch
from
September 22, 2026 00:16
09355e8 to
70fe822
Compare
gwdp
force-pushed
the
gwdp/webrtc-weak-link-tuning
branch
from
September 22, 2026 01:03
70fe822 to
b17a8a5
Compare
gwdp
force-pushed
the
gwdp/h264-encode-level-cap
branch
from
September 22, 2026 01:03
4b43e82 to
97b2c20
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
minBitrateBpswas 90% of the target, so bandwidth estimation had nowhere to back off to on a path slower than the target. The encoder kept overshooting and the stream wedged.maintainFramerateholds frame rate by dropping resolution. A 1206-wide surface holds 60fps at 300x654, where UI text is unreadable.How
max(300 kbps, target / 10), never above the targetdegradationPreferencetobalancedTest Plan
dnctl: loss 58% -> 1.5%, rtt 420ms -> 125ms