Correct NOPT timestamps #440
Open
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
stronk-dev
force-pushed
the
md/feature/normalize_nopts
branch
from
835f194 to
25fd3c7
Compare
stronk-dev
force-pushed
the
md/feature/normalize_nopts
branch
from
25fd3c7 to
388556d
Compare
stronk-dev
force-pushed
the
md/feature/normalize_nopts
branch
from
8c22d13 to
02b95e3
Compare
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.
This PR:
AV_NOPTS_VALUEfor the decoded frame PTS, falls back to LibAV'sbest_effort_timestampor the last seen PTS + frame duration otherwise.This PR definitely needs more testing and code review, but is put up here for brave guinea pigs in advance.