If the catalog becomes corrupted, you restore the previous (uncorrupted) catalog, you will lose a small amount of recent work (the last day or the last week), but nothing else. This is clearly a different issue, and for the benefit of anyone reading this far, the problem could have been prevented by a better backup strategy, using the built in catalog backup which backs up the catalog daily or weekly (and has nothing to do with the RAID system). Unfortunately, my raid controller didn't help because it immediately replicated the corrupt index files. Exposure X6 was made by Exposure Software company, previously known as Alien Skin. You can take your RAW photos shot from any camera, import them into the software, and make them more appealing through easy retouching. The database became corrupt and I can no longer utilize that database. Exposure X6 is a photo editing and management software with creative and powerful tools. Unfortunately, lightroom has no such option.Ĭase in point, I used to have a single, large lightroom database in which I had over 15,000 images. I just found out that Bridge has an option to use the build-in preview file as well so it too should be faster.
Lightroom not only renders multiple sizes of the image for preview but also uses your "default" ACR settings to render the preview and then saves this to the database, again much slower than just using the preview jpg that's already present in the canon raw files which is why photomechanic is faster. On the previous point you made about the database, you may be misunderstanding all that goes in with lightroom. (one of the reasons I no longer use a raid controller to auto-backup)
#Meglio lightroom or exposure x full
The problem is that lightroom generated a corrupt backup without a full verify that the original catalog was integrity-correct so both the backup catalog and the regular catalog were left corrupted and of course replicated to the backup through the raid controller.
0 kommentar(er)
