Please: please round consistently

[Uwe]

Hello,

why is this such a problem and creates multiple entries?

Example Focal Lenght: These are the records in the database. Why is not rounded to one decimal place after the comma in the database?

The result in the client is:

This is not a new bug/works as designed. Please fix it asap.

Please round only at a central point, from my point of view at the import or rescan, i.e. where the entry is made in the database. The client should only display what is in the database.

Regards, Uwe

[Uwe]

This bug is still present in build 2555.

[Uwe]

Hello,

the error is still present in build 2936 and thus there are two entries with the same focallength in the database and thus also in the UI.
The following status in the Exif/XMP data of the sample photos:
Photo.CR2 with focallength: 6,528
Photo.XMP with focallength: 6,528
Photo.TIF with focallength: 6,528 the TIF file has been developed from the CR2 file.
Situation in the database.
1. initial status
Photo.CR2 id_focallength = 102465, value = 6.528
Photo.TIF id_focallength = 2853, value = 6.5
2. Photo.XMP is renamed to Photo.XMP.SAV so that there is no connection to the Photo.CR2 file. Then the data is read in again from the Photo.CR2 using "Read Tags from File". Result:
Photo.CR2 id_focallength = 2853, value = 6.5
Photo.TIF id_focallength = 2853, value = 6.5
and thus only one entry in the database and in the UI
3. Photo.XMP.SAV is renamed to Photo.XMP again so that there is a connection to the Photo.CR2 file again. Then the data is read in again from the Photo.CR2 using "Read Tags from File". Result:
Photo.CR2 id_focallength = 102465, value = 6,528
Photo.TIF id_focallength = 2853, value = 6.5
and so the incorrect initial situation is reached again. This means that Daminion treats the focallength differently depending on whether it is reading from the RAW file or from the sidecar XMP file.

Regards, Uwe