Estimated time remaining in Info & Activity panel

[fisketjon]

When I left my PC yesterday evening it said >7 hours remaining. This morning it was down to less than 2 hours
4 hours later (now) is changing every minute 45 minutes, the suddenly 13 hours, 25 minutes, 1 hour 53 minutes, 44 minutes, 35 minutes, 35 hours 46 minutes, 2 hours 2 minutes
The last 3 within less than 5 minutes. Number of entries in the queue reduced by 10 , and then 14 entires

It seems that the calculations should be based on an average of a larger number of files so that a steadily decreasing (and thus more reliable) estimate could be shown. As it is now, it is just "noise".

BTW. The queue entries are film clips from camera or phone.

[Mario]

The stats considers the last 50 or 100 files (from the top of my head) and uses a sliding average. If processing times varies a lot (e.g. JPG files mixed with RAW or videos, automatic face recognition, files containing XMP face regions which require a lot of extra processing power, the average will pump up and down. Increasing the size of the sliding window may help in your case, but it might spoil the estimate for others. It's just a guestimate, and it is always right in the end

How many files do you process in a single batch that IMatch reports hours of runtime? I regularly produce test databases from 50K mixed files and even on my notebook this takes less than 3-4 hours, depending on how much other work I do at the time.

As the help suggests, processing images in batches of 5,000 to 10,000 can be a lot less effort and better planable. Unless you have batches with 5,000 video files, which are of course the slowest format to process.

[fisketjon]

How many files do you process in a single batch that IMatch reports hours of runtime? I regularly produce test databases from 50K mixed files and even on my notebook this takes less than 3-4 hours, depending on how much other work I do at the time.

Just a few; 36 647 

Does IMatch read each video in it's entirety? I thought it would read as much as is needed to produce a thumbnail, but then the average time should have been about the same for each file.

[Mario]

IMatch reads the entire video to produce a checksum. ExifTool may have to read large chunks of the video to gather metadata. FFPMeg reads key frames to produce the preview thumbnails for the File Window and to produce a suitable cache image.