Missing image has incorrect thumbnail shown in catalog
Just imported a few catalogs from LR 5.7.1 into new install of C1 20. Some images (CR2s) in catalog were (correctly) missing from HDD, however, occasionally instead of the warning triangle the thumbnails shown are from images with the same name in a different catalog and folder on HDD. Not a big problem but something odd is going on.
-
I would suggest running a verification.
Also, did you do any "cleaning preparations" on the LR catalogue to try to ensure that any pre-existing internal problems were eliminated before transfer and import to C1?
0 -
Thanks for the prompt response.
Verification: found errors and appears to have corrected OK, however, erroneous previews still appear.
Regenerate Previews: no change - same previews shown, even though the main Edit view shows file not available message.
Checked original LR catalog and no evidence of the incorrect previews which were from a different catalog several years later.
Optimised the LR catalog (first time since 2013, apparently; tut, tut) and Exported to new catalog, then imported to C1 and no issues observed in new C1 catalog. So, obviously, I should have done that.
They delete OK and don't cause me any harm. When I did my long import session, multiple catalogs were imported from LR without closing C1 between imports and RAM usage was quite high (~20GB) so perhaps that could be where the cross contamination came from? Perhaps, either Preview regeneration or the Verification needs to be slightly more thorough? (Otherwise, very pleased with performance, output and dual monitor experience compared to LR.)
0 -
Hi Steve,
Well caught!
I don't use catalogues but the only time I have had something similar with a session , years ago, turned out to be what I thing was a bad link somewhere in the depths of the core file system management (basically the reference numbering of a file fragment was wrong and allowed it to connect to places where it should not have connected and what were different files) and this cause me a number of seemingly random problems with crashes ever 10 or 12 images as I was processing some 3000+ files.
About half way through the edits I happened by chance to spot a slightly corrupt thumbnail for one file. It would have been near the end of my processing run.
Regenerating the thumbnail made no difference. I had a feeling something connected to the associated edit instruction file might be part of the immediate problem and possibly the crashing problem. So I deleted the image and reimported it. The thumbnail then generated correctly and there were no more crashes.
Your description sounded like something similar somewhere in the file system and for the stage you were at re-importing with a pre-clean, if nothing prior to that worked, seemed like the right thing to suggest.
FWIW I have, over the years, also has some exposure to PDF files where the internal database for the document appears to deliver a document that looks correct on screen BUT if one tries to process it for re-purposing or any other reason the entire exercise turns into a complete mess. There was no way to know that from just viewing the document.
In computer terms a PDF file is very much like any other image file and is built up from stored data "blocks" that form components of an image.
So it is entirely possible to have something that looks OK but is somehow dealing with internal issues in a way that is not cleaned up on export and is probably not even something for which there is a check. The only solution it to clean up in the original application software. For a PDF, as the PDF functionality software developed over time, that meant finding a way to regenerate the file via some form of export and recreate.
The same principle applies to the LR Catalogue Optimisation and, in turn, to C1's Verification processes.
Have fun with C1!
0 -
I had this happen in Lightroom once, the catalogue became corrupt and kept telling me that 60000 files were missing, I never managed to fix it. Sufficed to say that I didn't even bother to try the migration process when I moved to C1. One of the reasons I am not a massive fan of catalogues. I have been toying with not using catalogues in C1 and just using a session and browsing the files I want to edit, but I have around 300k images and I am not completely sure it is the right route.
0 -
Tricky one Mark.
FOr you legacy stuff - that you may never touch again in many cases other than viewing - not creating a migration probably makes sense.
For new stuff I'm not so sure. Going with sessions means you can move in other directions easily if something more comfortable comes up. Still have access to the legacy stuff on demand ... but with some care as C1 works on the Folder level rather than by file selection unless going through an Import process.
0 -
Replacing the missing images appears to work. As the image is correctly identified as missing in edit window I would have thought there was enough to repair/clear the browser preview. I think the conversion process has done a pretty good job overall.
I'm preparing two differing talks based on the last dozen years' work and the tagged information in the old LR catalogs is essential for that. I've been pleasantly surprised by the improvements in speed and ability to draw out better tonal range and detail, especially in the older images. As for using catalogs over sessions, I will probably be using sessions whenever "events" become allowed again and can return to snapping - I can see the advantages for outputs, etc.
0
Post ist für Kommentare geschlossen.
Kommentare
6 Kommentare