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

  • 1
  • Problem
  • Updated 7 months ago
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.





Photo of Birgit Aun

Birgit Aun

  • 8 Posts
  • 3 Reply Likes

Posted 7 months ago

  • 1
Photo of Robert Frost

Robert Frost

  • 406 Posts
  • 63 Reply Likes
I think you need to check 'Treatment and Profile' in the settings dialog as well as sharpening and noise
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
I see no reason why you would need to check 'treatment and profile' if you only want to save noise reduction and sharpening.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
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)...
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
Tested it, and on my Mac I do not have to check 'treatment and profile'.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
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.
(Edited)
Photo of Birgit Aun

Birgit Aun

  • 8 Posts
  • 3 Reply Likes
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".
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
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).
(Edited)
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
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.
Photo of Robert Somrak

Robert Somrak, Champion

  • 205 Posts
  • 57 Reply Likes
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.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
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).
Photo of Robert Somrak

Robert Somrak, Champion

  • 205 Posts
  • 57 Reply Likes
When I name files I try to remember to use the "old" DOS rules of illegal characters and avoid these kind of problems.  
Photo of Birgit Aun

Birgit Aun

  • 8 Posts
  • 3 Reply Likes
No, I didn't do a rename to neither of the presets I have working right now. They worked right off the bat and didn't cause any issues. The colon gets transformed to "-" in explorer viewle with some other process. Visible name with colon  is contained in the xml.
(Edited)
Photo of Birgit Aun

Birgit Aun

  • 8 Posts
  • 3 Reply Likes
Hmm but doing the same thing for sharpen without the colon does indeed work. Weird how I didn't get any issues with the first preset..
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1600 Posts
  • 648 Reply Likes
Well, whatever you did or didn’t, that “B” file is an indication of what went really wrong. You should be able to create a preset with sharpening and noise reduction only. There is no need to check ‘treatment and profile’ (that would be a bug, because that would mean that your preset also resets the profile) and there should be no need to add another adjustment and then remove that again.

Update: I see your last comment overlapped mine. When you created the first preset, you also created the group. Maybe that made the difference.
(Edited)