P: Develop presets not sorting correctly

35 Votes
Explorer ,
Apr 03, 2018 Apr 03, 2018

Copy link to clipboard

Copied

TheyRackMultipart201804039331215qg-c8f7b329-4af5-42e3-ba14-bd44aef398bd-279039350.pngRackMultipart201804039331215qg-c8f7b329-4af5-42e3-ba14-bd44aef398bd-279039350.png used to be sorted alphabetically. In version 7.3 the order is random

Bug Fixed
TOPICS
macOS , Windows

Views

7

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Apr 05, 2018 Apr 05, 2018
We're investigating this issue. Thanks for reporting.

Votes

Translate

Translate
replies 123 Replies 123
123 Comments
Adobe Community Professional ,
Apr 03, 2018 Apr 03, 2018

Copy link to clipboard

Copied

Yes, this is an old problem with MacOS X High Sierra, which unfortunately has returned. Adobe is aware of it and working on a fix.
-- Johan W. Elzenga

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Apr 03, 2018 Apr 03, 2018

Copy link to clipboard

Copied

Hi John, I referenced this in your PR bug. Thanks.

Senior Product Manager - Customer Advocacy - Digital Imaging

Votes

Translate

Translate

Report

Report
New Here ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

I also have the sorting issue using Mac OS 10.12.6

Votes

Translate

Translate

Report

Report
New Here ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

Renaming every preset in a given group and then returning them to their original name will fix the sorting, although this is not ideal for those of us with hundreds of presets.

Votes

Translate

Translate

Report

Report
Adobe Community Professional ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

But are they still sorted after a restart? This is an older bug that returned, and with the old bug you could force a correct sort order by adding a new presets. But after a restart the sort order was once again broken. I'm typing this on my iPad, so I can't check it myself.
-- Johan W. Elzenga

Votes

Translate

Translate

Report

Report
New Here ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

Same issue, Windows 10.

Votes

Translate

Translate

Report

Report
New Here ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

Renaming presets doesn't move them in the sorting order for me. They simply remain sorted in the same (unorganized) place. Windows 10.

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

Same for me using Windows 10 - would have hoped this release was tested first!

Votes

Translate

Translate

Report

Report
Community Beginner ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

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:

RackMultipart20180404998481hqo-0f0cf693-14e9-4691-a3da-bca8c8283670-25307344.png


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...

RackMultipart20180404542081mnc-c71dc0fd-b754-46f3-8b7f-c192b14d1bad-1720890488.png

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...

RackMultipart2018040426340t4wd-538d5155-ba21-4ad6-ac12-748c5a42ae7e-1940074241.png

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...

Votes

Translate

Translate

Report

Report
New Here ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

I have the problem on both MAC OS X Sierra and El Capitan

Votes

Translate

Translate

Report

Report
New Here ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

Great work, but are you really gonna correct all your presets by editing the metadata?  It would take me days I think...

Votes

Translate

Translate

Report

Report
Community Beginner ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

I'll edit the ones I make and send out updates to everyone who has bought my presets... but yeah, not gonna update every preset in my library... hopefully Adobe will solve?

Votes

Translate

Translate

Report

Report
Community Beginner ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

Hi Johan, see my response below. Not a problem with High Sierra... problem is with .lrtemplate to .xmp conversion.

Votes

Translate

Translate

Report

Report
New Here ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

This is excellent work, and at the very least will help Adobe narrow down a solution. Thanks for sharing!

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 04, 2018 Apr 04, 2018

Copy link to clipboard

Copied

Same here.

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

Same here on Win10  - ‎Shai Bachar‎ to Adobe Photoshop LightroomYesterday at 1:12am · 
NEW update NEW PROBLEMS. Hi Adobe. now what? new updated ruined the order of my presets and it's all mess now. instead of improving your slowing Classic CC, you're adding unnecessary presets of your own. I've never thought I'd consider working with other application. RackMultipart20180405401071wa6-f23e0c05-96a9-46f6-b19b-9fb67e561389-1637399480.pngYou're making me think it's time to do so... 1f641-3ab91626-e0cc-4653-808f-99b7d16dd4a5-1223080697.png😞

Votes

Translate

Translate

Report

Report
Adobe Community Professional ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

Since xmp files are plain text, this could be fixed with a script in a text editor or something like Perl. I don't use presets so it isn't a problem for me, just saying.

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

for the meanwhile, I rolled back to an earlier version. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

We're investigating this issue. Thanks for reporting.

Senior Product Manager - Customer Advocacy - Digital Imaging

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

Dear Adobe - based on the above, it appears this is an Adobe created problem.  You have a LOT of preset developers scrambling.  Please provide a fix asap.  It should be much easier on your end - based on the info provided by Nathan Johnson above - on what needs to be done.

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

I hope we get a fix soon, being a heavy user of Mastin Labs and VSCO Presets for my workflow it has disrupted my delivery to clients. I reached out to VSCO and Mastin Labs customer support who are aware of the issue but have little control on their side for a fix. What Nathan has highlighted seems to be correct and hopefully this helps Adobe release an update soon. Till then I have uninstalled Lightroom and re-installed and will not install my presets till there is a Lightroom update. Not going through the tiresome process of cleaning/renaming Presets directories. 

Votes

Translate

Translate

Report

Report
New Here ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

RackMultipart2018040594587ddoa-f0b48967-3ee5-46cf-af2b-4e7c4c49e9f3-38681020.jpg
...Oh, this is going to be SO MUCH FUN!!! THANKS ADOBE!

Votes

Translate

Translate

Report

Report
New Here ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

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++?)

Votes

Translate

Translate

Report

Report
New Here ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

To be fair Mastin and VSCO could offer updated presets which would sort correctly in the new version of LR if they wanted to.  They probably hope that Adobe issue a fix sooner.  Either way, this update is incredibly frustrating.  Personally, I have reverted to v7.2 and I will stick with it until the problem is resolved.

Votes

Translate

Translate

Report

Report
New Here ,
Apr 05, 2018 Apr 05, 2018

Copy link to clipboard

Copied

so absolutely frustrated.. i have purchased and made hundreds of presets over the years.. now... with the update.. they are not only all over the place.. but half of them can't be imported.. frustrated.. need a fix... 

Votes

Translate

Translate

Report

Report