Download ImageIngester/ImageVerifier User`s Manual

ImageIngester/ImageVerifier User’s Manual
Version 3.5
Page 75
Lightroom Develop Settings
C:\Users\[user]\AppData\Roaming\Adobe\Lightroom/Develop Presets
ImageVerifier Jobs
C:\Users\[user]\AppData\Roaming\ImageVerifier\IVMain
Log
C:\Users\[user]\AppData\Roaming\ImageIngesterPro\ii_log.txt
ImageVerifier
ImageVerifier (IV for short) traverses a hierarchy of folders looking for image files to
verify. It can verify PSDs, TIFFs, JPEGs, DNGs, and non-DNG raws.
Overall Operation
IV is designed to process large numbers of images. Folder hierarchies with 100,000
images or more should be no problem. In one test run, IV ran for 14 hours.
There are two kinds of verification that IV performs: Structure checking and hash
checking (described in a separate section, below).
All verification other than for raws is built-in. JPEGs and TIFFs are verified using
built-in libraries as well; PSDs are verified using code written specifically for IV. Raws
(e.g., NEFs, DNGs) are verified by running them through Adobe DNG Converter.
For all image files, structure checking is performed by reading the actual image data,
decompressing as necessary. This can find many errors, but not all, as some errors
are indistinguishable for image data. See below for more information.
The list of extensions for raw files is the same as ImageIngester's, except that,
unlike ImageIngester, there's a hidden way to change the extensions. Send mail to
[email protected] if you need this. (If your raw files end in TIF you can
set an option for that on the main window.)
The real work is done by subprocesses, so IV can take advantage of multiple CPU (or
multiple core) computers. If you have 4 CPUs, it should be capable of fully loading all
4 at once. You can control the number of subprocesses with a drop-down on the
main window, in case you want IV to take less that the whole machine.
For each verification run, called a job, you can choose the folders, whether to
process subfolders or just the top level, what kinds of images to process (PSD, TIFF,
JPEG, raw), the maximum number of errors to report, and whether to store the
results in a built-in database.
You can save the settings in a named job, which acts something like ImageIngester's
Master Presets.
On OS X only, there's a built-in scheduler that allows you to schedule jobs to be run
once at a specified time; daily at a specified time on specified days (e.g., Tuesdays
and Saturdays at 2am); and monthly on a specified day and time (e.g., the 3rd of
every month at 5am).
© 2007-2011 Marc Rochkind. All rights reserved.
2011-09-16