Sparse intra only decode #991
Open
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
…seeking Don't touch the initialization, metadata or audio code
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 fixes #986. It also brings the handling of rational numbers more in line with how ffmpeg does things, avoiding the use of floating point timestamp calculations.
With this change, if the output fps is lower than the source fps and the source is intra-only, then only packets that are actually necessary to decode are sent to the decoder. Frame threading is still done as before. This is most dramatic when decoding expensive formats like JPEG2000. If the output fps is the same or higher than the source fps then the behavior is as before.