Writing metadata to originals is corrupting my files.

Hey guys,
I am using Aperture 3.3 with 10.7.4. I am importing my files, but they are not being copied into the library. I am leaving them where they are. Next I add keywords to them and then use the command 'Write IPTC metadata to originals'. Doing this is corrupting my files. I am getting an unsupported file format warning in place of the files. When I go to the files in Finder, the files are junk. Thankfully I backup my photos before doing anything to them so no harm done this time.
Thanks
Jason

Hey Owen,
Thanks for replying. I just now tried again and the same thing happened. Now the first time I tried Aperture I stopped thinking something was wrong and I didn't want to mess up my files so I just continued using Picasa and iPhoto. This time I did the same thing, but came here and posted my problem. And after reading your reply I decided I probably should try some other folders full of photos. And guess what....no problems. It appears this one particular folder full of photos is somehow messed up and when I write the metadata back to the files they get corrupt. They are jpgs from 2000 and the camera was a Toshiba PDR-M3. Now other photos taken with this camera are working so it must be something with this set of photos.
Thanks again.
Jason

Similar Messages

Lighroom 3 writing metadata to image files?

Hi,
I have been wondering why my backups (differential) weregetting larger than they should, and I noticed that some of the files (.psd and .jpg, and mayde few .tiff) were modified. Interestingly, I do not see this happening to cr2-files, that I mostly use. After trying to figure out what's going on I noticed that corresponding xmp-files were modified also. This is not the issue due to their small size, but still I had not edited images that were changed for quite a while.
Change that I see in xmp-files is rather large, and presumably related to Adobe's change in xmp-data structure. Eg.
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c007 1.136881, 2010/06/10-18:11:35
">
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40
">
In addition to the sample above, whole xmp structure is changed. So I presume that maybe LR is writing metadata chages to xmp in the background?
What I find disturbing is that when checking changed jpg files, I saw the similar data written into the jpg files also (files were created with oldish Canon 20D, and not edited for quite a while). These are examples from changed jpg-files (not the same from which the abone xmp-data change was taken, but similar change is visible in the corresponding XMP):
Also jpg-file from offset 0x04 was changed from "50 60" to "51 18". Also offset 0x10 was changed (16 bits).
I have Lightroom configuration option "Include develope settings in Metadata Inside JPEG, TIFF and PSD Files" not selected. The option "Automatically write changes to XMP" is selected. To my understanding neither of these should not have impact to the issue. Is there something else I should check?
Change is made most likely by Lightroom 3.5 version, and has not occurred with previous versions. I have not notices this happening with 3.6, but I have been using it only few weeks. Is this known issue with previous version 3.5, or am I missing something obvious?
System running is Windows 7 pro 64bit. I have not have any issues with LR lately, except crashes that I white about a week ago.
Any advice on what's going on?

So I was missing something. Thank you Hal.
I had not realised that XMP goes inside of actual image files with those file types. Obviously my new backup routine spotted that, as I was on backuping only modified/new files.
I would much prefer that also with above mentioned file types XMP-data would be stored in sidecar files instead of modifying the original file. To support this there are two arguments that I think are valid:
1) modification of the file is always risky (and spesifically, with image originals I prefer to avoid that),
2) modification leads to the fact that "smarter" backup strategies relying on "full backup" supported with differential or incremental backups lead to unnecessary long backuptimes and media consumption.
That said, I prefer to have XMP-data also outside of the catalog so that other tools can also utilise it (further, in addition to the catalog with sidecars I have sort of failover approach, and some of you may now say "belt and syspenders" after mentioning backups...).
Is there a way to have all file types to utilise sidecars rather that modifying original file?

Error writing metadata to file

I am getting constant error messages from Bridge CS4 when trying to add keywords to my images "Error Writing Metadata to file "XXXX". It's very annoying and destroying my workflow. I have tried resetting original preferences, and using purge cashe. Finally I reorganized my entire folder structure which seemed to make the problem less frequent.
The circumstance that makes this error pop up most frequently is when I add keywords to a handful of files that already have another keyword assigned. Quitting the folder and then re-entering it solves the problem for the photos with the current error, but then 20 or so photos later I get the error message again.
Any Fixes?

A new suspicion was that the read/write data might be different for the images files themselves than it was for the folder holding them. So I applied the read/write permission to the image files themselves. No luck though. Still getting "Error writing metadata to file xxxx" Errors. Would love to be spending all this time editing photos instead of chasing down bugs. Brand new MacBook Pro and I'm spending more time trying to fix errors than using the software. ::sigh::

Error writing metadata to any file except jpegs

Hi all,
A coworker and I have been assigned the job of keywording all the photos in our database. We aren't photographers and are only messing with the keyword metadata on the photos.
But we've been having a consistent problem with Bridge CS4. When I attempt to add keywords to any file format except jpeg, it gives me an error message "Error writing metadata to " and the filename. Then to make matters even worse, Bridge continues trying to add the metadata to the same images over and over again until I do a forced shutdown.
We're running Bridge on a network with exported cache. The only thing I have found as a possible solution is a permissions setting problem, but I can't find any way to check on that.
Any help you can offer would be great. Thanks!

I had this same problem. This was the solution for me in my CS4.
Go to Bridge
Go to Preferences
Go to Metadata
Make sure IPTC and Keywords are checked.
This will allow you to add keywords to your metadata in bridge.
Here it is not checked:
Here it is checked:

Faillure writing metadata to some DNG files

I'm having a problem writing metadata to some dng files using Lightroom 2.6.1. When I try to apply a metadata template to a batch of files most of them get changes but a few don't. This only effects DNG files so far JPEG and TIFF seem to be OK. I have tried running the problem files through DNG converter and the new files have the same problem. Lightroom won't write to them.
I can change the metadata of these files from Bridge. The changes then appear properly in Lightroom. Afterwards I can change the metadata again from Lightroom.
I'm working on a MacBook Pro (Late 2008) and running OS 10.6.2.

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

Errors when writing metadata to files on Windows Server

Good day!
I have an iMac running OSX 10.9 (Maverick) and Lightroom 5.2.
My catalog is on the local iMac drive, and the images are on SMB shared drive (handled by Windows 2012 server).
I decided to do the final layout of my album using InDesign, and for that I needed to access to images using Bridge. So selected all the images (the rated once...) and issue a Metadata/Save command.
The system came back with errors on many of the files (such as Photos are read only, and unknown errors).
Retrying to save the metadata on image that was flagged with an error usually (but not always) worked.
I tried to select save the metadata for few (6) images in a time, many times it was ok, but sometimes, one or two of them failed (and retrying again usually solved the problem).
It looks to me like a timing related issue.
Any ideas?
(After spending about an hour on this, I have exported the images to my local drive...). In general I don't have similar problems with other apps.
Any ideas?
Yuval

I Yuval
I'm experiencing more or less the same behavior (see Read-only error when writing metadata to file over network (Synology DS1315+ using AFP) ). For me however, the problem is more pronounced if I use the AFP protocol and is better (I think as you described) if I use SMB (all done on a Synology DS1315+). With SMB it most often works but in very rare cases I also get the "read only" message!
Do you have solution to this? Or are you stuck as I am?
Cheers, Chris

Error when Writing Metadata to Files in Bridge (Mac) but not in Bridge (PC)

We get an error when writing metadata to files in Bridge (Mac) but not in Bridge (PC). In the same drive and folder, the PC can successfully write a keyword to a file on the PC, where the Mac returns an error. I have researched this at the Adobe Knowledgebase, but their answer seemed to indicate it was a global issue, and we don't see that behavior on the PC.
The client is a Mac of course, and the server volume is a Windows share volume. The Mac is bound to AD, and the domain\username and username formats have both been tried when logging in, but you receive the error in both.
Any help would be appreciated.
Thanks!
Rich Oliver

Hi, I'm having the same problem using FreeNAS (which uses Samba and Netatalk in the backend), but I tried with both AFP and SMB on Mavericks and Yosemite, I still have the same issue. I think it might be a timing issue with how lightroom interact with a slower write delay using network shares. I suggest you also chime into this thread: Lightroom 5 can't write metadata to DNG files I really hope this is resolved as this is impacting my productivity as I moved my workflow to my Macbook with a shared NAS.

Error writing metadata to photo files

I am using CS6 and have moved to a new computer with a clean install of CS6 under Windows 8.1. In the past I had no problem using Bridge to append my personal metadata file to photos (RAW files, NEF). With the new installation I am getting the repeated message " Error writing data to...." even after trying all the " fixes" suggested by the help files.
Can anyone help me to resolve this issue?
Thanks.

I found an answer, somewhat different. I did more search and found that you need to be administrator and for Adobe to see you as administrator, for many functions to work, such as writing metadata to files or putting stars on photos to rank them. I could do neither.
THEN, I tried opening Bridge by right clicking on the icon, and opening the file as administrator (a choice). Everything worked. So, why was Adobe not seeing me as administrator. My user account was the only account on the computer and has administrator privileges.
I started doing searches on that, and stumbled, yes stumbled, on what I think is a solution to that situation.
I set up my account so that I needed a password to log in. Once I did that, Bridge worked fine. But, I still did not want that additional startup step. You can then back to change password and leave the password entries blank. Then, the computer starts up with blank passwords, zips past the welcome screen directly to the desktop, and Windows now sees me as the administrator, and so does Adobe.
Keep you fingers crossed folks, this seems to be working.

Writing metadata to media-file

Hello everybody,
I'm developing an application for viewing/editing metadata of media files (mainly MP3). Therefore I'm using JavaFX 2.2.
Viewing works like a charm, but I'm currently stuck at the editing part.
I've tried media.getmetadata().put("string", object) but this throws only an UnsupportedOperationException.
Am I doing anything wrong? Or is there any other way writing metadata to media files without using external libraries?
Thank you in advance

is there any other way writing metadata to media files without using external libraries? No.
JavaFX media libraries are currently only support playback and not editing (even for metadata).

DNG file modification date not changed by writing metadata?

I use LR 2.7 on Windows XP.   To my surprise, I just noticed that writing metadata updates (e.g., new keywords) from LR to the DNG files does NOT appear to update the file modification date, which suggests obvious issues for backup strategies (yes, I understand that a changed modification date introduces other backup issues).   I have verfifed that the metatdata does indeed change in the DNG files, so I am mystified.   Can someone shed some light on this?   Thanks.
js
www.johnshorephoto.com

Yes, I explicitely invoke "save metadata to file".   Furthemore, I have checked the behavior by (a) modifying DNGs in LR; (b) saving the metatdata to the DNG; (c) creating a new LR catalog and importing the revised DNGs.    The metadata changes do show up in the re-imported DNGs (and the metadata field "Metadata Date" correctly shows the recent change). Morevover, the file sizes do change (wth the metadata changes) even though the modification dates shown in windows explorer do not change.
However, I just redid the experiment to double check, and discovered an important clue - the mysterious behavior occurs when the DNG files are on a NAS device (in particular a Netgear ReadyNAS Duo.   To summarize:
     - When the DNG files are on a local hard drive, the file modification dates change as expected
     - When the DNG files are non local (i.e., on the network but on a NAS device), the file modification dates do not change even though the file sizes do change;
What's more, I see the same behavior when accessing the DNGs via Adobe Bridge (CS5) - i.e., if I change the metadata, I'm asked if I want to apply the metadata changes to the DNG, and I say yes (and confirm by looking via Bridge at a copy of the changed file).   On a local disk, the file modificaiton dates change (as do the modification date displayed in Bridge), but if the files are on the NAS, the modification dates do not.
Any additional thoughts?
js

Problems writing metadata in Bridge CS4

Anyone seeing this? When I add metadata to my RAW images in Bridge, I frequently get an "Error writing metadata" message. If I have selected a folder full of images, say 700 images, I get 700 error messages. The only option is to force quit.
The problem seems to happen reliably if thumbnails or preview images are still being created, though I've had it happen with a stable folder.
Another consequence of the force quit under these circumstances is that I lose all my image adjustments on my raw files. It seems the sidecar .xml files get corrupted.
I'm on Mac 10.4.11, and the problem happens on both the desktop and the laptop.

That explains why the problem is worse on the laptop. Here's what I have in the deesktop Mac Pro, which is only 15 months old:
ATI Radeon X1900 XT:
Chipset Model: ATY,RadeonX1900
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: ATI (0x1002)
Device ID: 0x7249
Revision ID: 0x0000
ROM Revision: 113-A52027-140
EFI Driver Version: 01.00.140

Locked Catalog, Corrupt & Locked files

I'm on Windows Vista, Lightroom 2.2.
Seem to be having trouble opening a catalog (message indicates that it is locked and not editable). Ive been using the same catalog for some months and haven't had any problems till I started on new computer.
Everytime I open lightroom fresh for the day it locks me out of the catalog.
Also problems with corrupt files when renaming, editing in photoshop and re-sizing via a photoshop action.
These problems have only started since using Lightroom.
I have reinstalled lightroom and added the 2.2 version, still seem to be having the same problems.
Any help would be appreciated.
Cheers,
Brent

jthinpa wrote:
Do you have other suggestions? I have three other pieces of information about the problem.
1. I have other catalogs that work just fine.
2. I see a message that says "Indexes failed to get updated in the database".
3. I can select an image and send it to Editor and make changes to image; but when I try to save changes, the edited image does not go to Organizer. I get a message that there is a new image in watched files, but when I try to import, it fails.
Please advise; this is my major photo catalog and I can't do anything with it.
Thanks,
John
That's not good news...
1 - a confirmation the catalog is corrupt
2 - I have never seen this message. Did you get it after trying to 'repair' or 'optimize' the database? It's important to know what exactly triggers this message.
3 - There is an acknowledged bug in PSE12 :
http://forums.adobe.com/thread/1328850
So, try 'repair' if you have not yet done it,
Then follow the workaround described in the above link to delete 'ElementsAutoAnalyzer.exe', reboot and check that it is no longer working in the background.
When in that catalog, are there operations you can still do such as 'writing metadata to files'?

How to fix a corrupt .avi file (from capture in CS3)?

So I was recording a VERY long meeting at work and recorded it to my PC via Premiere. Since the recording was unattended, the file size is 275GB! I didn't really think anything would go wrong since I have recorded large .avi files in the past.
Well when I try to import the .avi or play it in media player, it is saying it is corrupt/wrong file format. I tried a few avi repair utilities and none of them fixed it. I'm guessing the avi headers are missing, but I thought Premiere wrote progressive .avi files (at least their export is progressive and valid while its writing).
Any help to repair salvage the avi? I only need about 50% of the actual content.

>wonder why you can view a video that is currently being exported
Seeing what the computer is
DOING while it is doing it is really not the same as trying to open a file after the fact
I have an inexpensive standalone DVD recorder to be able to move a movie from a DirecTv Tivo box in one part of the house to a DVD player in another part of the house
I can watch the video on the TV while it is playing from the DTivo box to the DVD recorder
If I do not properly CLOSE the disc when the recording is done, the DVD will not play
An improperly closed file is, as you found, not going to work
As I said, my best GUESS is that hitting the full point on the drive caused needed information to not be written to the header (or file end) and now any software you use to try and play or edit that file doesn't know what the file
IS because the identity is lost
I will guess that is also why the AVI repair programs you've tried won't work... they need to have some starting information to work, otherwise the contents of the file are just so much random "noise"

Bridge 4.1.0.54: Error writing Metadata to some [....].jpg

I am sorting my files (.JPG) with bridge. Some files just can't get rated (bridge fails without giving me an error), and if I try to set other metadata (like keywords), bridge tells me "There was an error writing metadata to ".....JPG".
I have full access to the folder, it is an internal disk, the files are not locked. It affects about 5% of all files - this is the second shooting (&folder) where I have this problem. I don't see any differences between the files I can change and the ones where I can't.
I can rename the file with bridge, but that does change nothing. I tried purging the cache, it changed nothing.
I just found out: I can change the tags with Windows Explorer, Bridge does show them, and afterwards I can change them with bridge too. Someone got an Idea how I can avoid this step?
[Win7Pro x64, i7]

Jingshu Li wrote:
I tested your issue but haven't reproduced yet. Could you please provide more info?
1. You mentioned usually you will select tens of images (in the smart collection or search result) and apply metadata, and then you get the error. I'm wondering can you apply metadata successfully if you only select one image and then apply metadata?
2. Before you apply metadata, do you wait for the images thumbnails genaration complete?
3. Can you apply metadata successfully if you selete the images at their real location (not in the smart collection or search result?)
4. Your OS info, mac or win, and version?
I just set up a quick test, and it failed immediately. I haven't even been using Bridge today...
The computer runs CS5 on Windows 7 Professional 64-bit. I used to run CS3/CS4 on a different computer loaded with Windows XP Professional. I'm always up-to-date with OS/driver/application updates. Both systems exhibited the same problem.
The raw image 3-tier folder hierarcy is on a separate internal drive: P:\Camera\2011\08-15 Location\, P:\Camera\2011\08-16 Location\, etc.
The Bridge cache is on a separate internal drive: T:\BridgeCS5\, Camera Raw's cache is in T:\CameraRaw\.
The images are mostly Nikon NEF (D300), and ACR saves settings to 'sidecar' files. Most of the images have settings, and many have crops.
I created a new Collection, and dragged the contents of 7 image folders into it - a total of 407 images. None of these files have had keywords applied, but most had been worked in Camera Raw already. After waiting for thumbnail/preview generation to finish, I selected the collection, created a new sub-keyword, selected all images in the collection, and ticked the new keyword (automatically ticking the parent keyword). Within a few seconds, I started getting the "Error writing metadata..." warnings, and had to OK 15 images.
The failed images were spread across 3 of the 7 selected directories. Trying the same thing 30 minutes later resulted in the same errors. Trying each failed image individually gave the same error (either as part of the collection, or from it's own folder).
I opened one of the problem images in Camera Raw, and adjusted Blacks, clicking Done to save the settings. I then tried to apply the keywords again. This time it worked.
To answer your questions directly:
1. I have never experienced this problem keywording files individually (apart from after the errors, as mentioned above), but then I wouldn't usually be selecting lots of images to keyword individual images.
2. Yes, I always wait for the spinning circles to disappear, sometimes even longer!
3. I just tried applying keywords to a single folder of 102 images, and 2 failed to update. So the answer is No, it fails at real locations too.
4. Windows 7 Professional 64-bit, running on Intel Core2 Duo and 4GB RAM. Same thing happened before on a Windows XP Professional PC, running on an Intel Pentium 4 and 2GB RAM and a single hard drive.
I hope that helps.

Writing metadata to Nikon raw

Given the
recent statement by Nikon and Adobe and the provision of a mini SDK, does this allow the possibility to write metadata from Bridge to Nikon raw files? If so, I'd be enthusiastic to see it implemented.

Then why does anyone buy Nikon Capture or use programs like iView to write metadata to raw files? Granted, anyone with any sense also ensures they have a pristine backup.
Clearly it would be a risk for Adobe to do it blind (iView use the full SDK) but if the mini SDK doesn't allow the possibility of writing metadata, its desirability seems pretty moot.

Writing metadata to originals is corrupting my files.

Similar Messages

Maybe you are looking for