Inspiring

P: White balance dropper target location is offset on high-DPI Windows devices

Forum|Forum|9 years ago
August 15, 2016
54 replies
3266 views

There appears to be a bug affecting all recent versions of Lightroom on high-DPI Windows devices. It affects both CC and standalone versions, up to and including the current version (2015.6.1).

The issue is that when using the white balance dropper tool in the Develop module, the target location Lightroom uses does not correspond exactly to where the point of the dropper is located. Specifically, it seems to reference a position about 5 or 6 millimetres above the point of the tool.

The issue also affects the manual defringe dropper in the Lens Corrections panel. Other local develop tools seem not to be affected (brush, spot healing, HSL/Color/B&W picker, etc.).

To be clear: the issue affects Lightroom when the device is used in standard desktop mode with a regular mouse as the pointing device. It is not an issue with the touch screen, the pen or Lightroom's touch mode.

The problem is described in detail with screenshots here (in the original post and in my reply):
https://forums.adobe.com/message/8942657

It's also discussed briefly here:
https://www.reddit.com/r/Lightroom/comments/4wlf4i/lightroom_dropper_bug_on_surface_pro/

Windows

This topic has been closed for replies.

Show previous replies

R

rayv56912865

Participating Frequently

For the map issues I have been able to resolve by using the windows setting to control the Font Sizes and then setting LR Font Size setting to Auto (before it was set to a % value and I had problems).
Also the <CNTL-left Click> or just the <right click> were fine workarounds for the map module.

I has not solved the White Balance Eye dropper issue (and the other Targeted Adjustment tools (eg HSL) are also off but by a very small amount which I can live with.)

A

Arnie47

Known Participant

There are several issues about the mouse cursor Position being incorrectly handled (see also map module problems and problems with the alignment of the horizon and alignment tools).
Some discussion threads recommend to change the LR fonts setting to a certain value others (like this one) to choose a certain windows monitor scaling option.

Somehow one has the impression that LR somehow guesses where the mouse pointer could be...
In some functionalities (spot removal, etc.) it works correctly independent of any font sizes and monitor scaling options, in other tools it always makes troubles finding the right position.

Adobe, please unify this mouse readings by implementing it clean together for all tools!
Having bugs like this for years doesn't meet professional standards!

Bob Somrak

Legend

I agree this should be fixed. Its been around for a LONG time. You shouldn't have to mess with your scaling to make it work.

M4 Pro Mac Mini. 48GB

croucrou.com

Participating Frequently

the dropper works in photoshop and in caméra Raw, so adobe could do it

johnrellis

Genius

Here's an article that starts with the assumption of "typical" visual acuity rather than "maximum" but comes to the same conclusion:

4K Monitors: Can you actually see the difference?

"If you have average vision (which as we stated earlier is actually around 20/15 for a healthy adult), you would ideally want a 4K monitor at anything above a 14" screen size. This means that from a 14" laptop on up, the average healthy adult would ideally want to have a 4K screen. At the same time, unless you have 20/10 vision there should be no need for anything above a 4K screen on a laptop - so at least in terms of resolution a 4K screen is likely all laptops will ever need."

C

ChrigelKarrer

Inspiring

All other Windows Graphic programs don't show this misbehaviour on my 17'' Lenovo running at 3840x2160. I use my display for whatever application, from high-end games, architectural renderings, photo and video editing and i have no problem with any of the software i use.
In my house i have a Dell 27'' 4K Monitor and the same problem occurs, either in single monitor or twin monitor configuration, the damned eyedropper is offset.
This is definitively a problem of Lightroom for Windows and not of Windows as all other software works just fine without any offsets.
It is also unacceptable that Adobe ignore this problem, at least they could explain why they are not able to correct that.
On the end i cancelled all my Adobe subscriptions use now Capture One and it works just fine and no offset at any imaginable resolution.

F

Fishweasel

Inspiring

I don’t believe anyone is arguing it works in the native display. Many of us, however, need to increase the scaling due to eyesight challenges. This is not a just a Windows issue since it works with other programs. It’s Lightroom’s interaction with Windows - blame whoever you want for this issues but it was never a problem with Lightroom with 1080P resolution.

C

COBill

Known Participant

I can't argue with the math but from an optical engineer I met several years ago, he gave the following limits to the resolution of the eye-brain system. To see a difference, one must be closer than:

1.5 times the diagonal for 720
1 times the diagonal for FHD
50% of the diagonal for 4K

This would be 8.5" for your 17" 4K display. I've examine monitors in stores and my experience indicates that he is correct. I certainly support that with my 27" & 32" 4K monitors.

johnrellis

Genius

"4K resolution is meaningless on a 17" display, the human eye cannot see the difference unless it is within a couple of inches."

Hmm, can you cite a reference for that? My rusty trigonometry indicates otherwise.

According to this Wikipedia article, "The maximum angular resolution of the human eye is 28 arc seconds. ... For a pixel pair (one white and one black pixel) this gives a pixel density of 128 pixels per degree (PPD)." My calculations show that, viewing a screen at a distance of 15", 128 pixels/degree translates to 488 pixels/inch.

The Lenovo P73 UDH screen is about 3840 pixels and 15.5" wide, for a resolution of 247 pixels/inch, about half than the maximum the human eye can distinguish. That doesn't seem meaningless to me...