Bridge CS3 not writing metadata to JPEG files

For the last couple of months (without my noticing until a couple days ago) all JPEG files that I have edited using Bridge CS3 (on Windows XP) do not have the metadata built into the file. Here are the symptoms: use "File Info" to edit the metadata for a JPEG file (i.e. add a title, description, copyright info, etc.), all appears normal, but if you do any of the following, the metadata you entered disappears:
- duplicate (the metadata does not exist in the duplicate file)
- move or copy to another folder
- open in Photoshop or any other software that can read metadata (File Info shows none of the metadata you entered)
- rebuild the cache for the folder
Strangely, the metadata still appears with the file when you look at it in Bridge as long as you don't do any of the above.
This is really awful as I've put a lot of time into entering this metadata for hundreds of files. Older files (pre-Nov 08) don't have this problem and the metadata is "sticky" and doesn't get deleted. So, somehow my Bridge CS3 got corrupted along the way.
Has anyone experienced this and more importantly -- do you have a solution? I've tried reseting all Bridge settings (but that of course purged the cache and deleted all my metadata.)

Hey,
There are various date/time fields shown in properties panel in Organizer. The dates mentioned in general section are read from OS whereas the dates in EXIF field are read from image's EXIF data. In EXIF data there are three date/time fields-
1. Date time- This date/time info shows date modified of EXIF properties. So when you are writing a tag into imags's IPTC, you are doing some change in EXIF data. Hence this date should change to date when you are writing a tag into IPTC.
2. Date time original - Represents date time when a image was shoot.
3. Date digitized - Represents the date when the image was digitized (in digital camers there is hardly some delay between an image is shoot and it is digitized. So this field is always same as date original).
So, in your scenario, Date time in EXIF should change whenever you are writing any tag into its IPTC.
Please let me know if you need more info on it.
~Andromeda

Similar Messages

Import metadata to jpeg files

i want to import massively metadata to jpeg files.
Can you help me to import metadata such as keywords.
I have already tried with xmp toolkit of Adobe but the metadata
is not readable from file info in Adobe Photoshop CS2
What seems to be the problem ?
I 'm using windows xp

I can probably help with this.
I have a script called TagFromFilename that can apply fill in the details that can be extracted from the file path if the .wavs are stored in the layout <Album Artist>\<Album>\[D-]## <Name>[ - <Artist>].<Ext> where D is an optional leading disc number and <Artist> is an optional trailing artist (otherwise both artist and album artist are set to the grandparent folder). You just need to make sure that before you add the tracks to iTunes, that it won't rename the files. You can do this by turning off the Keep option if the files are inside the media folder, or the copy option if the tracks are located outside.
Alternatively I have another script called ExportImport which allows for almost any editable to be adjusted, as long as you can export the internal track IDs of each track and then marry them up with the data you want to import. See Batch Add Comments Tag Solution? for a previous example of how if might be done. I'll gladly go into more detail if you tell me what fields you already have and what identifying information is present.
tt2

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).

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:

Compatibility between LR 1.3, ACR 4.3, PScs3, & Bridge CS3 to read metadata in psd or tiff files

I would like Bridge, ACR, and PS to be able to read the metadata of pds/tiff files that are "developed" in LR when the metadata has been saved to the file inside of LR. Currently BridgeCS3, ACR 4.3, and PS CS3 don't see these changes.
The only way around this that I have found is to export or edit in PS option - both of which give you a new file. I don't want a new file - I want the original file (psd tiff) that was imported into LR to have the ability to be updated with the changes made in LR.
I have found that when you export the psd from LR it essentially flatens the image so you will no longer have access to any layers done in PS. Depending on how many edits you perform, whether they are done LR or PS, and the order in which you do them in directly impacts the amount of edit files you will end up with for the same photo. Your edit information then becomes scattered amongst all the different files instead of having one central file as a repository for the edits so you can backtrack if you need to (like through layers in PS and the history panel in LR).
I really like the LR interface and being able to drag with the different tools directly on the photo to edit. I just would like those changes to be reflected (once metadata is saved) amongst the other programs as well.

I have tried saving XML files with Tiffs and the only way I have been able to get Bridge to see the metadata changes from LR's develop module is to export the file to PS or Bridge. On export the file becomes flattened so you do not have the access to any previous layers made in PS. Also once exported from LR, you are unable to see the files history log (LR) as to the changes made in LR that had been previously written to the metadata. And of course the flattened PS element so you have no way to back track in edits if you chose to do so.

Bridge CS3 Not Showing JPG/PSD Files

Running version 2.1.1.9 on a Mac G5 Dual 2.5 w/4.5 GB of Ram under OS 10.5.2.
BRidge for some reason today first stopped showing entire folders of JPGs files. Refreshing folders and restarting Bridge did not fix the problem. Rebooted the machine and now entire folders of PSD files are not being seen either.
How do I trash the prefs for Bridge and any other ideas on fixing this?
Thanks,
mark

Trashing prefs did not help. Did a complete reinstall and seems to be working again.

Nikon D60 - Bridge CS3 cannot write Metadata

{This is a follow on to thread: http://www.adobeforums.com/webx/.59b6704d/1} It appears that Bridge CS3 is unable to write some of the IPTC metadata to pictures taken with my Nikon D60. When trying to change some metadata in a file I get the message "There was an error writing metadata to <filename>" Strangely this does not happen with all metadata fields. For instance, I can change the IPTC Core "City" or "Location" and the change works just fine. However, if I try changing IPTC Core "Creator" or "Copyright Notice" I get that error. I have confirmed that the problem is with the D60 pictures, as it occurs in two different machines (Both CS3, one Vista, one XP). Both machines are able to edit other camera's pictures OK. All files are in JPEG format, I have not tried anything in RAW format. I did find in a completely different forum (for BreezeBrowser, which I've never used) a reference to a similar problem. At least in that forum they mention that the Nikon D60 uses a "different" way of storing metadata which leads to the problem. BreezeBrowser will release a new version to address this issue. Any idea what the solution might be for Bridge and other Adobe products? Thanks! Carlos

I don't have my camera with me at the moment, so I'll have to shoot in NEF later. However, just for kicks I downloaded the latest version of ACR and checked against my current version. It appears to be the same (same size, same timestamp). I even replaced it, per the instructions with the download. No love.
As mentioned in my original post, the issue is limited to a few fields, in particular "Creator" (XMP) or "By-line" (IPTC). I went and added new data to this field using ExifTool. I added it to both IPTC and XMP fields since I know Bridge synchronizes them. The change took, and Bridge noticed it. But now Bridge will not let me modify any XMP/IPTC metadata. It won't even let me change the rating of the file!
I'm really at a loss here. I've searched through other threads and haven't found anything to enlighten me.

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 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.

Bridge CS3 not displaying .PNG thumbnails

This behavior started about 2 months ago and I cannot figure what changed or what to do to get rid of the generic .PNG icons and get back to the image thumbnails. It's not isolated to Photoshop generated .PNG's. Any app I have that can save in the .PNG format will appear as a generic icon in Bridge CS3.
.PNG's that were uploaded to our server prior to around mid-Feruary all have the proper thumbnails. Currently, replacing them or uploading the same file from before February produces the generic icon. Same thing in both in the main view and the Preview window.
The only thing that has changed on my machine between now and February was an OS bump from 10.6.1 to 10.6.3.
Every other format displays correct thumbnails. I've tried just about every suggestion dealing with missing thumbnails from the various "no thumbnail" posts in this forum...and still no luck. Does anyone have a suggestion or two...or three, that might help me clear this .PNG problem up? It's driving me bats trying to identify images.

I've tried just about every suggestion dealing with missing thumbnails from
the various "no thumbnail" posts in this forum...and still no luck.
Could you specify on that, meaning also purge cache for selection. Using
tool menu-cache, use the filter menu to select only PNG files for faster
approach.
And you may not like this but using a more then 3 year old app on a new
(intel based and 64 bit OS system) might also not be the best route. CS5 is
just out now and rebuild for 64 bit systems like Snow Leopard is.
Also keep in mind CS6 will be your last option to upgrade according to the
Adobe upgrade policy, after this you will need a new full license.

Index of EXIF-metadata from jpeg files by TREX

Hello,
I have the following scenario:
We have a central fileserver with a lot of marketing pictures. Our marketing people are looking for a solution to search pictures by data stored in the EXIF-metadata of the jpeg-files.
So I like to integrate this fileserver as a repository in KM, set up an index and let TREX do the search (as of note 663630 TREX can search the EXIF-Data of JPEG-Files).
As goodie I want to give the marketing people the possibility to browse through the pictures in an image gallery. This gallery should be consisting of a query-based taxonomy where all the pictures are sorted by special EXIF-data (e.g. name of the photographer).
Until now I have integrated the fileserver (as a FS-Repository) and create an index.
Before index creation I added the mime-type image/jpeg to the TREXValidMimeTypes.ini and restarted TREX.
After indexing the pictures could be found by its name, but the EXIF-data is not indexed.
Now my question:
Why TREX doesnt index the EXIF-metadata?
And how can I use the EXIF-data in an taxonomy?
System:
EP6.0 on WebAS 6.40 SPS16
TREX SPS16 Patch 2
KMC SPS16 Patch 2
Greetings from Berlin, Germany
Jens

Greetings to Berlin,
when triggered by KM, TREX will only index metadata that is known to KM as KM propertis.
I do not know in detail and am not at all sure, but you could try to create custom properties in KM that are called exactly like your EXIF-metadata, set them to "indexable", not fill them with values on KM side and then try again.
You may want to try this for just one of the EXIF-metadata as a test.
Even if that works somehow, the maximum result is:
- Property name existent in KM
- Property thus searchable an classifiable
- BUT property values will not show up in KM, as they will remain known only to TREX
Regards, Karsten

Problem writing metadata to Jpegs originating from Macs

Everything works great when trying to write metadata to a JPEG that originates from a PC. But since my company runs a website, we have to be able to handle JPEGs that come from Macs. I've run across an issue where trying to write metadata to a Mac-JEPG causes an error.
Specifically it occurs in TIFF_MemoryReader::ParseMemoryStream(*), where the code tries to find the tnailIFDOffset value. For PC-JPEGs, it returns a sensible value, but with Mac-JPEGS, the value is 0x65005020. Which is clearly beyond the image size.
The result being that no metadata is saved to the image. A workaround is to download the image, open in a PC Photoshop, and try again with that new image. This suggests the problem is in the file structure of Mac-JPEGs.
Does the toolkit support these images? Is there a better code-centric workaround? Do I have to re-encode the image to PC format before I use the toolkit?

Hi,
I have just started working with XMP data manipulation using XMP toolkit.
I am able to read and update XMP data successfully, but not getting an idea to write back to JPEG file.
Is there any API in XMP Toolkit to perform this task?
If not, Please give me some guidelines for this....
Thanks.

Bridge won't save metadata for .mov files

Hi.
I could be trying to do something that Bridge can't do (though I have read that it should). I am trying to add metadata to .mov files. Bridge allows me to enter the text both under 'File info' and in the Metadada IPTC Core fields, however when I 'apply' or click OK they don't save.
Well, in the IPTC Core when I click 'apply' they are there until I select another file then go back and they aren't.
I am using Bridge CS5 on a PC with XP.
Thanks

Thanks Curt Y. Under 'run as' there was two options both of which were noted as administrator - though I could only use one as we don't have the password for the other. I'm not using an external drive.
The strange thing is that there is no problem applying the metadata to images, just mov files.

Bridge CS3: Not importing clips into Premiere CS3

One of the videos on the Adobe site shows someone right-clicking a movie (MOV, I think) and choosing the option to "Open with Premiere Pro CS3".
I created a blank test Premiere CS3 project. From Bridge, if I right-click an AVI and choose to "Open with Premiere Pro CS3", focus switches to Premiere, but no clip is imported.
I'm using Windows Vista.
Any ideas on this one?

Jim, I *am* using Bridge CS3. Version 2.1.0.100
Windows Vista Ultimate
Eddie, yes the video tutorial shows how to open MOV video clips from Bridge CS3 into Premiere. My source clips are Windows AVIs. When I right click a clip in Bridge CS3 and choose the option to open with Premiere (actually the option is "Open With > Adobe Premiere Pro"), Premiere Pro CS3 gets focus (or opens if it's not already open), but no clip is imported.
Interestingly, I got hold of a sample MOV file (CheeziPuffs.mov that appears in the Adobe samples). When I right-click that file in Bridge, I am only given the option to open with QuickTime player. Premiere does not even feature as an option in the context menu.
When I ran up Bridge for the 1st time followin Premiere Pro CS3 and Encore CS3 installation, it popped up a dialog box and said that the new programs had been detected and did I want to register them with Bridge (or words to that effect), which I did. So far, so good. But my AVIs just plain won't open in Premiere when I ask Bridge to do so.

LR3 not writing metadata to xmp

Preferences set to automatically write changes to xmp file. LR3 has stopped writing changes to xmp.
When I choose a thumbnail and click the "!" in upper right corner + click "Retry Metadata Export", I get this message: "Could not write metadata. Your disk has less than 1 gigabyte of space left".
This is correct, as there is 200mb free space on the particular disk, but I would think this would be sufficient. So question is: how much free disk space do I need for LR3 to continue to automatically write metadata to xmp?

From the message you have received and the statement made in the requirements for running LR on the Lightroom home page
minimum1GB of available hard-disk space
it would seem likely that 1 GB is the minimum. However I would suggest rather a great amount of free hard disk space is required in order for LR to function efficiently. But the minimum is pretty clear.Once you go below this you will experience problems and not just with writing metadata to file, but writing changes to the catalog itself if that is located on a disk with less than the minimum requirements The metadata once written takes up very little space, but the process of writing it can require space on disk for temporary files etc. Just make sure you have lots of spare capacity on any drive you use with LR.

Bridge CS3 not writing metadata to JPEG files

Similar Messages

Maybe you are looking for