ImageVerifier

ImageVerifier (IV for short) traverses a hierarchy of Folders looking for image files to verify. It can verify TIFFs, JPEGs. PSDs, DNGs, and non-DNG raws (e.g., NEF, CR2). 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. They are described in detail below. Basic OperationAll structure verification other than for non-DNG raws is built-in; for DNGs IV uses Adobe`s DNG SDK directly. JPEGs and TIFFs are verified using built-in libraries as well. PSDs are validated using a method designed specifically for ImageVerifier that follows Adobe documentation for the PSD format. Non-DNG raws (e.g., NEFs) 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. (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. 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 (TIFF, JPEG, PSD, DNG, and/or non-DNG 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 presets, except saving is automatic.