The DAM Forum
Welcome, Guest. Please login or register.
May 20, 2013, 02:27:10 PM

Login with username, password and session length
Search:     Advanced search
Jan 9, 2012
John Beardsworth's new Lightroom site
Lightroom Solutions
27960 Posts in 5113 Topics by 2914 Members
Latest Member: imthedamstar
* Home Help Search Login Register
+  The DAM Forum
|-+  Software Discussions
| |-+  ImageIngester and ImageVerifier
| | |-+  Check for duplicate image and a corrupt file
« previous next »
Pages: [1] Print
Author Topic: Check for duplicate image and a corrupt file  (Read 1263 times)
Niall Horley
Jr. Member
**
Posts: 71


View Profile WWW
« on: May 10, 2007, 04:05:03 AM »

Marc,

I have just tested the latest beta in particular the check for duplicate image functionality. I have a question regarding the behaviour. Unfortunately I have a corrupt (CRW) image in the card. The image keeps getting ingested each time I run IIP. But it is being correctly named each time and I only have a single copy of the THM file ( its a Canon CRW file).

Thanks

Niall
Logged

Niall Horley
www.lifeatf8.co.uk
Marc Rochkind
Hero Member
*****
Posts: 1136


View Profile WWW
« Reply #1 on: May 10, 2007, 06:08:30 AM »

Niall--

I'm not sure this answers your question, but here goes:

Verification of raws occurs only when DNG Converter is run, and that requires a pre-conversion backup. Copying from the card to the backup is done without verification. Verification occurs when DNG Converter copies from the backup to the primary folder.

Are you seeing the corrupt image in the backup but not in the primary folder? Both places?

Duplication detection occurs when the images are copied from the card to the backup. It often works even on corrupt images, but not always.

What exact behavior are you seeing?

--Marc
Logged

Niall Horley
Jr. Member
**
Posts: 71


View Profile WWW
« Reply #2 on: May 10, 2007, 08:56:27 AM »

The file is being copied to both the backup location and then onto the primary location. So each time I ingest the card with the corrupt files I am getting 2 more copies of the file with the 0000n postfix aded to the name. I was surprised that IIP was able to correctly name the file using the exif data (This may be being extracted from the the THM file) but then not spot it was a duplicate.

I suppose I was hoping the file would not be copied multiple times. What I will do is see if image verifier thinks the file is corrupt.

Niall
Logged

Niall Horley
www.lifeatf8.co.uk
Marc Rochkind
Hero Member
*****
Posts: 1136


View Profile WWW
« Reply #3 on: May 10, 2007, 10:58:56 AM »

Niall--

I may have misunderstood your previous post... I thought you had said the file failed the verification test in IIP.

Anyway, duplication detection occurs only if two files with the same name would otherwise be placed in the same folder. Once you get an 000n suffix, that's no longer the case. The question is why the duplication detection didn't work on the second ingestion.

Any idea?

--Marc
Logged

Niall Horley
Jr. Member
**
Posts: 71


View Profile WWW
« Reply #4 on: May 10, 2007, 11:55:23 AM »

I have no idea why it failed the duplication test, I do know the file is corrupt as I can not view it. I do not know if that has any think to do with it. What is stranger is that the THM side car file was not duplicated. With canon CRW files I assume you extract the meta data fom the THM file.

If it is any use I can upload the file for you.

Thanks

niall
Logged

Niall Horley
www.lifeatf8.co.uk
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!