- Welcome to photools.com Community.
Recent posts
#1
General Discussion and Questions / Re: Hide parent folders in Med...
Last post by Mario - May 22, 2025, 06:44:50 PMAll folders indexed by the database will be shown in the Media & Folders View.
You cannot hide entire levels of folders. This would make things a lot more complicated for IMatch for no good reason.
If you want an "alternative" view on your folders, just use categories, which were designed for this, among many other things.
Categories allow you to create multiple representations / organizations for your image collection, all of which which can be totally independent from the physical storage location.
You can do create the categories manually or make them dynamic using formulas like @Folder[] or @RFolder. So many possibilities with this.
You cannot hide entire levels of folders. This would make things a lot more complicated for IMatch for no good reason.
If you want an "alternative" view on your folders, just use categories, which were designed for this, among many other things.
Categories allow you to create multiple representations / organizations for your image collection, all of which which can be totally independent from the physical storage location.
You can do create the categories manually or make them dynamic using formulas like @Folder[] or @RFolder. So many possibilities with this.
#2
General Discussion and Questions / Hide parent folders in Media &...
Last post by stefanjan2 - May 22, 2025, 06:25:28 PMI'm storing recent years on m.2 SSD and older years on a Synology NAS.
Folder structure is like this:
Database
\\SynNAS\data *
Photos Earlier *
1945
1946
...
E:
Photos Latest *
2024
2025
Ideally I would like to hide the * asterix folders so that the folder structure looks like this:
Database
1945
1946
...
2023
2024
Folder structure is like this:
Database
\\SynNAS\data *
Photos Earlier *
1945
1946
...
E:
Photos Latest *
2024
2025
Ideally I would like to hide the * asterix folders so that the folder structure looks like this:
Database
1945
1946
...
2023
2024
#3
General Discussion and Questions / Re: Discrepancy with camera ma...
Last post by Mario - May 21, 2025, 07:34:46 PMQuoteNow all the files that were not showing up in that category are showing up. I don't really understand why that worked, but thanks!Look at how the category is constructed, which tags it uses for its levels.
If a file has no value for the tags, it will be moved into the "Other" category.
IMatch creates (and uses in many features) a virtual tag named photools.com:IMatch.cameraname that cleans up the naming mess camera vendors have produced over the years. For example, Nikon has used make values like
NIKON CORPORATION NIKON
NIKON CORPORATION
NIKON
and sometimes includes the NIKON also in the model name, adding redundancy: "NIKON NIKON Z7".
Other vendors did the same. They don't care.
A make/model like "NIKON CORPORATION" / "NIKON Z7" is transformed by IMatch for the cameraname tag into "NIKON Z7", and this makes a perfect value for a data-driven category, for sorting, for the value filter in the Filter Panel etc.
Now that you have copied over metadata with your Template into the "official" make/model tags, features based on make/model can work, the cameraname tag holds a useful value etc.
Of course it would be better if your RAW processor would not wipe these important tags.
RAW processors adapt their processing / presets / corrections usually based on certain tags like make/model and lens data.
Wiping or changing this data is thus not a good idea.
#4
General Discussion and Questions / Re: Discrepancy with camera ma...
Last post by sybersitizen - May 21, 2025, 07:16:26 PMQuote from: Mario on May 21, 2025, 08:45:05 AMExifTool usually produces make/model from the official EXIF make/model tags.Yes.
Switch the Metadata Panel to the Browser layout to see all tags IMatch has imported.
Do you see usable make/model data somewhere?
QuoteIf so, use a Metadata Template to copy it into the official tags.I created a template and applied it to one file. Now all the files that were not showing up in that category are showing up. I don't really understand why that worked, but thanks!
Thanks also to JohnZeman. Photo RAW definitely has some issues with regard to metadata. My immediate needs seem to be addressed, but I'll consider your solution if any problems persist.
#5
General Discussion and Questions / Re: Discrepancy with camera ma...
Last post by Mario - May 21, 2025, 08:45:05 AMExifTool usually produces make/model from the official EXIF make/model tags.
Switch the Metadata Panel to the Browser layout to see all tags IMatch has imported.
Do you see usable make/model data somewhere?
If so, use a Metadata Template to copy it into the official tags.
Data not there?
Check the image in the ExifTool Command Processor ("List Metadata" preset).
Any useful data there?
If so, you have to enable the non-standard tags in the IMatch Tag Manager so IMatch imports them in the future, making them available for Metadata Templates to copy into EXIF make/model.
Note: When you update make/model, use the XMP tags. Then write back and check if ExifTool has written the data back to EXIF too. ExifTool handles make/model in special ways. If it has not copied the data into EXIF, change your Metadata Template to also update the EXIF make/model alongside the XMP make/model and retry.
Switch the Metadata Panel to the Browser layout to see all tags IMatch has imported.
Do you see usable make/model data somewhere?
If so, use a Metadata Template to copy it into the official tags.
Data not there?
Check the image in the ExifTool Command Processor ("List Metadata" preset).
Any useful data there?
If so, you have to enable the non-standard tags in the IMatch Tag Manager so IMatch imports them in the future, making them available for Metadata Templates to copy into EXIF make/model.
Note: When you update make/model, use the XMP tags. Then write back and check if ExifTool has written the data back to EXIF too. ExifTool handles make/model in special ways. If it has not copied the data into EXIF, change your Metadata Template to also update the EXIF make/model alongside the XMP make/model and retry.
#6
General Discussion and Questions / Re: Discrepancy with camera ma...
Last post by JohnZeman - May 20, 2025, 11:03:37 PMI'm not familiar with Potensic/Atom but I also use ON1 Photo Raw to process my raw files and for awhile I had metadata problems with it too. I solved my problem by telling ON1 to export the processed raw file as a TIF or JPG with NO metadata.
Then back in IMatch I use file relations to copy the metadata I want from the original raw file to the processed JPG or TIF version.
Then back in IMatch I use file relations to copy the metadata I want from the original raw file to the processed JPG or TIF version.
#7
General Discussion and Questions / Discrepancy with camera make a...
Last post by sybersitizen - May 20, 2025, 09:57:57 PMI use ON1 Photo RAW for processing many of my files, such as photos from my Potensic Atom drone. However, I know Photo RAW fails to preserve a number of metadata tags, including the primary ones for camera make and model. As you can see in the attached screen shots, IMatch does know about the camera make and model when I look in the Metadata panel, but it does not include any files in the Potensic/Atom category.
This issue is not unique to IMatch. It occurs in other software as well ... but there is obviously some other make/model tag that is present and working.
Mario, do you know how I can correct those two missing tags in files produced by Photo RAW?
This issue is not unique to IMatch. It occurs in other software as well ... but there is obviously some other make/model tag that is present and working.
Mario, do you know how I can correct those two missing tags in files produced by Photo RAW?
#8
General Discussion and Questions / Re: Propagation - menu item gr...
Last post by ERBRO - May 20, 2025, 08:57:47 PMHEllo Mario,
Thank you for all these clarifications. I will apply your recommendations with the next project and if it is still unclear I will recontact you.
Best regards
Eric
Thank you for all these clarifications. I will apply your recommendations with the next project and if it is still unclear I will recontact you.
Best regards
Eric
#9
General Discussion and Questions / Re: Propagation - menu item gr...
Last post by Mario - May 20, 2025, 06:24:50 PMMake sure that your versions are correctly detected.
Use the Version panel to see all versions for the master you select.
Most metadata is propagated when you write-back the master!
When a master is selected, this variable lists the file name of all it's versions:
{File.Versions|replace:~;=={crlf}}
You usually never need to refresh the relations. Once you have set up a maste/version relation, IMatch automatically detects masters and versions when it rescans a folder. For example, when you create new versions of a master file outside of IMatch, e.g. in your image editor.
You manually refresh the relations if you make a change to the relation definition or you create a relation definition when masters and versions are already in the database.
If you add a new version to the database but it is not automatically detected, double-check your file relation setup.
Use the Version panel to see all versions for the master you select.
Most metadata is propagated when you write-back the master!
When a master is selected, this variable lists the file name of all it's versions:
{File.Versions|replace:~;=={crlf}}
QuoteI refreshe the relation to connect the the RAW withthe corresponding jpg (there can be several jpg for one RAW)
You usually never need to refresh the relations. Once you have set up a maste/version relation, IMatch automatically detects masters and versions when it rescans a folder. For example, when you create new versions of a master file outside of IMatch, e.g. in your image editor.
You manually refresh the relations if you make a change to the relation definition or you create a relation definition when masters and versions are already in the database.
If you add a new version to the database but it is not automatically detected, double-check your file relation setup.
QuoteI update the metadata of all pictures of the Project withsome genetal data (Location, Country, event, etc) using a metadata template.Depending on which data you propagate (details, please), make sure that metadata changes you make to the master don't wipe out metadata changes you make to versions when the master is written back.
#10
General Discussion and Questions / Re: Propagation - menu item gr...
Last post by ERBRO - May 20, 2025, 05:03:44 PMHello Mario,
I use this option after having try different cases and the data where not propagate. Maybe I do something wrong but I can not figure out what.
My Folder structure is inherit from Capture One session
Example :
Project XYZ
\Capture
\Output
\Selected
\Trash
Thge pictures are imported in the Project XYZ\Caoture folder within cpature one (RAW files)
I develop in Cpature one the RAW. When I'm happy with the result, I create (=export) JPG still from within Cpature one. The JPG are place in the Project XYZ\Output folder.
When I'm ready with my project, I go in iMatch where I following Workflow
1. I update the metadata of all pictures of the Project withsome genetal data (Location, Country, event, etc) using a metadata template.
2. I add to the RAW file keywords. then write-back.
3. I refreshe the relation to connect the the RAW withthe corresponding jpg (there can be several jpg for one RAW)
4. As it does not propagate (or not always ?) I selct the RAW with version (not all the RAW have jpg so some of them have no versions) and click on propagate.
Maybe reading how I work will hep to detext what I do wrong.
Best Regards
Eric Bromey
I use this option after having try different cases and the data where not propagate. Maybe I do something wrong but I can not figure out what.
My Folder structure is inherit from Capture One session
Example :
Project XYZ
\Capture
\Output
\Selected
\Trash
Thge pictures are imported in the Project XYZ\Caoture folder within cpature one (RAW files)
I develop in Cpature one the RAW. When I'm happy with the result, I create (=export) JPG still from within Cpature one. The JPG are place in the Project XYZ\Output folder.
When I'm ready with my project, I go in iMatch where I following Workflow
1. I update the metadata of all pictures of the Project withsome genetal data (Location, Country, event, etc) using a metadata template.
2. I add to the RAW file keywords. then write-back.
3. I refreshe the relation to connect the the RAW withthe corresponding jpg (there can be several jpg for one RAW)
4. As it does not propagate (or not always ?) I selct the RAW with version (not all the RAW have jpg so some of them have no versions) and click on propagate.
Maybe reading how I work will hep to detext what I do wrong.
Best Regards
Eric Bromey