Skip to main content
Adobe Photoshop Family

10 Messages

 • 

366 Points

Tue, Apr 3, 2018 6:39 PM

Solved

Lightroom Classic: Develop Presets did not all convert to new format in 7.3

On the first start up the new LR 7.3 converted 3 folders of develop presets, but not the rest (I have them organized by where I got them).  I can now not make new folders in the Preset panel to import the missing presets.  Any I import only go into User Presets.

Responses

Official Solution

Employee

 • 

1.7K Messages

 • 

32.4K Points

3 years ago

I've investigated Joseph's issue. The problem seems to be in the file naming of the original .lrtemplate file itself. If the original .lrtemplate file name contains any special characters (in this case, it is the forward slash "/" in the .lrtemplate file name). On macOSX, forward slash "/" has special meaning, which is is the folder delimiter.

If you manually change the “/” character in the .lrtemplate file name to a space character, then relaunch Lr and it would convert the preset correctly.

Joseph, I have replied to your email regarding the two specific .lrtemplate file that has the "/" in them. Lr should have handle this kind of exception better. I’m making a fix that better handles and report the issue in Lr.

https://helpx.adobe.com/lightroom/kb/not-all-presets-are-converted.html

Principal Scientist, Adobe Lightroom

17 Messages

 • 

280 Points

Simon, I appreciate this official response, but it is most certainly not addressing the full issue here.  This issue is present throughout my original presets folder and effects a large number of .lrtemplate presets (regardless of their name).
See https://forums.adobe.com/thread/2473692

33 Messages

 • 

478 Points

Julian, this was my first reaction, but actually after removing the "/" characters, the remaining presets throughout my folders all converted.  The "/" was causing the conversion process to abort before it was finished.

Yes, they are not all in the correct order, but this is another issue (see this thread... https://feedback.photoshop.com/photoshop_family/topics/develop-presets-not-sorting-correcly )

17 Messages

 • 

280 Points

Seth, I hear you, but although the renaming of presets may be an issue for some, it is absolutely not the core issue you here and that is what I am trying to highlight.  None of my presets have special characters in the name or folder name.
Something with the conversion process is stopping the import conversion of old .lrtemplate files either based on the alphabet or the number of total presets imported (meaning that maybe it stops after a certain maximum number?  Likely not the case but just an idea)
THAT SAID.  I just figured out a way to work around the issue that seems almost too ridiculous to be true.  In my instance, preset folders starting with the characters S-Z did not import.  With the addition of an earlier character or number in the alphabet, LR seems to now recognize them.  I simply added a "1" in from of all the folders that didn't import and it worked fine.

33 Messages

 • 

478 Points

Julian, it is indeed a mess... personally, after finding that all the presets were not ordered correctly after being converted, I've reverted to v7.2. I simply can't afford to spend so much time on it and I'll wait until it's all sorted.  Hope you have better luck!

5 Messages

 • 

152 Points

Simon Chen I do not have presets with a "/ " in their name.  Yet they did not appear in the 7.3 version of LR.  There has to be some other explanation?

Official Solution

Employee

 • 

1.7K Messages

 • 

32.4K Points

3 years ago

Here is a help doc on the issue https://helpx.adobe.com/lightroom/kb/not-all-presets-are-converted.html.

Successfully converted .lrtemplate develop preset would be renamed with a prefixed tilde character "~". If the preset conversion stopped prematurely, you can go through your original .lrtemplate develop preset folders and find the first instance of the .lrtemplate file that did not convert (without the prefixed tilde "~"). And see if the file name has any special characters such as the forward slash "/" or ":" in it. Try change the special character to hyphen "-" and relaunch Lr again. Alternatively, you can manually prefix the .lrtemplate file that did not convert with a tilde "~" character, Lr would skip converting this specific develop preset on the next launch and continue the conversion for the rest of the develop presets.

If you continue to have issues, please zip up your .lrtemplate develop presets and send me private message with a downloadable link, I can investigate for you. Please don't send a zip file as an attachment in the email. It would be quarantined by the email server. The issue would be fixed in the next Lr update. Thanks.

Principal Scientist, Adobe Lightroom

11 Messages

 • 

220 Points

Was about those presets that don't contain / and haven't converted ?

Employee

 • 

1.7K Messages

 • 

32.4K Points

That could happen if the preset itself could be malformed for some reason. For example, one of the presets that I examined at contains an ill-defined CameraProfile field in the preset that references a weird naming camera profile, such as

CameraProfile = "400H?\185 - C"

Apparently, the backslash would throw off the conversion code as well. Upon closer examination of the other presets in the same set, the problematic preset should refer to "Adobe Standard" profile instead, like

CameraProfile = "Adobe Standard"

So it was a bug in the original preset.

Principal Scientist, Adobe Lightroom

11 Messages

 • 

220 Points

So do I now have to go thro' 100's of presets and check or will this be addressed in the next update?

Employee

 • 

1.7K Messages

 • 

32.4K Points

The next update will fix the common case (file name that contains the special characters) and report the full paths of presets that did not convert. If you like, send me a zip link and I can run the latest build to see where the problems are.

Principal Scientist, Adobe Lightroom

11 Messages

 • 

220 Points

OK thanks will do

Adobe Administrator

 • 

679 Messages

 • 

13K Points

3 years ago

Hi Don,

At first I thought I could no longer make a new preset folder but after playing with it a bit I found I needed to scroll up to find "New Group"

Like this:



Does that help?

10 Messages

 • 

366 Points

Is that when you create a new preset?  Not clear how you got there.

557 Messages

 • 

11.9K Points

That’s correct. It’s not quite clear, nor is it intuitive but when you click the plus sign to create a preset, at the top, where it allows you to select the folder(i.e. User Presets), click on it and it should be the first option.

10 Messages

 • 

366 Points

I can create a folder this way, then manually import my presets that did not copy and convert on the first start up of LR 7.3.  A cumbersome workaround.    

107 Messages

 • 

1.5K Points

3 years ago

Hi,
so far I cannot reproduce this issue. All presets converted here.
Also I can:
  • right click on a folder and import directly into it
  • move presets between folders by dragging them with the mouse
To create a new folder, I just created a new dummy preset that I deleted when I no longer needed it.

Hope that helps.

107 Messages

 • 

1.5K Points

3 years ago

Found New Group in the Develop-menu. Also accessible via Alt + Ctrl + N. But apparently this isn't working.

Champion

 • 

5.8K Messages

 • 

102.3K Points

Confirmed here.

10 Messages

 • 

366 Points

Yes, it is broken.  Has someone reported this bug? 

Adobe Administrator

 • 

679 Messages

 • 

13K Points

tracking issue in new thread

Please reference the new conversation here: Lightroom Classic 7.3: Keyboard Shortcut for Presets "New Group" not working.

Champion

 • 

5.8K Messages

 • 

102.3K Points

3 years ago

Don, check your file permissions for presets that aren't converting. It's a long shot, but some of mine were set to Read-Only and didn't convert correctly until I changed them. File locations are listed here: Lightroom Classic File Locations

10 Messages

 • 

366 Points

We are having the same discussion on your forums ;) 

33 Messages

 • 

478 Points

Hi Victoria, how do I restart the conversion process once I have amended the permissions?

Champion

 • 

5.8K Messages

 • 

102.3K Points

Just restarting Lightroom will convert any that don't have a ~ on the filename

10 Messages

 • 

366 Points

This is with the presets in the old location? It did not work for me.  

Champion

 • 

5.8K Messages

 • 

102.3K Points

This is getting confusing with the same conversation in 2 places. ;-)  Which shall we use to carry on? Here is probably best so the engineers can follow.

17 Messages

 • 

280 Points

3 years ago

reposting this from the adobe Lightroom support forums.

Updating to the new Lightroom Classic CC v 7.3 I found I was missing a large majority of my user presets.  In this new version of LR presets are converted from .lrtemplate to .xmp presumably to help with previous cross application issues and keeping everything in a central location.  After some digging, I realized they also have moved the active preset bank from the Lightroom to the CameraRaw folder (the preferences menu still directs you to the Lightroom folder which is an issue when importing anything new).  It also only converted and moved about 1/2 of my user presets converting every folder A-R but stopping there leaving behind the most necessary previous "User Preset" custom folder.

SO

1) The Lightroom Preferences Presets menu "Show Lightroom Presets Folder" needs to be updated to direct to the CameraRaw settings folder if that's where presets now live.

2) How does one convert .lrtemplate files to .xmp (or how can I reinitiate the automatic conversion that began when initially I updated the application itself).

macOS High Sierra 10.13.3

iMac Pro 3 GHz Intel Xeon W

128 GB ram

Radeon Pro Vega 64 16GB

99 Messages

 • 

1.7K Points

3 years ago

I never even use presets but my new version of LR is stuck in "updating presets" after 20 minutes at least.    MBPr 13" 2015 16gb 1tb I7 everything updated including OS.   

Employee

 • 

1.7K Messages

 • 

32.4K Points

Try force kill the Lr 7.3 process and relaunch and see what happens.

Principal Scientist, Adobe Lightroom

11 Messages

 • 

220 Points

3 years ago

Same here only half of my presets converted, have now un-installed v7.3 and re-installed v7.2 which reinstated the lost presets. Over to you Adobe to sort this issue. 

System MacOS High Sierra latest update.

2 Messages

 • 

76 Points

How do you reinstall v7.2? I have sessions I need to edit and my presets are missing.

Adobe Administrator

 • 

679 Messages

 • 

13K Points

In the Creative Cloud Desktop app click on the arrow to the right of "Open" in the Lightroom Classic CC row then choose "Other versions" like this:

2 Messages

 • 

74 Points

3 years ago

Hello,

I am experiencing this problem as well.
-----------------------------------------------------------------------------------------------------------

A large portion of my LR presets are missing, including the user presets folder.

I have re-installed, down-graded, up-graded again, removed and replaced presets with backup copies and this did NOT resolve this issue with LR 7.3.


MacBook Pro (Retina, 15-inch, Mid 2015)

2.5 GHz Intel Core i7

16 GB 1600 MHz DDR3

AMD Radeon R9 M370X 2GB


macOS High Sierra

Version 10.13.4


Everything worked perfectly BEFORE the latest update and all presets were visible and usable.


PLEASE help.

Employee

 • 

1.7K Messages

 • 

32.4K Points

3 years ago

If you experiences the preset conversion issue, please zip up your .lrtemplate develop presets and send me (sichen AT adobe DOT com) a downloadable link, we would investigate. Thanks in advance.

Principal Scientist, Adobe Lightroom

2 Messages

 • 

74 Points

Hi Simon,

I've sent the requested zip file to you via email.

Looking forward to your update.
Thanks

33 Messages

 • 

478 Points

Just sent you a file Simon... cheers.

Employee

 • 

1.7K Messages

 • 

32.4K Points

Seth, your issue is the same as Joseph.

I have replied your email with instructions to correct two of the problematic .lrtemplate files that also have forward slash "/" in the file name. If you manually change the “/” character in the .lrtemplate file name to a space character, then relaunch Lr and it would convert the preset correctly.

Principal Scientist, Adobe Lightroom

1 Message

 • 

60 Points

I send you examples of a lot of the presets not converted here... 

33 Messages

 • 

478 Points

Thanks for your help Simon :)

2 Messages

 • 

128 Points

3 years ago

After the conversion the sort order is also wrong. I have named my presets like 01 xxx, 02 xxx etc. These presets now appear in a random order.

The conversion also seems to ignore the language setting of Lightroom. My user presets are now in the folder "User presets" whereas before they were located in a Dutch folder name (which by the way was always the last folder in the list).  

26 Messages

 • 

990 Points

Having same issue. Makes absolutely no sense how my presets are now ordered... 

Example: 


Why is it not alphabetical? It just appears completely random...

13 Messages

 • 

358 Points

26 Messages

 • 

990 Points

Great, think I solved it.. I posted in the other thread, but it is listed as a Mac Sierra issue, and the issue has nothing to do with Sierra... so posting here as well...

Basically, when Lightroom Classic 7.3 is converting between .lrtemplate files and .xmp files, it's assuming that we want the "internalName" to now become the "SortName".

More details...

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,  at some point, the title was changed, but the internalName did not.

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" propertyAnd 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!

17 Messages

 • 

280 Points

3 years ago

I've found a workaround that is a bit ridiculous.  The automated conversion tool is not being hung up by special characters ("/" or otherwise)... at least not in my case.  It feels a bit tone deaf that they've published that as a solution when the issue as documented clearly runs deeper than that.

For whatever reason, my presets only converted folders named with starting characters A-R.  As a last ditch effort after 3 days of it not being addressed, I added a "1" to develop preset folders that did not previously correctly import.  This shoots them to the top of the list alphabetically and... lo and behold... Lightroom now imports them perfectly fine.

There's still no easy way to rename preset folders within Lightroom now that location data is written as text within .xmp files, but at least this will get your presets imported and usable.  Hopefully they deal with the ordering/renaming bug soon.

Employee

 • 

1.7K Messages

 • 

32.4K Points

Your workaround just changed the order that your presets are converted. There might still some presets not converting at the end?

Principal Scientist, Adobe Lightroom

17 Messages

 • 

280 Points

No.  Just converted the dozen folders that were originally unconverted (those with characters at the end of the alphabet).  Bumping them to the top of the list did the trick - and that includes the conversion of files with odd characters ("/" or otherwise).

2 Messages

 • 

116 Points

The suggestion that preset names containing "/" does not seem to do any difference. A few presets got converted, but not even all of my own created in Lightroom, regardless of file names.

Adding a "1" in front of the folder name made Lightroom add "~" in front of the .lrtemplate files and import them. I'll try to do that on a few more to see if I can get them all in.

17 Messages

 • 

280 Points

Glad it worked for you as well David.  It seems like a much more cohesive solution and I'm not sure why it's not being addressed by Adobe officially.

2 Messages

 • 

76 Points

3 years ago

I just downgraded to 7.2 and everything was back and fine thankfully. I hope they get everything figured out soon.

5 Messages

 • 

152 Points

3 years ago

Uninstalled 7.3, reinstalled 7.2.  All presets are back.
Now I'll wait for Adobe to fix the issue!