[claudio ercoli]

Hi,

I have seen that xmp file is always created, also choosing to build data embedded into the NEF file.

Is there a way to avoid this creation?

Thanks in advance

Claudio

[DavidB]

I have seen that xmp file is always created, also choosing to build data embedded into the NEF file ... Is there a way to avoid this creation?
Not if you want to add IPTC data to your images in DL Pro. With the current (XMP) standard for IPTC data, the only way of attaching the data to RAW files is with XMP sidecar files. This was essentially Adobe's decision, but it was then ratified by the IPTC, so that is the standard everyone now has to follow.

Old standard IIM can still be embedded in the RAW files, but not without creating the XMP files for the new standard data as well.

You can prevent DL Pro from adding IPTC data by unticking the "Add IPTC/XMP data ..." option near the bottom of the General tab of Preferences. If, later on, you want to add IPTC data to the NEF files, in a program such as BB Pro, you will still create XMP sidecar files.

You could of course choose to add IPTC data only to your converted JPEG or TIFF files, if that fits your workflow, and in that case the data will be embedded in the image file and no sidecars will be created.

I hope this helps.

[claudio ercoli]

Ok, it is clear, but I don't understand why Microsoft with windows vista, choose to include the info into the nef instead of sidecar files.
For this reason, under my point of view, also dlpro should permit this option without create sidecar,
Otherwise, because vista does not require it, to maintain a clean directory structure, I have to delete all the xmp files.

anyway it's just an idea.

Thanks

Claudio

[Chris Breeze]

DLPro uses the same method as Adobe and creates an XMP sidecar file when adding XMP data to raw files. There is a danger that modifying raw files may prevent some raw converters from being able to convert them.

[DavidB]

I don't understand why Microsoft with windows vista, choose to include the info into the nef instead of sidecar files.
If Microsoft did this, they are going against the agreed data standard. That is, of course, nothing new with Microsoft, and they have made a lot of trouble for everyone with their cavalier approach to standards like HTML.


For this reason, under my point of view, also dlpro should permit this option without create sidecar
Chris's reasons for not doing this are, in my view, very sound. Even a cursory review of posts to this forum will demonstrate how much we all need to maintain data compatibility between applications, and how far that ideal has been compromised in practice.