Pages: [1]   Go Down

Author Topic: Nesting X-Rite ColorChecker Passport profiles into image files  (Read 1172 times)

Jalok

  • Newbie
  • *
  • Offline Offline
  • Posts: 43
Nesting X-Rite ColorChecker Passport profiles into image files
« on: September 22, 2014, 09:44:25 am »

Is it possible to nest DNG color profiles created by X-Rite ColorChecker Passport LR plugin into DNG/RAW files? The product is great but I'm afraid having to manage a bunch of custom profiles among their respective images.
Logged

Redcrown

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 507
Re: Nesting X-Rite ColorChecker Passport profiles into image files
« Reply #1 on: September 22, 2014, 02:59:02 pm »

Yes, but it's a bit tricky. I discovered this some time ago when I sent a DNG file to someone only to discover that my custom profile was not embedded in the file. All other adjustments to the raw were embedded, but not the profile.

When the other person opened the DNG on his system, the profile defaulted to Adobe Standard. Turns out that the DNG contained a "tag" for the custom profile, but not the profile itself. Since his system did not have that custom profile loaded, it defaulted to Adobe Standard. And no error message or other indication of the missing profile was displayed.

Here is what we learned:

In ACR, when you make changes (and just click Done) your DNG (or XMP) file is updated. In Lightroom, if you "Save Metadata" from the Library module the same thing happens. But in both cases, the profile "tag" is included and not the profile itself.

In ACR, if you "Save" a new DNG, that DNG will have the full profile embedded. In Lightroom if you Export a new DNG, that DNG will also have the full profile embedded. Those DNGs can be moved to another computer that does not have the profile and they will be OK.

Unfortunately, ACR does not allow you to overwrite the existing DNG when you do a save. ACR automatically generates a new file name to avoid duplicates. No way to avoid that. However, Lightroom does allow you to overwrite existing DNGs when you Export DNGs.

After I learned this I discovered I had some other trouble. I had deleted forever some custom profiles for an old camera I no longer owned. But I still had some raw files from that camera. When I checked them, they all had Adobe Standard as the profile (default). I was screwed, but fortunately those raw files were not very valuable.
Logged

Jalok

  • Newbie
  • *
  • Offline Offline
  • Posts: 43
Re: Nesting X-Rite ColorChecker Passport profiles into image files
« Reply #2 on: September 22, 2014, 03:39:57 pm »

Yes, but it's a bit tricky. I discovered this some time ago when I sent a DNG file to someone only to discover that my custom profile was not embedded in the file. All other adjustments to the raw were embedded, but not the profile.

When the other person opened the DNG on his system, the profile defaulted to Adobe Standard. Turns out that the DNG contained a "tag" for the custom profile, but not the profile itself. Since his system did not have that custom profile loaded, it defaulted to Adobe Standard. And no error message or other indication of the missing profile was displayed.

Here is what we learned:

In ACR, when you make changes (and just click Done) your DNG (or XMP) file is updated. In Lightroom, if you "Save Metadata" from the Library module the same thing happens. But in both cases, the profile "tag" is included and not the profile itself.

In ACR, if you "Save" a new DNG, that DNG will have the full profile embedded. In Lightroom if you Export a new DNG, that DNG will also have the full profile embedded. Those DNGs can be moved to another computer that does not have the profile and they will be OK.

Unfortunately, ACR does not allow you to overwrite the existing DNG when you do a save. ACR automatically generates a new file name to avoid duplicates. No way to avoid that. However, Lightroom does allow you to overwrite existing DNGs when you Export DNGs.

After I learned this I discovered I had some other trouble. I had deleted forever some custom profiles for an old camera I no longer owned. But I still had some raw files from that camera. When I checked them, they all had Adobe Standard as the profile (default). I was screwed, but fortunately those raw files were not very valuable.

Thank you very much, sir, for you kindly explanation. I think this would be a nice feature for a future LR/ACR release: the possibility to embed custom profiles once they are used for a given image file.
Logged
Pages: [1]   Go Up