Lightroom Mobile 4.2.1 (Android): can no longer view highlight/shadow clipping or sharpening masks

  • 1
  • Problem
  • Updated 4 months ago
  • Solved
Hello, 

On all previous versions of Lightroom Mobile for Android (Samsung Note 9), I could press and hold on the image while dragging the exposure, highlights, shadows, whites, blacks, or noise reduction sliders to get a preview of which areas were clipping (for the exposure controls) or which areas were masked (for sharpening masking.) I believe the details and radius sliders are also affected by this.

On the most recent version, instead of seeing the aforementioned previews, I am simply seeing the Image (Before) view, like I would see if I wasn't dragging any slider. This has definitely been introduced recently.

Apologies if this is a duplicate, but I was unable to find any other posts that mentioned this. Is it a known issue?

Best regards, 

Jay
Photo of Jay Wheeler

Jay Wheeler

  • 4 Posts
  • 0 Reply Likes

Posted 5 months ago

  • 1
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5593 Posts
  • 1182 Reply Likes
I just tested on a Galaxy Note 8 and it is is working for me.  Remember that you have to drag the slider with two fingers to see the hinting masks. 
Photo of Jay Wheeler

Jay Wheeler

  • 4 Posts
  • 0 Reply Likes
Thanks so much for your reply, Rikk.

The key thing that I didn't realize was that on the latest version, the second finger has to actually drag ON THE SLIDER ITSELF. On previous versions, hinting masks would appear if you were to drag a slider with one finger and then place a second finger ANYWHERE on the screen; this was quite a convenient means of accessing masks for various dexterity-related reasons and as such, was the habit that I had developed. The new version, while less lenient and somewhat more difficult to access, does indeed behave as you have described.

Thanks again for the clarification. On a side note, do you happen to know whether this change to a "more strict" enforcement driving the hinting mask behavior interface was actually an intentional one? As a programmer, this seems like the type of unintended side effect that could easily result from cleaning up the code behind some seemingly unrelated behavior, which was implemented without any intent of making the hinting masks somewhat less convenient to access.

Cheers,

Jay