Implement static preamble #43
Merged
Conversation
This file contains 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
onitake
force-pushed
the
feature/preamble
branch
3 times, most recently
from
a3ef9f9 to
cff078d
Compare
onitake
force-pushed
the
feature/preamble
branch
from
cff078d to
50a4926
Compare
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.
This is a hackish workaround for clients that can't manage to synchronize with a stream correctly when receiving packets in the middle of a unit, without getting the PAT and PMTs as well as H.264 SPS and PPS first.
It allows sending a static TS preamble with every client connection, that should allow immediate initialization of the decoder.
Warning: When sending a preamble that doesn't match the data follows, this can lead to even worse results.
Potential problems: