New XMP-CRS fields with the New Lightroom

[blue-j]

Adobe Lightroom has introduced "Color Grading," and this new functionality brings with it a dozen or so new fields.  I see some of them, but they don't appear all to be noticed by ExifTool yet, and not yet included in the XMP-crs formal list on ET's page:

https://exiftool.org/TagNames/XMP.html#crs

Color Grading Midtones Hue     xmp:xmp-crs:colorgrademidtonehue
Color Grading Midtones Saturation     xmp:xmp-crs:colorgrademidtonesat
Color Grading Midtones Luminance     xmp:xmp-crs:colorgrademidtonelum

Color Grading Shadows Hue     <unrecognized>
Color Grading Shadows Saturation     <unrecognized>
Color Grading Shadows Luminance     xmp:xmp-crs:colorgradeshadowlum

Color Grading Highlights Hue     <unrecognized>
Color Grading Highlights Saturation     <unrecognized>
Color Grading Highlights Luminance     xmp:xmp-crs:colorgradehighlightlum

Color Grading Blending     xmp:xmp-crs:colorgradeblending
Color Grading Balance     <unrecognized>

Color Grading Global Hue     xmp:xmp-crs:colorgradeglobalhue
Color Grading Global Saturation     xmp:xmp-crs:colorgradeglobalsat
Color Grading Global Luminance     xmp:xmp-crs:colorgradegloballum

I have exported a Develop Preset with all fields checked that were available for your reference, attached.  Please note that not every single checkbox was available to me to be checked, as shown in the screenshot.  Thanks for your attention to this!  I also welcome any further input as to what else might be new in the new CC 2021 release.

- J

[Phil Harvey]

Thanks.  I'll add the new tags in your sample XMP to the next release.

I can't add ones for which I don't have an XMP sample, so please let me know if you figure out how to generate any more new tags in the XMP output.

- Phil

[blue-j]

Thanks so much!!

....Working on it!  I'm doing a deep dive into this schema.  I may not survive...  :p

- J

[blue-j]

I figured it out:

Color Grading Midtones Hue     xmp:xmp-crs:colorgrademidtonehue
Color Grading Midtones Saturation     xmp:xmp-crs:colorgrademidtonesat
Color Grading Midtones Luminance     xmp:xmp-crs:colorgrademidtonelum

Color Grading Shadows Hue     xmp:xmp-crs:SplitToningShadowHue
Color Grading Shadows Saturation     xmp:xmp-crs:SplitToningShadowSaturation
Color Grading Shadows Luminance     xmp:xmp-crs:colorgradeshadowlum

Color Grading Highlights Hue     xmp:xmp-crs:SplitToningHighlightHue
Color Grading Highlights Saturation     xmp:xmp-crs:SplitToningHighlightSaturation
Color Grading Highlights Luminance     xmp:xmp-crs:colorgradehighlightlum

Color Grading Blending     xmp:xmp-crs:colorgradeblending
Color Grading Balance     xmp:xmp-crs:SplitToningBalance

Color Grading Global Hue     xmp:xmp-crs:colorgradeglobalhue
Color Grading Global Saturation     xmp:xmp-crs:colorgradeglobalsat
Color Grading Global Luminance     xmp:xmp-crs:colorgradegloballum

So.... the new version of Lightroom (and Camera Raw) drops Split Toning entirely and replaces with Color Grading.  Adobe has chosen to use some of the old Split Toning metadata fields to complement the new Color Grading fields.  How would you like to handle it?  On our side, we will name them all as above, but my little Phil voice in my head says to keep them in Split Toning because that's what they are labeled and people are still using older versions....  Correcto?  - J

[blue-j]

From the horse's mouth:

"Color Grading is an extension of Split Toning — it can do everything Split Toning did, plus much more," Adobe's Max Wendt explains in today's announcement. "Your existing images with Split Toning settings will look exactly the same as they did before, your old Split Toning presets will also still look the same when you apply them, and you can still get the same results if you had a familiar starting point when doing Split Toning manually."

https://techcrunch.com/2020/10/20/adobe-lightroom-gets-a-new-color-grading-tool-auto-versions-graphical-watermarking-and-more/

[Phil Harvey]

Thanks, but I need to see the original XMP to get the correct case of the XMP property names, and see a value to tell what format to use.

For example, you say "colorgrademidtonehue" in your post, but the XMP sample gives:

Code Select Expand

   crs:ColorGradeMidtoneHue="0"

which is different, and presumably takes an integer value.  (If you could write values other than 0, fractional values if possible, it would be easier to tell the format.)

Edit:  I see now.  The lower case ones were the ones in the sample, and the rest already exist, so there are no more new tags to add.

I will just use the same tag names as Adobe uses for the XMP properties.  (The ExifTool tag names are not case sensitive so I am free to change this to whatever I like, but I need to write the correct case for the XMP properties.)

- Phil

[blue-j]

Well... it's not possible that you had the fields already, as color grading didn't exist until a few days ago.  I do have -u switch and maybe that's why they showed?  Or some other reason?  But the ones I listed in all lowercase, though recognized by ET, are still not listed in your schema page.  Not sure what that all means...?  But I believe you have not formally supported these fields before, except for the CamelCase split toning entries.  - J

[Phil Harvey]

Sorry, I meant no more new tags (after the ones I had already added from your sample XMP, which will appear in ExifTool 12.09).  [and no, I didn't edit my previous post again to add the word "more". ]

- Phil

[blue-j]

Coolio, Captain!  Thanks!!!!  : )   - J

[blue-j]

Oh my.  The plot has thickened.  Attached please find a new XMP export from ACR 13 that has adjustments to every damn slider I could find.  It looks like there are more fields that ET sees but are not listed on the schema page....!  AutoToneDigest is one.  Another is AutoToneDigestNoSat.  I don't have the skillz to identify quickly such fields; I just run into them - I hope the attached will empower you to!  - J

[Phil Harvey]

Great, thanks!:

Code Select Expand

> exiftool ~/Desktop/ACR13_fields.xmp -v | grep adding
  [adding XMP-exif:SensitivityType]
  [adding XMP-crs:LensProfileIsEmbedded]
  [adding XMP-crs:AutoToneDigest]
  [adding XMP-crs:AutoToneDigestNoSat]
  [adding XMP-crs:ToggleStyleDigest]
  [adding XMP-crs:ToggleStyleAmount]
  [adding XMP-crs:LookSupportsAmount]
  [adding XMP-crs:LookSupportsOutputReferred]
  [adding XMP-crs:LookCopyright]
  [adding XMP-crs:LookGroup]
  [adding XMP-crs:LookParametersVersion]
  [adding XMP-crs:LookParametersProcessVersion]
  [adding XMP-crs:LookParametersClarity2012]
  [adding XMP-crs:LookParametersConvertToGrayscale]
  [adding XMP-crs:LookParametersCameraProfile]
  [adding XMP-crs:LookParametersLookTable]
  [adding XMP-crs:LookParametersToneCurvePV2012]

- Phil

Edit: The first reported tag above points out a new LR bug -- SensitivityType should be in the "exifEX" namespace, not "exif".

Edit2: This is a problem:  The crs:Look structure has an element called "Name" (resulting in an ExifTool tag name called "LookName"), but Adobe has also introduced a crd:LookName tag.  Since the crs and crd namespaces share all the same tags, this causes a conflict in ExifTool that I need to resolve somehow.

[blue-j]

I do not see evidence that the CRD namespace is in use anymore.  When I view default files provided with the latest Lightroom, they are composed of CRS data, without exception.

Also, checking their open source page, I only find CRS:

https://www.adobe.io/open/standards/xmp.html#!adobe/xmp-docs/master/XMPNamespaces/crs.md

I suspect the CRD namespace is no longer in operation, but I am not an expert on this area and don't feel like I should be the one signing the death certificate.  :p

- J

[Phil Harvey]

DNG Converter 13.0 writes crd:LookName

- Phil

[blue-j]

Is that a matter of backward compatibility?  CRD was certainly once used, and DNG Converter is designed to be able to output for a lot of old versions... I'm not sure what you should decide...?  CRD appears deprecated (it doesn't look like a smart idea in the first place, as we are now seeing) but it's still out there in the wild.  - J

[Phil Harvey]

All I know is that DNG Converter 12.1 didn't write this, so it has been added recently.

- Phil