Lightroom: Not displaying feather mask correctly

  • 2
  • Problem
  • Updated 3 years ago
  • (Edited)
Merged

This conversation has been merged. Please reference the main conversation: Photoshop: Non-destructive blur for masking doesn't save correctly anymore

Lightroom (CC 2015.4) does not preview the TIFF (or PSD) correctly when feathering is used on layer masks.

The shot at the top is in Photoshop (CC 2015.1.2) with a feather adjustment layer to create the eye shadow and below is how the TIFF looks in Lightroom. It also exports exactly the same and has caused a major issue when I've exported all my edits only to find the images I've sent to clients do not look as expected. My only option it seems at the moment is to create a merged copy layer before saving the image.

Photo of Terry King

Terry King

  • 2 Posts
  • 1 Reply Like
  • frustrated

Posted 3 years ago

  • 2
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15462 Posts
  • 2292 Reply Likes
Can you provide the source tiff I could use to see how the document/settings are constructed? (share via Creative Cloud or dropbox URL?)
Photo of gmaingret

gmaingret

  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Mask Feather in tiff are not handled in Lightoom.

I used to use mask feather instead gaussian blur on mask feather, I find it much more comfortable.
I noticed with the latest photoshop and lightoom that some mask feather are not handled in LR once the tiff is saved. I didn't try with a psd file.

Open a photo from your LR catalog
Add an adjustment layer like Curves and move the curve wherever you want
Paint on the mask with a hard brush
Move the Feather slider to about 150px for a 24MPx picture.
Save it and go back to LR

In LR, I notice that the area I painted on the mask is not blurred. As if I let the feather slider to 0.
Besides, if I use a real gaussian blur on my mask instead of the feather, this issue doesn't appear. So it is really a mask feather issue.

This conversation is no longer open for comments or replies.