This situation often occurs if files in a hard-drive folder are imported with the option, thus creating two copies of the file on the hard-drive. It is possible that the file reported as a "Duplicate" is stored in another folder and already exists in the Catalog.
Lr does not 'like' having more that one entry in the Catalog for identical files, no matter where they might be in your system. Lightroom is looking at EVERY PHOTO IN YOUR CATALOG to determine if a file may be a "duplicate", and not just the "other" files in this one folder. The file name was not even similar to any of the other 14. Please let me know if this solution works for any others of you with this problem. So I am mystified as to why LightRoom thought this was a duplicate. Neither was the file size or date and time.
In another folder but with only 14 photos in explorer and just one missing file in LightRoom, I was able to carefully check the details of this supposed duplicate which was being excluded. Lo and behold, the missing files were suddenly displayed, and then successfully imported. Next step, there were no files shown to import until I unticked the option "prevent importing duplicates" (or similar wording). (this is important otherwise LightRoom will carry out the process but fail to import the pictures without telling you why it did not!). I selected the option "show import dialog before importing". Interestingly, I noticed that this option was greyed out on any folder where there was not a discrepancy (between Lightroom and Explorer). I right-clicked on the offending folder in the LightRoom and then clicked synchronise. In one instance I had five files in LightRoom but over a hundred in the explorer folder. I could also see that the LightRoom folder was pointing at exactly the same folder in explorer. It may not be the same for everyone that has had the problem, but here goes.Īfter viewing all the suggestions above, I was confident that I had not created copies, or was stacking pics. I am a new LightRoom user and I had exactly the same issue. I can see that this thread is quite old but some of the replies are recent so clearly it is an ongoing problem.
0 kommentar(er)
