differences for "XMP storage location" parameter

[jj95]

I have been searching for a clear explanation on "XMP storage location" parameter

In V7 there are 3 possibilities

- according to the XMP standard
- always as a sidecar file
- according to the XMP standard with sidecar file

What is exactly the difference between each ?

In my case I have left the first choice, which seems to be the default one, but when importing number of files, I get loss of performance, as the synchronisation process is sometimes very low or sometimes freezes. I was wondering if changing the parameter for XMP storage location could help.

[Hert]

First of all: a warm welcome to the forum.

You mention performance as a possible reason to change this. Best to check these if you get hickups:
1. Make sure that your catalog files are on the fastest drive available, preferably an internal SSD drive
2. Make sure that the catalog folder is excluded for *all* virus scanners that you have installed, if Windows then also exclude the catalog folder in Windows Defender
3. At least try to compact the catalog once to see if that makes a difference. After a large database upgrade (as in V7 to v2023) then a one-time manual compact of the catalog may be helpful.

Below is what the Tips system has to say about that field.

The differences are:
1. According to the XMP Standard. This means that metadata is written embedded for file formats that can have them embedded (eg JPG/TIF/DNG/PSD). Other file formats, like RAW formats, will have the XMP written in a sidecar file

2. Always as a sidecar file. As the name suggests, with this setting you will always get a XMP sidecar file and XMP is never embedded in the file. This is not recommended if interoperability with other software is important. The standard is what XMP supporting software follow and so you should not expect any other software to look for XMP in a sidecar file for formats that should have it embedded by the standard

3. According to the XMP Standard with sidecar files. This is a combination of the first two. Basically you will get embedded XMP for formats that can hold XMP but you will also always get a sidecar file.

XMPStorageLocation.png (232.23 KiB) Viewed 2189 times

[jj95]

Dear Hert

Thank you for your clear response !

Concerning my setup, I am using V7, with catalog on SSD and images on the same SSD, plus on an external HDD (USB).

Will v2023 improve performances ?

How can I activate help popups ?

[jj95]

For point 2, I have only Windows Defender, but I will exclude the catalog folder
For point 3, I have done recently compact operation, but I will redo

[Hert]

Will v2023 improve performances ?

The same data needs to be synchronized, so no.

How can I activate help popups ?

Click the ? icon in the left sidebar. Then select Tips

[jj95]

Thanks.

I will give feedbacks when compact operation will be done.

I have launched modification of thumbnails size, downto 1024 px, in order to, I hope, decrease thumbs database (currently 20 Go). PSU is currently processing ....

[jj95]

The poor performance was coming from troubles with the SSD itself ....

It is corrected now, and seems faster.

Meanwhile, I have upgraded to PSU v2023, migrated and compacted the database.

Thumbnails downto 1024 px, in order to decrease thumbs db file size (now 14 GB for 76 k images)

Concerning XMP parameter, I have left to default one "According to the XMP Standard".