Save As - XMP

I've noticed that when I perform a Save As on a file
initially, there is no option for XMP. XMP appears to be included
automatically. When I perform Save As again on the file I then have
an option to include/omit XMP.
Is there any kind of preference to disable XMP by default? I
do NOT want XMP file saved. It drives me bonkers to save multiple
files that I plan to use where size is the key only to find a few
have ballooned in size because of the added XMP data.
Thanks!

chris134 wrote:
> I've noticed that when I perform a Save As on a file
initially, there is no
> option for XMP. XMP appears to be included
automatically. When I perform Save
> As again on the file I then have an option to
include/omit XMP.
>
>
Is there any kind of preference to disable XMP by default? I
do NOT
> want XMP file saved. It drives me bonkers to save
multiple files that I plan
> to use where size is the key only to find a few have
ballooned in size because
> of the added XMP data. Thanks!
>
If you export rather than save, XMP data is stripped out
Jim Babbage - .:Community MX:. & .:Adobe Community
Expert:.
http://www.communityMX.com/
CommunityMX - Free Resources:
http://www.communitymx.com/free.cfm
.:Adobe Community Expert for Fireworks:.
Adobe Community Expert
http://tinyurl.com/2a7dyp
.:Author:.
Lynda.com -
http://movielibrary.lynda.com/authors/author/?aid=188
Peachpit Press -
http://www.peachpit.com/authors/bio.aspx?a=d98ed798-5ef0-45a8-a70d-4b35fa14c9a4
Layers Magazine -
http://www.layersmagazine.com/author/jim-babbage

Similar Messages

LR4 save to xmp has the wrong timezone adjustment for xmp:MetadataDate

After installing LR4 and converting a catalogue, I saved the metadata for an image in LR4 and did the same for the same image in LR3.6 (on a different machine).
The value for xmp:MetadataDate written by LR4 seems to be wrong. My timezone is UTC+8h for Western Australia. Here is an extract from the xmp file written by LR4:
   xmp:CreatorTool="Ver.1.00"
   xmp:ModifyDate="2012-03-03T18:10:27.00"
   xmp:CreateDate="2012-03-03T18:10:27.00"
   xmp:MetadataDate="2012-03-09T08:03:17+08:00"
Note the MetadataDate is my local time + 8h (I saved just after 8am). The timezone offset should be -8h.
On my laptop, I repeated this with LR3.6 and the ame extract from the xmp file it wrote is:
   xmp:CreatorTool="Ver.1.00"
   xmp:ModifyDate="2012-03-09T08:54:51.475-08:00"
   xmp:CreateDate="2012-03-03T18:10:27.00"
   xmp:MetadataDate="2012-03-09T08:54:51.475-08:00"
LR3.6 adjusts both the ModifyDate and the MetadataDate by -8h, which is correct if the time is meant to be UTC.
Why LR3.6 has changed the ModifyDate to the time that the xmp file was written, I'm not sure - LR$ doesn't and I wouldn't expect it to either since the raw file (NEF in my case) isn't modified.
Looks like a bug in LR4 regarding the MetadataDate written to the xmp file.

I'm confused -- you say "my timezone is UTC+8h for Western Australia". That is, if it's 13:00 local time in London, it is 21:00 local time in Western Australia.
Thus, 08:00 local time in Western Australia should appear in the XMP timestamp as 08:00:00+08:00. (That's how the timestamps are defined.) So it sure seems to me that LR 4 is doing the right thing.
LR 3.5 had a bug in which the signs in the XMP:MetadataData fields got reversed:
http://feedback.photoshop.com/photoshop_family/topics/xmp_metadatadate_has_wrong_time_zone
Though LR 3.6 claimed to have fixed that bug, I didn't verify, and I don't see anyone else who verified.

Can I save PS edits in an xmp file to be read by LR?

The reason I ask this is I have hundreds of photos that were taken on a 5D with a scratched filter, so I am treating the marks as dust bunnies and getting rid of them in the same way, using spot healing and for the scratches, whtever the feature is called where you use the spot healing brush but you 'draw lines'.
However I am one of the many who suffer appalling performance in Lightroom edits so after maybe 20 spot heals the computer slows down so much so as to be unusable. So I then send the file into PS/CS6 as the same doesn't happen there.
I quickly fix all my spots and scratches and then I appear to only have the option of saving the file as a TIF back to LR.
What I'd love to do is save the xmp file, and then have LR update the image given those xmp changes.
Is this possible or do I have to continue to have the extra TIF file?

Hmmm I can't replicate what I did now. The problem with using ACR is that the spot removal tool is just that, a spot. It doesn't allow the removal of scratches, which is the whole point of what I'm doing. If I hit 'Done' after healing a spot it does indeed write to the xmp file, but then I hvae to delete the preview and refresh in order to see the change. I could cope with that if the ACR spot removal was the same tool as in LR, where you can do scratches as well.
Oh well, I'm halfway there so should be grateful for that. Cheers.

Acrobat X save metadata to XMP file problem

I am having no luck saving metadata from a PDF to an XMP file using Acrobat X. This has worked properly for me in previous versions of Acrobat, but since upgrading to Acrobat X 10.1.7 the XMP file is given no name automatically, and when saved is zero K and contains no data. I am running on a Mac Pro 3,1 using OS X 10.7.4. I have found only one other mention of this problem in the forum, but it was not answered clearly. Is anyone else having this problem?
Many thanks for any assistance with this!
2014 Update: Still no solution to this. Am I alone with this problem?

Hi Steve,
Thanks for your time on this. Our workflow includes having to repurpose xmp metadata from existing PDFs and apply it to new PDFs. This involves going to the "Document Properties" dialogue, selecting "Description", then "Additional Metadata". From the sidebar of the Additional Metadata dialogue, we would choose the "Advanced" option, which would then allow us to either "Save" the xmp data to a file, or "Replace" the PDF's current metadata with data from an existing xmp file.
This worked perfectly up until we moved to Acrobat X, at which point we were no longer able to save the xmp data to a file. We are able to use the Replace function, but it's critical that we also are able to Save the data.
As David noted, we are also able to successfully Save an xmp file using Acrobat XI Pro running on Windows 7. However, all our production work is done on our Macs, so we hope to regain this capability on the Mac version of Acrobat X Pro or XI Pro.
Cheers and thanks.

Save XMP file for an entire folder?

I have my automatic XMP saving turned off. Now I want to selectively be able to save my XMP files as needed. I thought that I used to be able to save the XMP files for all the photos in a folder at once. however, now it seems that I can only save the XMP file for only the actively viewed photo (regardless of how many in the folder are actually selected). Does anyone know how to do this?
(Aslo, what happens when there are mixed JPG and RAW files selected when I want to save the XMP data?)
Thanks,
Nick

Nick,
CRTL+A will select all photos in a folder. The CRTL+S will do the xmp writing for all photos that need it. It goes pretty quickly. You can watch the progress bar in the upper left.
Mel

Are snapshots required to save develop settings to XMP?

Here's the scenario: I typically make my changes in post-processing such as contrast, exposure etc, in the develop settings. When I'm done, I create a snapshot called "done". I do this because I fear that without creating a snapshot, the develop settings might not be written into the XMP, so that if I ever have to recover those settings, (say if I transfer a photo to my laptop, and the corresponding XMP file), they'd be gone without a snapshot. Anyone know if this is true?

The way Lightroom works, your develop settings are saved to the database. Every time in the future that you return to a photo and go into Develop Module, your settings are there for you to see (and change). Your develop history and metadata is also there. You do not have to turn on any options in Lightroom for this to happen, it is automatic, and cannot be turned off.
Thus, there is no need to write your develop settings to xmp. You can if you want to, but this does not happen automatically. You can Ctrl-S to save your metadata (including develop settings) to the xmp. You can turn it on so writing the edit settings and other metadata happens automatically (Edit->Catalog Settings->Metadata, check Automatically Write Settings to XMP) When you save to XMP, your final edit settings are saved, but not the history of steps that you followed to arrive at the final edited position. The primary reason you would save to XMP is so that your metadata and edits can be read by other applications; however there are only a few programs that can read and interpret your edits that are stored in XMP (Lightroom, Photoshop, Photoshop Elements and Bridge); many other programs can read the metadata (like keywords and captions). If you are not interested in communicating with other programs, there is no need at all to save your metadata and edits to XMP.
Creating a snapshot does not cause anything to be written to XMP, and in fact if you choose to write your data to XMP, you do not need a snapshot to save your develop settings. Everything gets written without a snapshot, if you choose to write to XMP, and everything gets saved to the database without a snapshot being created.
In general, you do not need snapshots for the purpose you are using them for. Snapshots are an optional way of saving conditions along the way to your final edit.
Please read The Lightroom Starter Kit to learn more about how Lightroom operates, as quite honestly, you seem confused about how Lightroom works.

[JS][CS5] - Save XMP thumbnails by artboard?

Is it possible to save illustrator XMP thumbnail previews by artboard? It seems like Illustrator saves a single thumbnail with all art regardless of the number of artboards.
Does anyone know if there is a property that can be set to save multiple thumbnails to the XMP packet by artboard when saving to a native Illustrator file?

Sorry I've not actually looked that far yet… I know that ID has the preference to do this as I use it. But AI has not, it may be possible to add custom XMP to include this and that has been on my to do list for a while… What is using this XMP?

XMP files not moved

I have searched the fourm and there are a couple of responses to similar questions, but I I can't seen to find how to move the XMP files when I drag a folder of photos from one external drive to another external drive.
I drag the folder with 500 photos over the photos go but I get a message saying the following files did not transfer and its all my XMP files for the images I transfered. How can I get the folders and the edits to transfer from a 500gb to a 4TB external hard drive
Thank you in advanced
Joe Cosentino

Lr creates XMP-files only for Raw images - although the box in >catalog Settings >Metadata tab speaks of " ... write changes to XMP>.
But true XMP-files in the sense of side-car files, i.e a separate little file that sites next to its image file are only created in the case of Raw images. In the case of JPGs, TIFFs, PSDs the changes are written into the header of the file (but not in the image pixels!) and a separate xmp-file is not created.
Lr saves changes to XMP (i.e. writes the changes into the header of JPGs, TIFFs, PSDs and creates separate "true" xmp-files for Raw images) only if you do this either manually (by pressing Ctrl / Cmd + S / or doing >Metadata >Save Metadata to file) or by checking the box <Automatically write changes to XMP> in >Catalog Settings >Metadata tab.
I you do neither of these, Lr will not save to XMP and will not create xmp side-car files for Raw images.
My remark about <Show hidden files> was not meant for Lr. What I meant was that you move the files in your OS (Mac Finder / Win Explorer); and in Win Explorer is an option to <Show Hidden Files> under >Tools >Folder Options >View tab.
If you move images in your OS Lr will show the old folder with a question mark and will show images as "missing". You then have to re-link Lr to the new location of the images.
See here on how to do that: http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm
Since it seems to work now, better stay with moving images from within Lr - until you understand the issues involved in moving images in your OS.

ACR not using .xmp files after 03/09/2011

I'm using ACR 6.4.1.145 and Bridge CS5 on a Windows 7 x64 Pro machine. Canon S95 and G12 CR2 files created before 04/09/2011 behave exactly as they should: changes aved in .xmp files are recognized and applied in Bridge thumbnails and when the image is re-opened in ACR.
Images created on 04/09/2011 and any later date (tested by altering the file dates) have their changes saved in an .xmp file, but this file is not applied to the thumbnail in Bridge, the Bridge thumbnail does not indicate the .xmp file exists, and the .xmp changes are not applied when the image is reopened unless the .xmp file is loaded manually.
I have purged the cache, restarted Bridge, and restarted Windows. I've moved the images to a different directory, then a different drive. I've loaded the images from the SD card several times now. The problem persists.
All assistance appreciated.

Thanks Thomas.
I am pretty sure the CR2 files don't contain any .xmp data. For one thing, the problem only occurs on my installation. If I use another computer, everything works as it should.
The problem has returned, however. I just tried to make changes in ACR to images created today, and although ACR saves the .xmp, it does not recognize it when I open the image again. I have to load the .xmp manually.
I will bet that tomorrow, the problem has gone away. That would make it somehow time/date dependent. More important to you and anyone else trying to help, it seems to happen only on my installation of CS5. Something has gotten corrupted, I think. If the problem persists, I will probably try a re-install, but I hate the patching proces that follows.

LR 5.3 bug: local adjustments not saved in XMP

Hi,
I'm seeing the following bad bug on my mac, with LR5.3
If I save metadata to disk and immediately reload, I lose some adjustments, like brushes, tone curves, etc.
I compared some old .xmp and the .xmp saved by LR5.3 and indeed there are some sections missing.
Can anyone confirm? This looks like a P0 bug to me. What's the procedure for notifying Adobe?

did you wait for LR to save all the 10000 XMPs?
yes, I waited... 24 hours. but again, time is not the issue. This happens even for a single picture, albeit it does not happen for any picture.
I open a picture, save metadata, switch to finder/terminal, look at the .xmp manually and I see all the legitimate differences (e.g. softwareAgent changed from LR4.1 to LR5.3), but also a lot of sections are missing.
If I switch back to LR and re-read metadata from the file, I lose all the local edits, etc.
are you sure the Write rights of the restored files are OK?
Have you tried the same operation on the local disk?
yes and yes.
I think I found the pattern:
this happens for pictures that have been upgraded from PV2010 to PV2012 in LR4.
If I edit one of these pics in LR, it shows "Process version 2012", and in history I see "Update to current process (2012)".
However, the .xmp file on the disk says: "crs:processVersion = 5.7" (which is 2010, IIRC).
If I select "Process Version 2010" and then again "Process Version 2012", and I re-save the xmp, then it looks good.
Do you have any clue of what's going on?

Extract Metadata from PDF as xmp file

Hello!
I have the following problem: I do always File->properties->additional metadata->advanced-> save as .xmp. How could I write this actions in Javascript?

Thank you for your reply. Unfortunatelly I know javascript badly. I have found the code that creates metadata and open it as pdf (but i need xmp):
var r = new Report();
r.writeText(this.metadata);
r.open("myMetadataReportFile");
I also found the code that must create new next file, but it doesn't work:
var filePath = 'C:/Temp/filename.txt';
var fileSysObj = new ActiveXObject('Scripting.FileSystemObject');
fileSysObj.CreateTextFile(filePath);
Habe you any ideas how to combine these codes to solve my problem? (I know javascript badly and can#t do it)
Thank you for your hepl!

Develop Settings: jpg/xmp

Hello,
first off some background, that I would appreciate corrections on, if I understood something wrong.
a) Lightroom saves the settings it will apply to files in the database, but if the catagog option "Automatically write changes into XMP" is checked, LR will create a XMP file all files in which it stores the develop settings.
b) This setting applys to all files (raw, DNG, JPG, TIFF, PSD) unless the setting "Include Develop settings in metadata inside JPEG, TIFF and PSD files", in which case XMP files are not created for the named file-types, where the develop settings are saved into the metadata of the file itsself.
And now my problem:
I always have the "Automatically write changes into XMP" settings turned on, so that on a database corruption the develop settings are directly associated with the files and can be re-imported to another database. I have imported some 15000 files (60% raw, 40% jpeg) and have started to develop them. All raw files have a XMP file associated with them and modifications to Keywords and develop Settings lead to the XMP files being changed and the raw files remain unchanged. But... for JPEGs LR saves all changes into JPEGs according to the "Include Develop settings in metadata inside JPEG, TIFF and PSD files" setting, which was on for some reason or other. Since it would be so much easier for incremental backups if the JPGs were not modified and only XMPs were changed, I turned the "Include Develop settings in metadata inside JPEG, TIFF and PSD files" setting off. But nothing changed. Still no XMP files are appearing despite changes to the files.
Is there any way to force LR to move the develop settings from within the JPGs to external XMP files?
Thanks all!

inforumman,
Your questions:
a) Correct, but saving to XMP does NOT replace saving in the Lr catalog. Save to XMP is in addition to saving in the catalog.
b) The wording "saving the XMP" is a bit misleading, insofar as an XMP-file will be created only in case of Raw files, whereas with TIFFs, JPGs, PSDs the metadata (edits or other metadata) is written into (the header of) the image file - but NOT into the image pixels.
c) As LRuser24 already said, it is not possible to have Lr write an XMP-file for JPGs, or for TIFFs, or for PSDs.

Xmp sync problems--corrupted files?

I have been having lots of problems getting my xmp metadata sorted out. I am a new user to Lightroom, but I think I have figured out most of what I need successfully.
I use a variety of programs to edit the xmp data (mostly Lightroom and exiftool right now), so I know the importance of the "Automatically write XMP data to file setting" (ON in my case). After a few days (actually more like a week) of writing xmp data and then reading into (or synching folders in) Lightroom, I found a number of "metadata conflicts" in my catalog. Since these are basically impossible to fix for a large catalog (since there is no way to show the files that have conflicts), I started over and created a new catalog, and imported all 40,000+ images into it.
However, with my new catalog (with presumably no metadata conflicts), the first image that I tried to change the metadata on gave me a metadata conflict (presumably when Lightroom tried to save the xmp data after I changed it). This was a jpg file, so the metadata is being (or not being) written into the file. Reading the metadata from the file into Lightroom did not fix the problem. The Metadata Status field in the Lightroom Metadata panel says "Unknown" and clicking on the word "Unknown" brings up a panel saying "There was an unknown error while writing metadata to this photo. Retry?", and neither retrying the save nor importing the settings from disk resolves the conflict.
I think that the problem is that the jpeg is somehow corrupt, because if I save a copy in Photoshop, I can read and write the metadata in that copy. And, the copy has, I think, the same metadata as the original. (Of course, the image is probably imperceptibly degraded because I re-jpeg'd it).
There is no message in Console (I'm on Mac). (See PS)
I am worried that I have a number of files with this kind of problem, and I'd like to find the problem and fix it. Any ideas for a strategy to go about doing this? I guess I could "Save Metadata" for all files in my catalog (thus updating the file modified date for all 2 TB of data, and causing a massive backup issue), and then look through my catalog for those elusive exclamation points. But I'd like something better.
I have no idea how the jpeg could have gotten corrupted, but I do have an archived version that I could look at.
Any thoughts on next steps?
TIA
Alan
PS--I did find this in my console output hundreds of times:
8/10/11 2:40:00 PM    Adobe Lightroom 3[404]    KeywordUsageStatistics    ERROR    Bad popularity entry for 1937630: occurrences is negative: -1
I don't know if that is related, but it worries me.

After moving LR3.5 and catalogs to a new computer running Windows 7 and LR from an XP system, I suddenly had 6400 files with exclamation points--failure to synch metadata or similar warnings on every file. If I thought I had one without the error, if I clicked on it--there error showed up.    It was very frustrating and I was wondering if I was going to have to keep my old computer forever.
After I searched for a couple of hours and found that there have been several discussions concerning failures to sync xmp sidecar files and failures to write metadata on this forum and others. Some of the postings had angry rants against Adobe. On my system, it was not Adobe that should be blamed, it was Microsoft:
On one of the Adobe threads, I noticed a post that the person had multiple external drives and the problem did not show itself on one drive. The person said that changing the permissions on the other hard drives solved the problem.   I tried this and it worked for me. I did not have this problem with this same drive on my XP system. I will try to find that other forum and thank the person who gave me the solution.

RAW + old photoshop generated .XMP file conversion to DNG

I have a set of camera raw files (.mos) and .xmp side car files that were generated in photoshop several years ago. I am thinking about converting all of the files and side cars to DNGs because Leaf Capture software is no longer being updated.
Before I do I want to confirm that Lightroom can read both the raw AND the corresponding side car files and convert them into single dngs. I also want to know if the .xmp information is extractable after the dng is created in the same way that the raw/original file is extractable.
I've been trying to test lightrooms ability to read .xmp files on my own. I added a .mos file in a folder with a corresponding .xmp file and a .mos file in a folder without a corresponding .xmp file. Lightroom reads similar adjustment information for both images but only generates a preview that more closely resembles a finished retouched .PSD of the added .mos file that does not have the .xmp file in the folder it was added from. I'm at a bit of a loss regarding how to proceed.

nonovsco wrote:
Upate on situation: I followed up with the individuals that created the files and found out that the side car files were in fact generated by leaf and not photoshop. i tried another test and it looks like the folder with a .mos +.xmp file is now reading differently than a .mos file by itself. both suggest that changes were made to the files with modulations in the "develop" section of lightroom.
You can view the XMP file data in Notepad or any other text editor, just select 'Open' and select 'All File Types' so you can see the XMP files. It should be possible to store both C1 and LR develop settings in the same XMP file, but there may be some naming conflcts. Review of an XMP file with both C1 and LR develop settings saved to it should show the two different develop data sets in Notepad. Conversion to DNG should save ALL XMP data, but you may lose some of the (edit) Leaf proprietary data that may be in the raw file's metadata. For now I'd hold onto the raws + XMPs, even if you do convert to DNG.
You can use EXIFtoolGUI to examine the metadata in the new DNG files and compare it to the original XMP file's data. My Canon DSLRs appear to have all of the manufacturer's 'Makers Notes' copied over from the raw file into the DNG metadata.
http://freeweb.siol.net/hrastni3/foto/exif/exiftoolgui.htm

To XMP or not to XMP

I was bitten by the Lightroom 5.0 History bug (images developed in earlier versions of Lr lost complete histories if the history state was changed in the Develop module) and was able to recover because I had good backups. I've updated to 5.2 since, so I don't expect to run into that again. One thing I noticed during my recovery operation is that Lr will warn me if there is a mismatch between metadata in the catalog and metadata in the image file. Overwriting the metadata in the image with the metadata in the recovered catalog fixed the some issues with the effects of the bug, but it got me thinking -- what if the metadata hadn't been written to the image file at all?
I'm more of a video guy than a photo guy, and I set up Lr to automatically write metadata to the files because that's what I do for my video files when I use Premiere Pro. But I think my recovery would have been easier and less stressful if I hadn't had to see or base a decision on the intimidating metadata mismatch warning that Lr presents.
So I'm asking for general opinions -- what do you think about the pros and cons of having Lr automatically write metadata to XMP?
Jeff

Samoreen wrote:
But you will regularly forget Ctrl-S anyway .
Actually, I never forget. Or perhaps I should say if ever I do forget, it will be caught.
There are two times I save metadata:
1. When I've done enough editing I'd be bummed if it got lost, but I'm not finished yet.
2. When I'm finished.
finished means "finished for now" - most photos are published after they're finished, and re-published after they're finished again...
In the former case (1), I just don't worry about it too much, in the latter case (2) it's done as part of a "finalization ritual" which (takes snapshots of and also) assigns metadata to finished photos... I use the ChangeManager plugin for that, but there is more than one way to accomplish a goal. For example, Jeffrey Friedl has Folder Status plugin for "managing change" on a folder basis instead of photo basis. You can also follow a self-designed procedure which does not require plugins.
The concept is: once saving xmp becomes part of a workflow that includes assigning (and/or clearing) metadata, it's the assigned (or cleared) metadata that drives the relationship (status) between catalog settings and xmp on disk.
I turn xmp status indicators off, and rarely look at the metadata status collection(s). Why?
1. They sometimes say metadata needs to be saved when it doesn't.
2. They sometimes say metadata wasn't saved when it was.
3. They may seem to indicate you should read metadata when you shouldn't.
4. Metadata conflict status depends on date/time only, not contents, and so many "conflicts" are simply false alarms.
etc.
i.o.w. it's never been a reliable (nor robust) feature in Lightroom, and I just don't need it, since I have other "metadata status" metadata that I have complete control of, which *is* reliable.
If I ever get confused, ChangeManager's "Compare Catalog to Disk" feature gives a complete list of all differences between develop settings and metadata in catalog and those in xmp on disk.
I don't necessarily recommend everybody do things how I do them, since my way (although robust) employs plugins - it's not "as simple as possible", and there is something to be said for simplicity.
My main point is that if you can figure a way to assure xmp is saved when appropriate, manual method may be best.
If you can't or just don't want to, then auto method may be best for you. And of course there are those that rely on the catalog exclusively and never save xmp - that's another way to go.
UPDATE:
=======
Perhaps the most important aspect to me of saving manually: I want to save (finalized) xmp only after scrutinization, since part of the goal is NOT to save screw-ups in xmp! - they're already in the catalog .
=======
Rob
Message was UPDATED by: Rob Cole

Save As - XMP

Similar Messages

Maybe you are looking for