- Welcome to photools.com Community.
Recent posts
#61
Solved Bug Reports (for next version) / Re: Can't delete Lat and Lon i...
Last post by hamishr - June 26, 2025, 03:56:43 PMThanks Mario.
#62
Solved Bug Reports (for next version) / Re: Can't delete Lat and Lon i...
Last post by Mario - June 26, 2025, 01:58:18 PMFixed for the next regular release.
#63
Solved Bug Reports (for next version) / Can't delete Lat and Lon in th...
Last post by hamishr - June 26, 2025, 10:38:09 AMIf I duplicate an event and then edit the duplicated event, in the Place tab, I can't delete Lat and Lon, although I can replace them with new coordinates (but not zeros).
#64
Solved Bug Reports (for next version) / Re: IMatch 2025.4.2 "File Cate...
Last post by Bolitho - June 26, 2025, 07:10:35 AMYes, it's fixed with 2025.4.4 - Thank you!
(The offline help still shows 4.2 - but there shouldn't be any difference.)
(The offline help still shows 4.2 - but there shouldn't be any difference.)
#65
General / Re: AI: Single Queued entry ru...
Last post by Jingo - June 26, 2025, 12:53:28 AMNo worries Mario... I was hopeful that the missing (and then added after my manual action) CimEngineAIAutoTagger might be a clue into the issue... but I guess not.
Overall, it is simple for me to just switch tabs or perform some other activity which seems to "wake" IMatch up to process the queue entry so if no one is experiencing this.. it is ok and probably just my database.
I'm tempted to just create a new database, loading all the metadata from the files and "starting over" to see if that resolve things.. but at the end of the day, it is a minor issue with an easy workaround.
Always happy to share my DB if that might help as well.
Cheers! - Andy.
Overall, it is simple for me to just switch tabs or perform some other activity which seems to "wake" IMatch up to process the queue entry so if no one is experiencing this.. it is ok and probably just my database.
I'm tempted to just create a new database, loading all the metadata from the files and "starting over" to see if that resolve things.. but at the end of the day, it is a minor issue with an easy workaround.
Always happy to share my DB if that might help as well.
Cheers! - Andy.
#66
General Discussion and Questions / Re: Unchanged metadata (XMP fa...
Last post by mlavicka - June 25, 2025, 08:08:56 PMFor consistency, I believe the pen being set on reading in region info is the same as in this thread: https://www.photools.com/community/index.php/topic,15034.msg105350.html#msg105350
Where it was discussed as an issue with the order of operation, not just related to timestamps.
From Mario: This behavior is by design. When it imports face regions, IMatch no longer "knows" that the file on disk may have XMP face regions. When XMP face regions are found, the existing PersonInImage data is dropped and, at some later time, recreated. Changing this behavior would be quite complex and "expensive".
I assume that is still the case.
Where it was discussed as an issue with the order of operation, not just related to timestamps.
From Mario: This behavior is by design. When it imports face regions, IMatch no longer "knows" that the file on disk may have XMP face regions. When XMP face regions are found, the existing PersonInImage data is dropped and, at some later time, recreated. Changing this behavior would be quite complex and "expensive".
I assume that is still the case.
#67
General / Re: AI: Single Queued entry ru...
Last post by Mario - June 25, 2025, 05:38:16 PMI will again try to reproduce this. I've never experienced this and no other user reported this.
This might be very well something that happens only with your database.
I've looked at the log from yesterday and it looked OK. Entries were enqueues, the queue was not disabled or paused, the queue was signaled with type 10 (AutoTagger) after new entries were added etc. It should just run whatever is in the queue.
Issues like this are hard to debug, because he behavior may even depend on the number of processors installed, Windows thread pooling and whatnot. When I can reproduce it, I can fix it.
This might be very well something that happens only with your database.
I've looked at the log from yesterday and it looked OK. Entries were enqueues, the queue was not disabled or paused, the queue was signaled with type 10 (AutoTagger) after new entries were added etc. It should just run whatever is in the queue.
Issues like this are hard to debug, because he behavior may even depend on the number of processors installed, Windows thread pooling and whatnot. When I can reproduce it, I can fix it.
#68
Announcements / Re: IMatch 2025.4.4 Released
Last post by JohnZeman - June 25, 2025, 05:20:01 PMI can confirm the bug is fixed. 
#69
Announcements / IMatch 2025.4.4 Released
Last post by Mario - June 25, 2025, 04:50:07 PMThis update from today fixes the blank "File Categories Panel" bug discovered yesterday.
If you have installed the 2025.4.2 version released yesterday, please update.
If you have installed the 2025.4.2 version released yesterday, please update.
#70
General / Re: AI: Single Queued entry ru...
Last post by Jingo - June 25, 2025, 01:21:10 PMLeft IM running all night.. Queue has not processed.
Switching tabs from Media & Folders to Categories and back does force the Queue to process so same process is needed.
I then see in the log an CimEngineUpdateQueue and the CimEngineAIAUtoTagger entry get added to the log (new version attached to show progression overnight and steps needed this morning to fire the queue).
I believe the Queue entry briefly showed a change from 1 (busy) to 1 (invalid) after I did the tab switch and saw the Autotagger running message appear... but, it processed correctly after that.
Not sure what else I can do... perhaps something is blocking the system from performing the CIMEngineUpdateQueue immediately all the time via a code check?
Thx!
Switching tabs from Media & Folders to Categories and back does force the Queue to process so same process is needed.
I then see in the log an CimEngineUpdateQueue and the CimEngineAIAUtoTagger entry get added to the log (new version attached to show progression overnight and steps needed this morning to fire the queue).
I believe the Queue entry briefly showed a change from 1 (busy) to 1 (invalid) after I did the tab switch and saw the Autotagger running message appear... but, it processed correctly after that.
Not sure what else I can do... perhaps something is blocking the system from performing the CIMEngineUpdateQueue immediately all the time via a code check?
Thx!