Lightroom Classic: How to change AlreadyApplied attribute in Metadata

  • 1
  • Question
  • Updated 4 weeks ago
  • (Edited)
Hi, a while back, I discovered an issue where the AlreadyApplied field in the metadata on some of my JPEGS was flipped to YES on export, even though the changes had not been written to the pixel level. The only way I have to fix this is to make a small adjustment to the photo in LRCC and then export it again, but someone suggested it might be easy to write a script to change that field.

I'm hoping someone can guide me in the right direction for how to do that. I'm somewhat tech savvy, but my coding is general limited to HTML and CSS. I'm trying to prepare myself to transition back to LR Classic, but I need to get all my edits updated in my Classic library before I do that.

Any help would be appreciated.

Here is the original thread on this, if that's helpful: https://feedback.photoshop.com/photoshop_family/topics/issue-with-xmp-alreadyapplied-field-incorrect...
Photo of Jon Anscher

Jon Anscher

  • 182 Posts
  • 23 Reply Likes

Posted 4 weeks ago

  • 1
Photo of David Converse

David Converse

  • 445 Posts
  • 130 Reply Likes
Yes you would need to write a script that would address and change that field.

Adobe has a Bridge SDK with sample scripts and documentation. There are also lots of scripts online to download, that work with XMP metadata. I'd start there.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4286 Posts
  • 817 Reply Likes
Jon,

I would test this on a single image first before scaling it. 

  1. Isolate the images into a single collection
  2. Grid View in Library
  3. Quick Develop Panel
  4. Select All
  5. Hit the [ > ] Temp button to raise the Temperature relatively to existing adjustements
  6. Wait for all images to update
  7. Hit the [ < ] Temp button to restore the Temperature value to step 4 state.
Does the field reset properly?
Photo of Jon Anscher

Jon Anscher

  • 182 Posts
  • 23 Reply Likes
Nope, Just tried that with a single photo. It did not reset it. The only thing that will is either changing the AlreadyApplied attribute manually (I've been using exiftool) or changing an attribute in LR CC (Desktop) prior to exporting it.
Photo of Jon Anscher

Jon Anscher

  • 182 Posts
  • 23 Reply Likes
I wish there was a way to quick develop in LR CC, because (hopefully) that would make exporting new copies easier at least.

The bigger problem is trying to identify which photos this happened to, since it's inconsistent, and since I don't honestly know how long it's been going on. Luckily, most of my shots are RAW, but I still intersperse JPEGs throughout. I might just need to accept I'm going to lose some edits along the way.
Photo of David Converse

David Converse

  • 445 Posts
  • 130 Reply Likes
That specific field ONLY applies if you have Camera RAW adjustments that have not been applied. That would mean you opened a JPEG file in Camera RAW or within Lightroom and made changes. Exporting from a RAW to JPEG applies the changes. Also note that removing the Camera RAW XMP metadata upon export will remove that setting.

A Lightroom script would be written in Lua and you'd need to use the Lightroom SDK for development; obviously the Bridge SDK would work for fixing those images in Bridge.
Photo of Jon Anscher

Jon Anscher

  • 182 Posts
  • 23 Reply Likes
Yeah, so there's a bug in Lightroom CC. I import the JPEGs to LR CC, edit them, export a bunch of them as Original + Settings and they inconsistently import with either (a) the adjustments visible when you open them in Develop panel in LR Classic or (b) with the adjustment not visible and the AlreadyApplied field marked as true.

Unfortunately, I am out of me depth when it comes to writing a Script for the LR SDK. I'm not opposed to learning, but I may need to start with some basics first.
Photo of David Converse

David Converse

  • 445 Posts
  • 130 Reply Likes
You might consider switching to RAW files, or making changes in Photoshop instead.
Photo of Jon Anscher

Jon Anscher

  • 182 Posts
  • 23 Reply Likes
I do shoot RAW, but not for everything. I certainly don’t need hundreds of RAW photos of my cats. Not to mention when I shoot film, I don’t have a choice to have them scanned as RAW. And it’s far more expensive to have them scanned as TIFF (if that would even make a difference). And in all honesty, I’ve Ben toying with switching to JPEG more often because it’s a pain having to recover the colors and dynamic range I get in camera after I import a RAW photo into LR

Not to mention, LR CC now has lost those edits on photos inside it’s own program, without trying to export originals. I’m far more likely to choose an editing tool that can handle my files than to change my files to match my editing tool.