John-do you have access to the LR Metadata item "Metadata Status" that appears directly below File Type in the Library Metadata panel. If so, rather than deal with time and date info, your Save could be triggered on LR's "Has been changed".

-- Dave

John-that's exactly what I'm seeing. The 1 second difference in the times is causing photos to show up in the Smart Collection after the update has been performed. The Smart Collection is constructed with the Rule-

DNG update is Save.

--Dave

OH boy! 

Dave

Oh John- are you working on a plug-in to show if any DNG previews in a catalog need to be updated (without having to go thru each bucket).

--Dave

Mike- I get the logic, but with the check box selection "Keep Existing Hashes" (located next to "Store Hashes"), it seems like two belts and suspenders type of protection. No big deal, but it does require extra key strokes.

thanks for replying tho-

--Dave

Marc/Mike- In reading this post, am I to assume that Job = Preset. I'm trying to adopt IV to my bucket workflow (already registered owner of IIPro). I was trying to establish "presets" to differentiate between creating hashes for new buckets and checking hashes on old buckets. BUT, creating a "New" job does not retain the selections. Help?

--Dave

Peter - probably could wait for the book update, but a couple of questions if appropriate? I use a DNG workflow. My collection of photos is currently @15,000, folder & bucket method. I currently manually save metadata and adjustments to "originals" (backup to disk).

1. I have lost the answer to this question in the fog of learning LR. I assume Print uses info from the catalogue in order render all adjustments made to the originals and then print. Yes/no?

2. If the answer to #1 is yes, are you suggesting, especially in my case, where there is potentially only one catalogue, that I could simply NOT update my originals (by keeping any changes in the Catalogue) and therefore-
     a. significantly reduce potential corruption issues to my originals, and
     b. make any photo movement from folder to folder within LR, so it "remembers" file location. I very seldom move photos, since I use the bucket method.

thanks in advance-

Dave

John-sorry to hear about your troubles. Great to hear you weren't contemplating a permanent move to a pub existence. But, then again your site isn't up yet. 

--Dave

John- Is there a problem with your website? Or are you "composing" from the Pub again?

--Dave

Nope-just got used to his frequent updates!

--Dave

Peter- any idea where Marc is? Last post was @ Nov. 2nd.

--Dave

Jonathan- you are not to specific regarding how you have set up for keyword ingest, but-
1. review the manual for the use of "Quick Fields".
2. Make sure you enter the correct structure for Quick Field (ie, {@QF.Caption} into the fields in Content portion of the Metadata section.
3. once you've got that concept down then-
4. in the case of Keywords (in the same Preset), enter {@Keywords}, drop the "QF." Any keywords you have set up in the Keyword Preset should now ingest accurately.

YMMV

--Dave

Peter/Geoff- "same" for Lightroom. Metadata changes to DNG(s) can be instantaneous, while updates to the DNG Preview can take "longer" (whether done manually or automatically)!

--Dave 

Dan- Lacking in what? I'd be surprised at this point in LR's development if it was less than robust at dealing with DNGs. I use DNGs for my workflow. I use ImageIngester to create DNGs with full-size JPEG previews from my Nikon RAWs. I then import those DNGs into LR(2.1). I have several catalogues. One has @6000 photos(DNGs). In LR, I have set Preview Cache size to 1440 pixels with "Medium" Preview Quality. That 6000 catalogue (lrcat) is 101 MB in size. The companion Preview Cache (lrdata) file is 2.78 Gig. Any modifications to the DNG in Library (keywords, etc.) and/or Develop Module (adjustments) reside in the catalogue until they are updated to the photo either manually or automatically. There is even a command to update the DNG Preview with any adjustments you have made since creating the DNG!

My advice would be to play around (time permitting) with version 2.1. Its much faster in many respects from 2.0 (never mind v1.x). I suspect the biggest drawback to you using LR may very well be your already considerable investment (and comfort level) with iView.

--Dave

Peter/Doug- thanks guys. Love these Forums.

--Dave