No sidecar file on dng's?

I have setup LR to use sidecar files. Im using DNG.But there are no sidecars files in the same directory as the dng files.Maybe DNG save the info Inside the file?

Okey, thank you.
One more question. Is the metadata, such as the keywords, rating info embedded to?

Similar Messages

Sidecar file for DNG missing?

Currently I'm a little bit confused about what is happening to my LR cat.
After I have detected VCs with out of sync metadata in my LR catalog - see http://www.adobeforums.com/cgi-bin/webx/.3bc4bbeb
now it shows up a DNG-image with the question mark on top right of the thumbnail in grid view. Moving up the mouse over the icon gives me the hint that the sidecar file is missing!
The DNG has modified develop settings and metadata (after import). So far so good. In metadata panel it says that I (should) have an .xmp sidecar for this DNG.
My problem: I thought that I have read that DNG get all develop-settings and metadata written as xmp directly into the DNG-file - not into sidecar xmp.
LR1.1 on WinXP SP2.
Harald

I just recognized that LR seems to maintain 2 classes of DNGs.
a) DNGs I converted from CR2 upon import process are marked as "Digital Negative (DNG)" in metadata field for file format.
b) DNGs which I previously converted from CR2 to DNG using ACR converter some time ago are marked as file format "RAW".
The DNG which causes the trouble as mentioned above is one of the category b, so it is converted by ACR converter before import into LR.
Does LR behave as intended by design? Is Adobe even aware of this behavior?
Harald

How do I convert already imported and edited RAW (NEF) files + it's Sidecar file, to DNG?

Using Lightroom 4 now on a Mac. I have an extensive number of RAW (NEF) + Sidecar combos, that I wish to convert in groups, if possible, to DNG format, so the data of the sidecards is retained, and the DNG created does not need to be reedited from its origional camera state. What is the best way of doing this with a large number of files?

Does Library>Convert Photo to DNG not do this?
Edit: just checked. It does. While the DNG replaces the file in Lightroom, the Raw and the XMP are still there on the disk.
Edited to add more info

Feature Request: Metadata Export to Sidecar Files

I want to be able to export an image file's metadata to a sidecar XMP file that is named after the image file but with an .xmp extension. For proprietary raw files, that's the default. For DNG files, I can tediously force it by locking the file, loading it into Camera Raw, and selecting the "Export Settings to XMP" function. However I want to do this for several hundred or some thousand image files at once—so loading them all into Camera Raw just to make it export the metadata is not really a feasible method.
Worse yet, for JPEG files exporting the metadata to a sidecar file is not possible at all, as far as I can tell. When the JPEG file is writable then the exported XMP metadata will go into the file itself. When the JPEG file is write-protected then Camera Raw will entirely refuse to export the XMP metadata. This behaviour is inconsistent with other file types, as Camera Raw will happily export the XMP metadata to sidecar files for write-protected DNG files. By the way, there is another inconsistency between write-protected DNG files and proprietary raw image files, as Camera Raw will export XMP metadata for both into sidecar files but Bridge will export XMP metadata to sidecar files only for proprietary raw image files but not for write-protected DNG files. That doesn't make sense.
If an image file is write-protected then any changes to the metadata must go into sidecar files—as simple as that. Why are proprietary raw image files, write-protected DNG files, and write-protected JPEG files behaving differently in this respect? Sidecar files are fully supported for proprietary raw files, half-way supoorted for DNG files, and not supported at all for JPEG files.
Anyway—I need a way to select an arbitrary number of image files of any kind (in Bridge, not in Camera Raw) and then export all their metadata to sidecar files, one sidecar file for each image file, at the push of a button. It would be nice if I weren't forced to tamper with file locking first, just create those damn sidecar files when I'm asking for them. I'd even be happy with a createMetadataTemplate() or saveMetadataToSidecar() function in Bridge's scripting interface. There, I found a function to load a thumbnail's metadata from a metadata template (i. e. an XMP file; see applyMetadataTemplate() function)—but no way to save a thumbnail's complete metadata to a metadata template. If there is a way then please tell me. If there is no way yet then please provide one as soon as possible!

Curt Y wrote:
My first question is why you want to export metadata to sidecar files. With DNG one of the touted advantages is that all the metadata is written to the file and no XMP file is needed or created.
This actually is a disadvantage that keeps me from using DNG format. XMP sidecar files are extremely useful to transfer updated metadata from the working set to the backup archive. Sidecar files do make life a lot easier.
Usually I will download the memory cards' contents to the computer's internal hard disk. Then I will add some bulk metadata, rename the files, and make a backup to at least one, preferably two external hard disks. Then I will continue working on the images—refining captions, adding more keywords, add labels and rankings, apply ACR settings. Finally I'll want to update the metadata in the backups. With sidecar files, that would require the transfer of kilobytes. Without, I'll need to transfer gigabytes because I'm forced to update the whole image files when actually I only want to update the metadata ... just because Bridge is too dumb to let me export the metadata to sidecar files. Or actually, it does let me export the metadata to a sidecar file—but only for one image file at a time which is totally useless when I need to update the metadata of hundreds or thousands of image files.
The DNG format does support sidecar files. DNG files can have their metadata internally 'under the hood' or externally in a sidecar file. When there is a sidecar file accompanying a DNG file then Camera Raw or DNG Converter will read and use it just as they would for proprietary raw files ... that's very convenient. Only Bridge doesn't allow the user to take advantage of that flexibilty but forces him to use internal metadata always, whether it makes sense or not.

How do I force lightroom to (re)load an XMP sidecar file?

Good morning from Boston!
I am new to Lightroom and just finished importing my Aperture library into Lightroom 5 on a Mac. For that, I followed the instructions on Adobe's landing page and Lightroom solutions. For those not familiar with the instructions, you essentially export all your originals with an XMP sidecar file and then export all the adjusted/edited files as 16-bit TIFFs. Then you add them all back into Lightroom and get everything back into Catalogs, Labels, Ratings, and such by using keywords that were added while in Aperture. It took forever, but worked pretty well overall. I had about <1% fewer images in LR5 than in Aperture, which were likely suspected duplicates. So far, so good.
Here's is my problem. My keywords didn't always transfer over (the Keywording panel is empty). I did search forums and plug-ins, but seem to only find issues related to EXIF and GPS data. I also used "Metadata:Read Metadata from File" and "Metadata:Update DNG Preview & Metadata," which didn't do anything. I am suspecting that "Read from File" means "read from the image file itself but not from the sidecar file." Take file IMG_5888 as an example. This particular one was taken as RAW (.CR2) + JPEG on a Canon Rebel XS, but I am having the same issue with RAW only on my Canon EOS 6D. Same goes for JPG + XMP. Puzzling thing is that other files loaded just fine.
In the directory/folder where the file is, it looks like this:
IMG_5887.CR2
IMG_5887.JPG
IMG_5887.XMP
IMG_5887.dng
IMG_5888-2.JPG
IMG_5888.CR2
IMG_5888.JPG
IMG_5888.XMP
IMG_5888.dng
IMG_5889-2.JPG
IMG_5889.CR2
IMG_5889.JPG
IMG_5889.XMP
IMG_5889.dng
The .dng were generated by Llightroom. Now, the sidecar files typically have something like so in them (I cut out some keywords for clarity—you get the idea):
<rdf:Description rdf:about='' xmlns:photoshop='http://ns.adobe.com/photoshop/1.0/'>
</rdf:Description>
<rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>
<dc:subject><rdf:Bag>
<rdf:li>Black Head Trail</rdf:li>
<rdf:li>Cliffs</rdf:li>
<rdf:li>Maine</rdf:li>
<rdf:li>Monhegan</rdf:li>
<rdf:li>RAW</rdf:li>
<rdf:li>Sunrises</rdf:li>
<rdf:li>United States</rdf:li>
<rdf:li>Waves</rdf:li>
</rdf:Bag></dc:subject>
</rdf:Description>
So, the keywords were exported from Aperture, but for some reason, Lightroom isn't always loading them from the XMP file.
On a related note, the keyword hierarchy that was exported as text file from Aperture and imported into LR5 worked well. Everything appears to be there and in its place.
Any ideas for a Lightroom rookie as to how I can get LR5 to read those XMPs? Over 20,000 didn't tag, so I would rather not do this by hand!
Many thanks in advance,
Paul

John, what a pleasure. Well, here is the update. First, copying over 300GB of pictures to a drive and then backing up said drive takes a bloody long time. But here is what happened, for others who might run into the same issue.
I first tried a small set of files to narrow down whether the issue was the Aperture export or the Lightroom import.
Conclusion: the "issue" is mostly on the Lightroom side.
What I found: Although Aperture will export an XMP sidecar for a JPEG, Lightroom will not read it, ignoring all keywords. I exported a set of JPEGs only and then opened the XMPs with an editor (well, the UNIX cat command, to be exact). The information was there, keywords and all. However, LR appeared to ignore XMP for JPEG. That said, if you have a RAW+JPEG in Aperture, the RAW XMP sidecar will overwrite the JPEG one, effectively leaving you with only the keywords for the RAW version. That shouldn't be an issue for most, but just in case you have different keywords for your RAW and JPEG images, be aware of this.
What I did:
Back up all the images and catalogs/libraries from Aperture and LR.
Make sure #1 worked out.
Make sure #1 worked out (not a typo; you really need a backup, as you will find out below).
Delete the old JPEG files that were uploaded into LR. I had them in a From Aperture folder, as instructed by John's article and Adobe's landing page (referenced in John's article), so I deleted all JPEGs in that folder. My Aperture database was not affected and in fact resides on a different drive.
Run find . -iname "*.JPEG" -delete [if you do not know how 'find' works, ask someone, as this can potentially delete every single file accessible to your computer!]
Run find . -iname "*.JPG" -delete [ditto! Don't tell me I didn't warn you!]This is why you need to backup everything. I was deleting copies/exports of the originals in Aperture (again, read John's article for the difference) and still had the originals in Aperture, on a different drive.
[I didn't worry about the unmatched/orphaned XMP files for the JPEGs only; they are tiny and don't hurt.]
In LR, select 'Library:Find All Missing Photos.' If asked, remove them from the Catalog only.
Create a Smart Album in Aperture and include only 'Filetype is JPG.'
Select all images in that album.
Export those original images per Adobe's landing instructions, but for this set of images, select 'Include IPTC' instead of creating a sidecar file.
When Aperture is done, open LR and Add the whole 'From Aperture' folder back to LR (make sure 'Ignore suspected duplicates' is selected.
John, as you rightfully pointed out, this is tricky. If my experience is any indicator, I would suggest migrating in 3 steps:
Export all RAW originals with IPTC in XMP sidecar files.
Export all non-RAW originals (which I would guess are mostly JPEGs) with IPTC included. (not a sidecar)
Export all versions as 16-bit TIFF.
If #2 is added, then the process is actually most straightforward. Steps 1–5 in the first block above were to clean up the mess that I had created and should not happen otherwise (famous last word...)
If the above is unclear, please let me know and I will expand on it. If I had the issue, I suspect others will as well.
Thank you for your help and suggestions. I am officially migrated to LR and up and running!
Cheers from Boston,
Paul

Sidecar files

Opened LR this evening and an error message appeared - sorry, didn't make a note of it.
Anyway, went to one of my folders and approx 14 images (dng files) reverted back to their original state and orientation. Each photo then had, in the top right corner in grid view, the ? telling me that the sidecar file was missing.
What's going on here and how do I get this sidecar file back or, more importantly, stop other sidecars going missing?

Try what John says. It may well be that somehow you moved them, etc, or LR simply lost rack of them.
However, LR will also put up ?s when in fact the images are not lost. Usually just clicking on the ? will make it disappear in this case. You can open images that are reported lost when they are not and work on them. If they are truly lost, you can't.
I have 20,000 images in LR for testing purposes and at any given time LR will report up to 289 images with ?s, but in fact only 4 or 5 are truly lost. Next time I open LR it may say 179 or some other number are lost. Go figure. Others have had the same glitch. It is annoying to say the least, and sooner or later it will be fixed.

Option to always use sidecar files for XMP

Lightroom gives you the option to write metadata to XMP files, which is convenient if you want to share data with other programs (ACR, various DAM programs). In the beta versions, this data would always be stored in .XMP sidecar files, presumably for safety reasons. However, V1 writes the XMP data into the image file itself for those formats that support it (DNG, JPG, TIFF).
I would really like to have the option to *force* Lightroom to use sidecar files for XMP data, like the betas did. The current V1 behavior (embedding data) is quite inefficient for fairly common backup scenarios.
For example, I tend to back up all my raw files onto DVD after importing and culling. In addition I make a daily backup of all metadata that gets sent over the internet to a web server - a relatively small upload. What happens if I use DNG for my raw files and update something as small as a keyword? Indeed, *all* of the corresponding DNG files are modified, and because my backup software cannot know that only the XMP data has changed, all files must be burned to DVD again. If the metadata were stored in sidecar files, a simple, efficient metadata backup would take care of things.
To implement this, a simple switch in the preferences would suffice, and the necessary code is already there. The only possible problem is the occurrence of two files with identical names, excluding the extension. For this case, I can see four different 'solutions':
1) Force XMP metadata to be synchronized between files with equal names
2) Make an .XMP sidecar file for only one of the files (always the raw file, for example)
3) Update the XMP specification to specify what should be done in this situation (maybe include the file extension in the XMP data)
Reards,
Simon

Actually, I don't (notice the 'if' :)). And this is only one of the reasons. I just picked DNG as an example, to keep things simple and because it seems Adobe wants DNG to work well for photographers.
However, the same applies to JPG and TIFF images. I often end up changing details in the metadata after the image has been finished. For example, to correct the spelling in a keyword that has been applied to half the images in my database... Talking about a nightmare scenario!
Simon

LR2.7 "Missing Sidecar Files" issue

Hello,
LR2-7, Win32 Vista:
in a folder of 182 photos within catalog of 16 k photos:
suddenly, most photos show in Library view and the stripline a top right corner question mark and icon stating "sicedar file missing". In Catalog preferences the checkbox for "automatically write changes to XMP files" is not set (was never set), the folder does not contain any other files than the photos:
- in the beginning of this problem, these were cr2 files. It was then possible, to click on the icon/questionmark and trigger a dialogue "forget sidecar / continue?" but only for single files, NOT for a selection on click - come on.
- I converted the entire folder to dng files (my usual setting), NOW, the question marks all are still there, but NO dialog available any more on click.
- I pressed ctrl-S to create a sidecar file - zero reaction, nothing. Is there a secret place for sidecar files I would have to know?
I can of course remove photos from the catalog, and re-sync - this cures the issue.
- Up until now, I had a reliable catalog of approx. 16k photos - is this the end of it? I do do backups, but I can't afford a "sometimes" performance of Lightroom.
- what do I do about development settings already done when removing /re-syncing photos to get rid of the icons and "missing sidecars" (I don't miss them, why does LR)??
Anyways, this issue pops up on the forum on 1.1 and 2.3 versions... any sugggestions how to go about this on 2.7? Is this a feature?
thanks,
Gerd

Dear dj_paige,
thank you for your note,
please see my comment to your email below in your text
DNG photos do not have sidecar files. So, their absence is not a problem.
- I know, I never generated any sidecar files and understand that there should be none for DNG. However, for the CR2 files, LR displayed the prominent ? and tooltip "sidecar file missing", and this persists even after converting to DNG.
I'm not sure what problem re-synching will cure. I do not recommend you "remove photos from the catalog, and re-sync", as you lose information that is catalog only (such as collection membership, edit history, color labels, pick flags and a few other things). In fact, I think it is a terrible idea.
- agreed. For this reason, I sent a note to the forum
If your catalog within Lightroom is working properly (and you haven't really convinced me that there is anything wrong), then again I don't know what the problem is.
- See above: for the CR2 files, LR displayed the prominent ? and tooltip "sidecar file missing", and this persists even after converting to DNG. Nothing else is wrong, HOWEVER, this icon and message is nonsense and should not be displayed
It sounds as if you are using the metadata as some form of backup of your catalog. It is not a backup; metadata enables you to share *some* information from your Lightroom with other applications. Other information in your catalog is not stored in the metadata written to files. The only way to create a backup of your catalog is to actually make a backup of the catalog file, which is a Lightroom option you can turn on. I consider making backups of your catalog file to be mandatory.
- NO, your assumption is incorrect. I do backup the entire catalog file.
Best regards,
Gerd

Xmp sidecar files- move/delete Bridge CS3

Hello
Anybody know a good way to hide the XMP files- or can they be moved to another folder? I don't suppose it is a good idea to delete these sidecar files
Is there a way for me to specify in Bridge CS3 that I do not want the .xmp files to be saved in the same folder as the images they are attached to?
How come .xmp files get saved for some of my tagged images and not others?
thanks

I suppose you could go ahead and make them all hidden files. But you're going to have to do that every time you start working on another new raw file. If you're going to work with raw images you might as well just get used to seeing them. Another alternative would be to use the DNG converter to convert your raw images to DNG files. Then you wouldn't have to worry about XMP files at all because all the metadata is stored within the DNG. But that's up to you.
Another thing to consider. If you hide all those sidecar files and then decide to move your images you will have to go through the process of making them all visible so that you can copy them. Personally, I don't think it's worth it.

Question on converting edited CR2 files to DNG

Sorry, I cannot find a separate DNG forum. If this question is in the wrong place, please direct me to the correct forum.
I have lots of CR2 RAW files on my computer, and I am considering converting them to DNG. Many of these RAW files have already been edited and so have a separate XMP sidecar file containing the edits in the same folder. If I convert (using the Adobe DNG converter) these edited RAW files to DNG, what is converted? The CR2 RAW file alone, so that the converted DNG file is the same as the original unedited CR2 file? If so, what happens to the orphaned XMP file? Ignored?
My concern is that I will lose all RAW edits if I convert to DNG because the conversion process ignores the edits contained in the separate XMP file.
Can someone explain this to me? Thanks.

So what you're saying is that the DNG conversion de-mosaics the image? I guess that's not surprising, since for compatibility with older Photoshop versions you'd have to deliver a more or less standardized format.
Kind of throws a big monkey wrench into claims that converting to DNG is functionally equivalent to opening raw images directly though... I was experimenting with a "fall leaves" image last night and no matter what I tried with the 2010 process I was still able to get more detail in bright red leaves with the 2003 process.
I suppose that says if you want maximum flexibility and control you'd better buy the Photoshop upgrades and stick to opening raw camera files directly. A variant on the "if you want to play you have to pay" adage.
-Noel
P.S., Does the DNG converter read the centralized database as well as XMP files? I personally prefer the database to the extra files.

How to save metadatas in RAW files (and not in external .XMP sidecar file)

Hello,
I would like to save metadatas (for example keywords) inside the RAW files, and not in external .XMP sidecar file.
How to do this in Lightroom ?
Thanks
Josh
PS: is XMP a file format (= .XMP files) or a metadata format that can be embedded either in a .XMP sidecar file or in the RAW itself ?

MarvinFoster wrote:
It's a horridly named catalog setting since if you are using DNG you don't have XMP files but it does the same thing, it updates the dng with the catalog settings.
XMP does not mean XMP FILES per se.
XMP is a metadata format/standard. so it´s not horrible named but simply missunderstood.
http://en.wikipedia.org/wiki/Extensible_Metadata_Platform
XMP can be used in several file formats such as PDF, JPEG, JPEG 2000, JPEG XR, GIF, PNG, HTML, TIFF, Adobe Illustrator, PSD, MP3, MP4, Audio Video Interleave, WAV, RF64, Audio Interchange File Format, PostScript, Encapsulated PostScript, and proposed for DjVu. In a typical edited JPEG file, XMP information is typically included alongside Exif and IPTC Information Interchange Model data.

Do I need to keep my xmp files after converting my raw files to dng?

I originally set up Lr to automatically build xmp files. Recently, I decided to go with dng files and have converted all my raw files to dng. Can I now delete all my xmp files and change my Lr setting so xmp files are no longer automatically produced?

WDKlein1000 wrote:
I think I've got this straight. My goal is to keep the xmp data with the image file (embedded into the file in the case of dng files) as well as in the Lr catalog. I still need to auto (or manually) save xmp files in order for Lr to save the xmp data internally to the dng file. Right?
Perfectly right.
WDKlein1000 wrote:
I've been converting to dng after I have done my initial Lr processing of the raw files and the sidecar files have already been produced. When I convert to dng, the side car files aren't automatically deleted.
I *think* if you say: do not delete previous raw, it keeps both xmp and original raw files. However, if you say: delete original raws upon conversion, it will delete both raw files and xmp sidecars. In other words, they are treated as a unit. So I suspect your raw files are not being deleted either, right? Note: if this is the case, then whenever you sync your folders, it's gonna wanna pull in all the original raws again. If it were me, rather than deleteing the xmp and leaving the sibling raws, I'd move both to a backup.
WDKlein1000 wrote:
I wonder if the sidecar files would ever be produced if I imported with the option to convert to dng and then wouldn't ever be editting the raw files?
They would not. If you know you are going to prefer DNG, it seems prudent to convert upon import.
WDKlein1000 wrote:
I know the sidecar files are relatively small, but I guess it wouldn't hurt to go back and delete them once the xmp data is embeded in the dng files. Right?
Right again - delete away...
UPDATE: I didn't see AR's previous post when I wrote this, sorry for redundancy.
Rob

I edited RAW files as DNG's and need the xmp files- are they embedded in the DNG files?

I was editing for someone else and the like the xmp files to see the RAW adjustments- I edited them as DNG because that is how I'm used to doing it. Now I know but they want me to supply the xmp files which did not write. Is there a wat to do this or do I need to re edit them as RAW's?

DNG files don't have XMP sidecar files. Everything is written to the header of the DNG. And as far as Lightroom goes, It will be necessary for you to specifically write the data to XMP files. Otherwise the adjustments will only be stored in the catalog.

Sidecar file has conflict

* I imported several thousands photos (JPGs) into lightroom.
* I edited metadata of these photos before import in lr with some other tools
* I selected "Automatically write changes into XMP" in lr catalog settings
* I reorganized my keywords
==> I saw that some of those photos has "Sidecar file has conflict" (the "!" sign at the upper right corner in grid view)
* I searched for the error and I saw, that some of the photos did only have IPTC and no XMP metadata included.
* If I copy IPTC data to XMP, I can save metdata to file in lr
==> My question: Because there are thousands of photos: Is there a way to search only those photos which have "Sidecar file has conflict" in lr?

To all contributing on this thread -
A .bat file called from a Shortcut Icon works as Rob suggested: only two lines (in Windows).
    Start sqlite3.exe "Lightroom 3 Catalog.lrcat" ".read BadToFile.sql"
    Start "" "C:\Program Files\Adobe\Adobe Photoshop Lightroom 3.3\lightroom.exe"
The BadToFile.sql includes the code previously suggested with a couple of lines to define file name and turn headers off. I then set up a smart collection for LR marked images. Now occasionally when I want to update image, instead of selecting all and updating them with Ctrl-S, I:
     1.     Exit LR and re-enter;
     2.     Run the LR Tranporter routine to mark images that are in the file list just created before start-up;
     3.     Select the smart collection and the select all images in there; then
     4.     Hit Ctrl-S.
Not a bad short-term solution. Also, if I then exit and repeat the step, it leave in those few images that can't ever seem to get updated with Ctrl-S and I can work on them individually by clicking the update icon or Updating DNG Previews (sometimes these work).
Anyway thanks for this thread.
Jeff
PS - The marking "Red" also works similarly but the downside is that when selecting the collection of those that are "Red", you can't save them before removing the "Red" or they will continue to have a mis-match when the "Red" is removed. You have to first save a quick or dumb collection to not lose the selected group. Also, if you have color labels in use, it overwrites them in "Red" and can't remember what color it was before - can be a bummer.
PSS - After playing with the sqlite command window, I agree that the table structures of this LR database seem a bit of a mess. It has probably morphed over time and may not be the best design if one were starting from scratch. I therefore wouldn't want to spend too much time working with this database as a re-structure seems in order sometime in the future.

Lightroom 5 not loading .xmp sidecar files during import

I have a folder of RAW images that also contain .xmp sidecar files that I am trying to import into Lightroom. The images import with no issues but it appears that Lightroom is ignoring the sidecar files since none of the metadata they contain are appearing in the catalog. I am seeing the same behavior when I take the same RAW/.xmp files and first run them through the DNG converter and then import the DNGs into Lightroom (again, no metadata). I have tried to update the catalog by both writing to file as well as reading from file but nothing I do will get the metadata read into the catalog. Anyone have any ideas? Thanks...

Rob Cole wrote:
Whoops - I just realized you had also tried force-reading metadata after import.
If that doesn't work, then either the xmp sidecar files were not named properly, or something in them Lr not liking (presumably)
If you can make a copy available (of original photo file + xmp sidecar, e.g. zipped) I can have a look.
PS - Lr will only read DNG sidecar if newer than DNG (and hence embedded xmp).
Rob
Thanks Rob. New to these forums so still trying to feel my way through it. I tried both using the context menu as well as the metadata menu option for a selected image with no success. I have tried this with an image I had previously converted to a .DNG and the metadata does not load into the catalog for those either. However, I can't determine that the .DNG version had the metadata loaded or not. I don't know enough about the file structure or have the tools to peer inside to verify. The .zip file is 12MB in size so I am unable to insert the RAW file but I can't figure out how to attach to .xmp file either. Will continue to research to see how I can do that...

No sidecar file on dng's?

Similar Messages

Maybe you are looking for