-
1. Re: completing import/previews with unreadable files
Ian Lyons Jan 12, 2010 3:42 PM (in response to Owen Carey)Having had similar a experience on at least one occasion I can feel your pain. Alas, I don't think that a lot can/will be done to change what Lr does when traps what it believes to be a corrupt or unreadable image. I'm certainly not aware of a preference that would allow Lr to bypass such images.
-
2. Re: completing import/previews with unreadable files
bill@sshaphotos Jan 17, 2010 10:35 AM (in response to Owen Carey)I just finished a folder sync with Lightroom 3 and also ran in to the same error.
It would be nice to move the Error Dialog box to display after everything is done, telling you all the errors it found.
Having the coming back after letting it run all night just to wait for a hour or more for it to build previews is unproductive.
Bill.
-
3. Re: completing import/previews with unreadable files
Owen Carey Jan 17, 2010 12:54 PM (in response to Owen Carey)thanks for the note Bill -
I also posted my question to the forum for new features in the next lightroom iteration. Seems like once the import stops and before the previews are made -- that's when the dialogue box opens stopping the previews from being made. I'm not an engineer and I don't write code, but it seems to me the software could and should continue with the task at hand ( import AND build previews) for all the image files that it has correctly imported, while it segregates and does not import -- and later confirms the unreadable files.
Actually I don't think that Lightroom actually imports the disputed files at all -- if they are .mov files I don't think they can -- if they are corrupt files, they advise me of the camera given file name - not the re-named file that my import menu would give it, leading me also to believe that they were not imported into the catalogue or moved into the assigned destination folders. I would love to get some clarification from adobe on this.
I would imagine that this is a matter of overlooked scriptwriting that has not yet come to their attention... or a script that could be made better if enough people had a problem with it. I was very much hoping to get a response from someone at adobe to my query -- but nothing yet -- hopefully the response will be the elimination of this roadblock in the next version or update. Often it's the squeaky wheel that gets the grease, and maybe there are not as many people out there as myself who have run into this problem, and posted inquiries to the forum. Theater shooters like myself who might shoot 2,500 to 3,500 images in 2-3 hrs, event photographers, sports photogs, wedding photographers and fashion photographers are all the kind of people who can shoot thousands of images in a day or a matter of hours. Unless we are sitting at the computer when the import finishes, we will be waiting for previews to build - be they standard or 1:1 previews - until after we have read and checked the warning dialogue. hopefully this will be fixed soon or we will get some sort of explanation.
I have a lot of admiration for the folks at adobe, their genius, their talent, their accomplishment and their responsiveness to our issues, so I hope this problem gets addressed soon - I cannot be the only one out there who was STOPPED at this point in the workflow.
cheers, and best of luck