importing sidecar files generated by other applications
When importing an image, darktable automatically checks if it is accompanied by a sidecar file. As well as looking for files named
<basename>_nn.<extension>.xmp (darktable’s XMP file naming formats) darktable also checks for the presence of a file in the form
<basename>.xmp (the naming format for Lighroom’s XMP sidecar files). Files with the latter naming format will be read by darktable but will not be written to. Once the image has been imported, darktable will generate an additional XMP file using its own naming convention.
At present, darktable is able to deal with the following metadata from Lightroom-generated sidecar files during the import phase:
- tags (including hierarchical tags)
- color labels
- GPS information
In addition, darktable has been designed to help migrate some image operations from specific other applications. The aim here is not to make darktable a drop-in replacement for any other software, but rather to help you recover part of the work you have invested into your image on migration to darktable. It is important to understand that this import process will never give identical results. The underlying development engines are very different from application to application, and additionally depend a lot on the specific image. In some cases, the results may be similar but often, further adjustment will be required in darktable.
This migration happens automatically when entering the darkroom view, provided that a corresponding XMP sidecar is found.
At present, darktable is able to handle the following development steps from Lightroom-generated XMP files (with the corresponding darktable module in parentheses):