Also, why are the default folders always stuck on the top? This is highly annoying, even with the favourites thing. It's getting in the way of my workflow. Also, why is there no way to rename a folder, or delete it. Auto-Delete when empty is a bit silly, and breaks fodler creation right now.
The new update is awesome, but your changes to the preset interface are just no good.
I agree with Stefan. The inability to reorder to suit the User's preference is highly frustrating and impacts my workflow. I believe this should be fixed as high priority matter. (FYI: I'm on a Windows 10 system.)
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.
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.
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!
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?
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.
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++?)
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. :)
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. :)
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?
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.
Same here on Win10 - Shai Bachar toAdobe 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. You're making me think it's time to do so... :-(
I agree that the new version is a mess. I too am seriously considering abandoning LR. It will be painful, but so is dealing with Adobe's continual release of dysfunctional 'improvements'. In this release not only are they messing with how the user is able to customize and reorder presets, but the new Profiles functionally absolutely screws up and adds unnecessary / unwelcome complexity to managing image tonality. You'd think that Adobe would be testing their products before release; and that they'd be using Focus Groups to assess their new ideas - apparently not. Its up to the customer to find the problems after the buggy software is released.
Art, I agree this release is a bit of a mess... but they are bugs that will be ironed out in future updates. In the meantime there is a simple solution - simply revert back to version 7.2 and it will work perfectly as it did before... (this is what I have done).
I do believe that the new 'Profiles' work a bit differently under the hood, but as far as my workflow goes they are just the same old profiles doing what they always did. We've all been using them for years whether we were aware of it or not, the only difference is that now they are more visible at the top of the basic panel. But as far as I see it is a UI change only, and it need only affect your workflow if you want it to.
Seth, My apologies for such a tardy response. I did decide to quit whining, to roll back to 7.2, and wait for other users to prove that Adobe can release stable, functional software. After rolling back to 7.2, I found that some of the new 7.3 bugs traveled backward with the roll-back - especially in the file management arena. Yes, disappointed again. Then 7.3.1 was released - more dysfunctional software. Remembering the question 'What is the definition of insanity', I am now considering abandoning the "Class CC" platform altogether.
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.
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.
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.
I'm currently re-renaming ~400 presets. I know how frustrating this is, and based on the nature of the problem I know how slim my chances are that a LR update could fix the problem, sooner than I could...
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...
You Lose Preset Folders when you Import a new folder of presets. All newly imported presets display ONLY in USER PRESETS folder. Not individual folders.
That will NEVER work. Allow us to import a folder as we did in the past. We cannot work with hundreds of presets in the User Folder. Did Adobe do any beta testing on this?
As far as I can tell, the only way within Classic to create new preset folders is to create a new (dummy) preset, and within the New Develop Preset dialog, you can click the Group drop-down menu and choose New Group to create a new group/folder for your new preset. Once the preset is created, it will be in the new folder you created at the same time. You can then drag and drop presets into that folder as needed. Note, empty folders disappear, so don’t get rid of your dummy preset until you put others in that folder. You can use this convoluted process to rename a folder by creating a new folder with the renamed-name, moving presets into that new folder, and the empty folder with the old name goes poof.
Check out the link for more info and photos of the steps required.
My presets are in order, other than 1, 10, 11, 12, then 2, 20, 21, 3, 4, 5 ... come on, what is this, the 1990s? I haven't seen ordering like than since last century. SMH.
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.
used to be sorted alphabetically. In version 7.3 the order is random
Responses
Official Solution
JeffreyTranberry
Adobe Administrator
•
15.8K Messages
•
295K Points
3 years ago
Sr. Product Manager, Adobe Digital Imaging
0
JohanElzenga
Champion
•
3.3K Messages
•
58.1K Points
3 years ago
Johan W. Elzenga,
http://www.johanfoto.com
2
JeffreyTranberry
Adobe Administrator
•
15.8K Messages
•
295K Points
3 years ago
Sr. Product Manager, Adobe Digital Imaging
2
0
ed_rudolph
12 Messages
•
332 Points
3 years ago
1
0
cameronbraun
20 Messages
•
700 Points
3 years ago
2
aaron_texeira
13 Messages
•
358 Points
3 years ago
1
0
nathan_johnson_3lteqs2eyjmws
26 Messages
•
990 Points
3 years ago
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...
10
shai_bachar
2 Messages
•
90 Points
3 years ago
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.
4
charles_putnam
16 Messages
•
288 Points
3 years ago
0
j_kundi
3 Messages
•
100 Points
3 years ago
3
0
matthew_baldon
4 Messages
•
112 Points
3 years ago
...Oh, this is going to be SO MUCH FUN!!! THANKS ADOBE!
0
0
ellen_rosenberg_1vldmn4nygh53
3 Messages
•
102 Points
3 years ago
0
jenny_lens_45b8db7uc90ry
7 Messages
•
176 Points
3 years ago
That will NEVER work. Allow us to import a folder as we did in the past. We cannot work with hundreds of presets in the User Folder. Did Adobe do any beta testing on this?
2
jenny_lens_45b8db7uc90ry
7 Messages
•
176 Points
3 years ago
0
0
aimee_giese
4 Messages
•
278 Points
3 years ago
0