<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
You are correct. I don't need that option checked and I will disable it. When I first started migrating over to DigiKam from Windows Photo Gallery, I followed the DigiKam tutorial for "Setup of digiKam for Windows compatibility" and the option was checked.
I didn't see a downside to it and didn't even realize what would happen if I unchecked it.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I don't shoot in Raw but what you said is good to know. At this point I realize I won't be going back to the Windows Photo Gallery program so I'll try to pay more attention to what DigiKam uses for default options.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks!<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Digikam-users <digikam-users-bounces@kde.org> on behalf of Remco Viëtor <remco.vietor@wanadoo.fr><br>
<b>Sent:</b> February 2, 2022 3:11 AM<br>
<b>To:</b> digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users@kde.org><br>
<b>Subject:</b> Re: [digiKam-users] Reread metadata from files: Can this extend to XMP sidecars?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On mercredi 2 février 2022 04:57:16 CET Will Rose wrote:<br>
> Ah ok that was my problem. Thanks! I had:<br>
> <br>
> - Read from sidecar files (Unchecked)<br>
> - Write to sidecar file (Checked)<br>
> ---- Write to XMP sidecar for read-only item only<br>
> - Sidecar filenames are compatible with commercial programs (Checked)<br>
I don't understand why you need that last one. From your posts, I get the <br>
impression that your sidecars are created and used by Digikam. By default, <br>
digikam uses <filename>.<ext>.xmp for its sidecars, the compatibility option <br>
changest that to <filename>.xmp.<br>
> The solution was to make the "Read from sidecar files" option checked on the<br>
> system that was trying to read from the XMP sidecars into the database.<br>
> <br>
> It was a little messier than I had hoped though, but not really DigiKam's<br>
> fault. If you have your iPhone set to record "live photos", what gets saved<br>
> is 1 image in HEIF format, and 1 video in MOV format. However, they use the<br>
> same filename (i.e., IMG_1803.HEIF, IMG_1803.MOV). Unfortunately that means<br>
> that if I add a tag to the HEIF file, which gets written to XMP sidecar, I<br>
> have to make sure I don't add a tag to the matching MOV. If I do, it<br>
> overwrites the XMP sidecar with the video's metadata.<br>
So if you do NOT check the option for compatible sidecar names, you won't have <br>
such problems, as you'll get two different sidecars: IMG_1803.HEIF.xmp and <br>
IMG_1803.MOV.xmp ...<br>
<br>
(having identical base names for images is very common when shooting raw: you <br>
have the raw file *and* the generated jpg, png and/or tiff, which only differ <br>
in their extension; some programs store the development steps in the sidecar, <br>
and you certainly don't want those applied again to the exported files...)<br>
<br>
Remco.<br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>