Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added links to the ways of importing sidecars to the overview/sidecars page #721

Merged
merged 3 commits into from
Jan 25, 2025
Merged

Added links to the ways of importing sidecars to the overview/sidecars page #721

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ab1fa09
Update sidecar.md
kofa73 Jan 25, 2025
1cbf293
Fixed link to sidecar-import.md
kofa73 Jan 25, 2025
6f5d38f
Fixed link to history-stack.md
kofa73 Jan 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/overview/sidecar-files/sidecar.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,7 @@ Your work is automatically synchronised to the sidecar files without the need to
In addition to the sidecar files, darktable keeps all image-related data in its library database for fast access. An image can only be viewed and edited from within darktable if its data has first been loaded into the library database. This happens automatically when you first [import](../../module-reference/utility-modules/lighttable/import.md) an image. If an image is subsequently re-imported, the database will be updated from the contents of its XMP file.

Once an image has been imported into darktable, the database entries take precedence over the XMP file. Subsequent changes to the XMP file by any other software are not visible to darktable -- such changes will be overwritten the next time darktable synchronizes the file. On request, darktable can be configured to search for updated XMP files at startup, offering a choice to update the database or overwrite the XMP file where changes are identified. This configuration can be changed in [preferences > storage > XMP sidecar files](../../preferences-settings/storage.md#xmp-sidecar-files).

To import sidecar files created by other applications, see [importing sidecar files generated by other applications](./sidecar-import.md).

To load a sidecar file (e.g. one received from another darktable user), see [load sidecar file](../../module-reference/utility-modules/lighttable/history-stack.md).
Loading