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

  • 34
  • Problem
  • Updated 1 year ago
  • Solved
  • (Edited)
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.
Photo of Don Smith

Don Smith

  • 9 Posts
  • 3 Reply Likes

Posted 2 years ago

  • 34
Photo of Rick Spaulding

Rick Spaulding, Champion

  • 564 Posts
  • 235 Reply Likes
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?
Photo of Don Smith

Don Smith

  • 9 Posts
  • 3 Reply Likes
Is that when you create a new preset?  Not clear how you got there.
Photo of Jerry Syder

Jerry Syder

  • 314 Posts
  • 143 Reply Likes
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.
Photo of Don Smith

Don Smith

  • 9 Posts
  • 3 Reply Likes
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.    
Photo of Henrik Zawischa

Henrik Zawischa

  • 88 Posts
  • 7 Reply Likes
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.
Photo of Henrik Zawischa

Henrik Zawischa

  • 88 Posts
  • 7 Reply Likes
Found New Group in the Develop-menu. Also accessible via Alt + Ctrl + N. But apparently this isn't working.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4899 Posts
  • 1907 Reply Likes
Confirmed here.
Photo of Don Smith

Don Smith

  • 9 Posts
  • 3 Reply Likes
Yes, it is broken.  Has someone reported this bug? 
(Edited)
Photo of Rick Spaulding

Rick Spaulding, Champion

  • 564 Posts
  • 232 Reply Likes
tracking issue in new thread

Please reference the new conversation here: Lightroom Classic 7.3: Keyboard Shortcut for Presets "New Group" not working.
(Edited)
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5181 Posts
  • 2021 Reply Likes
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
Photo of Don Smith

Don Smith

  • 9 Posts
  • 3 Reply Likes
We are having the same discussion on your forums ;) 
Photo of Seth Carnill

Seth Carnill

  • 33 Posts
  • 3 Reply Likes
Hi Victoria, how do I restart the conversion process once I have amended the permissions?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5181 Posts
  • 2021 Reply Likes
Just restarting Lightroom will convert any that don't have a ~ on the filename
Photo of Don Smith

Don Smith

  • 9 Posts
  • 3 Reply Likes
This is with the presets in the old location? It did not work for me.  
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5181 Posts
  • 2021 Reply Likes
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.
Photo of Don Smith

Don Smith

  • 9 Posts
  • 3 Reply Likes
I was just trying to make it clear for Seth, and to confirm I was doing what you suggested.  I have imported all manually, so I am just trying to help now.  
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
Permissions don't see to be the problem.  Folders named A-R automatically converted to .xmp (and renamed the old files with a tilde), but anything S-Z will not auto convert.  This includes those with open permissions.  
I've done to work around where I've created a dummy folder and imported manually - this seems to be working, but also isn't renaming the original .lrtemplate files with a "~" which I imagine will create duplicates once the conversion tool is fixed...
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5181 Posts
  • 2021 Reply Likes
Anything non-standard about the S-Z presets? A different character in a folder name or preset name, something like that?
(Edited)
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
No, and regardless the standard Lightroom created "User Presets" folder did not automatically convert so that should speak to there being some choke in the conversion process that's not based on permissions.
A few of us are seeing the same issue. https://forums.adobe.com/thread/2473692
Photo of Seth Carnill

Seth Carnill

  • 33 Posts
  • 3 Reply Likes
Permissions don't seem to be the issue with me either... all folders containing presets have read and write permissions.  

Only 1 folder of presets was converted for me (and not fully)... it was the first folder (alphabetically) in my Develop Presets folder.  

I have approx 80 folders of presets in total.

Also converted were some presets made by DVLOP which I had purchased... I think these may have already been installed in the ACR folder, so it's unclear whether the new LR 7.3 was converting old presets or just using the ones that already existed in the ACR folder... (at this point I'm as confused as Lightroom seems to be....)
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
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

Photo of Art M.

Art M.

  • 88 Posts
  • 18 Reply Likes
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.   
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1633 Posts
  • 546 Reply Likes
Try force kill the Lr 7.3 process and relaunch and see what happens.
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
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.
(Edited)
Photo of Melanie Baldi Cabaniss

Melanie Baldi Cabaniss

  • 2 Posts
  • 0 Reply Likes
How do you reinstall v7.2? I have sessions I need to edit and my presets are missing.
Photo of Rick Spaulding

Rick Spaulding, Champion

  • 564 Posts
  • 235 Reply Likes
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:

(Edited)
Photo of Joseph Pollard

Joseph Pollard

  • 2 Posts
  • 0 Reply Likes
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.

(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
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.
Photo of Joseph Pollard

Joseph Pollard

  • 2 Posts
  • 0 Reply Likes
Hi Simon,

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

Looking forward to your update.
Thanks
Photo of Seth Carnill

Seth Carnill

  • 33 Posts
  • 3 Reply Likes
Just sent you a file Simon... cheers.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
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.
Photo of Brian Skovgaard

Brian Skovgaard

  • 1 Post
  • 0 Reply Likes
I send you examples of a lot of the presets not converted here... 
Photo of Seth Carnill

Seth Carnill

  • 33 Posts
  • 3 Reply Likes
Thanks for your help Simon :)
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
Simon, I have hundreds of presets not converting with no exceptions in regard to their naming.  Relaunching LR does nothing in terms of importing presets.  I've even tried rearranging a few of the already converted .xmp presets (in the cameraraw folder) and even those new arrangements don't properly update within LR.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5169 Posts
  • 2021 Reply Likes
> I've even tried rearranging a few of the already converted .xmp presets (in the cameraraw folder)

As in you tried to put them into folders? That doesn't work "the old way" any more - the folder names are now stored as part of the preset text, rather than working on OS folder names. 
Photo of Michael Meyer

Michael Meyer

  • 7 Posts
  • 6 Reply Likes
It seems the OS folders are ignored once the presets are imported to xmp, the group name is now in the xmp file.

   <crs:Group>
    <rdf:Alt>
     <rdf:li xml:lang="x-default">This preset will show up in this Group</rdf:li>
    </rdf:Alt>
   </crs:Group>
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
That is right.
Photo of Roy Venema

Roy Venema

  • 2 Posts
  • 2 Reply Likes
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).  
(Edited)
Photo of Nathan Johnson

Nathan Johnson

  • 25 Posts
  • 22 Reply Likes
Having same issue. Makes absolutely no sense how my presets are now ordered... 

Example: 


Why is it not alphabetical? It just appears completely random...
Photo of Nathan Johnson

Nathan Johnson

  • 25 Posts
  • 22 Reply Likes
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!
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
Official Response
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
(Edited)
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
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
Photo of Seth Carnill

Seth Carnill

  • 33 Posts
  • 3 Reply Likes
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 )
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
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.
Photo of Seth Carnill

Seth Carnill

  • 33 Posts
  • 3 Reply Likes
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!
Photo of Terri Jankelow

Terri Jankelow

  • 5 Posts
  • 2 Reply Likes
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?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
Hi Teri, 

There could be issues with the .lrtemplate themselves. It would be great if you can send me a download link to those presets that did not convert for you so that I could investigate. Thanks in advance.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
Official Response
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.
(Edited)
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
Was about those presets that don't contain / and haven't converted ?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
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.
(Edited)
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
So do I now have to go thro' 100's of presets and check or will this be addressed in the next update?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
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.
(Edited)
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
OK thanks will do
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
Hi
Just emailed you
Thanks
Chris
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
Try sichen AT adobe DOT com. Did not get the email.
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
OK will send again
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
Simon did you have any luck with my presets?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
Hi Chris, 

No luck in receiving the download url.
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
Ok resent resent again
(Edited)
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
Simon any luck converting my presets?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
Hi Chris, Unfortunately I never got a chance to receive your email. Did you send to sichen@adobe.com? Thanks.
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
Yes I've sent this 4 times now, if you don't get it this time I'll just wait until Adobe sorts out the issues before installing the latest version.
Thanks
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1635 Posts
  • 550 Reply Likes
Hi Chris, That is very weird, still not getting it. I have received similar requests from other customers and their email seems to be able to get through.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5169 Posts
  • 2021 Reply Likes
Chris, you're welcome to send to me at uploads@lightroomqueen.com and I'll pass them onto Simon if they're failing when they come from you directly.
Photo of Chris Toombes

Chris Toombes

  • 11 Posts
  • 3 Reply Likes
Thanks for the offer Victoria but I think I’m just going to wait until Adobe sort out the preset issues along with a number of performance issue that have also returned since the update. My workflow needs to remain consistent and I can’t afford to waste anymore time on trying to make v7.3 work. Personally I think Adobe needs to offer a free month for the hassle it’s causing its subscribers.
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
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.

(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1633 Posts
  • 548 Reply Likes
Your workaround just changed the order that your presets are converted. There might still some presets not converting at the end?
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
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).
Photo of David Pahmp

David Pahmp

  • 2 Posts
  • 2 Reply Likes
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.
Photo of Julian Manuszewski

Julian Manuszewski

  • 16 Posts
  • 2 Reply Likes
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.
Photo of Melanie Baldi Cabaniss

Melanie Baldi Cabaniss

  • 2 Posts
  • 0 Reply Likes
I just downgraded to 7.2 and everything was back and fine thankfully. I hope they get everything figured out soon.
Photo of Terri Jankelow

Terri Jankelow

  • 5 Posts
  • 2 Reply Likes
Uninstalled 7.3, reinstalled 7.2.  All presets are back.
Now I'll wait for Adobe to fix the issue!
Photo of SevenJ

SevenJ

  • 1 Post
  • 1 Reply Like
When I first upgraded the new version I couldn't find any of my presents. I spend some time on the web looking for answers. By the time read up on the problems and came back to my Mac all the presets had populated. I found some other things had moved around. Dehaze in now in basics, camera profiles have moved. Looks like an improvement overall.
Photo of Katalin Hollay

Katalin Hollay

  • 1 Post
  • 0 Reply Likes
I still cannot find any of my hundreds of develop presets I paid for. Uninstalled 7.3 and reinstalled 7.2 and the presets were missing from there, too. Called Adobe and after being on hold two hours, I hung up. Poor customer service. ON1 is starting to look very inviting.
(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 6001 Posts
  • 1322 Reply Likes
Katalin, sorry about your on-hold experience. Let's see if we can get you working again.

Have you installed 7.3.1 which was released earlier today? It had a fix for missing presets that might be affecting you. Give it a try and let us know if they reappeared.
Photo of Terri Jankelow

Terri Jankelow

  • 5 Posts
  • 2 Reply Likes
So you simply left the new version for a while and later found that the presets had appeared?  How long did you wait? I find that strange!
Photo of Jim Thielen

Jim Thielen

  • 1 Post
  • 1 Reply Like
Upgraded my MacPro((2009)/El Capitan, 500gbSSD, 16 gb ram) and only 3.5 of my 52 files converted.
Same story on my 2009 Macbook Pro (same specifications) and only 3.5 of my 52 preset files converted.
Both machines had a message come up saying it could not convert some files to the xmp format.

Same message on multiple restarts.

No changes after several hours.

Downloaded Matt K's new profiles. I did some work on my MacPro, saved everything. Went to open the same file on my Macbook Pro a bit later and the profile did not stick. Also Matt's profiles loaded into the MacPro but would not show up in Lightroom on the Macbook Pro.

Too much drama.

Uninstalled 7.3 and reinstalled 7.2, replaced the changed files with my archived files and everything is now working.

I won't be upgrading again until Adobe gets this sorted out.
(Edited)
Photo of Michael Hart

Michael Hart

  • 4 Posts
  • 1 Reply Like
Same here. They need to realize they blew it this time.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 6001 Posts
  • 1322 Reply Likes
Lightroom Classic CC 7.3.1 was released earlier today and should give some relief on this issue. Let us know what you are seeing after you install it.
Photo of gmagic

gmagic

  • 2 Posts
  • 0 Reply Likes
All this has got me totally confused.

I updated Lightroom to 7.3.1 (macOS) and saw a dialog telling me it was "Updating Develop Presets to XMP" with a progress bar.  I thought, well, go ahead.  But at the end it threw a dialog saying, "There were errors converting custom develop presets to XMP".  Further down, the dialog said, "The following preset files could not be renamed:".  It showed a huge list which I managed to copy, and see that basically it referred to all my VSCO presets.

Now, I read in the comment by Simon Chen that "Successfully converted .lrtemplate develop preset would be renamed with a prefixed tilde character".  But, if I look at the presets that apparently couldn't be converted to XMP (in: ~/Library/Application Support/Adobe/Lightroom/Develop Presets), I see that they are in fact prefixed by a tilde character, in fact, by two tilde characters.  So were they converted, or not?

I also read in the comment by Julian Manuszewski that, "they also have moved the active preset bank from the Lightroom to the CameraRaw folder".  But equally strangely, my CameraRaw folder (~/Library/Application Support/Adobe/CameraRaw/Settings) does contain the very presets (XMP) that I was told by Lightroom couldn't be converted.

I haven't a clue therefore what is going on, or what I should do.  I only know that Lightroom is throwing this warning dialog every time I launch it.

Any suggestions?
(Edited)
Photo of Chinoy Gupta

Chinoy Gupta, Employee

  • 78 Posts
  • 35 Reply Likes
Any lrtemplate prefixed with ~~ is already converted to XMP in 7.3.1. If you are seeing the conversion dialog on Lr startup that means, there still some unconverted presets which either have single ~ or no ~ at all. Can you check for those?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 6001 Posts
  • 1322 Reply Likes
If you take the group of ~ or ~ ~ presets and (temporarily) move them from the Lightroom preset storage folder to hide them and then launch Lightroom again, do you:

1. see any attempt to reconvert the presets?
2. have any missing presets?
Photo of gmagic

gmagic

  • 2 Posts
  • 0 Reply Likes
@Chinoy, @Rikk - I checked, and indeed there were some presets that were prefixed by a single tilde character (though none not prefixed by a tilde at all), yet these had been converted and worked properly in Lightroom.

Eventually I took the drastic measure of deleting all the presets, from all locations, except the Lightroom defaults, and I'm in the process of re-installing them.  I just couldn't put up with the slow launch and that dialog every time.

I guess I'll never know the cause of that odd behaviour, but thank you for your help and suggestions.
Photo of Chinoy Gupta

Chinoy Gupta, Employee

  • 66 Posts
  • 29 Reply Likes
There are two parts to preset conversion. One is to convert actual preset settings from lrtemplate to XMP format and store them in new file. The second part is to rename the lrtemplate file by appending ~~ to its filename. Since in your case, you were able to see all the presets in Lr UI, that means the first part completed successfully. But since errors were reported and some files were present with single ~, looks like second part failed. This maybe be because of permission issues.
Photo of SPJ

SPJ

  • 17 Posts
  • 2 Reply Likes
How do we fix this? I just noticed that I was missing a bunch of presets. I've marked the presets that didn't get imported/converted in red.


And...
Photo of Chinoy Gupta

Chinoy Gupta, Employee

  • 66 Posts
  • 29 Reply Likes
Hi Jason,

Will it be possible for you to share one of these presets so that we can investigate it?

Thanks,
Chinoy
Photo of SPJ

SPJ

  • 17 Posts
  • 2 Reply Likes
**Update**
  • I tried searching the LR CC forums and there is no report of this issue there.
  • I realize that this forum thread is pertaining to LR Classic, but I am observing this issue in LR CC v.1.3.
  • I applied the single ~ to some of the presents I need to use now, and nothing happed when I launched LR CC.
  • According to the naming structure in LR Classic, my presets have converted and I have been able to verify this in the Finder.
Problematic Presets:
https://drive.google.com/open?id=1SnfWliSTnAOPL1bEeheJ1fFUBo4hcoBQ

I've given you the "converted" ones too. Let me know if you need anything else; do you need the XMP that LR Classic created?
Photo of Chinoy Gupta

Chinoy Gupta, Employee

  • 66 Posts
  • 29 Reply Likes
Hi Jason,

In Lr Classic 7.3.1 all of them are getting converted successfully. Are you facing the issue in Lr Classic or Lr CC?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1573 Posts
  • 514 Reply Likes
There is no automatic preset conversion process in Lr CC v 1.3, where you need to manually import the presets that you need. There is some good instruction here http://natephotographic.com/import-presets-new-lightroom-cc-2017-2018/
Photo of SPJ

SPJ

  • 17 Posts
  • 2 Reply Likes
@Chinoy: 
  • In LR Classic, it appears that all of the presets have been converted successfully. Everything has a double tilde (~~) appended to the file name.
  • In LR CC, not everything was converted as I demonstrated in the screenshots I shared in my earlier post. The presets that show up and that are working fine in LR CC have a single tilde (~) appended to the file name. 
  • So, the issue here is LR CC.
@Simon:
  • Thank you for trying to help, but I've done all of those steps prior to 1.3 coming out.
  • It's when 1.3 for LR CC was released that these problems occurred.
  • I didn't include the file path in my previous screenshots, but I will include them here.


It's just annoying that here we are in 2018 and we are still dealing with work arounds and such in Adobe products. If we were back in 2000 or 2005, yeah I might understand, but the way other companies like Apple, Google, and VSCO make software that "just works" sets the bar high. It's not to say there aren't bugs, but...just saying.

On a side note, I (like many others) find it annoying that many background services are loaded and ran after any cold boot even when no Adobe software has been launched — thus, taking up computing resources such as CPU processes which in turn eat up battery life. This software design harkens back to the Windows 95/98 days...which...is...unacceptable and this is coming from a Mac user.

**Update - 30-MAY-18 @ 09:30**
  • I just tried to import the problematic presets again into LR CC v1.3 as outlined in the link that @Simon Chen shared and no luck. 
  • LR CC v1.3 reports that the presets have been imported successfully, but they are not populated in the preset panel.
  • I've restarted LR CC after importing the problematic presets, and they still do not show up.
**Update @ 09:50**
  • So, if you import the problematic profiles individually, or mass selecting them when the dialog box pops up, then they get imported into the User Presets folder. Thus, ignoring the parent folder in which they are stored in.
  • If you want to maintain folder hierarchy, then you need to import the folder containing the presets that you want to import.
  • Importing the same file multiple times will result in copies & duplicates of the presets which will show up as duplicates inside of LR CC; an underscore with the copy number is appended to those preset files that were imported again.
  • In order to delete the duplicate presets, you will need to right-click > show package contents on the LR CC catalog as outlined by Nate.
**Update @ 10:05**
  • Deleted all of the VSCO presets.
  • Re-imported them at the parent directory Develop Presets.
  • From the looks of it, all of the presets were successfully imported.
  • The bad news — all of the presets are clumped into the Develop Presets tab inside LR CC
  • What didn't happen: the sub-folder organization was ignored. Refer to my previous post which shows the snapshot of my preset organization inside Finder.
  • Will start over and try the import process again this time importing the folders that I want to keep the presets organized in one at a time.

**Update @ 11:26**
  • You can mass select the folders in which you have the presets organized during the import process and LR CC will keep them sorted inside the application accordingly.
  • Problem resolved: I had to re-import the problematic presets. 
  • Starting over from scratch was the easiest.
(Edited)