Lightroom Classic 7.3: Develop presets not sorting correctly

  • 35
  • Problem
  • Updated 5 months ago
  • Solved
  • (Edited)
They used to be sorted alphabetically. In version 7.3 the order is random
Photo of Winston Mitchell

Winston Mitchell

  • 25 Posts
  • 1 Reply Like

Posted 2 years ago

  • 35
Photo of Nathan Johnson

Nathan Johnson

  • 26 Posts
  • 22 Reply Likes
OK - I think I've solved this little mystery... it doesn't have anything to do with High Sierra (it's happening to me on El Capitan) BUT with the XMP presets conversion (and differences in convention between the .lrtemplate files and the .xmp files). 

Inside an .lrtemplate file, there are two name properties... "internalName" and "title"... when you initially create a preset file, they are both the same. But it is possible for the "title" to become different than the "internalName" (especially for preset developers who are editing .lrtemplate files directly). 

Example of .lrtemplate file:




So here, I must have changed the title directly in a text editor.

In any case, this didn't matter, because ALL PREVIOUS VERSIONS OF LIGHTROOM only looked at the "title" property to determine how to sort presets.

Enter LR Classic 7.3 and the .xmp conversion...

XMP also has a number of properties related to the name of the preset. The "Name" property is the displayed name...

BUT... XMP has a "SortName" property. And this property determines how Lightroom actually sorts the presets.

When LR 7.3 converted .lrtemplate files to .xmp files, it took the "internalName" and placed it in the "SortName" property... 

Example...



AND unlike all previous lightroom versions, the .xmp presets actually do get sorted by the sortName property... 

So now, inside Lightroom Classic, you see presets that are mostly sorted, but with seemingly random deviations from that sorting...



All that to say, I wish that Adobe hadn't assumed that we wanted the internalName to now be used a sorting device (which it never had been before). But I don't think it is cool that now we have the ability to do custom orders without changing the display name!

Now... I've got a lot of presets to update...
Photo of Matthew Baldon

Matthew Baldon

  • 4 Posts
  • 1 Reply Like
I hope Adobe can solve this with an update, but since the file name / sort name discrepancy is already baked into the .XMP file itself, I'm not sure how Adobe could fix the problem with a Lightroom update itself.

On that note, can anybody figure out how to do this in KomodoEdit? (Notepad++?)
Photo of Nathan Johnson

Nathan Johnson

  • 26 Posts
  • 22 Reply Likes
So... I got tired of updating presets manually, so I went ahead and built a bash script for Mac users that fixes sorting automatically...

Tested with around 1,000 presets on OS X El Capitan... took about 10 seconds for the script to go through all of them, restarted Lightroom Classic 7.3, and everything is ordered just like it was. :)

Just put the script and instructions to use up for free on my website. http://natephotographic.com/lightroom-classic-7-3-presets-sorted-wrong-order/

Really curious to hear how it works for other (especially Sierra and High Sierra folks)?
Photo of Nathan Johnson

Nathan Johnson

  • 26 Posts
  • 22 Reply Likes
So... I got tired of updating presets manually, so I went ahead and built a bash script for Mac users that fixes sorting automatically...

Tested with around 1,000 presets on OS X El Capitan... took about 10 seconds for the script to go through all of them, restarted Lightroom Classic 7.3, and everything is ordered just like it was. :)

Just put the script and instructions to use up for free on my website. http://natephotographic.com/lightroom-classic-7-3-presets-sorted-wrong-order/

Really curious to hear how it works for other (especially Sierra and High Sierra folks)?
Photo of Seth Carnill

Seth Carnill

  • 33 Posts
  • 3 Reply Likes
Wow Nathan, great work and thanks alot for sharing!  
I notice that the script works on the original .lrtemplate files, and then LR Classic will re-convert them into the xml format.  My question is - what happens to the presets that have already been converted?
Photo of Nathan Johnson

Nathan Johnson

  • 26 Posts
  • 22 Reply Likes
You're welcome!

OK - so removing the ~ from the .lrdevelop file causes it to overwrite the equivalently named .xmp file when it is re-converted.

The script I wrote will only do this in cases where there is found to be a mismatch between the "internalName" and the "title". So it should only overwrite the .xmp files where there was a mismatch. This should help at least limit issues caused by conversion, or accidentally overwriting a .xmp file you have changed. That said, if you've made a lot of changes to the .xmp files directly, probably a good idea to backup before using the script.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15633 Posts
  • 2369 Reply Likes
Official Response
We're investigating this issue. Thanks for reporting.
Photo of Aimee Giese

Aimee Giese

  • 4 Posts
  • 9 Reply Likes
I will chime in too that I have purchased many presets and spent hours organizing them so they appear above the defaults, using = and 1,2,3 to flow in a way that is fast for me. This is a major cramp in my editing time to search around for the ones I want. Please fix asap, Adobe.
Photo of Aimee Giese

Aimee Giese

  • 4 Posts
  • 9 Reply Likes
While you are at it - make it so we can delete the defaults ;)
Photo of Nathan Johnson

Nathan Johnson

  • 25 Posts
  • 22 Reply Likes
Here's  a little trick... You can delete all the default "classic" folders, which makes it at least a little more usable.

On Mac, right-click on the Lightroom CC Classic (inside the Lightroom CC Classic folder, in your Application folder). And select "Show Package Contents"




Navigate to "Contents > Resources > Settings" and then delete the "Classic"  folder





Restart Lightroom CC Classic, and BOOM! No more of those annoying Classic folders!




There. That looks a little better.

I haven't been able to get the other defaults off... even after deleting them, they still persist.  It's like trying to delete Internet Explorer off of Windows...

Hope that helps!
-Nate
Photo of Don Risi

Don Risi

  • 6 Posts
  • 1 Reply Like
Yeah, I deleted them, did a search for one of them (just to see if it was still anywhere on the system), and rebooted.  They're still there and still functioning.  Very frustrating.