Learning about XMP files...

If you were like me, not aware of this format and its usage, you might consider to lookup Adobes official pages and read white paper about its design and use:
http://www.adobe.com/products/xmp/
This acronym is being used currently in several differing meanings, so look for "Extensible Metadata Platform," and not for example for "Extended Module Player," to name only one other use of XMP. Adobe's XMP is available under Creative Commons license, correct me if I am wrong:
http://creativecommons.org/technology/xmp

Something else that may be of interest. There are ISO standards based on PDF, such as PDF/A (ISO 19005-1). These standards describe the use of XMP.
I don't know exactly how far XMP has been standardised itself, but it is certainly referenced and exploited by at least one ISO standard.

Similar Messages

Learning about my files

I just want to learn all about my new computor

Hello,
This forum is specifically for Fast ESP 5.3 or FSIS or FSIA products.
Did you have a question related to one of these Enterprise Search prodcuts?
Thanks!
Rob Vazzana | Sr Support Escalation Engineer | US Customer Service & Support
Customer Service & Support
Microsoft| Services

Writing to XMP file or one file per folder?

I am about to start using LR2. Used to using PS and Bridge. I use DNG and tiffs, and jpgs. I am used to having one file per folder for bridge's info. I do NOT want an XMP file per picture file. How does LR2 do this? I have read a few posts about XMP files and such. Is there a setting to make one file per folder, or does LR2 make XMP files for each picture?

>XMP sidecars are only created for proprietary raw files (eg CR2, NEF, etc) and only when you save metadata out to file.
Good, so since I do not use proprierary RAW's, I am safe. Thanks. I do plan to save metadata to the files, so in the future, other programs can use it.

Cant open xmp files in photoshop element 8

i thought i was able to open xmp files with ps element 8. am i missing something or
does this program not do it? I have over 560 pictures from a wedding that i cant open. they were taken with a canon camera by a relative and would love to view them! also whenever i click on organize it shuts down pse 8. i'm so fed up with this program already and i just got it today! help!

will do that! thanks for the info. im just learning about all this. excited to play around n the photoshop with my pics!
Date: Mon, 22 Nov 2010 09:31:35 -0700
From: [email protected]
To: [email protected]
Subject: cant open xmp files in photoshop element 8
An xmp file is not an image. Usually those are the files containing the settings used for raw conversion, any metadata keywords, and other data that PS/PSE can't write to the files themselves. If those really are all the files on your disc, contact the photographer, because it sounds like someone made a mistake.
>

What happened to .xmp files?

I have noticed recently that my Bridge program (cs4) has not been automatically exporting .xmp files into the folder where I store my images. I have been doing a lot of reading, but still can't seem to find a solid answer as far as what to do.
I have figured out how to export .xmp files into another folder, but what's the point of that? I want the metadata for my images to stay with my images. When I move them from folder to folder using Bridge, the xmp files used to move also, so I never lost my metadata.
I also empty my cache fairly often. I noticed that Bridge was no longer exporting xmp files when I emptied my cache and ALL my metadata that I had added to my images was gone, just like that.
I am a photographer and need that information to go somewhere permanent automatically, not in the cache which is supposed to store temporary file information.
Anyone have any idea?
Thanks so much!

Tai Lao wrote:
Your post #29 is completely blank
Strange, I responded using email and this normally functions well, maybe the chance in formatting and quoting did not get through?
I don't want you to think I'm ignoring you.
How could you think of that...
here is a copy of the mail, hope the formatting keeps clear!
>> Omke Oudeman wrote:
>>
>> As far as I understood the producing of magenta colorcast is a fault by
>> Pentax and the recovery utility does only work on original Pentax DNG, the
>> PEF files already have some compression and don't display all the sensor
>> data, Right?
>
> Wrong, very wrong. But that is definitely off topic.
It is what I understood (after briefly scanning through page) from this post that advices to shoot in K20 generated DNG instead of the PEF format.
http://www.pentaxforums.com/forums/pentax-dslr-discussion/67532-how-use-k20s-black-pixels- hidden-dngs.html
>> Omke Oudeman wrote:
>>
>> …I did something else, I opened 2 files in ACR, one the original CR2 and the
>> other the DNG conversion of it. ............ I could not find one single >>difference between both files…
>
> That is irrelevant. The issue is that there is some information inside the
> raw files that is not currently used either by the Pentax software or by
> Adobe, but that a third party (Gordon B. Good in this case) was able to
> utilize in order to improve the quality of certain converted raw files.
For your files in certain conditions at high iso this seems to be the case, the DNG files converted by Adobe DNG converter do miss the border pixels needed for the script from GordonBGood.
I tried to download that application but it seems only for Windows, how do you manage to use it?? Thought you have given up on Windows long time ago??
Nevertheless I also tried the apply image method you quoted from Bruce Fraser in an other post, using subtract with offset 128 and both perfectly the same.
I do agree that Raw converters from nowadays can get more out of the Raw data then they did 8 years ago, trying an 8 year old raw file gives a much better result (but then you also have to keep in mind that our knowledge and skills in Digital imaging have grown in combination with better color management understanding and good calibration soft and hardware is also due to this!)
Also I'm not afraid my benefit from the future Raw converters will differ if I use DNG instead of the original Raw, but that is my personal believe. The result I get nowadays for combination of DNG and PS are already more then satisfying, and sure it will be better in the future but for that I have also faith in DNG :-)
> Yes, I use PSDs exclusively. However, if you don't think TIFF will be around
> in 15 years, why do you think DNG will? After all, *+Adobe owns the TIFF
> format+* as well as the PSD format.
>
> If you trust Adobe to keep the DNG alive for 15 more years, why don't you
> trust that same corporation to keep supporting TIFF, a format for which they
> paid darned good money to acquire?
That is just a question of the market, as you could see that our young friend that started this post never uses it and I do hear more voices saying they don't use it or don't see the use for it. Eventually there will be no need for letting seldom used formats taking space in menu's and applications.
DNG however is still talk of the town, whether you like it or not. And therefore more likely to be around in 15 years time. But you are right, If I was to know about what was going on in 15 years from now I would not be a photographer but a fortuneteller and in my free time bathing in countless money :-) :-)
> Another one of the reasons why I don't like DNGs is, number one, that they
> take an awful lot longer to open than the raw files.
That I still can't understand unless you have chosen to use the original raw file included and created a double size for the file. But as stated in earlier post, not the case on my system.
> Not that any of this—or anything else in the world for that matter—should be
> an issue for me then.
Statistically you have lived the greatest part of your life and knowing your health is not something to be jealous of (to put it mildly) your statement about this also is something only time will learn.
Let's wish we still can have a long period for our little chats, agreed or not.
I will give up on getting you to DNG (for now as it is...) :-) :-)
Vriendelijke groet,
Con cordiales saludos
感谢你和亲切的问候

Network storage drive...where can I learn about these?

I have so many questions, and frankly, the answers I've seen looking (briefly, admittedly) around these threads scare me. Gee, Wally, what ever happened to Apple as the computer you didn't have to know computer programming to use?
Now, before you all get your panties in a bunch telling me that I'm responsible for knowing how to use my hardware, I know...and I do want to know.
So what I want to know now is how can I learn about the various types of "shares", and what they mean for hooking up a network drive for backup, etc.
I have a WD 1TB drive which I believe uses "SMB", whatever that is. It's got two folders on it currently, "Public" which I can access, and "WD Backup", which I can't. I also can't seem to use it as a Time Machine drive, which is what I want to do with it. And, or course, I can't re-format it, which I'd love to do as my wife hates the folder designations on it, and would like to have one folder called "iMac Backup" on it.
Answers which don't involve Terminal will get extra points, but I've dealt with Terminal before, so take your best shot. And ask for clarification if you need it. Thanks.

Unfortunately, networking and file-sharing aren't quite so simple in part because there's decades of history and dozens of companies involved in getting it into the current state. If you want dead-simple, you can get an Apple Time Capsule or AirPort with an external drive and be done with it. However, if you really want the most from network storage, you'll probably want to read up...
WD make a number of drive, some network-attached, some not. We'll assume that you have one of their basic consumer network-attached drives.
"SMB" stands for "Server Message Block" protocol and it was the local area network file-sharing protocol developed for Windows for Workgroups circa 1992 (it was later renamed CIFS - Common Internet File System - by Microsoft in 1996 because of the rising popularity of the Internet, despite the difficulty in getting it to work in anything but a small local network). SMB/CIFS is still widely used today for Microsoft Windows networks, though much of the equipment that serves those files are built on Linux or FreeBSD and not Windows.
Access to shares on an SMB server (such as your hard disk) is controlled through a configuration utility provided with the drive or via a web application built into the device (that you access through your browser). Consult your manual. Generally speaking, however, SMB servers offer different ways of identifying whether or not you can access a share: 1) based on the computer connecting (in which case, everyone is considered the same user), or 2) based on a username/password combo. Generally a server will only operate in one mode. Shared directories can also allow or deny "guest" access (access without a password). All of this should be configurable through the drive utility or web application which you access with your web browser. Generally, an SMB server can only operate in one mode.
It sounds like the Public directory is configured to allow guest access, and I'm guessing that "WD Backup" is a share that's password-protected and intended to be used with Western-Digital's own software of the same name. You should be able to add and create new directories as necessary through the provided utility or the web interface.
You are correct, you cannot use Time Machine with an SMB file-sharing service. Time Machine will require AFP (Apple Filing Protocol) or NFS (Network File System) support. Western-Digital only has 3 network drives that support AFP and Time Machine: My Book Live, MyBook World, and WD ShareSpace. OS X also has some basic requirements about the performance and capabilities of network storage in order to use it with Time Machine, so you really want to look for drives that state up front that you can use Time Machine with them (for example, WD World Edition: http://www.wdc.com/wdproducts/updates/docs/en/appletimemachine.pdf )
I'm not sure why you can't reformat the drive. This is supported on all WD products (though, if you've moved a bunch of data to it already, perhaps it would be a hassle).
You can do backups of your Mac over SMB, but it's complicated by the fact that SMB is quite old and isn't capable of storing information about the file permissions, ownership, etc. It will be reliable for data files, but not for applications, etc. There's a work-around, of course. You can create a disk image on the SMB share using Disk Utility (make sure you create an HFS+ image) and backup to that. If you go that route, I would suggest either Carbon Copy Cloner or SuperDuper to perform your backups. They are true backup tools, not versioning tools like Time Machine.

How can I use an old XMP file on a new set of images??

I have an older XMP file that contains settings used to retouch some previous images in a particular way. I'd like to apply those same settings to a new set of images. How can I use that older XMP file on a new set of images in Lightroom?
The contents of the XMP file are as follows:
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40
">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
   <crs:Version>6.0</crs:Version>
   <crs:ProcessVersion>5.7</crs:ProcessVersion>
   <crs:WhiteBalance>Custom</crs:WhiteBalance>
   <crs:Temperature>4700</crs:Temperature>
   <crs:Tint>+4</crs:Tint>
   <crs:Exposure>-0.35</crs:Exposure>
   <crs:Shadows>5</crs:Shadows>
   <crs:Brightness>+50</crs:Brightness>
   <crs:Contrast>+25</crs:Contrast>
   <crs:Saturation>-8</crs:Saturation>
   <crs:Sharpness>25</crs:Sharpness>
   <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
   <crs:ColorNoiseReduction>25</crs:ColorNoiseReduction>
   <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
   <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
   <crs:VignetteAmount>0</crs:VignetteAmount>
   <crs:ShadowTint>-1</crs:ShadowTint>
   <crs:RedHue>0</crs:RedHue>
   <crs:RedSaturation>0</crs:RedSaturation>
   <crs:GreenHue>0</crs:GreenHue>
   <crs:GreenSaturation>0</crs:GreenSaturation>
   <crs:BlueHue>0</crs:BlueHue>
   <crs:BlueSaturation>0</crs:BlueSaturation>
   <crs:FillLight>0</crs:FillLight>
   <crs:Vibrance>+5</crs:Vibrance>
   <crs:HighlightRecovery>24</crs:HighlightRecovery>
   <crs:Clarity>+8</crs:Clarity>
   <crs:Defringe>0</crs:Defringe>
   <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
   <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
   <crs:HueAdjustmentYellow>0</crs:HueAdjustmentYellow>
   <crs:HueAdjustmentGreen>0</crs:HueAdjustmentGreen>
   <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
   <crs:HueAdjustmentBlue>0</crs:HueAdjustmentBlue>
   <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
   <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
   <crs:SaturationAdjustmentRed>0</crs:SaturationAdjustmentRed>
   <crs:SaturationAdjustmentOrange>0</crs:SaturationAdjustmentOrange>
   <crs:SaturationAdjustmentYellow>0</crs:SaturationAdjustmentYellow>
   <crs:SaturationAdjustmentGreen>0</crs:SaturationAdjustmentGreen>
   <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
   <crs:SaturationAdjustmentBlue>0</crs:SaturationAdjustmentBlue>
   <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
   <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
   <crs:LuminanceAdjustmentRed>0</crs:LuminanceAdjustmentRed>
   <crs:LuminanceAdjustmentOrange>0</crs:LuminanceAdjustmentOrange>
   <crs:LuminanceAdjustmentYellow>0</crs:LuminanceAdjustmentYellow>
   <crs:LuminanceAdjustmentGreen>0</crs:LuminanceAdjustmentGreen>
   <crs:LuminanceAdjustmentAqua>0</crs:LuminanceAdjustmentAqua>
   <crs:LuminanceAdjustmentBlue>0</crs:LuminanceAdjustmentBlue>
   <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
   <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
   <crs:SplitToningShadowHue>138</crs:SplitToningShadowHue>
   <crs:SplitToningShadowSaturation>13</crs:SplitToningShadowSaturation>
   <crs:SplitToningHighlightHue>0</crs:SplitToningHighlightHue>
   <crs:SplitToningHighlightSaturation>0</crs:SplitToningHighlightSaturation>
   <crs:SplitToningBalance>0</crs:SplitToningBalance>
   <crs:ParametricShadows>0</crs:ParametricShadows>
   <crs:ParametricDarks>0</crs:ParametricDarks>
   <crs:ParametricLights>0</crs:ParametricLights>
   <crs:ParametricHighlights>0</crs:ParametricHighlights>
   <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
   <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
   <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
   <crs:SharpenRadius>+1.0</crs:SharpenRadius>
   <crs:SharpenDetail>25</crs:SharpenDetail>
   <crs:SharpenEdgeMasking>0</crs:SharpenEdgeMasking>
   <crs:PostCropVignetteAmount>0</crs:PostCropVignetteAmount>
   <crs:GrainAmount>0</crs:GrainAmount>
   <crs:ColorNoiseReductionDetail>50</crs:ColorNoiseReductionDetail>
   <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
   <crs:ToneCurveName>Medium Contrast</crs:ToneCurveName>
   <crs:ToneCurve>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>32, 22</rdf:li>
<rdf:li>64, 56</rdf:li>
<rdf:li>128, 128</rdf:li>
<rdf:li>192, 196</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
   </crs:ToneCurve>
   <crs:CameraProfile>Adobe Standard</crs:CameraProfile>
   <crs:CameraProfileDigest>3DA8CE4A626CE36A1D0C55BF157793C9</crs:CameraProfileDigest>
   <crs:HasSettings>True</crs:HasSettings>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

I’m pretty sure Adobe NEVER intended for someone to copy an XMP file from one photo to another outside of LR as a way to replicate settings.   You can make a preset from a photo, as discussed, or if you don’t want to do that, copy-paste the settings from a representative photo that you initially select to one or more new photos. You could have a special LR folder that holds standard photos to copy/paste from. Of course creating a Develop preset from the representative photo is the “normal” way to handle such situations, but maybe you have hundreds of different situations to copy settings from and don’t want to create presets for each one, but I’d argue that you could create a complex folder hierarchy for your presets and still have them findable without that much problem.
As far as the mystery about why some photos show Reset and some show From Metadata, is the Process Version (down in Camera Calibration) of the photo before reading the settings the same between the two situations? And in general, are these virgin photos newly imported into LR or have some been modified in LR, already? Does an XMP file already exist for any of these, where that XMP is being overwritten by your external-to-LR copying? Or do you have auto-write-XMP enabled and your hand-copied XMP is getting overwritten by LR, automatically, before you have a chance to read in anything?

4.1.1 SDK Problems with missing xpacket tags in sidecar XMP files

The current 4.1.1 SDK has problems with sidecar XMP files that don't have the xpacket headers and trailers, i.e:
<?xpacket begin='ï»¿' id='W5M0MpCehiHzreSzNTczkc9d'?>
<?xpacket end='w'?>
is missing. Now, unfortunately Adobe Bridge CS2/CS3 does not export these xpackets in sidecar XMP files.
The standard, http://www.aiim.org/documents/standards/xmpspecification.pdf, is also very vague about it all:
● Write external metadata as though it were embedded and then had the XMP Packets
extracted and catenated by a postprocessor.
The grammar is strange(past tense had) and the spec implies that the xpacket should be extracted and again catenated... Someone should review this document and clearly state if xpacket statements should be in sidecar files or not. I suspect myself that they should be there, but the standard is very vague.
Anyway, there are two places in the SDK code where changes might be needed:
XMPFiles::Initialize has XMP_Asserts in case the xpacket header/trailer is missing, but the underlying assert is only active in debug builds.
XMPScanner::PacketMachine::FindNextPacket () also has in its truth table the assumption that the xpackets exist.
There could be even other places in the code that assumes that the xpacket tags are present in all files, which includes text XMP sidecar files.
Anyway.
a) Shouldn't bridge export the xpacket tags? Same with any other application?
b) If the spec is vague, then the SDK should not assume that the xpacket tags are present.
Any comments? Has someone already fixed this issue as I suspect a lot of apps using the the XMP SDK would break concerning reading XMP sidecar files? Thx, Kent

I was able to work around the problem by creating a mapped view of the .xmp file (this creates an array in memory backed by the file on disk, so there's no need to read the file into a separate internal buffer), and constructing the SXMPMeta object directly from the buffer. (The ctor for that class calls ParseFromBuffer, so this is the same thing as was suggested by other messages in this thread.)
It seems that Adobe needs to do one of these things:
(1) say that Bridge CS3 has a bug, and agree that Bridge CS3 should include a proper xpacket header when writing xmp sidecar files
(2) say that the XMP Toolkit has a bug, and that the SDK should be able to parse sidecar files without an xpacket header, and agree to fix the toolkit
(3) say that Bridge CS3 and the XMP Toolkit behave as expected, but then provide a sequence of steps by which users of the XMP Toolkit are expected to read xmp sidecar files written by Bridge CS3
Does Bridge CS4 write an xpacket header to the xmp sidecar files?
Maybe what I could do is create a custom file handler for .xmp sidecar files, so I could use the SXMPFiles for everything, instead of having to special-case .xmp files.
My needs are pretty modest though, and it might be just as simple to use the MS DOM-based XML parser for load the xmp sidecar file. I bet I could get the data I need (only the "Rating" for now) using a simple XPath expression.
-Matt

Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata

The cmd-keys / shortcuts doesn't work in the xmp file info panel btw. in the xmp / iptc fields (e.g. cmd+c, cmd+v, ...) of Adobe Bridge CS6 (Mac OS 10.6.8 and 10.7.3). You are not able to cut and paste info from one box to another like previous versions.
This bug only appears in the xmp file info window (opened via alt+i) in Bridge CS6 - if you edit information or metadata in the file info panel in Photoshop CS6 copy and paste from one field to another works.
The shortcuts also work under Windows (tested under Vista).
I noticed this minor bug already one in the Photoshop CS6 Beta more than one months ago. I hoped that this was corrected in the official test version, but unfortunately it is not. Although it is a minor bug, it is IMHO a basic function and would be very helpful in my daily work - it is too bad, that such a small thing is making working with the application a little bit annoying.

Thanks! If there is a workaround or simple solution, I would be very glad if you could inform me.
Christian
(signature removed by the Admin)
Am 14.05.2012 um 13:49 schrieb FrankBiederich:
Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
created by FrankBiederich in XMP SDK - View the full discussion
Thanks for your report; we'll look into it.
Frank
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
To unsubscribe from this thread, please visit the message page at Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in XMP SDK by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.
Message was edited by: Arpit Kapoor

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.

XMP Files in LR 1.4.1

Hi, In using LR I find that my image folder contains not only my FPG and RAW file but also many images have an associated XMP file. I have Three quesitons:
1) Am I correct that the xmp file holds the edits I made in LR? In other words the original RAW file is untouched but as I "develop" an image the sequence of changes are placed in the XMP file.
2) If #1 is correct, is that the only way to store the changes? When I first researched LR I thought I saw something acout having a choice of storing such info in either XMP or the LR Catalog. What are my options and how do I select which one I want to use?
3) When I select a bunch of images in the grid, then right click on a different folder and select "move selected images to this folder" it moves the JPG and the RAW and updates the catalog to know the image is in a new file. However, it seems that the XMP's are still in the original folder. Is this normal? Should I move the XMP files to the same folder that the images are now in?
Thanks -- Dan

Am I correct that the xmp file holds the edits I made in LR? In other words the original RAW file is untouched but as I "develop" an image the sequence of changes are placed in the XMP file.
No, this is incorrect. The edits are stored in the catalog file. You can make Lightroom write a copy of the edits to an xmp sidecar, but it will be a copy, not the main repository. If you choose to write xmp files, either explicitly or automatically, indeed the original RAW is untouched. If you edit the xmp sidecar in another program, Lightroom does NOT automatically pick up on the changes. You would have to explicitly read from it. If you do that Lightroom will overwrite the settings in the catalog file with those in the sidecar.
2) answered above. You cannot choose. The main store is always the catalog file.
However, it seems that the XMP's are still in the original folder. Is this normal?
As far as I know, if lightroom wrote the xmp file, it should move it along. Perhaps another program (bridge or ACR for example) wrote them. In that case Lightroom doesn't know about them and won't move them along.
Should I move the XMP files to the same folder that the images are now in?
As Lightroom doesn't really care about them you only need to do this if you want to keep things nice and tidy I guess.

Camera Raw does not read previously saved XMP files (Canon 60D)

Hi,
I want to ask if it is a real problem or just me doing something wrong.
I open RAW files made with Canon 60D (Photoshop CS5, Camera Raw 6.6), then I do what a do (cropping, exposure changes, sharpen ... etc.), then I click the Done button. Camera Raw saves XMP files along with the RAW files. After this I want to do some more editing, I open the RAW files, but Camera RAW does not "remember" what it did just minutes before. I suppose that it is not reading the XMP files that it created.
So is it me or it is some kind of bug?
I don't have this problem when editing RAW files made with Canon 400D.
Thanks for your time!

Bo LeBeau wrote:
If I understand correctly the issue is not viewing in Bridge, but rather that ACR doesn't remember the changes.
There is a discussion in the Camera Raw forum about this issue of not always reading the changes after clicking Done in ACR.
But no solution.
http://forums.adobe.com/message/4096784#4096784
Yes, ACR doesn't remember/show the changes I made.
It seems that I have the same problem as the other forum member from the link. I tried to recreate the issue, but this time all went well and ACR displayed the changes I made ...
It is strange because I had the issue numerous times on two different windows PC's ...
Message was edited by: Orhan Chakarov

Acrobat X freezes when I run a JavaScript Action after about 200 files.

Acrobat X freezes when I run a JavaScript Action after about 200 files, batches with less than 200 files work well. I can watch the Acrobat.exe process in the resource monitor and when the Threads reach about 2000 and the Working Memory reaches 500mb, Acrobat freezes. The JavaScript creates 2 redaction areas, applies the redaction, then saves the file to another location. I've tested it on both Windows Server 2008 and Win7 32bit. I'm running Acrobat X Pro fully update to 10.1.10.

It is possible to have the Redaction tool search for a text string across multiple PDFs without using the "Action" wizard or batch processing. You will have to learn the exact steps to properly set the properties for each string of text. You can also review the items marked for redaction and either accept, remove or adjust as needed each one.
There are 3rd party tools that can also redact PDFs and they existed long before this feature was added to Acrobat. Appligent Document Solutions Redax..
Appligent even has a server based product for large amount of files or using watched folders.

Looking for answers on XMP files - where should they be stored as sidecar files? With the original raw file or in a separate folder?

Looking for answers on XMP files - where should they be stored as sidecar files? With the original raw file or in a separate folder?
Relatively new user of Adobe LR5 and PS CC, about a year old.
If they should be stored somewhere beside the folder that contains the originals, where and how to change the settings?
If I choose to write metadata to the original files, is that sidecar files or does the XMP file show separately?
To be honest, I usually find a video and I cannot figure this out. I have never received an answer on any of my questions by the way.

Hi there,
You answered a prior question from me so I wanted to reach out to you about this. I just need a step by step on how, if possible, to View LRCC on my MacBookPro when the main interface is on my iMac

Bridge CS5 not recognizing xmp files created on CS6?

An employee of mine edited several shoots, using her own computer. She has CC and used Camera RAW. I still use CS5 and am trying to process the files she edited (I have the RAW and the xmp files). Typically, I process these through Bridge. However, Bridge doesn't seem to recognize her xmp files. Any ideas on 1. why this is happening, and 2. how I can apply her xmp files when converting the RAW to jpeg? We are talking about 1500 images. Thanks!

What camera model is she using? What camera raw version are you using on your CS5? Is her camera model supported by your cs5 acr?
Perhaps she could process her raw files+xmp into dng files to pass on to you.

Learning about XMP files...

Similar Messages

Maybe you are looking for