-
Notifications
You must be signed in to change notification settings - Fork 334
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
BUG: --orientation (rotation) option behaves differently on different displays #467
Comments
Are both displays connected through HDMI? |
Yes, both are connected through HDMI. |
Pi3 won't make a difference. Can you confirm that with the same Pi2 and the same sdcard, running the same omxplayer command that the two displays behave differently with the rotate option? |
Yes. That was the same Pi. |
Can you add to config.txt:
and check it boots on both displays. That should force both displays to 1024x768. |
Sorry for late response. I also checked on another FullHD display (other than my DELL) and there there is still a problem with rotation (90 and 270 add mirror as described in my first post here) |
What do you have gpu_mem set to? |
Yes. You we're right. |
Hello,
I'm using omxplayer (version below, currently 4 commits behind master) and I would like to use
--orientation
argument to rotate the displayed video, but I've noticed that on 2 displays I have tested this argument behaves differently.On one display which is
1024x768
it rotates properly (--orientation 90
rotates 90 degrees, 0, 180 and 270 are also rotated correctly).On another display which is DELL display with
1920x1080
resolution the result is following:--orientation 0
displays normal video (OK)--orientation 90
rotates video 180 degrees and mirrors the output (WRONG)--orientation 180
displays video rotated 180 degrees (OK)--orientation 270
displays mirrored video (WRONG)Has anybody else noticed such a behaviour?
Is this a bug?
Is this issue/request related?
How can I rotate video on second display properly?
omxplayer --version
:The text was updated successfully, but these errors were encountered: