Repository navigation
fix: normalize VideoFrame rotation to 0, 90, 180 or 270 - #457
Merged
Merged
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
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.
VideoFrame accepts any multiple of 90°, but the Swing and JavaFX views swap width and height only for exactly 90 or 270, so a frame with -90 or 450 was scaled wrongly and could be cut off.
The constructor now keeps the rotation as its equivalent in 0, 90, 180 or 270, so the views, the native decoder wrapper and applications only ever see those values. Both views get a test comparing -90 with 270 and 450 with 90.