Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/content/60/9972860/html/smf/Sources/Load.php(225) : runtime-created function on line 3

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/content/60/9972860/html/smf/Sources/Load.php(225) : runtime-created function on line 3

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/content/60/9972860/html/smf/Sources/Load.php(225) : runtime-created function on line 3
Latest posts of: Ferguson
The DAM Forum
Welcome, Guest. Please login or register.
May 18, 2021, 08:48:58 PM

Login with username, password and session length
Search:     Advanced search
28033 Posts in 5147 Topics by 2903 Members
Latest Member: kbroch
* Home Help Search Login Register
  Show Posts
Pages: [1]
1  General / General Discussion / Website compromised? on: February 08, 2017, 09:48:32 AM
Today I started receiving malicious pornographic spam to the email address I use at this forum.  The email was used only for this, and to register my purchase of ImageIngesterPro, and nothing else, thus either that gentleman's email, or this web site has been compromised.

That email will be deleted momentarily so I will not see any correspondence that follows, but wanted to let the community know to be aware of the compromise.

2  Software Discussions / ImageIngester and ImageVerifier / Re: Image Verifier and Daylight Savings Time on: June 13, 2012, 06:25:24 AM
I thought this was the place to come for support.   It would appear the product is no longer active?
3  Software Discussions / ImageIngester and ImageVerifier / Re: Image Verifier and Daylight Savings Time on: March 07, 2012, 08:55:46 PM
Well from the date this might be too late for anyone to care.  I hadn't done a check in a long time and wanted to check up on Lightroom 4, so I ran a verification, but before I upgraded from 1.2.4 to 1.3.1.

Huge numbers of images showed invalid, and when I dug into it most seemed to have a different time.  I did one directory and 43 of 53 did not match, and when I stored them they all stored with an hour different as shown under "manage hashes".

This was Windows 7 x 64, and I've had no other time zone problems.  The image itself shows 13:26:50, but in the database the new one is recording the EXIF Digitized Time as 12:26:50.  It would appear to be a bug introduced in 1.3.1.

Not pretty.  I hope I saved the old program (but silly me I let it update all the hashes, fortunately I saved the old ones).
4  Software Discussions / ImageIngester and ImageVerifier / Re: IV, (potential) New user, Questions on: April 24, 2009, 05:06:29 AM
I bought it and have spent some time with it now. 

I found a corrupt NEF.  It wasn't corrupt at download (because Lightroom imported and created a preview), it hasn't been modified since according to the modify date, but it is bad (really bad, Lightroom can't read it). On a raid-1 disk.  So a tool like this is useful.

It is reporting quite a few PSD files as invalid. 

Probably invalid: T:\Photos\2007\20071215\20071215_1473.psd
   (Wrong expanded width (columns = 3144; expanded = 6288))

If I open them in CS3 and re-save, the problem goes away.  Not sure what to make of that, it was produced by CS3.  Maybe a prior update.  Interesting.

The one thing I can't figure out how to do (and maybe because you cannot) is how to detect a lost file, not a corrupt file.

Is there a way to compare the saved hashes against a new run, effectively an existence check -- did you see all the files?

E.g. if Windows had a directory hiccup and a file either disappeared from disk, or from the directory structure because a pointer got lost, could it notice?  Lightroom does not, at least as best I can tell, unless you either synchronize or touch the image manually or export it, all a bit painful.
5  Software Discussions / ImageIngester and ImageVerifier / Re: IV, (potential) New user, Questions on: April 23, 2009, 11:15:17 AM
Thanks Peter.  I think I understand. 

I did find out at least one cause of the invalid TIFF indication -- if I export from LR without compression into TIFF they validate, if I export with compression they do not.  And the hand-off file from Lightroom 2.3 to CS3 is apparently a compressed TIFF.  I'm not sure if that is the default or not, I see that I can change it in the preferences.

But at least this compression from Lightroom will not validate.  FWIW.

I wish there was a standalone version.  $40 is not a lot of money, granted, I just hate buying something I won't use to get the free tool.   Undecided
6  Software Discussions / ImageIngester and ImageVerifier / IV, (potential) New user, Questions on: April 23, 2009, 07:26:46 AM
I use Lightroom and am happy with the image load from it, but was looking for a verifier program and managed to stumble into this product and later this site (thanks to a tip on Lightroom Forums).

It appears that one has to buy the ingester to use the verifier.  Unfortunate but not a big issue (or did I misunderstand).

My first use of the verifier I had about 10 NEF's and 3 of them had been edited, so had corresponding TIFF's produced by Lightroom (I did not save the edits from CS3, just used it to cut/paste some crops).

The NEF's all verified (after I downloaded the DNG converter), but the TIFFs all say they may be invalid.  They display fine in both Photoshop, Lightroom, and IrFanview.

I initially dismissed IV as broken, but someone on LRF suggested I look more closely, and this "feature" does seem to be documented.  Also unfortunate, especially that it would appear to fail on a pretty common product's TIFF's.  Not sure what that means.

Does anyone have insight?

Fundamentally what I want is something to run parallel to Lightroom, and periodically check that no bad things have happened, tell me which images have been changed, allow me to relatively easily dismiss those changes when on purpose (e.g. I do a bunch of metadata updates or keywording of old shots).

I THINK it will work in that mode.

Are there any issues using it without the Image Ingester portion?   (Not asking a licensing question but whether one presumes the other was involved)

Are there any more lightroom-integrated choices? (For example taht might reconcile changes known to Lightroom's catalog against changes in hash and only show those that weren't know).

And should I worry that it doesn't do TIFF's well?  I understand the issue that "anything can be inside a TIFF" but is Adobe really producing non-conforming TIFF's?

Linwood Ferguson

PS. Windows Vista, Lightroom 2.3, Nikon
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!