I have meticulously kept the DOP sidecars (once I learned just how important they can be at times) if I can't get this sorted, I will "hide" the database and allow another to be built and see if that resolves the situation. I might never have considered the database as being the culprit, but after your explanation, it is my first suspect on the list. If you do have the previous DOP files though a new database will be created from them as you enter each folder that contains them. Be advised however that if you do not have DOP files for your previous edits that you will lose all your previous edits. "Buckskin's test files xyz" then restart Photolab and retest.Īs for the corrupted DB, I'm afraid the only solution is to delete it and let the program create a new one. A way to test this is to put your "virgin" files into a completely new folder containing no DOP files with a new name that Photolab has never seen before i.e. I suspect that this has happened to you and when you try to edit your "virgin" files the database is finding something that it thinks matches and is trying to apply some previous edits from it's memory. Unfortunately the database can become corrupted too. Please note that It is the folder name as well as the file name that Photolab recognizes for it's use in the database. ![]() It it finds none, then and only then will it apply your default preset. The way your preferences are set up, it will look first for a DOP file in the same folder matching the file you are working on and if it finds none then it will search the database for a matching entry in this folder. It's a fail-safe in case the DOP file gets lost or corrupted. ![]() Okay, Photolab uses a two-staged process to keep up with your edits, a database and the DOP sidecar files for each individual file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |