-
-
Notifications
You must be signed in to change notification settings - Fork 11
Slow for rotated monitors #7
Comments
I am not sure if this is it, but the image copy operation is very slow if the image width is not a multiple of 16. All standard resolutions are, but if you rotate, it is the height that must be divisible by 16. Is it? |
Thank you for the quick reply! Prompt:~$ xrandr -d :8 [removed irrelevant lines] DP-3 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm Just to be sure, I am running a 64 bit system, that does not change the 16? |
Is only the rotated one laggy? Is the DP-3 okay? If so, it's definitely not the problem I had in mind, as that one was the XShmGetImage being slow, and that would affect both displays. Also, if DP-3 is okay and only the rotated VGA-0 is laggy, it's likely not a problem of screenclone. |
Yes, only the rotated display is laggy (and without rotation everything is fine). Funny enough, after experimenting, I see that only actions like dragging a window with the mouse or resizing are (very) laggy. If e.g. an xterm scrolls with lots of information, that does not lag at all. To clarify: if I drag (with the mouse) a window so that both monitors show part of it, the non-rotated monitor shows smooth movements, and the rotated one does not update until I release the window or pause the movement. Without rotation, all is fine. |
That's seriously crazy. :-) |
Hi, and many thanks for programming and sharing this. Works great for my thinkpad, and
I can connect two external monitors without problems.
I can even set up the second monitor to be rotated: set mode size of virtual display to
the total needed resolution in xrandr, then rotate the second monitor using
xrandr -d :8 --output DP-3 --auto --output VGA-0 --auto --right-of DP-3 --rotate left
(xrandr -d :8 tells me there are two monitors connected at DP-3 (display port) and VGA-0)
Everything works very smooth if I do not rotate.
If I rotate, things are correct, but the rotated display is very laggy. I do not know why, perhaps
the damage events are not updated correctly?
Any input would be appreciated!
The text was updated successfully, but these errors were encountered: