- Welcome to photools.com Community.
Recent posts
#31
General / Re: Very slow imports and miss...
Last post by stefanjan2 - June 29, 2025, 09:29:00 AMI also often have a problem with thumbnails not showing after import and have to rescan to fix.
#32
General / Re: Very slow imports and miss...
Last post by ubacher - June 29, 2025, 07:26:14 AMI have the same problem: Thumbnails don't show after import. Not always - but with 185 Raw files import on idle system it did.. Rescan fixes it.
#33
General / Re: Very slow imports and miss...
Last post by dcb - June 29, 2025, 01:47:47 AMThanks Mario. Here is some more information. I appreciate your help.
Setup
Test
1. Start IMatch (Performance Mode)
2. Waited for files to ingest
3. Wrote back metadata
4. Reviewed log file (attached). Could find nothing other than a SLOWCAT
Thoughts
It it always subjective but I think that ran faster and more as I expected. Previously I had the imatch6 folder excluded from anti virus and this time it's just the IMatch2025x64.exe. This time, progress was much faster. Prior to the AV change, IMatch was freezing, and reporting times like 1.25 hours(!) to finish, though in reality it did not take that long.
I'm happy to leave this for now Mario, but can return if I notice any further slow downs.
Setup
- Put IMatch into debug log mode. Closed IMatch
- Created new 10 images that have not been previously ingested. Each image is CR3, DNG and JPEG so 30 images totaling 1.13GB.
- Copied images to S:\memories\import\_SD Card folder.
- Confirmed Sophos Home virus checker has IMatch executable as an exception
Test
1. Start IMatch (Performance Mode)
2. Waited for files to ingest
3. Wrote back metadata
4. Reviewed log file (attached). Could find nothing other than a SLOWCAT
Thoughts
It it always subjective but I think that ran faster and more as I expected. Previously I had the imatch6 folder excluded from anti virus and this time it's just the IMatch2025x64.exe. This time, progress was much faster. Prior to the AV change, IMatch was freezing, and reporting times like 1.25 hours(!) to finish, though in reality it did not take that long.
I'm happy to leave this for now Mario, but can return if I notice any further slow downs.
#34
General Discussion and Questions / Send to viewer from Files with...
Last post by fisketjon - June 29, 2025, 01:28:47 AMQuickview showed the correct photo, but the viewer displayed a completely different photo. After I confirmed the faces in the photo shown in the viewer the photo that was displayed in the Unconfirmed Faces disappeared as if I had confirmed faces in that photo.
#35
General / Re: IMatch freezes when readin...
Last post by dcb - June 29, 2025, 12:51:26 AMHi, David from the other thread about slow import. For what it's worth, I've also experienced slowdown when doing forced propogations using F4,P. I'll get some testing done today and a log through to Mario.
#36
General / Re: IMatch freezes when readin...
Last post by thrinn - June 28, 2025, 10:52:53 PMAnother test: I switched back to the standard Performance Profile. Selected just 16 ARW files. Hid all panels with F9,Backspace. Pressed F4,P to propagate MD. Immediately, IMatch got stuck "Propagating".
Log file shows a lot of "Failed to get transaction or CS lock" messages:
After waiting about 15min, IMatch finished propagating. But 15min to propagate MD for 16 files from ARW to JPG?
At least, this time I did not get any ##BLOCK messages.
IMATCH6_LOG.zip
Log file shows a lot of "Failed to get transaction or CS lock" messages:
Code Select
06.28 22:37:32+ 63 [6464] 02 I> CIMCollection::InnerCalculate: Failed to get transaction or CS lock for 'Callout'After waiting about 15min, IMatch finished propagating. But 15min to propagate MD for 16 files from ARW to JPG?
At least, this time I did not get any ##BLOCK messages.
IMATCH6_LOG.zip
#37
General / IMatch freezes when reading me...
Last post by thrinn - June 28, 2025, 10:30:23 PMAfter installing the newest version, I suffer from frequent freezes where the UI is completely blocked. This happens in the "Reading Metadata" phase after a write-back, when IMatch re-reads some of the changed files. But I see it also when I try to explicitly propagate metadata (F4, P).
In the log file I see many ##BLOCK messages like below, often in combination with a "TranBegin wait loop" with a very long time (>130.000 ms):
I already dialled down the Performance Profile to "Low", just in case. I use Windows 11 with Defender, IMatch process and executable declared as exception, whole folder containing the database likewise, even the folder containing the photos. We are talking about ARW and JPG, no large TIFFs or videos or such.
I suspect that somehow the file relation rules interfere with the "Reading Metadata" step: Specifically, I shoot ARW+JPG, and I have a Buddy rule as well as a Version rule to link the JPG as buddy and version to the ARW master. Some Metadata is propagated, but this has never been a problem before. Included is some XMP metadata, some collections (Pins, Dots), and some categories.
The attached log file (incomplete, as I had to close IMatch the hard way) is from a session where I tried to propagate metadata for about 350 ARW files.
Is there any possibility to find out what exactly is blocking by what? At the moment, I have no idea where to look.
I saw one other bug report from today concerning slow import, but in my case, the initial metadata load when ingesting new files did not have any issues. Propagation and Write-back, however, caused the blocking.
IMATCH6_LOG.zip
In the log file I see many ##BLOCK messages like below, often in combination with a "TranBegin wait loop" with a very long time (>130.000 ms):
Code Select
06.28 22:05:15+ 1234 [71B4] 50 I> TranBegin wait loop: 600 134453ms.
06.28 22:05:15+ 0 [71B4] 10 I> ##BLOCK: 29108 (71b4) 'Engine.UPDQDelegate.Meta' TransBegin 0 ms from bool __cdecl CIMRelationManager::Propagate(const class std::vector<unsigned int,class std::allocator<unsigned int> > &,bool,class CBitVector *,const class CBitVector *,bool) (3647) lev: 0I already dialled down the Performance Profile to "Low", just in case. I use Windows 11 with Defender, IMatch process and executable declared as exception, whole folder containing the database likewise, even the folder containing the photos. We are talking about ARW and JPG, no large TIFFs or videos or such.
I suspect that somehow the file relation rules interfere with the "Reading Metadata" step: Specifically, I shoot ARW+JPG, and I have a Buddy rule as well as a Version rule to link the JPG as buddy and version to the ARW master. Some Metadata is propagated, but this has never been a problem before. Included is some XMP metadata, some collections (Pins, Dots), and some categories.
The attached log file (incomplete, as I had to close IMatch the hard way) is from a session where I tried to propagate metadata for about 350 ARW files.
Is there any possibility to find out what exactly is blocking by what? At the moment, I have no idea where to look.
I saw one other bug report from today concerning slow import, but in my case, the initial metadata load when ingesting new files did not have any issues. Propagation and Write-back, however, caused the blocking.
IMATCH6_LOG.zip
#38
General / Re: Very slow imports and miss...
Last post by Mario - June 28, 2025, 02:44:20 PMNo logfile attached. Not much data to work with.
A log in debug mode (see log file) is the first thing we need to analyze this.
Probably a starving problem with the SSD as the bottleneck?
Switch the performance profile to "Balanced" or "Low" and retry and then force a rescan of the 32 CR2 files to see if there is a change.
Which virus checker are you using and have you made exceptions for the database folder and IMatch2025x64.exe?
A log in debug mode (see log file) is the first thing we need to analyze this.
QuotePhotos and database are on the same drive.
Probably a starving problem with the SSD as the bottleneck?
Switch the performance profile to "Balanced" or "Low" and retry and then force a rescan of the 32 CR2 files to see if there is a change.
Which virus checker are you using and have you made exceptions for the database folder and IMatch2025x64.exe?
#39
General / Very slow imports and missing ...
Last post by dcb - June 28, 2025, 02:01:48 PMI'm running 2025.4.4. In this version and the last I've noticed an incredible slow-down in import speeds. I'm not suggesting it's a bug per-se but thought this the best place to report it.
There are two things happening and I've not yet been able to determine why.
1. Imports used to be fast. Tonight I've imported just 32 cr3 files and it's taken several minutes. In this past this would have been no more than 30 seconds (guessing, but I know it's much, much slower now).
2. After the import most images are missing a thumbnail and need a force-update to create it.
Tonight it was .cr3 but I'm seeing the same behaviour with .dng, .jpg, .afphoto (Affinity Photo).
My anti-virus is Sophos Home. I've excluded both the IMatch folder in it's entirety and also my photo drive. I've even fully disabled it.
Metadata write-back is perfectly fast.
Overall IMatch is very fast. It's just the initial import and thumbnail that's slow. I'm running Windows 11, 32GB RAM, AMD Ryzen 5600 CPU. New device, less than 12 months old. Photos and database are on the same drive, a M.2 motherboard fitted SSD.
I don't know what to look at next. The problem only began with the version previous to the current.
There are two things happening and I've not yet been able to determine why.
1. Imports used to be fast. Tonight I've imported just 32 cr3 files and it's taken several minutes. In this past this would have been no more than 30 seconds (guessing, but I know it's much, much slower now).
2. After the import most images are missing a thumbnail and need a force-update to create it.
Tonight it was .cr3 but I'm seeing the same behaviour with .dng, .jpg, .afphoto (Affinity Photo).
My anti-virus is Sophos Home. I've excluded both the IMatch folder in it's entirety and also my photo drive. I've even fully disabled it.
Metadata write-back is perfectly fast.
Overall IMatch is very fast. It's just the initial import and thumbnail that's slow. I'm running Windows 11, 32GB RAM, AMD Ryzen 5600 CPU. New device, less than 12 months old. Photos and database are on the same drive, a M.2 motherboard fitted SSD.
I don't know what to look at next. The problem only began with the version previous to the current.
#40
General Discussion and Questions / Re: IMatch 2025.4.4 Released -...
Last post by Mario - June 28, 2025, 10:01:54 AMIMatch upgrades don't alter settings, unless I mean to. And in that case I document it in the release notes.
Upgrading the database system has nothing to do with settings.
1. No change related to orientation. Please provide a minimum of information, like file format,
where is the orientation wrong? File Window? Viewer? If you use RAW, WIC or photools.com RAW processing?
2. That's a File Window setting (hierarchical mode) I guess, which is stored per File Window. No change with that. I assume this is what you have "configured". It helps to provide more details, like what you actually have configured, which option or settings you have used etc. I can only guess otherwise.
3. "Not displayed at all". IMatch does not remove sub-folders from your database once added. It will by default not add new sub-folders found under folders in the database, but notify you to perform a rescan of the parent folder.
Adding folders to a database does not touch other folders. A folder is only marked for rescan when the last modified on disk timestamp is newer in the database, or when IMatch detects a file newer than the folder during the initial folder scan. May this be the case, you or some other application changing the folder timestamps or adding files without you knowing?
The log file from that session would contain more information, e.g. what you did, what IMatch found in the file system, if and which folders were considered as outdated.
The update is out for almost a week, and no reports from other users, no emails about similar problems. I use the same update on my 3 PCs without any issues.
Upgrading the database system has nothing to do with settings.
1. No change related to orientation. Please provide a minimum of information, like file format,
where is the orientation wrong? File Window? Viewer? If you use RAW, WIC or photools.com RAW processing?
2. That's a File Window setting (hierarchical mode) I guess, which is stored per File Window. No change with that. I assume this is what you have "configured". It helps to provide more details, like what you actually have configured, which option or settings you have used etc. I can only guess otherwise.
3. "Not displayed at all". IMatch does not remove sub-folders from your database once added. It will by default not add new sub-folders found under folders in the database, but notify you to perform a rescan of the parent folder.
Adding folders to a database does not touch other folders. A folder is only marked for rescan when the last modified on disk timestamp is newer in the database, or when IMatch detects a file newer than the folder during the initial folder scan. May this be the case, you or some other application changing the folder timestamps or adding files without you knowing?
The log file from that session would contain more information, e.g. what you did, what IMatch found in the file system, if and which folders were considered as outdated.
The update is out for almost a week, and no reports from other users, no emails about similar problems. I use the same update on my 3 PCs without any issues.