Bridge CS6 overwriting/corrupting image EXIF data.

  • 2
  • Problem
  • Updated 6 years ago
Bridge CS6 overwriting/corrupting image EXIF data.

Hi - I'm having a serious issue with Bridge CS6 overwriting and/or corrupting my EXIF data.

The situation is this. In Bridge CS6, open a folder with some images in it. Select an image. Right-click on it and select File Info. In the XMP dialogue box fill in the IPTC fields as deemed necessary. Save this as a template. Have usually done this via the Export button and saving this as an .xmp file. In that Bridge CS6 folder, select the remainder of the images. On the menu bar, select Tools and then, Replace Metadata. In the fly-out menu selected and click on the template created above.

OK, now review the updated images. In my situation all the updated images now have the the same date and time. THIS IS/WAS NOT THE EXPECTED BEHAVIOUR.

Put another way, while using Bridge CS5 I NEVER had this experience. While running the above routine in Bridge CS5, ONLY the IPTC data was overwritten and NEVER the EXIF data. In Bridge CS6 it now seems that both the IPTC and EXIF data are being overwritten.

Added to the above, while using such a template created in Bridge CS5 and using it to apply metadata changes to images in Bridge CS6, it kills off the image orientation settings - meaning to say that all the vertical images "lost" their corrected orientation (as done in camera) and reverted back to their "native" state - as in shifting back to the horizontal.

If this is a bug as I suspect it is, it has severe implications. Not only is my EXIF being trashed in the process, its making a monkey of my efforts. Other than the orientation thing, the original EXIF data is also required for image archiving, image search and host of other activities. As it is, there seems to be no way to recover this EXIF data. Thus, all the affected images will need to be trashed, requiring me to call up my back up images.

While I know the difference between Append and Replace, this behaviour in CS6 is "unexpected". I had things working fine in CS5. Can't say the same thing for CS6. Please refer.
Photo of r coles

r coles

  • 4 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 2
Photo of Paul Riggott

Paul Riggott

  • 346 Posts
  • 132 Reply Likes
Why are you doing this? you are asking for trouble!
Create a proper template Tools - Create Metadata Template
As the way you are doing it will update all fields that it can to match the exported xml.
Do not do this!
Doing it wrong for years does not make it right now!
Photo of r coles

r coles

  • 4 Posts
  • 0 Reply Likes
Hi, appreciate your comments and yes, that would be the way to go - as in Tools/Create Metadata Template.

But, this doesn't solve the issue. In a sense what you're trying to tell me is this, things worked before because this was a "bug" in Bridge CS5 and earlier and now, after it has been "fixed" in Bridge CS6 that this is now an "undocumented feature"?

As I sort of understand things, I thought there was this "convention" of sorts out where no application would ever write directly to the EXIF data - usually created by the camera - unless explicitly requested by the user. I mean, isn't this why there are EXIF editor applications out there? So, how come Adobe - in all its wisdom and experience - is now "defying" this convention?

My point is this, at some point or other, I or someone else is going to be using Replace Metadata to apply changes to whole batch of images - and not just to images on a one to one basis - and is going to end up with exactly the same issues I've described above. The point being, it worked perfectly well before, so why change it now.
Photo of r coles

r coles

  • 4 Posts
  • 0 Reply Likes
Hi, appreciate your comments and yes, that would be the way to go - as in Tools/Create Metadata Template.

But, this doesn't solve the issue. In a sense what you're trying to tell me is this, things worked before because this was a "bug" in Bridge CS5 and earlier and now, after it has been "fixed" in Bridge CS6 that this is now an "undocumented feature"?

As I sort of understand things, I thought there was this "convention" of sorts out where no application would ever write directly to the EXIF data - usually created by the camera - unless explicitly requested by the user. I mean, isn't this why there are EXIF editor applications out there? So, how come Adobe - in all its wisdom and experience - is now "defying" this convention?

My point is this, at some point or other, I or someone else is going to be using Replace Metadata to apply changes to whole batch of images - and not just to images on a one to one basis - and is going to end up with exactly the same issues I've described above. The point being, it worked perfectly well before, so why change it now.
Photo of Paul Riggott

Paul Riggott

  • 346 Posts
  • 132 Reply Likes
What you are doing is totally wrong and the extract of metadata is for other purposes, it was never to be used globally on other documents, you are messing:-
orientation, dates, colour profiles, resolutiion and other fields. It never did work as you think it did, it is highly dangerous and should never be used.

Creating a Metadata template once can then be applied to all your documents, and it will only affect the fields you have filled in.
Photo of Wanderlens

Wanderlens

  • 11 Posts
  • 1 Reply Like
I have this same problem with a metadata template I created previously and regularly apply to batches of photos. I never had any problem with it overwriting exif data until CS 6, and I don't think it was doing it originally in CS6, but it does now. When you chose the middle option in the popup window to keep original metadata, but replace matching properties, it never messed with the created date before. Now it changes the created date, which is not acceptable behavior.
Photo of r coles

r coles

  • 4 Posts
  • 0 Reply Likes
Hi Kayte,

I'm glad I'm now not alone on this matter. As it happens, I'm now seeing more and more people picking up on this issue. Seems like the sycophants here - who see Adobe never getting it wrong - can't seem to get around this one either and cannot seem to accept that there's an issue or bug here.

Just the other day was trying to "modify" a template. While using template editor - this under Tools >> Edit Metadata Template, it took 3 and more successive open and close cycles to eventually "kill" the "Date Time Original" item "stuck" in the Camera Data (EXIF) section of the template. This included "unchecking" the check box and trying to keep it "unchecked".

While this data item, might - and I use the word "might" loosely here - be the "original" date, I have noticed this date could be anything else but the "original" date. And, if it is, its the date and time taken off the first image in a batch of images to which one may want to apply the template - thus OVERWRITING all the images in that batch with NOT only the same date - as may be intended - BUT ALSO THE SAME TIME, which is usually DEFINITELY NOT INTENDED. All this is equally "NOT acceptable behavior" - as in Adobe overwriting my original and camera generated EXIF data.

Hope someone out there is paying attention to this thread...
Photo of Paul Riggott

Paul Riggott

  • 346 Posts
  • 132 Reply Likes
There are consequences when playing Russian roulette, don’t blame others when the gun goes off!
Photo of Wanderlens

Wanderlens

  • 11 Posts
  • 1 Reply Like
I actually found the solution. If you go to Tools, Edit Metadata Template, you'll see that in your old templates, now there's a check box checked saying to copy the created date, as well as other stuff. You can uncheck the boxes for everything you don't want copied. I don't know what they did that changed this to make it now copy the created date by default (or why), but at least you can undo it so you can use your existing templates without overwriting EXIF data..