I was debugging my PC's samba connections with Wireshark, when I started seeing constant xmp file access errors. I have never used sidecar files, but in any case I made sure that the read/write options on Digikam aboyt sidecar files were disabled STEPS TO REPRODUCE 1. Make sure that read/write sidecar files are disabled 2. Select any image in your library 3. Use any tool to see digikam file access. Observed for first time with wireshark 4. Digikam try to access to the xmp file sidecar (1.jpg, search for 1.xmp and 1.jpg.xmp in the same folder). OBSERVED RESULT Digikam try to find for each selected image, the sidecar xmp. even when the use of sidecar files is disabled. This is an avoidable waste of resources especially when the photos are being accessed remotely, for example via SMB EXPECTED RESULT Since the use of sidecar files is disabled, Digikam should never attempt to access sidecar files. It's not really a big problem, especially when we work with local files, but in remote files, where we usually have lower performance and higher latency, any improvement is welcome. SOFTWARE/OS VERSIONS Windows: 11
I'll debug it tonight, but I'm pretty sure digiKam won't look for sidecars during startup scan if the option is disabled. A quick look at the code confirms this. If you select a single image in the GUI and have the Properties tab open, it will look for a sidecar. This is intentional because the property is intended to show whether the image has a sidecar, regardless of the setting to read or write sidecars. Maik
It can be a rule in Exiv2 engine where we don't have a control in digiKam side... Gilles
Thanks for the support. It seems to happen only when selecting an image, no matter if the properties panel is open or closed
A search for a sidecar only occurs when the Properties tab is selected, regardless of whether the sidebar is collapsed or expanded. This behavior is desired because we want to indicate whether a sidecar exists. This is not a loss of performance, it is only searched for when a file is selected individually. There are more sidecar searches when copying and moving images. We need to make sure that if sidecars are present, they are also copied/moved. Otherwise they would be left orphaned, regardless of whether sidecars are activated or not. I close the bug, the behavior is technically necessary. Maik