-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification of ProjectionPoseRoll direction #822
Comments
Yes Not sure what a more mathematical unambiguous term could be. |
@Nevcairiel @v0lt Do you agree to implement this change in your projects? I will handle the update for mpv, but I'd like to synchronize with you both to ensure we make these changes around the same time. This coordination will help prevent confusion among users. EDIT: Since the mpv 0.38 release is around the corner we decided to pull it in before. So there is that for waiting on others... |
I would like to see 2 MKV reference samples rotated by +90 and -90 degrees. A good sample would be a vertical video shot on a regular smartphone and converted to MKV. |
These samples are bad because all files have the same video stream, which looks correct when nothing is rotated. I'd like to see reference samples that only look right after rotation. A good example is a video shot on a smartphone (when the sky is above and the grass is below). |
It's unclear what is meant by the "forward vector" in the ProjectionPoseRoll element documentation (https://www.matroska.org/technical/elements.html#ProjectionPoseRoll). As a result, some players rotate clockwise and some rotate counter-clockwise.
It is stated unambiguously in the specification notes (https://www.matroska.org/technical/notes.html#rotation) that the correct video display rotation direction for a positive ProjectionPoseRoll value is counter-clockwise. I wanted to confirm that that was the case: ProjectionPoseRoll=90 should cause the video to be rotated 90 degrees counter-clockwise during playback.
See also mpv-player/mpv#13830.
The text was updated successfully, but these errors were encountered: