Camera model no longer read from WIndows Explorer value after ExifTool change

[Wim]

The Camera model of my .heic file is 'iPhone 12' as can be seen with statement
exiftool -model myfile_tst.heic
I changed the Camera model (-model) with exiftool (to 'iPhone 12x') with statement
exiftool -overwrite_original "-model=iPhone 12x" myfile_tst.heic
Subsequently I changed the Camera model in windows explorer file details (to 'iPhone 12xy').
If I now run statement
exiftool -model myfile_tst.heic
it seems the changes in Windows Explorer are no longer seen, as the output is always 'iPhone 12x'.

I have this issue with Exiftool 12.51 and 12.52 on Windows 10 22H2 (OS Build 19045.2251).

Is this a bug? Some difference between the Windows explorer Camera model tag and the -model tag written by exiftool?

Original .heic file and screenshot with statements input/output attached.

[Phil Harvey]

Which version of the HEIC file did you upload?  You should look at the version written by Explorer with the "iPhone 12xy" model using the command in FAQ 3.  If the "12xy" isn't in the file, then could it be that Explorer is changing some external file property and not writing to the actual file?

- Phil

[Wim]

Hi Phil, thanks for your prompt reply. The uploaded file is the original file without any changes to the Model tag.

There is indeed a duplicate in the end result.
I now understand the process:
The original file only has [IFD0] Model.
The 'Exiftool -model=' command updates the [IFD0] Model but also creates  a [XMP-tiff] Model.
Subsequent changes in Windows Explorer update and show the [IFD0] only, whereas exiftool by default shows the [XMP-TIFF]. (Subsequent updates with Exiftool update both.)

Workaround for the confusion is to write with exiftool with prefix IFD0 to avoid the creation of the XMP-tiff, by using statement
exiftool "-IFD0:model=iPhone12x" myfile_tst.heic
(see also faq 9b)

Nice to learn that exiftool can be used in a perfectly controlled way :-)
I leave the answer to the following thoughts to your most valued opinion:
Is the default creation of the XMP-tiff (when not using prefix) expected behavior?
And is showing the XMP-tiff by default (not IFD0) expected/wanted?
In this use case (working with Windows Explorer) it seems unwanted to me.

[Phil Harvey]

Is the default creation of the XMP-tiff (when not using prefix) expected behavior?

This is a byproduct of the fact that HEIC is a QuickTime-based format, and ExifTool creates tags in the XMP group by default for this format.  It makes sense to change this for HEIC, since EXIF is preferred in this variant.  I'll change this in the next release.

And is showing the XMP-tiff by default (not IFD0) expected/wanted?

Good point.  I'll change this too.

- Phil

[Wim]

Great. Thanks for all the nice work.

Best regards

Wim