Repository navigation
Conversation
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.
Video FEC: Reed-Solomon parity on its own datagram channel
Every lost video slice used to cost a whole frame, and every lost frame cost a keyframe. On links with random loss, that repair traffic limited the bitrate more than the link's capacity did. At 0.1% loss on the netem broadband profile, a session settled near 10 Mbps on a 50 Mbit link and sent 27 keyframes in 30 s.
This PR adds forward error correction. The host sends Reed-Solomon parity after each frame, and spectre rebuilds lost slices from it, with no keyframe and no round trip.