So I did my update from 1.7.1 to 1.10.5 yesterday, and as usual a "deep compare" between them.
Nice work Pierre, there is something new for everyone!
And since we have a new XnThusiast who writes out the changes I came accros the greatly approved support for Exiftool.
I got interested in using it for the Browser Details view.
Until now I always used an Open with... to start a cmd file calling exiftool to gather the attributes for my camera's that I was interested in.
After doing some reading it seems that a path must be filled in Settings, Integration, Paths.
Remarkable, since exiftool comes with XnViewMP already.
Anyway, I filled the field with: C:\Program Files\XnViewMP.1.10.5\AddOn\exiftool.exe.
Probably that is the curlpit, and exiftool needs to be started with a parameter? Though I can't imagin.
Anyway, still very curious how someone can write about an option in Catalog (Store Exiftool Fields) that I don't have, no matter what I do.
There is no Store Exiftool Fields checkbox in my case, not even when I drag settings to fullscreen:
My guess is that I should be able to open the Exiftool list at the red arrow, but it's empty:
Also the Catalog filter shows no "EXIF" as mentioned would be new, only "Date":
So then come all the tests that can be done, none of them resulting in an option "Store Exiftool Fields" option being available:
(in all my tests my own configuration is out of the picture)
1-Put away my settings so XnViewMP comes out of the box at first startup.
2-Copy one of my Windows 11 VM's to use it as test, downloaded the installer (I always use zip) and installed, filled the exiftool path, added some camera files.
3-Did the same with a Manjaro (linux) VM, same result.
4-Then downloaded version 1.9.6 as this was the version where Store Exiftool Fields was metioned the first time.
None of the tests resulted in finding an option Store Exiftool Fields.
The only thing I noticed during testing is that there is some strange behaviour regarding the location of my xnview.ini file, it disappeared from where it should be and reappeared in C;\ProgramData, but I'll investigate that later.
So, wat am I doing wrong?
How to use the new exiftool functionality
Moderator: xnview
-
HanVroon
- Posts: 232
- Joined: Thu Jan 28, 2010 7:30 am
How to use the new exiftool functionality
You do not have the required permissions to view the files attached to this post.
-
user0
- XnThusiast
- Posts: 2850
- Joined: Sat May 09, 2015 9:37 am
Re: How to use the new exiftool functionality
it has been moved to Metadata group in Settings > Metadata
-
HanVroon
- Posts: 232
- Joined: Thu Jan 28, 2010 7:30 am
Re: How to use the new exiftool functionality
Thanks! I overlooked that.
Path to exiftool isn't necessary, just the Exiftool checkbox and Update metadata (with a folder with camera files in focus).
Path to exiftool isn't necessary, just the Exiftool checkbox and Update metadata (with a folder with camera files in focus).
-
jkm
- Posts: 412
- Joined: Sat May 11, 2024 12:43 am
Re: How to use the new exiftool functionality
I'll can shed some light on this for you, if I may...
Using a shortcut in the manner you describe is now obsolete. You won't have to do that anymore. Advanced metadata collection is now integrated into XnViewMP and will happen automatically once the appropriate settings are made.
XnViewMP was long bundled with exiftool, but it was an antiquated version. Exiftool underwent significant implementation changes in 2024 that provided much faster execution in certain usage scenarios, that Pierre had never incorporated. (The version bundled with XnViewMP is now reasonably current, but is still updated infrequently.) So allowing XnViewMP to use a separate installation of exiftool provides for a few benefits:
1. The user can upgrade exiftool at will without monkeying with the XnViewMP folder contents
2. Customized exiftool configurations or .Exiftool_config files need not be backed up and restored when upgrading or reinstalling XnViewMP; they are safe in a different location.
3. The user can easily switch between bundled and custom versions of exiftool, if needed.
You can learn more about upgrading or using a separate instance of exiftool here: viewtopic.php?t=49746
So if you just want to use the default version of Exiftool that is bundled with XnViewMP, and don't need a customized .Exiftool_config, then simply leave the "ExifTool Path" setting blank. That causes the app to use the bundled version of exiftool. That is the normal case for most users, and that's why that field is blank by default: it just works. Essentially, it's an override field to be used if needed.
Take the following steps:
1. For Settings:Integration:Paths:Exiftool path, just empty this setting out; leave it blank.
2. Ensure Settings:Metadata:Exiftool is enabled/checked under Metadata Import.
3. Click OK, then close and restart the app.
4. Go to Settings:Catalog, and click the "Update Metadata" button. This will collect comprehensive Exiftool metadata for all the image files in your catalog. You should see a progress bar that may last a few minutes depending on the size of your catalog. This will likely be faster than running exiftool on your own, because it's multithreaded.
When that's all done, you could restart the app just to ensure all counters in the Catalog Filter update. You should then see populated metadata trees in the Catalog Filter, and be able to add enhanced metadata columns in Details view.
The "Update Metadata" should really only need to be a one-time step, since you are upgrading. You could use it later if you make a lot of metadata changes outside the app. But generally, XnViewMP will scan new files as they are added to the catalog, so the information will be automatically added to.
Hopefully this helps...
[Edit: I see you posted while I was typing.]
Yes, that was the intention. The new capabilities are very powerful.HanVroon wrote: Fri Mar 20, 2026 1:32 pm So I did my update from 1.7.1 to 1.10.5 yesterday, and as usual a "deep compare" between them.
Nice work Pierre, there is something new for everyone!
I think you might misunderstand my role, but that's ok, it doesn't matter. If you'll accept assistance from someone whose account is so much newer than your own, I'll try and help you.HanVroon wrote: Fri Mar 20, 2026 1:32 pm And since we have a new XnThusiast who writes out the changes I came accros the greatly approved support for Exiftool.
I got interested in using it for the Browser Details view.
Until now I always used an Open with... to start a cmd file calling exiftool to gather the attributes for my camera's that I was interested in.
Using a shortcut in the manner you describe is now obsolete. You won't have to do that anymore. Advanced metadata collection is now integrated into XnViewMP and will happen automatically once the appropriate settings are made.
Actually, no, that setting does not need to be filled in, except in certain circumstances. The setting is only required if you want to use a different instance of exiftool than the one bundled with XnViewMP. This is to make it easier for users who have more customized installations.HanVroon wrote: Fri Mar 20, 2026 1:32 pm After doing some reading it seems that a path must be filled in Settings, Integration, Paths.
Remarkable, since exiftool comes with XnViewMP already.
Anyway, I filled the field with: C:\Program Files\XnViewMP.1.10.5\AddOn\exiftool.exe.
Probably that is the curlpit, and exiftool needs to be started with a parameter? Though I can't imagin.
Anyway, still very curious how someone can write about an option in Catalog (Store Exiftool Fields) that I don't have, no matter what I do.
XnViewMP was long bundled with exiftool, but it was an antiquated version. Exiftool underwent significant implementation changes in 2024 that provided much faster execution in certain usage scenarios, that Pierre had never incorporated. (The version bundled with XnViewMP is now reasonably current, but is still updated infrequently.) So allowing XnViewMP to use a separate installation of exiftool provides for a few benefits:
1. The user can upgrade exiftool at will without monkeying with the XnViewMP folder contents
2. Customized exiftool configurations or .Exiftool_config files need not be backed up and restored when upgrading or reinstalling XnViewMP; they are safe in a different location.
3. The user can easily switch between bundled and custom versions of exiftool, if needed.
You can learn more about upgrading or using a separate instance of exiftool here: viewtopic.php?t=49746
So if you just want to use the default version of Exiftool that is bundled with XnViewMP, and don't need a customized .Exiftool_config, then simply leave the "ExifTool Path" setting blank. That causes the app to use the bundled version of exiftool. That is the normal case for most users, and that's why that field is blank by default: it just works. Essentially, it's an override field to be used if needed.
Yes, well you know Pierre... He later moved it. Thanks for bringing that to my attention; I updated the document.HanVroon wrote: Fri Mar 20, 2026 1:32 pm There is no Store Exiftool Fields checkbox in my case, not even when I drag settings to fullscreen:
Yes, you're right, but it's empty because the data hasn't been populated yet.HanVroon wrote: Fri Mar 20, 2026 1:32 pm My guess is that I should be able to open the Exiftool list at the red arrow, but it's empty:
You haven't mentioned it, but if you have a customized .Exiftool_config file, you should use the installation of Exiftool that uses that file, but if you don't (or have never heard of ".Exiftool_config") then just...
Take the following steps:
1. For Settings:Integration:Paths:Exiftool path, just empty this setting out; leave it blank.
2. Ensure Settings:Metadata:Exiftool is enabled/checked under Metadata Import.
3. Click OK, then close and restart the app.
4. Go to Settings:Catalog, and click the "Update Metadata" button. This will collect comprehensive Exiftool metadata for all the image files in your catalog. You should see a progress bar that may last a few minutes depending on the size of your catalog. This will likely be faster than running exiftool on your own, because it's multithreaded.
When that's all done, you could restart the app just to ensure all counters in the Catalog Filter update. You should then see populated metadata trees in the Catalog Filter, and be able to add enhanced metadata columns in Details view.
The "Update Metadata" should really only need to be a one-time step, since you are upgrading. You could use it later if you make a lot of metadata changes outside the app. But generally, XnViewMP will scan new files as they are added to the catalog, so the information will be automatically added to.
Hopefully this helps...
[Edit: I see you posted while I was typing.]
-
HanVroon
- Posts: 232
- Joined: Thu Jan 28, 2010 7:30 am
Re: How to use the new exiftool functionality
Thanks for the detailed explanation!
It contributes to an online kind of documentation for everyone since the forum topics are well indexed in search engines.
It has always been pity that there is no all-encompassing manual of XnViewMP. Only Pierre could do that because we're only guessing. But... writing new features is more important than documenting.
Writing that, here is something about exif header data and the XnViewMP catalog:
(I did several tests, in between deleting the DB ifles and overwriting my xnview.ini with the 1.7.1 version)
Have a folder with camera files in focus in the Browser
Enable Exiftool in Settings, Metadata
Run "Update metadata" in Settings, Catalog.
Restart XnViewMP.
Check Settings, Browser, Columns, in the right column of that window, at the bottom, Exiftool now can be opened.
It will reflect the exif tags found in the camera files in the folder that is opened in Browser, especially the makernotes.
To see the makernotes of differend (brand) cameras, move the Browser to a folder with files of that other brand and run "Update metadata" in Settings, Catalog again.
It can probebly be a good idea to have a special folder with a camera file from each brand and model someone has used over decades.
Then focus the Browser on that folder and run Update metadata.
Tested that, all the specifice makernote exif tags of different brands were there at once.
It contributes to an online kind of documentation for everyone since the forum topics are well indexed in search engines.
It has always been pity that there is no all-encompassing manual of XnViewMP. Only Pierre could do that because we're only guessing. But... writing new features is more important than documenting.
Writing that, here is something about exif header data and the XnViewMP catalog:
(I did several tests, in between deleting the DB ifles and overwriting my xnview.ini with the 1.7.1 version)
Have a folder with camera files in focus in the Browser
Enable Exiftool in Settings, Metadata
Run "Update metadata" in Settings, Catalog.
Restart XnViewMP.
Check Settings, Browser, Columns, in the right column of that window, at the bottom, Exiftool now can be opened.
It will reflect the exif tags found in the camera files in the folder that is opened in Browser, especially the makernotes.
To see the makernotes of differend (brand) cameras, move the Browser to a folder with files of that other brand and run "Update metadata" in Settings, Catalog again.
It can probebly be a good idea to have a special folder with a camera file from each brand and model someone has used over decades.
Then focus the Browser on that folder and run Update metadata.
Tested that, all the specifice makernote exif tags of different brands were there at once.
-
HanVroon
- Posts: 232
- Joined: Thu Jan 28, 2010 7:30 am
Re: How to use the new exiftool functionality
One thing still wonders me, the mysterious "EXIF node".
If it exists, I cant get it
If it exists, I cant get it
You do not have the required permissions to view the files attached to this post.