Skip to main content
Adobe Photoshop Family

9 Messages

 • 

238 Points

Sun, May 6, 2018 7:16 AM

Cannot create sharpening & noise reduction preset (Lightroom Classic v 7.3.1, Windows 10)

Hi!

I made a new group for develop presets (#2018) and I was able to save a new fresh preset there. However, I can't make another one with sharpen/noise settings.

I did try turning it off and on again! Please see images attached.





Responses

438 Messages

 • 

6.5K Points

2 years ago

I think you need to check 'Treatment and Profile' in the settings dialog as well as sharpening and noise

Champion

 • 

3.1K Messages

 • 

55.9K Points

I see no reason why you would need to check 'treatment and profile' if you only want to save noise reduction and sharpening.

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

3.1K Messages

 • 

55.9K Points

Well, may it is needed after all! See the remark of the OP further. She checked 'Saturation', but that automatically checks 'treatment and profile' as well, if I'm not mistaken. Strange (I would call this a bug)...

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

3.1K Messages

 • 

55.9K Points

Tested it, and on my Mac I do not have to check 'treatment and profile'.

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

3.1K Messages

 • 

55.9K Points

2 years ago

Don't use a colon in the name of the preset. The name of a file can't have a colon, because that is a the separator for folders as well and so it's an illegal character for file names.

When you created the first preset the colon was automatically changed to a '-' (probably because a group had to be created as well), but now it results in a file called 'B' and no extension.

Johan W. Elzenga,

http://www.johanfoto.com

9 Messages

 • 

238 Points

That's not at all what's causing the issue.

A workaround was to use any other checkbox, I think I used "saturation", and then save it. It worked. To get rid of the saturation setting, I selected to update the preset and then pushed "ok".

Champion

 • 

3.1K Messages

 • 

55.9K Points

Really? The screenshot clearly showed a file without extension with the name 'B'.

Checking 'Saturation' also checks 'treatment and profile', so maybe that was the correct solution after all (although I would regard that as a bug).

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

3.1K Messages

 • 

55.9K Points

I did a little test. I don't have a Windows system to test this on, but on my Mac I can save a sharpen en noise reduction preset just fine. I don't have to check 'treatment and profile' and I don't have to use some work around of checking something else as well and then update the preset later.

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

745 Messages

 • 

13.3K Points

The colon only causes a problem during the CREATION of a preset.  Strangely you can right-click a preset and use "Rename" and can change a character to a colon.  I see the OP already has a preset with a colon so they must have done a rename.

Champion

 • 

3.1K Messages

 • 

55.9K Points

Yes, that was my thought too. The screenshot clearly shows that the colon resulted in a file called 'B' without an .XMP extension, so I still think that's what caused this.

I think you're right that the OP probably renamed that other preset. Renaming a preset will also change the name field inside the XMP file, so if you use a colon, Lightroom will use that colon for the internal name (and that's the one you see in Lightroom), but it will use a dash in the file name because a colon is an illegal character (and that is what the screenshot shows).

Johan W. Elzenga,

http://www.johanfoto.com