Log in to post in the forums, comment on the blog and submit or rate photos in the photo contests.
New Content Since Last Visit
No New Content Since Last Visit
backup batch Beta canvas categories category color management conversion Convert crop database date develop dng Edit editor email Embed EXIF fixed format import IPTC Keywords mac metadata NEF Nikon print pro Pro 2.5 Pro 3 Process process mode RAW resize Rotate save search slideshow thumbnails TIFF upgrade vista windows 7
Sign up to get special e-mail only offers, photography and software tips from ACDSee.
Philip Weir
Member
More than one application can write an XMP sidecar file. Does anyone know if these files are cummulative? In my specific case I've got Photomatix that writes its tonemapping settings into an XMP file. I then use ACDP3 to develope/categorise which itself generates a XMP file. However, does the resultant XMP file contain the necessary data for both Photomatix and ACDP3? Or does one replace the other?
Thanks, Philip
Sam Dring
Moderator
Philip
Apart from standardized fields such as iptc, apps write their specific processing parameters (and in the case of ACD, their embedded cats etc) to an application-dedicated part of xmp which is readable only by the app which created it. So you can use photomatix, Pro3 and others and they will not 'interfere' with each other. Photomatix cannot, of course, interpret the parameters of Pro3 not vice versa.
Philip Weir
Member
Thanks Sam. I hoped that might be the case and its nice to have someone confirm it.
newname
Member
This does not apply to every application. LR for example imports all xmp data, even data which it does not know how to handle. When exporting this data from LR the xmp data of other apps will be overwritten.
newname
Sam Dring
Moderator
This does not apply to every application. LR for example imports all xmp data, even data which it does not know how to handle. When exporting this data from LR the xmp data of other apps will be overwritten.
newname
Well, as a user of LR I would be VERY interested to know what gets overwritten. I am, of course, willing to stand correctd but I find that very hard to believe and it has never happened to me
Philip Weir
Member
This does not apply to every application. LR for example imports all xmp data, even data which it does not know how to handle. When exporting this data from LR the xmp data of other apps will be overwritten.
newname
Oh dear! Maybe some testing is in order? If time permits I'll also check out the XMP specs.
OlyPaul
Member
This does not apply to every application. LR for example imports all xmp data, even data which it does not know how to handle. When exporting this data from LR the xmp data of other apps will be overwritten.
newname
Not strictly true as xmp will hold the accumlative processing parameters of many different applications including LR and ACDSee pro3 together without one overwriting the other as long as they are written to the correct field by the application.
In fact most apps abide by the IPTC core parameters except Adobe , most apps write the title to the headline field of the IPTC core, of course Adobe has to be different to eveyone else and write it to the object field, of course this is a annoyance if you are writing something else to the object field as filling in the title in LR will overwrite it.
I also would be interested in a example where except for the above this is happening in LR2 .
Sam Dring
Moderator
This does not apply to every application. LR for example imports all xmp data, even data which it does not know how to handle. When exporting this data from LR the xmp data of other apps will be overwritten.
newname
Didn't have time to check last night but just done an export from LR (raw to jpeg) and using exiftool can confirm that the jpeg retained the Pro3 xmp entry. Could it be that you are selecting 'minimise embedded metadata' when you are exporting from LR?
Interestingly having processed a raw file in Pro3 for comparison purposes, I saved as jpeg and Pro3 STRIPS OUT ALL xmp
Marc Sabatella
Moderator
Strips out the XMP from the raw file, or didn't include it in the jpeg? The former seems unlikely (and definitely doesn't happen to me with my raw files, but the later would be normal if you don't use the option to preserve metadata on saves.
Sam Dring
Moderator
Strips out the XMP from the raw file, or didn't include it in the jpeg? The former seems unlikely (and definitely doesn't happen to me with my raw files, but the later would be normal if you don't use the option to preserve metadata on saves.
Well I've just tried it again, processed a CR2 raw; save as jpeg; preserve meta and xmp all stripped out of jpeg.
Marc Sabatella
Moderator
OK, I've verified that using Save As from Develop mode on a RAW file does not result in XMP metadata being preserved. My initial thought was so what, there's nothing of value in that XMP info for the JPEG - any IPTC info would be stored in the IPTC area as well, and RAW processing parameters don't have relevance any more. But that is of course a very ACDSee-centric view; you might have ratings created by another program or who knows what else of value in there. And actually, come to think of it, I've always been surprised that database information embedded by ACDSee doesn't appear to be preserved on batch edit (aka batch processor) operations, either, despite my requesting tha metadata be preserved.
I guess this is sort of in keeping with ACDSee's general philosophy of not creating XMP areas in JPEG unless necessary (presumably to avoid some of the situations where XMP maps similar EXIF & IPTC fields onto each other). But it doesn't seem to be ideal behavior here.
Sam Dring
Moderator
Marc
any IPTC info would be stored in the IPTC area as well
I'm not sure if I'm missing something here but that transpires (for me) not to be the case. For example, xmp iptc core is stripped out
Attached Image:
Marc Sabatella
Moderator
You mean you have IPTC info in the RAW file that is *not* preserved in any way in the JPEG file that you generate form that RAW file, even with the Preserve Metadata option checked? Definitely not what I see. Guess it might depend on exactly how you are generating the JPEG - I went to develop and hit Save/ Save As. Of course, I'm working from PEF, not CR2, but I can't see why that would matter.
Sam Dring
Moderator
You mean you have IPTC info in the RAW file that is *not* preserved in any way in the JPEG file that you generate form that RAW file, even with the Preserve Metadata option checked? Definitely not what I see. Guess it might depend on exactly how you are generating the JPEG - I went to develop and hit Save/ Save As. Of course, I'm working from PEF, not CR2, but I can't see why that would matter.
Marc
Just tried again on a new CR2. The only iptc carried forward into the jpeg is a shown below. I did as you - dev then save as jpeg preserve metadata. Strange!
Attached Image:
Subscribe to this topic via RSS
You must log in to post.
