Finding manually inserted tabs, that no longer exist?

[Aubrey]

Is there any search that can be performed to find non-existent tabs within a database?

I've cleaned up many of the composite tabs, but there are still some manual tabs that I have used, goodness knows where...

I expect that the answer to my question is no!

Aubrey.

[Mario]

I assume you mean metadata tags, not "tabs"?

No, unfortunately there is no way to find tags used in variables (only these need checking).
Renamer, Custom File Window Templates, Text Export, Design & Print, MT Templates, Metadata Mechanic App, Copy Data app, ...
I think that's basically it.  And only for variables using Composite tags explicitly. If you have used the (recommended) Metadata Tag ShortCodes, you're good.

I had to check 8 databases and it took less than 30 minutes.

ExifTool renaming tags was a quite a unique event and I had a lot of work to do in the database itself to make it as seamless as possible.
Checking features with variables is something only the user can do.

[Aubrey]

I assume you mean metadata tags, not "tabs"?

Yes I mean meta tags.

This afternoon I have started to try and convert using Metadata ShortCodes, but I'm not having any success.

Attached is a an image of the layout editor. You can see that on the right and left of footer 3 I want to place the aperture. This is a test, I've spent last 1 1/2 hours trying to get this to work, I'm convinced the syntax is correct.

On the left is the full code for aperture, this works fine. On the right is the short code, nothing appears on the right. If I use the full name in the custom template (as on the left), the right side aperture appears so it is not a font issue.

What am I doing wrong?

Aubrey.

[Mario]

What does the VarToy App Show for your variables?

I get the same for both:

{File.MD.Composite\Exif::Aperture\Aperture\0}
{File.MD.aperture}

Also: Aperture is a standard attribute for File Window layouts. You don't need to use variables for it. Just select Aperture from the Attribute drop-down list.
I tried it in a template (the Composite variable left, the short code right) and it works.

Make sure that all your footers above the one are filled so the layout engine can layout the data correctly.
The XAML is sometimes a bit awkward when you try too much.

[sinus]

Aubrey

Here this works also in the File Windows Layout.
Did you try to change both, because somtimes it is not easy to see all stuff in the File Windows Editor.
Only to be sure, that it is not working for you.

[Aubrey]

{File.MD.Composite\Exif::Aperture\Aperture\0}
{File.MD.aperture}

First is OK in VarToy.
{File.MD.aperture} is empty as is {File.MD.shutterspeed}

{File.MD.file.name} is filled correctly.

Also: Aperture is a standard attribute for File Window layouts. You don't need to use variables for it. Just select Aperture from the Attribute drop-down list.
I tried it in a template (the Composite variable left, the short code right) and it works.

I'm using Aperture concatenated with other variables:
The following works fine (I think it was modified from something  Markus sent me a few years ago):
{File.MD.Exif::Main\37386\FocalLength\0|numformat:int,3} {File.MD.Exif::Main\41989\FocalLengthIn35mmFormat\0|prefix:(;postfix:mm)}{File.MD.Composite\Exif::ShutterSpeed\ShutterSpeed\0|value:formatted;postfix: secs} {File.MD.Composite\Exif::Aperture\Aperture\0|prefix:f/}  {File.MD.Exif::Main\34855\ISO\0|prefix:ISO:} {File.MD.Exif::Main\37380\ExposureCompensation\0|prefix:EV:} {File.MD.Exif::Main\37383\MeteringMode\0|value:formatted;substr:0,5}

I'm really just trying to replace the full metadata tag with short codes. It wasn't working so I checked a simple example to troubleshoot.

Any ideas as to what might be the reason that aperture, shutterspeed are not populated. Is it possible I have changed some parameter in preferences (I've gone through the preferences metadata tabs but don't see anything)? I have not recently touched preferences.

Update:
I created a new database with 1 file. Same issue in this database. {File.MD.aperture} is not recognized.

Aubrey

[Mario]

Send me your new database.
All eight databases I have here handle the shortcode without problem.
Also attach the file C:\ProgramData\photools.com\IMatch6\config\immbcfg.xml ZIPpped to your reply (no personal data in that file).

Did you have any issue when migrating the database?
Any special setup, unusual folder for storing IMatch preferences? Restored an old Pack & Go perhaps?
if the config file is wrong, IMatch will still try to use the old short codes on your machine, which won't work with the new ExifTool version.

[Aubrey]

Mario,
You are certainly asking the right questions! I think you may have hit on my issue, and no need to send a database.

I've just come back from travelling.
2019.16.2 is still installed on my laptop. I've tested that database.
{File.MD.aperture} works fine. Good!

When I move database from laptop to desktop, I usually  copy the database across.
This time I did a pack and go. I think (not certain) that my workflow was:
1. Install 2019.8.4 on desktop
2. Copy across pack and go file
3. Perform  restore operation
4. Run 2019.8.4

This would mean that I probably overwrote new control files that had been installed by 2019.8.4

What do you suggest should be my procedure now?

I'm planning to uninstall and reinstall IMatch? Would "repair" be sufficient.

I have many database backups so not worried about losing data.

Aubrey.

In answer to your questions:
No obvious messages / issues when migrating
No unusual folders
Restored pack and go(from 2019.16.2) AFTER installing 2019.8.4

[Mario]

If you have replaced the current metadata configuration file with an older version, the standard tags will not work.
Just re-install / repair your IMatch installation to get the proper file back.

You can check by opening "C:\ProgramData\photools.com\IMatch6\config\immbcfg.xml" in a text editor and then searching for name='shutterspeed'
The <mapto> below shutterspeed must look like

<mapto>Composite\Exif::ShutterSpeed\ShutterSpeed</mapto>

If the Exif:: is missing, the file is wrong.

This will make the standard tags work again.

[Aubrey]

Mario,
Re-installed  - repair did not appear to be sufficient.
All working.

Thank you for the trouble shooting.

Aubrey.