Re: Detect external sidecar modification

Thank you very much. It actually works as expected. I must have done
something wrong during my test yesterday.

Best regards,
Daniel

Am Di., 11. Nov. 2025 um 13:34 Uhr schrieb Maik Qualmann <
[email protected]>:

> Yes, digiKam detects changes to sidecar files if the modification date has
> changed.
> With the sidecar file setting enabled, digiKam uses as internal
> modification date from either the image or the sidecar file, whichever is
> more recent.
>
> I suspect you need to enable the option to re-read the metadata when
> changes occur in the digiKam metadata settings. Only then will a deep scan
> be performed that detects all changes.
>
> Furthermore, you need to check which metadata fields you are modifying
> externally and ensure that these are also read first in the advanced
> digiKam metadata settings (at the top of the list for each metadata type).
>
> Maik
>
> Am Di., 11. Nov. 2025 um 13:03 Uhr schrieb Daniel Schröer <
> danielschroeer-gM/[email protected]>:
>
>> Hello,
>>
>> I am new to Digikam. I am trying to configure it so that it works
>> together with another application (Immich in my case).
>>
>> I have configured it to  read from and write to sidecar files. Also, I
>> have checked "Scan for new items at startup", but not "Fast Scan".
>>
>> As I understand it, the program should detect externally modified files
>> upon startup. Does this also apply if only the sidecar file has been
>> changed, but not the actual image file? What if a previously non-existent
>> sidecar has been added externally?
>>
>> In my experiments this was not recognized. Is there a way to make it work?
>>
>> I am grateful for any comments and suggestions.
>>
>> Best regards
>> Daniel
>>
>