Bugfix: fix Ogg packets spanning multiple pages#6
Merged
Conversation
kahrendt
added
bug
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
1 participant
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.
When an Ogg packet spans multiple pages, the demuxer is supposed to buffer the contents of the packet on the first page internally. When the following pages arrive, it should be concatenated in the internal buffer until it is complete.
This fixes a bug where the zero-copy path would be activated on the final Ogg page that has the end of the packet, which would completely ignore the contents in the internal buffer that the demuxer was assembling.