Lightroom Classic: Profile does not show up in the Profile Browser

  • 2
  • Problem
  • Updated 1 year ago
  • Acknowledged
  • (Edited)
I have made a number of profiles to be used with Lightroom Classic CC. Two of them (V1 and V2) are made with the same lens and camera, just under different lighting conditions, and with the same X-rite Colorchecker Passport plugin.

Only one of them shows up in the Profile Browser; if I move V1 to a different folder and restart Lightroom, V2 shows up in the Profile Browser and vice versa.

I'm on the latest versions: Lightroom Classic CC 8.2.1 on MacOS High Sierra 10.14.4.

Is there a way to have both profiles available in the Profile Browser? Thanks.
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes

Posted 1 year ago

  • 2
Photo of Andrew Rodney

Andrew Rodney

  • 1059 Posts
  • 245 Reply Likes
What do you mean by V1 and then V2? IF you made an actual ICC camera profile, instead of a .DCP profile, LR will not see nor use it. 
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
V1 and V2 are shorthand designations of the two profiles I tried to use. The profiles are .dcp files, Lightroom recognizes them but not both at the same time.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 2924 Posts
  • 1257 Reply Likes
Is it possible that both profiles have the same internal name (which is what Lightroom uses) but different file names? That would explain this behavior.
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
I made different names for both profiles. The X-rite plugin for Lightroom asks for a profile name, which shows up in Lightroom after a restart, and the resulting file name is the same.
Photo of Andrew Rodney

Andrew Rodney

  • 1059 Posts
  • 245 Reply Likes
ICC profiles have an internal and external name, software almost always accesses the internal name. Not sure about .DCP profiles. So yes, it is possible with one of those kinds of profiles. 
Photo of Todd Shaner

Todd Shaner, Champion

  • 1969 Posts
  • 667 Reply Likes
" with the same X-rite Colorchecker Passport plugin"

These were created using the X-Rite plugin, but you most likely renamed using Finder. Renaming the file does not change the internal name so only one profile shows up, if they have the same internal name. Download the X-Rite Profile Manger, which will allow you to change the internal name. Both profiles should then appear after restarting LR.

https://www.xrite.com/service-support/downloads/d/dng-profilemanager-software

Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
I changed the profile name in X-rite's DNG Profile Manager. That action changes the file name as well; later I change the file name in Finder and reload in the DNG Profile Manager.

See the picture attached, where two profiles are shown in the DNG Profile Manager with the corresponding files in Finder. In this example the V1 designation has been removed from the profile's name and file name.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1969 Posts
  • 667 Reply Likes
"That action changes the file name as well; later I change the file name in Finder and reload in the DNG Profile Manager."
Why are you changing the filename after renaming the files using DNG ProfileManager? Just name one with V1 and the other V2, leave the file names alone,  and they should both appear inside LR. You must restart LR so it can reload the renamed files!
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
Even if I leave the file names alone after changing the profiles' names, the problem persists. See my experiment below. And yes, after each change I restart Lightroom.
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
I did some further experimentation and I got stumped: the Lightroom profile browser shows both profiles if I use anything else than V1 or V2 as the last characters of the profile names. As soon as I change back to V1 and V2, one of the profiles is missing in Lightroom's profile browser. I find it hard to believe, but it looks like Lightroom's Profile Browser specifically ignores version numbers at the end of a profile name. Could it be that only the highest version number is shown? Just guessing...
Photo of Todd Shaner

Todd Shaner, Champion

  • 1969 Posts
  • 667 Reply Likes
The two profiles are identical except for internal and filename as shown below using MS Word Compare. LR is detecting this and pushing the older file into the Legacy profile folder. They both render identically.
Are you sure you didn't create them by accident using the same CCPP image file? The other possibility is that the two "different" lighting conditions were actually close to the same color temperature and tint. Upload the two CCPP raw files used to create the V1 and V2 profiles and I'll take a look at them for differences.

UPDATE: I renamed the two profiles Colorchecker Classic Standard-1 and Colorchecker Classic Standard-2 using the X-Rite ProfileManager and now LR sees both in the Profiles folder. Next I renamed the profiles back to their original V1 and V2 names and they no longer appear together in the Profiles folder. This appears to be a bug when using the V1 and V2 descriptor in the profile name. I'll change the status for this post to 'Acknowledged.'





Comparison of profiles using MS Word Compare
(Edited)
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
I'm glad you could reproduce what I had experienced and that you acknowledged this as a bug.

Furthermore, your screenshots show the Colorchecker Classic Standard V1 profile under the Legacy group and I had suppressed this group via the Manage Profiles... function in Lightroom's Profile Browser. After enabling the Legacy group I indeed found the Colorchecker Classic Standard V1 profile under that group. So the mystery of the non-appearing profile is solved, leaving only the mystery why Lightroom decides to show it in the Legacy group.

Thank you very much for your support, I now can work my way around this bug.
(Edited)
Photo of Bhargav

Bhargav, Official Rep

  • 84 Posts
  • 20 Reply Likes
Hi Ad,

Thanks for reporting the issue.
We are able to reproduce it at our end.
We'll investigate it further to identify the root cause and get back to you with further details.

Thanks,
Bhargav
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
Great, thanks!
Photo of Todd Shaner

Todd Shaner, Champion

  • 1969 Posts
  • 667 Reply Likes
Thanks Bhargav!
Photo of Thomas Knoll

Thomas Knoll, Employee

  • 15 Posts
  • 10 Reply Likes
If you use profile names ending in Adobe's profile version numbering method (v1, v2, etc.), then all but the highest number profile is put in to the legacy section (which is hidden by default).  If you don't like this feature, don't end your profile names in "v1", "v2", etc.
Photo of Ad Dieleman

Ad Dieleman

  • 58 Posts
  • 3 Reply Likes
Thanks for the confirmation. I used versioning to differentiate between experimental profiles, hence my problem.