You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I set scaling to 2.4, on both 4k and 1920x1200 displays, when I ask for dmabuf screen capture, the DMABUF region is two pixels too small in both directions. This is visible in the vvv.txt attached to russelltg/wl-screenrec#41 (comment):
This then later causes issue in my application because I crop it to regions calculated from scaling, so it causes error when the copped region is larger than the full screen!
Works in sway.
How to reproduce
Set scaling to 2.4
Do dmabuf capture. A way to do this is with my screenrecorder. -vvv logs all wayland events.
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered:
russelltg
changed the title
Dmabuf capture reports the incorrect size when using weird scaling settings
Dmabuf capture region has incorrect size when using weird scaling settings
Mar 6, 2024
Hyprland Version
System/Version info
Bug or Regression?
Bug
Description
Reported initially at russelltg/wl-screenrec#64, but reproduced by me as well
When I set scaling to 2.4, on both 4k and 1920x1200 displays, when I ask for dmabuf screen capture, the DMABUF region is two pixels too small in both directions. This is visible in the vvv.txt attached to russelltg/wl-screenrec#41 (comment):
This then later causes issue in my application because I crop it to regions calculated from scaling, so it causes error when the copped region is larger than the full screen!
Works in sway.
How to reproduce
Set scaling to 2.4
Do dmabuf capture. A way to do this is with my screenrecorder.
-vvv
logs all wayland events.Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: