Author Topic: new files not always detected  (Read 255 times)

chupacabra

  • New Members
  • *
  • Posts: 11
new files not always detected
« on: January 24, 2021, 09:04:48 AM »
I am using imatch and capture one. I find a file I want to edit using imatch then switch to capture one and edit the file, then export it to the same directory as <filename>-V.jpg and sometimes I end up with <filename>-V1.jpg. I've seen this a handful of times today.

Usually imatch finds  these new files within a few seconds to maybe 30 seconds and shows them on the screen. Then I can stack the file straight out of the camera and the "_V" file. Sometimes, though, the new file doesn't show up in imatch even after a few minutes. I will search for <original-filename> (no suffix) and it shows my original file but (when this happens) it never shows the new file.

When this happens I can go to the Windows file manager and rename the new file to something different like <filename>VVV or whatever and then my new file shows up in imatch almost immediately.

I think I remember there being a timer that controis this in the imatch settings somewhere and I think I set it to one minute.

What could cause this and is there another way to get the new file to show up in imatch without doing the rename thing in the file manager?

Using Windows 10 and imatch 2020.12.6.

Mario

  • IMatch Developer
  • Administrator
  • *****
  • Posts: 27956
Re: new files not always detected
« Reply #1 on: January 24, 2021, 10:51:02 AM »
IMatch waits for about 30s after the last update operation for a folder is completed before it rescans the folder.
Since this was never before reported (and there are many C1 users working with IMatch), check the IMatch log file (log file) for error messages and warnings. Or ZIP and post the log file here after you experienced the problem. IMatch logs when it scans a folder, it logs when new files are found etc. Use Help menu > Copy LogFile.

Tveloso

  • Full Member
  • **
  • Posts: 228
Re: new files not always detected
« Reply #2 on: January 24, 2021, 02:22:48 PM »
...and until you get to the bottom of this, a better more direct work-around (than renaming the file in Windows), would be to initiate the re-scan manually, by selecting the folder containing the “missing” file in the Media and Folders View, and pressing Shift-F5
--Tony

chupacabra

  • New Members
  • *
  • Posts: 11
Re: new files not always detected
« Reply #3 on: January 24, 2021, 09:32:24 PM »
here's an example from today.

imatch shows file TX-2010-04-09 17.39.45.JPG.

went to capture one, edited this file. then exported it as TX-2010-04-09 17.39.45-V.JPG

I waited a few minutes for the "-V" version to appear in imatch but it never did.

I've attached a screen capture from windows file explorer showing the original file and the "-V" file.

Below is a snipper of the imatch log file:

Code: [Select]
"01.24 14:06:07+ 4156 [2F78] 00  I> # Process Memory Info: WSC: 448MB, WSP: 2028MB, PF: 39660873
01.24 14:06:13+ 5844 [2F78] 02  I> D:\Pictures\Texas\TX-2010-04-09 17.39.45.JPG loaded in 359ms. Result: 2
01.24 14:06:13+  110 [2F78] 02  I> D:\Pictures\Texas\TX-2010-04-09 17.39.45.JPG loaded in 359ms. Result: 2
01.24 14:06:19+ 6000 [2F78] 00  I> # Process Memory Info: WSC: 445MB, WSP: 2028MB, PF: 40097392
01.24 14:06:29+10093 [1B78] 02  I> FWFind: 62
01.24 14:07:52+82344 [157C] 02  I> FWFind: 62"

Why does it show imatch scanning file X-2010-04-09 17.39.45.JPG? That file hasn't been changed. There are two log entries for this file.  Not sure if that is significant or just part of normal processing.

The log file does not show the "-V" file though. This is from 10 minutes or so after I exported the new file.

I renamed the "-V" file to <filename>V.jpg and imatch found it and displayed it after about 10 seconds.

The "V" files still aren't displayed in the log FWIW.

Mario

  • IMatch Developer
  • Administrator
  • *****
  • Posts: 27956
Re: new files not always detected
« Reply #4 on: January 25, 2021, 07:16:41 AM »
Please run IMatch in debug logging mode (See log file) Help menu > Support > Debug Logging.
And always include the full log file.

"Loaded" can mean many things, e.g. loading the file into the Quick View Panel or the Viewer. This is not an entry for IMatch checking for new files or updated files.
Result 2 usually means "Path not found". Which is strange.

Try this.
Close IMatch. Do whatever you do with your exporting / renaming in C1.
Start IMatch. Does the folder show up as "modified" in the Media & Folders tree? Does IMatch rescan it (the updated icon vanishes)?