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: ccclapp
The DAM Forum
Welcome, Guest. Please login or register.
October 31, 2020, 09:48:00 AM

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  Software Discussions / ImageIngester and ImageVerifier / IV False Errors if dont Boot into Safe Mode?? on: August 25, 2010, 11:33:45 PM
Hi Marc, Peter, et al:

I am testing IV (and several other back-up/verification software) to write an article on DAM workflow but am experiencing an issue:

Unless I boot into Safe Mode, I get many false errors on hash and verify (I am not referring to structure issues due to noncomplying tifs.  I am referring to the hash creation/verification).  This mostly occurs with very large .tif files (150 mb), especially ones that are "RAW" Viewscan film scans at 64 bits (R.G.B plus inferred).

I have found this issue both on Vista 64 and a clean install of Win7 64.  I turned off Indexing/paging/system restore and all anti virus or firewall software (none installed on the clean Win7 OS partition).  I have also tried keeping the source and destinations on the same partition.

If I hash and hash check the same files multiple times with IV in normal start-up (vs Safe Mode) I get errors on different files from one run to the next.  If I then repeat in Safe Mode, I don't get errors.

Even on the clean OS install with no other programs loaded, I get this condition.

The PC otherwise runs perfectly.

Does anyone have any wisdom for me?  I am working on several TBs of image files and want to be sure my back-up/archive is correct and verified.

Thanks for the guidance you give us all here and elsewhere!

Caleb Clapp
2  Software Discussions / ImageIngester and ImageVerifier / Re: Putting Original (in-camera) file name in a field not working?? on: July 27, 2009, 03:10:39 PM
If I look at the image metadata in Bridge I do see the original file name, as hoped.  Thus the issue is only seeing it using the Examine feature in II (which is not an issue), so case closed.  Wink

Thanks
3  Software Discussions / ImageIngester and ImageVerifier / Putting Original (in-camera) file name in a field not working?? on: July 27, 2009, 02:47:57 PM
Can one add the original (in-camera) file name to a field?  The manual says {@filename} gives you this, but it does not generate anything.

In my Caption/Description field, here is what I am trying to do:

Camera File Name: {@filename} / Date and time shot: {@datetime} / New file name: {@filenameNew} / Download date and time: {@DateTimeCurrent} / Parent Folder Name: {@datetime,1,4}/{@datetime,1,4}_{@datetime,5,2}_{@client.name}-{@project.name}_CCC / Description of folder images: {@project.description, - }{@QF.7-Caption/Description}

And this is what is generated:

IPTC.Caption:

Camera File Name: / Date and time shot: 20090216_144930 / New file name: 090216_ G9__CCC / Download date and time: 20090727_171758 / Parent Folder Name: 2009/2009_02_MA-WingBeachwKids_CCC / Description of folder images: CCC and Kids at Wingsht beach during summar vacation after Pony Farm


Everything else works fine, but not {@filename}.

Thanks
4  Software Discussions / ImageIngester and ImageVerifier / UserData Fields?? on: July 27, 2009, 10:48:29 AM
I dont see in II where the UserData fields are located, shown below:

UserData
UserData.id: {@UserData.id}
UserData.field1: {@UserData.field1}
UserData.field2: {@UserData.field2}
UserData.field3: {@UserData.field3}
UserData.field4: {@UserData.field4}
UserData.field5: {@UserData.field5}
UserData.field6: {@UserData.field6}
UserData.field7: {@UserData.field7}

Are these called something else in the program??

Thanks
5  Software Discussions / ImageIngester and ImageVerifier / Error ingesting from cards?? on: July 27, 2009, 10:35:20 AM
If I ingest w II from a card on any card readers (I've tried two and both work with LR, Downloader Pro, Etc) I get the following message and the ingestion is aborted:
"P:\
ERROR:  Error assessing path (1)
I do not get any errors if ingesting from my hard drive.

Has anyone else experienced this?

Thanks
6  Software Discussions / ImageIngester and ImageVerifier / Re: Camera Model in File Name on: July 27, 2009, 10:19:01 AM
I would like to add to this question:

I understand how to get model name using exif.Model.  I use {@exif.Model,-2} to get only the last two letters of the name for my Cannon 5D and G9.  However, the last two letter designation does not work well for models with more than three letters identifying model # (such as G10 and (Fuji) X30, etc, etc).  One noce feature in Downloader pro is the ability to script the "last word" of the model name. This picks up 5D, G9, G10, X30, etc, etc.  Since I use model name in my file naming macro, I dont just want to expand the # of characters or use the whole model name (Cannon Powershop G10).

Is there a way to script using "last word", "first Word" etc w II?  If not, this would be very useful in this and other scripts.

Thanks

--Caleb
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!