Skip navigation
Currently Being Moderated

Writing metadata to some jpegs fails.

Jun 29, 2012 12:41 PM

Tags: #metadata

I have a problem writing metadata to some of my jpegs and can't figure out why.

I "save metadata to file" with Command-S on Mac, go away and come back to find the 3 horizontal lines and Down Arrow are back. Saving individually or as a group of pictures, makes no difference, and its always the same photos that Fail.

 

tired of looking at this...=⬇ (except there are 3 horiz. lines)

 

any help, anyone?

John

 
Replies
  • Currently Being Moderated
    Jun 29, 2012 4:38 PM   in reply to johnnf

    If it is the same files over and over, it's an issue with those files. Could be a permissions issue or a corruption of the file that is preventing the metadata from being saved.

     

    Are all of these files stored in the same folder(s)? If so, is it all of the JPEGs in this location? Might try just moving them to a new folder.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2012 5:23 PM   in reply to johnnf

    I had a similar problem (same symptoms) a while back - fixed it using exiftool.

     

    (jpeg's metadata block was afu)

     

    My (admittedly not too easy to grok) notes regarding that fix:

     

    To fix asdf.jpg problem: maker-notes offset error in the face of a bad interopIFD directory, do this:

     

    - exiftool -all:all= asdf.jpg -tagsfromfile @ -all:all -F (fixes maker notes despite bad interopIFD directory - removes all tags and rebuilds exif metadata from all readable tags.

    - exiftool asdf.jpg -tagsfromfile noprob.jpg -interopIFD:InteropIndex (copy desired interopIFD tag or any other unreadable tag from a non-problematic image - beware to copy only compatible values, otherwise set manually if you can figure out what to set them to).

    - exiftool asdf.jpg -tagsfromfile noprob.jpg -interopIFD:InteropVersion (ditto, etc...)

     

    FWIW, I submitted an 'Idea' to Adobe to re-write jpeg metadata when such errors occur (subject to user approval) - don't hold breath...

     

    R

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2012 7:59 PM   in reply to Brett N

    Brett N wrote:

     

    Could be a permissions issue or a corruption of the file that is preventing the metadata from being saved.

     

    I think Adobe should consider making a distinction between such stuff, and notify user of problem area.

     

    e.g. there is a big difference between "file is read-only", and "file is corrupt", and it's easy enough for software to check, but inexperienced users: not so much.

     

    R

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2012 9:19 PM   in reply to Rob Cole

    Not being nitpicky Rob but tell me why "Adobe" should do this?? Adobe is a huge corporation with many. many business areas. There is a big difference between Adobe and Adobe Photoshop Lightroom.

    I think the way to phrase it is: "It would be great for Lightroom to give more accurate error messages that inform the user of what a problem is." and "As Lightroom is a DAM tool it would make sense for it to include a file integrity checking process."

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2012 2:27 PM   in reply to johnnf

    John, Lightroom doesn't have internal methods for moving files on disk, it uses the OS tools I don't think there is anything to fix at this stage.

    If you want to have further staff responses I recommend you post here which is the site for bug reporting. This forum is a user to user forum for users to help users, staff visit here but do not moitor it to the same degree as Photoshop.com.

    You are more than welcome to post a link or provide one by PM to one or more of the files so others can check it for you. I would be happy to see if I can see what is up with your files.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2012 2:51 PM   in reply to johnnf

    Hi John,

     

    There is a GUI for exiftool, but I've never used it. Note: fixing jpegs with exifTool (and preserving existing metadata) is a *very* advanced task, whether GUI or command-line. You may want to consider simpler alternatives, e.g.

     

    Export the jpeg as an 8-bit tiff (or jpeg) and add-to-catalog, then stack the original under it in case you learn a better way to correct it in the future, or just delete original...

    (Lightroom creates all new metadata block upon export, so metadata corruption is fixed that way)

     

    There may be other tools that can simply correct bad jpegs - I haven't researched. (you may lose some hopefully-not-too-critical metadata).

     

    Or maybe Geoff will fix them for you.

     

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 1, 2012 12:40 PM   in reply to johnnf

    johnnf wrote:

     

    I found that the image exported as Adobe 98 was a little "brighter" whereas if I exported as PhotoPro the new copy was indistinguishable.

     

    I assume you mean in the develop module. In library module it should look exactly the same when exported as AdobeRGB, no?

     

     

    johnnf wrote:

     

    Is there a reason I would not want to export as PhotoPro.

     

    Usually it's best, I think, to export 8-bit jpegs to be used as Lr masters, in AdobeRGB. ProPhoto is designed for primary use as a 16-bit edit space, not an 8-bit output space.

     

    But, I'm not so much of an expert in this area as some who may comment... - there are things I don't understand like how monitor profiles factor in to what you see...

     

     

    R

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 1, 2012 1:56 PM   in reply to johnnf

    In my case, jpeg metadata block was corrupted by ACDSee, and it was always the same problem, so the fix was the same for all of them.

     

    Can you see what "Software" last wrote metadata block?

     

    If you're done dealing with this for now, then just forget it - I will understand...

     

    R

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 3, 2012 1:50 PM   in reply to johnnf

    Hi John,

     

    I'm not sure if that's it or not. I was trying to ascertain which software before Lightroom last updated the metadata block, since it is probably the culprit.

     

    You can use exiftool to find out. Unfortunately I don't remember the tag name. Anyway, *if* you want to investigate further, the object is to "Sherlock Holmes" the common denominator amongst the problem files.

     

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 3, 2012 3:42 PM   in reply to johnnf

    johnnf wrote:

     

    well its camera to LR, ..., the majority of these "problem" images were never in Photoshop.

     

    Then presumably the metadata was corrupted by Lightroom itself.

     

    You can at least try to read all the tags using exiftool - sometimes there's a clue.

    Also, try updating a tag, since that can be even more revealing.

     

    Happy independence day to you too.

     

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 12:45 PM   in reply to johnnf

    John, I don't know how this relates to your initial problem but I'll think you'll find that the 'software' version 1.00 being referred to is the Firmware version of the camera. I've just checked a few recently taken images with a new compact and both the camera Firmware version and the 'software' field in Lightrooms metadata are both showing version 1.00

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 1:47 PM   in reply to johnnf

    John,

     

    I doubt your speculation is spot on, but then I don't really have a better theory.

     

    Metadata is wonky, and if Lr is only editor, then it's the likely culprit, although it may be worth updating the camera firmware if there is an update available.

     

    Ciao for now,

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 2:14 PM   in reply to johnnf

    johnnf wrote:

     

    The odd thing is that these photos have been assigned metadata in LR before without a problem, wonder if its a LR4.0 or 4.1 issue, its really gotten ridiculous since the 4.1 upgrade, whereas before I had maybe 20 pics doing tis, now its over 2000.

    It's possible. There were substantial changes to the metadata updating code in v4. I've been mostly editing raws with sidecars and haven't noticed this problem on any file yet. This is one of the reasons I'd prefer the option for Lr to not overwrite originals when updating metadata. If your metadata was being written to an xmp sidecar instead of the original jpeg, the jpegs would never have become corrupted. This is one of the smaller of many reasons..., still...

     

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 2:22 PM   in reply to johnnf

    Unfortunately, that option does not exist in Lightroom. But you can cast a vote for it here:

     

    http://feedback.photoshop.com/photoshop_family/topics/add_an_option_to _prevent_writing_back_into_input_files

     

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 16, 2012 3:37 AM   in reply to johnnf

    Hi John, I think that this may be the issue. Until recently I had Lightroom automatically update the metadata but I changed this setting,for performance reasons, and now do batch updates at the end of each session, using a smart collection to detect the images that need updating. It is only since making the change that I have been experiencing this problem. I only have 7 files that can't be updated. 6 of them are JPG and one is DNG.

     

    I'll try the export and reimport action and see if this will solve the problem.

     

    Peter

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 16, 2012 4:48 AM   in reply to Peter_McC

    I created a preset to export to same folder as original, same format as original, and stack with (above) original. I used this on the seven files, and it has solved the problem without losing any metadata.

     

    The jpegs had at some point been processed by Photoshop Elements as they were imported/edited using that application in 2010 but the metadata problem didn't show up until recently when I was making some adjustments in Lightroom. I somehow think this may be related to the GPS tag though I don't have sufficient evidence.

     

    The DNG file was strange in that it was straight the camera with no Lightroom adjustments, although I did add GPS info in the Map module. Anway it is now fixed as well as the jpegs.

     

    With this preset it would be possible quickly to fix a large number of image files. Just create a Smart Collection to display the problem files and run the preset on them all in one go. The only things that I am aware of that you would need to look out for are (1) if they are in a collection other than a smart collection, or have been published to a service like Flickr or to the Hard Disk the link will be broken, and (2) If you like to sort photos by date/time added, they will be out of the sequence (capture time is fine).

     

    When you are satisfied that this has worked OK then you can delete the images from the "Metadata Not Up To Date" smart collection. Select all, go to all photos, they should remain selected and press Delete. You could do a thousand in one go if you have the nerve for it

     

    Hope this helps.

     

    Peter

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points