CSS Simon wrote:
I think it's that dangerous.
Not deleting images from card after importing poses more potential for data loss - that is not just a theory, it has been my experience, and that of many others too, and you can see why if you think about it enough. Computers are quite adept at keeping track of which images have been successfully imported, and not deleting any images that haven't...
*All* imported images must be deleted from the card at some point, after importing (unless you buy a new card every time one fills up) - in my opinion, the best time to do it is immediately after it has been discerned that image has been successfully imported, rendered, and backups made...
Regarding corruption, it's easy for a computer to tell if an image file is OK, in general, but not so easy to tell if all the image data is OK. As it stands, Lr software is making the determination implicitly, without asking, that the image data in a raw file is not corrupt, when it converts it to DNG upon import. If the raw data was corrupt upon import, then if a good file is subsequently read, the good file would be considered corrupt, due to checkcode mismatch. Thus Lr would allow you to edit the corrupt image, but only if not replaced by a good version of it. A better strategy would be to ask the user after import - are all of these images OK? (e.g. no funny stripes or rectangles), if so, then convert to DNG, and compute the check codes over them for future corruption detection, and delete them from card if that option is enabled, and user has approved the rendered images and the prompt.
While I'm at it, there is no good reason not to compute integrity check codes for proprietary raw and jpegs too... - that omission is another pet peeve of mine.
Rob