IMatch 2023.8.2

[Tveloso]

The new Menus look really nice!  Thank you Mario.

I had a question on #02308 (Forced Update of Files) because of the way I have the XMP Face Region flags set.

When the user performs a forced update for a file, IMatch now deletes existing face annotations from the database before re-importing metadata from the file. This ensures that the handling for the XMP::IPTCExt:PersonInImage works and existing metadata in that tag is re-imported.

I have the Import XMP Face Regions flag turned off, under Edit->Preferences->Metadata2:

   

I do this because I am mostly indexing iPhone Photos these days, and I prefer to use IMatch's Face Recognition (over the Face Regions created by the Phone).

Will IMatch still perform the Face Annotation Deletion discussed in that Release Note, during a Force Update, if the user has elected to not import XMP Face Regions?

[Mario]

Yes. A forced update is supposed to delete all metadata in the database and import the file like a "new" file.

Under which conditions to you have to force-reload a file when you have created face regions?

[Tveloso]

Thank you Mario.  It makes sense that a Force Update is supposed to do that.

Under which conditions to you have to force-reload a file when you have created face regions?

I don't actually have a need to do that (I can't actually remember the last time that I've used that option), and probably especially not after I have already run Face Recognition to create Face Annotations (and the corresponding Face Regions after write-back).

[Mario]

OK.
The change I did corrects an oversight when forcing a rescan. If the file already had face annotations, XMP regions were ignored and that's wrong. The new behavior corrects this and also allows the new treatment of PeronInImage to work.

[Damit]

Some great updates that seem to deal with some very familiar issues.