Build 108

[Ferdinand]

Downloaded, installed and running.  Thank you!   

[picolo]

Same here...
Thanks!

[sinus]

Also here, great work, thanks a lot! 

[Mario]

Thank you all for the quick feedback.

[JohnZeman]

Something seems to have changed in 108, I don't know if it's the latest version of ExifTool or what but initial testing indicates the

Code Select Expand

{File.MD.Composite\Description\Description\0}

Tag is not being updated.

[JohnZeman]

Neither does the

Code Select Expand

{File.MD.XMP::dc\description\Description\0}
tag seem to showing any values now.

[Mario]

I have switched the default "Description" tag to use the XMP metadata tag, because Composite Description is replicated into XMP, but does not support multi-language XMP tags. The "Default" Metadata Template so when you reload it into the Metadata Panel you get this tag.

Composite::Description is also not listed on the ExifTool Composite Tag page:

http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/Composite.html

which is another reason for not using it anymore.

[Mario]

Neither does the

Code Select Expand

{File.MD.XMP::dc\description\Description\0}
tag seem to showing any values now.

This is a variable. Where do you look at the variable?
Or do you look in the metadata panel?
Did you try to force a rescan of the metadata for the file?

Many things in the way IMatch handles metadata have changed in the 5.0.108 and I guess maybe all users should reload all metadata.

[picolo]

Mario, which of the rescan options do you suggest?

[Mario]

Ctrl+Shift+F5, then Reload Metadata.

[jch2103]

A nice set of fixes!

What's your target for providing text in the Readme.html file? I assume for the public release?

I assume the provided set of File Formats is intended to be read-only, to simplify things at your end. E.g., I wanted to add .flac files, and had to add that as a new category, rather than editing the existing Audio File Formats.

[picolo]

Ctrl+Shift+F5, then Reload Metadata.

Thanks...

[JohnZeman]

Neither does the

Code Select Expand

{File.MD.XMP::dc\description\Description\0}
tag seem to showing any values now.

This is a variable. Where do you look at the variable?
Or do you look in the metadata panel?
Did you try to force a rescan of the metadata for the file?

I'm using both the metadata panel and a script to check this Mario.  A screen shot of my metadata panel is attached.

When I export an image from Lightroom 5 that has a description, i only see that description in the IPTC caption (non-editable in IM5) and the

Code Select Expand

{File.MD.XMP::tiff\ImageDescription\ImageDescription\0}

variable (See first attached screen shot).  However if I edit the description in the above xmp variable and then do a metadata writeback, the original description from Lightroom replaces my edit.  If I edit the description of the

Code Select Expand

{File.MD.XMP::dc\description\Description\0}

variable and do a metadata writeback, my edits do not seem to be copied to any other variable.

In other words at the moment I don't see a way I can now edit a description that had been originally entered in Lightroom 5.

By the way, I have done a metadata rescan, the issue stays the same.


[attachment deleted by admin]

[Mario]

Which language do you use under Edit > Preferences > Metadata? It should be set to "Neutral".

[JohnZeman]

I had it set to en but I just now changed it to Neutral and I immediately see some changes in my metadata panel for descriptions.

Will do my tests again now.

[Mario]

Oops. I just noticed that I did not mention this required change in the release notes. Bugger. Too many things in my head... I'll write that right away.

[jch2103]

Mine was also set to 'en', but I had never set it or changed it. I'll change it as soon as the metadata refresh is completed (another hour to go for 38,000 files).

[JohnZeman]

Ok, that seems to have fixed everything.  After changing the language to Neutral and my description field for editing captions to

Code Select Expand

{File.MD.XMP::dc\description\Description\0}

everything seems to be working the way it should now.

[bonsai]

Hi Mario,

installed build 108 over the existing database, set language to neutral, updated the thesaurus to neutral as well like you explained.
Then did a force rescan for all images, all went ok. Double and triple entries in the metadata I have to edit manually, but this was clear to me.
It seems that this bug is gone, I'll have an eye on this 

And thank you so much for "Support for Custom File Formats", great 

Btw, performance seems to be better...

[Gerd]

Hi,

also just updating ... started on 19:00 and now still "Rebuilding Search Index ...". The process-indicator stays at round about 80% ...

I will wait ... 

Regards
Gerd

[Mario]

Search index updates take seconds for databases with a few thousand files, maybe two minutes for 30,000 files.
It helps if you let us know how many files your database has, if there is disk activity, ...

The search engine update is a atomic database operation, with a bazillion of disk I/Os. Disk performance is all that matters here. External disks, USB 2.0 disks, NAS or network storage causes slow search index updates / rebuilds.

[Mario]

Made a quick check. 110,000 files database on USB 3.0 stick.
Rebuild search engine index completed in about 4 minutes.

[Gerd]

Hi Mario,

I had to leave at 19:30 and was back at 21:00 ... all finished! there are a lot of the same actions now with CIMCollectionManager and "Get File Data", but I think, that is normal background-process. This processes have started round 19:45, so (I hope I see this correct) it took 45 min.

I have the feeling, that getting selected pics from Category-View oder Folder-View is on my computer now much more quicker!!!

Good work! Thanks, Mario!

Regards
Gerd

[cytochrome]

First contact with 108: everything (metadata wise) is so slow... There are 39 K files in this base. And I use immediate write back and I write to raw, no xmp, this may explain that?

At first Imath detected a new Exiftool (I use 9.35 with other programs), then went livid and inaccessible for  a good 20 minutes.

And now, every folder I click on induces a new torpor of 1-3 minutes. Id I click anywhere in the files window IMatch faints and gets all pale .

I am doing now a CTRL Shift F5 to see if this is of any help.

Francis

PS I set metadata langage from the start (well once the exiftool thing was over) to neutral and have detected no problem so far.

[Mario]

There is something pretty unusual on your machine. Can you please attach the log file?

At first Imath detected a new Exiftool (I use 9.35 with other programs), then went livid and inaccessible for  a good 20 minutes.

IMatch ships with and uses only it's own copy of ExifTool. As mentioned in the release notes, I shipped the current 9.35 version of ExifTool with IMatch 5.0.108 so  IMatch will update your database on the first open. Even on a slow machine and with a 100,000+ files database this takes about 2 minutes, plus the required search engine update afterwards. I wonder why this is so slow on your system. Virus Checker? Slow disk? External storage?

And now, every folder I click on induces a new torpor of 1-3 minutes. Id I click anywhere in the files window IMatch faints and gets all pal

IMatch needs to load a lot of data from your disk when you open a folder. Are perhaps updates running in the background (Check Info & Activity Panel).

[cytochrome]

The PC is a 6 year old Dell, intel dual core with 4 gb ram, runs Win7 64 bits.

I took a snapshot logfile while it was updating (it seems IM spends much time updating, when I change folder it updates, when I click on different images it updates and so on, some other users like Gerd also see a lot of updating apparently).

This db contains 39000 files, mostly NEF, RW2 and JPGs

I added a new headline to a folder of 102 NEF 10 min ago, it is still updating...

Just got an error message : 13 errors and 0 files offline or read only...

Francis

[attachment deleted by admin]

[Ferdinand]

I have switched the default "Description" tag to use the XMP metadata tag, because Composite Description is replicated into XMP, but does not support multi-language XMP tags. The "Default" Metadata Template so when you reload it into the Metadata Panel you get this tag.

Composite::Description is also not listed on the ExifTool Composite Tag page:

http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/Composite.html

which is another reason for not using it anymore.

I'm a little puzzled.  A while back, were we talking about the desirability of using composite fields for editing, were we not?  And now you saying not to?  Is this just for the Description field?

[Mario]

Ferdinand, I'm learning new things about ExifTool every week  . It's a moving target, like metadata in general.
And multi-lang XMP metadata is an extra heap of complexity on top. I've learned the hard way that LR deletes non-neutral metadata values when you update the same tag, for example. LR apparently supports only neutral language. Bridge displays and updates only neutral tags, but at least does not delete tags in other languages...

1. I found that ExifTool emits the Composite.Description field, but it is not documented.
2. Attempts to update the filed with a language tag are ignored with a "Compsite::Description-en" does not exist.
IMatch 5.0.108 is the first version which writes multi-language tags with the appended langid as required by ExifTool so this problem was not immanent before.
3. Setting Composite::Description only will delete tags in non-neutral languages.
4. For the same reason I've also swapped some of the other Composite tags used for the IMatch Standard tags to their XMP counterparts.

As long as only the Neutral language is used and the XMP tags are edited, propagation etc. seems to work very well in that setup.

[Ferdinand]

Is this problem just for the description composite, or is it for all the composite fields?

[Mario]

The multi-lang problem affects only multi-lang XMP tags and the associated Composite fields.
As long as you stick to the Neutral language you can continue using Composite fields.

[Ferdinand]

So to be clear:

   
• If you use a metadata language other than "Neutral" you'll have problems with any composite tag that you edit; and
• If you use "Neutral" as the language then any composite field is ok to edit; so
• As a precaution against what language a user might have set, the default panel uses XMP rather than composite.

Is this right?

[DaweP]

I am sorry to report some troubles with 108.
I am not able to save metadata to the file (keywords / rating) as before. The yellow triangle appears with the message that there was error and no files were off-line or read-only.
I have not changed anything in the DB settings from 106.
After this problem appeared, I tried to reload (refresh) the metadata by all means (normal rescan, force update, reload metadata), but the triangle icon is still there and the data are not written to the file :-(
David

Edit:
Furthermore, newly indexed images do not not have the exif data loaded propperly (not loaded at all).

Edit 2:
It seems it has been mentioned here:
https://www.photools.com/community/index.php?topic=688.0

[Mario]

Is this right?

Yep. At least to my current understanding of ExifTool, Composite tags, multi-lang XMP tags and mapping 

[Mario]

The output panel for ExifTool will tell you if you are affected by that problem.
And also the IMatch log file.

If it's the dreaded "file not found" error, I have that improved for build 110 again. I will ship and update within the next days, I'm just rolling up some other changes as well.

Since this is a bug (you cannot process metadata) I would prefer if you could add a bug report in the bug report forum.
Posts like this, made in a General forum and in response to some different topic, will not make it on my bug list. I will just forget about it, sorry. 
I cannot keep all this in my head and search all boards for potential bug reports. I often work on bugs a week after they have been reported...

Remember:

If in doubt: Add it as a bug report. Check for similar reports before you add a new report.No problem with that. I can always file it as "no bug" if it's not a bug. But if it is in deed a bug, I have all the info I need in one place, a proper topic number etc.

[DigPeter]

Just downloaded B108 and converted thesaurus to neutral language.  All going fine to time of wruiting.

[cytochrome]

So to be clear:

   
• If you use a metadata language other than "Neutral" you'll have problems with any composite tag that you edit; and
• If you use "Neutral" as the language then any composite field is ok to edit; so
• As a precaution against what language a user might have set, the default panel uses XMP rather than composite.

Is this right?

I envy you if you find it clear... I use a personal Metadata panel to show only what I am interested in. After reading Mario's post "Updated Default Metadata Panel layout for download" I made the manual change for Description, but I still have a lot of Composite definitions (because I too got had the impression that it was the thing to do).

Now I am lost. What is a trusted setting that will write xmp/iptc to place holders that IMatch AND the other application in the outer world will read?

AT this time I use:

{File.MD.XMP::dc\creator\Creator\0}
{File.MD.XMP::dc\description\Description\0}
{File.MD.XMP::photoshop\Headline\Headline\0}
{File.MD.Composite\City\City\0}
{File.MD.Composite\Location\Location\0}
{File.MD.Composite\State\State\0}
{File.MD.XMP::iptcCore\CountryCode\CountryCode\0
{File.MD.Composite\Country\Country\0}
{File.MD.Composite\GPSAltitude\GPSAltitude\0}
{File.MD.Composite\GPSLatitude\GPSLatitude\0}
{File.MD.Composite\GPSLongitude\GPSLongitude\0}
{File.MD.Composite\GPSPosition\GPSPosition\0}
{File.MD.Composite\Rating\Rating\0}

Should I replace the Composite fields and with what?  (It works well with meta lang set as neutral).

Francis

[Ferdinand]

I envy you if you find it clear... I use a personal Metadata panel to show only what I am interested in. After reading Mario's post "Updated Default Metadata Panel layout for download" I made the manual change for Description, but I still have a lot of Composite definitions (because I too got had the impression that it was the thing to do).

Now I am lost. What is a trusted setting that will write xmp/iptc to place holders that IMatch AND the other application in the outer world will read?

I wanted to be clear about what Mario was saying.  I'm not so clear about what it means for metadata previously entered in V5 using composite tags and non-neutral metadata language.  I haven't done it really seriously, as I'm waiting patiently for some bug fixes.

I too have a custom metadata layout.  It's using XMP fields, partly because I created it before composite fields became flavour of the month.  My layout seems to work.  I'd have thought that with MWG on XMP would be a safe bet.