Additional fixes for FFmpeg 3.1+#14188
Merged
hrydgard merged 3 commits intohrydgard:masterfrom Feb 21, 2021
Merged
Conversation
FFmpeg 3.1+ reads the frame rate only into private data, and can only expose it publicly when using the find stream info API that reads too far ahead.
Closed
2 tasks
5 tasks
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
2 participants
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.
Noticed an issue with bad frames in certain Valkyrie Profile videos, because it was sending 0 size packets switching to flush mode. Really, we should flush - but it's tricky because we never know when the frame is actually ending. One of the tricky things about using the FFmpeg decoder APIs for this.
Also somehow forgot to pull over the sceAtrac changes, was working on another branch with vcxproj updates for FFmpeg 4.3.
Lastly added a workaround for #11490.
-[Unknown]