Skip to content
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

Grimblast on hyprland with a monitor scaling above 1 results in blurry screenshots #69

Open
IceDBorn opened this issue Nov 10, 2023 · 12 comments
Assignees

Comments

@IceDBorn
Copy link

Screenshot with scaling set to 1

image

Screenshot with scaling set to 1.15

image

@fufexan
Copy link
Member

fufexan commented Nov 10, 2023

I think that's the application not properly supporting the fractional scaling protocol, and being blurred itself.

@IceDBorn
Copy link
Author

Nope, the app was crystal clear upon screenshotting. I even used a magnifier app to replicate the screenshot and it was like the first screenshot where the scaling is set to 1.

@ZerdoX-x
Copy link

@IceDBorn by the way, do you have --freeze option on? 99% of blurriness i get is from this option.

@IceDBorn
Copy link
Author

I use the option, but I do not get any blurriness with it when the scaling is set to 1.

@ZerdoX-x
Copy link

let me put the question differently. do you get less blurriness when scaling is >1 and screenshot is made without --freeze option?

@IceDBorn
Copy link
Author

Nope

@anotherwanwanyi
Copy link

I'm experiencing a similar issue.
I use a laptop connected to a monitor.
图片
As picture shows, my laptop screen scaling is set to 2, while the monitor scaling is set to 1.5.

It seems like the blur comes from the "--freeze" option.

eDP-1(Scaling 2) Screenshot with -f(--freeze):
图片

eDP-1(Scaling 2) Screenshot without -f(--freeze):
图片

HDMI-A-1(Scaling 1.5) Screenshot with -f(--freeze):
图片

HDMI-A-1(Scaling 1.5) Screenshot without -f(--freeze):
图片

The third and fourth images are both blurry, but the third one is blurrier. I suspect the blur in the fourth image is due to the 1.5x scaling, while the blur in the third one is also influenced by the --freeze option.

Another more intuitive way to verify this is to simply set the scaling to a non-integer value (e.g., 1.5) and bind the keys as follows:

bind = , Print,                     exec, grimblast -n -f copy area

Just press "Print" again and again, and the blur will overlap continuously.
However, using grimblast -n copy area won't cause that blur.

@fufexan
Copy link
Member

fufexan commented Feb 26, 2024

If it's the freeze option's fault, then hyprpicker is at fault. @vaxerski

@vaxerski
Copy link
Member

it's not hyprpicker, it's hyprland. On fs screenshots of an area are blurry. That's why freeze makes it more blurred, because blurring happens twice. (hyprpicker is 1, grim is 2)

@purrpurrn
Copy link

purrpurrn commented Apr 21, 2024

Why do hyprpicker and grim blur the image? I don't want any kind of blur :(

@decoded-satapathy
Copy link

I have expireinced the same issue, with scaling set to integer values (1, 2, 3....) I get a sharper screenshot, while with non integer scaling (1.25, 1.5 ...) I get visibly blurry screenshot

Screenshot with scaling set to 1.25
image

Screenshot with scaling set to 1
image

I haven't used the --freeze option.

@ZerdoX-x
Copy link

We already confirmed the issue:

it's not hyprpicker, it's hyprland. On fs screenshots of an area are blurry. That's why freeze makes it more blurred, because blurring happens twice. (hyprpicker is 1, grim is 2)

please do not bump with "me too"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants