IV Issues

[rsmith1]

I am also using Vista Business on my laptop, and it does belong to a domain, in case that is relevant.  I can confirm that the file path is saved with the job.  I can even open the saved job file in the AppData folder with Notepad and see the file path(s) in that saved job file.  One interesting note, which may be perfectly normal for Vista, is that the ImageVerifier data is stored under Desktop | <login name> | AppData | Roaming | Image Verifier | IVMain.  I am guessing that this path must be slightly different on the Home editions that can't join a domain, but I have no way to check.

Mike: can you find the Image Verifier directory under AppData on your Vista box?  If so, the IVMain folder should contain one file for each of your saved jobs in addition to "Default".  If you use Notepad to open some of these files, what do you see?  Do you have any lines that start with the word "Folders"?  I have one line in the job file per folder that I add to the job.

[Mike Buckley]

Randall,

Thanks for being so helpful in trying to figure out this stuff.  You and Marc are being so persistent that I've got to mention that it's really not a major problem for me that a saved job doesn't also save a filepath on my system.  My interest is mostly to inform Marc that his current documentation is at odds with how things seem to work on my system and, considering that the program is still in the beta status, I'm confident that he would want to know that.

Mike: can you find the Image Verifier directory under AppData on your Vista box?

It's located in the following path:  Desktop >> Homw (that's not a typo) >> AppData >> Roaming >> ImageVerifier (no space between the two words) >> IVMain

  If so, the IVMain folder should contain one file for each of your saved jobs in addition to "Default".  If you use Notepad to open some of these files, what do you see?

I have the Default fle and two additional files.   All of them are shown below in their entirety.

Default
Version   1
Date   Mon Feb 09 10:18:30 2009
ProcessNoExtension   0
TIFisRaw   0
CheckHashes   1
CheckStructure   0
VerifyRaws   1
IgnoreTIFFErrors   0
Folders   C:\Users\Homw\Pictures\Catalogued
ExtensionsJPEG   -JPG-JPEG-
ExtensionsTIFF   -TIF-TIFF-
ExtensionsRAW   -CR2-CRW-DCR-KDC-MRW-NEF-ORF-PEF-RAF-RAW-SRF-X3F-EEF-ARW-SR2-MEF-
ExtensionsDNG   -DNG-

Compare Hashes on Local Drive
Version   1
Date   Wed Feb 04 10:30:00 2009
ProcessNoExtension   0
TIFisRaw   0
CheckHashes   1
CheckStructure   0
VerifyRaws   1
IgnoreTIFFErrors   0
Folders   C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Utah\Capitol Reef National Park
ExtensionsJPEG   -JPG-JPEG-
ExtensionsTIFF   -TIF-TIFF-
ExtensionsRAW   -CR2-CRW-DCR-KDC-MRW-NEF-ORF-PEF-RAF-RAW-SRF-X3F-EEF-ARW-SR2-MEF-
ExtensionsDNG   -DNG-

Store the Hash in Catalogue
Version   1
Date   Mon Feb 09 10:21:02 2009
ProcessNoExtension   0
TIFisRaw   0
CheckHashes   0
CheckStructure   1
VerifyRaws   1
IgnoreTIFFErrors   0
ExtensionsJPEG   -JPG-JPEG-
ExtensionsTIFF   -TIF-TIFF-
ExtensionsRAW   -CR2-CRW-DCR-KDC-MRW-NEF-ORF-PEF-RAF-RAW-SRF-X3F-EEF-ARW-SR2-MEF-
ExtensionsDNG   -DNG-
Folders   C:\Users\Homw\Pictures\Catalogued\Galleries\Family\Matthew Jr\Johns Hopkins NICU

Thanks again!

--Mike

[rsmith1]

You can see that there is a Folders entry for each job.  But when you open these jobs, the Folders section of the UI remains blank?  If so, I would think that Marc would definitely want to know about that.

[Mike Buckley]

Seeing that each file has a "folders" line, I did some more investigating.

One time when I opened IV and immediately brought up each of the saved jobs, the folders indeed changed as each job is brought up.  But only one time out of about six attempts.  Immediately after the one successful attempt, I then ran a job.  Having done that, the saved jobs no longer consistently brought up their respective saved folders.  Sometimes one job would and sometimes no jobs would.  Never did more than one of the jobs bring up their respective folders.

The only pattern I was able to detect is that the saved job that most often brings up its folder is the job file, "Store the Hash in Catalogued."  I was never able to get either of the other two jobs to bring up their respective folders.

--Mike

[Mike Buckley]

You can see that there is a Folders entry for each job.  But when you open these jobs, the Folders section of the UI remains blank?

No, it isn't blank.  Instead, it's a file path that usually is not the file path shown in the folders line.  As best as I can remember, if I run a job and bring up a different saved job, the filepath remains unchanged and causes me to manually edit the filepath.

[Marc Rochkind]

Mike--

Try IV Version 1.2.03, just posted today. The results panel is now resizable, and you can skip subfolders.

I'm unable to reproduce your job-saving problem. It always works for me, and I've received no other reports. Perhaps Randall will come up with some info.

--Marc

[Mike Buckley]

Thanks, Marc!  It is really a BIG help now that the results panel is now resizable.  In fact, I waited to examine a long filepath until after downloading the new version.

Thanks also for adding the flexibility to choose whether subfolders are to be verified.

It is probably just a coincidence, but after installing the new version the job folder is now being saved as part of the saved job in one of my three saved jobs.  One is better than none!   

You might remember that in my initial post to you, I reported Issue #1 as a situation that a lot of files were being returned after comparing hashes even though I had not edited the images or changed their metadata.  I have since learned that my DAM software changes a file when syncing the thumbnail with the database even though no other changes are made.  That explains why the two hashes are different and makes me believe that IV is working properly.

--Mike

[Mike Buckley]

Marc,

I've got some new issues.

After installing the new version, I ran a job on all of my images.  The instructions were to store a hash and keep the existing hashes.  It should have stored hashes on only 12 valid files.  Instead it stored the hashes on all 5592 valid files.  The job that should have taken only a few minutes took almost 35 minutes.  Is it possible that the new version is not supposed to recognize the existing hashes that had been created by the previous version?

The above job finished running at 3:03am.  (Yep, I worked in the middle of the night.) I ran the exact same job minutes later, beginning at 3:18am.  In between running the two jobs, I had no software loaded that could have added new image files.  However, the job stored 13 hashes.  In this case, I can think only of the following possibilities: the report is inaccurate or ImageVerifier did not recognize the 13 existing hashes. 

Any ideas?

--Mike

[Marc Rochkind]

Mike--

No changes were made to the hashing in the new version, but a very old version did have a different hash.

I can't really provide an answer without having a lot more data, such as what was actually stored before and what the new files were. Can you possibly reproduce the problem with preserved before and after image files?

--Marc

[Mike Buckley]

Marc,

About the job that stored a new hash in all of my files the first time I ran the new version rather than keeping the hashes: It occurred to me a long time after I wrote the post that the normal confirming dialog box informing whether or not the hashes will be overwritten did not appear.  Instead, immediately after clicking "Run," the job began without the confirming dialog box.

To compare two files of the same image, I would need to restore one of the files from the backup set.  I'd rather not have to go to the trouble, but I appreciate you offering to take a look at them.  If the issue persists, I'll eventually send some to you.

--Mike

[Marc Rochkind]

Mike--

Well, that certainly is strange. If you can reproduce the problem of that dialog not appearing, I'd be interested in trying to track it down.

--Marc

[Mike Buckley]

Marc,

If the confirming dialog box fails to appear again, I'll be sure to mention it.  However, I use IV almost daily and that happened only once.

--Mike

[Mike Buckley]

Marc,

I explained in an earlier post that I suspected that the file count may not be being reported accurately.  I'm now convinced that that's the case.  For me, this is an unimportant issue.  I'm reporting it only in case you and others care about it. 

Take a look at the two job reports shown below.  Notice that, according to the reports, the second job processed one more file than the first job.  It also stored two more hashes. Yet the number of kept hashes remained unchanged.  That combination is a mathematical impossibility. 

The reports should indicate that the second job stored one hash, not two.

Job: Store the Hash in Catalogued
Start Date/Time: 2009-02-18 09:31:33
Stop Date/Time: 2009-02-18 09:35:09
Status: OK (interactive)

(No Suspected Invalid Images recorded.)

Run Log:

Verification Checks: Structure
Existing Hashes Kept (not rehashed)

Total processed: 7457
Total skipped: 917
Total hashes kept: 6539 (not verified)
Total valid: 1 (1 hashes stored)
Total invalid: 0Total indeterminate: 0
Total error: 0
Total hash error: 0

Valid JPEGs: 1

Skipped Extensions:
   DOC: 6
   XMP: 911

--------------------------------

Job: Store the Hash in Catalogued
Start Date/Time: 2009-02-19 00:59:02
Stop Date/Time: 2009-02-19 01:02:14
Status: OK (interactive)

(No Suspected Invalid Images recorded.)

Run Log:

Verification Checks: Structure
Existing Hashes Kept (not rehashed)

Total processed: 7458
Total skipped: 917
Total hashes kept: 6539 (not verified)
Total valid: 2 (2 hashes stored)
Total invalid: 0Total indeterminate: 0
Total error: 0
Total hash error: 0

Valid JPEGs: 2

Skipped Extensions:
   DOC: 6
   XMP: 911

--Mike

[Marc Rochkind]

Mike--

I will investigate this file-count problem. I suspect what's happening is that the hashes aren't getting stored. As there are other problems with the saving of the folder list, these problems may be related. This could also explain the other problem you reported a few days ago.

Regarding the job-saving problem: Does the job named "Default" save its folder list?

Can you email me the external log (Help menu), just to see if there's any info there?

--Marc

--Marc

[Mike Buckley]

Marc,

Yes, the "Default" job saves the folder list.  Considering that tonight for the first time all of my jobs are now saving the folder list, I don't know if that information is helpful. 

When I access the External Log, two windows appear containing the information shown below about the two sessions that occurred today.  They show activities only for today's date.  Is that what is supposed to be shown?


2009-Feb-19 02:08:44: App launched
2009-Feb-19 02:09:07: Verifying folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)
2009-Feb-19 02:11:13: Processed folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)(209 files)
2009-Feb-19 02:11:13: Waiting for process 988 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 4960 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 7536 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 4328 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 5908 in finishAllWorkers
2009-Feb-19 02:11:14: Waiting for process 3928 in finishAllWorkers
2009-Feb-19 02:11:14: Waiting for process 3264 in finishAllWorkers
2009-Feb-19 02:11:15: Waiting for process 3336 in finishAllWorkers
2009-Feb-19 02:18:09: Verifying folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)
2009-Feb-19 02:20:09: Processed folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)(209 files)
2009-Feb-19 02:20:11: Waiting for process 5332 in finishAllWorkers
2009-Feb-19 02:20:14: Waiting for process 5100 in finishAllWorkers
2009-Feb-19 02:20:14: Waiting for process 7468 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 6824 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 6488 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 3160 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 7040 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 5836 in finishAllWorkers
2009-Feb-19 02:20:46: Quitting

-----------

2009-Feb-19 22:14:38: App launched
2009-Feb-19 22:15:44: Verifying folder C:\Users\Homw\Pictures\Catalogued\Pictures not by Mike or Joellen
2009-Feb-19 22:15:44: Processed folder C:\Users\Homw\Pictures\Catalogued\Pictures not by Mike or Joellen (2 files)