Of Catalogs and Imports/Exports
I'm trying to debug the flow between C1P and Aperture via Catapult and made some good progress for a while, I was able to send an editted image and its edit history and forth half a dozen times, but now I have some practical issues I need to solve.
1) How do I go about deleting a catalog - I created some extra catalogs with useful names like Test1, Test 2 and so forth, some of them seem to be corrupted and not working any more (and don't have anything important inside). I can hide the file where C1P can't find it, but C1P still seems to have cache somewhere and wants to open it.
2) If I am exporting an image from C1P, and I wish it to write a TIFF file and a XMP sidecar file, how do I cause it to update the XMP file. I have seen a number of times where the XMP file is not updated at the time when the file is exported, and then it has the wrong version of edits in it. So far the only strategy I have come up with is to delete the sidecar file before exporting, and then C1P immediately writes a new sidecar.
3) I assume that if the XMP file and the RAW file are together int he same folder, then C1P should import both - does it associate the two simply because they have the same name, or is there a more complicated mechanism.
4) Does C1P have a mechanism where it will not import an image file if the file is already in the catalog?
5) What is the best way of completely deleting a an image file from the catalog, so that C1P will not object to re-import it?
6) Some of my test catalogs give the following console messages when they start "Wrong Browser Cache Content" and then "Data integrity Check failed" - after that I have import difficulties with them. I have tried "verify Catalog", but that doesn't find anything wrong. Is there anything else I could try?
1) How do I go about deleting a catalog - I created some extra catalogs with useful names like Test1, Test 2 and so forth, some of them seem to be corrupted and not working any more (and don't have anything important inside). I can hide the file where C1P can't find it, but C1P still seems to have cache somewhere and wants to open it.
2) If I am exporting an image from C1P, and I wish it to write a TIFF file and a XMP sidecar file, how do I cause it to update the XMP file. I have seen a number of times where the XMP file is not updated at the time when the file is exported, and then it has the wrong version of edits in it. So far the only strategy I have come up with is to delete the sidecar file before exporting, and then C1P immediately writes a new sidecar.
3) I assume that if the XMP file and the RAW file are together int he same folder, then C1P should import both - does it associate the two simply because they have the same name, or is there a more complicated mechanism.
4) Does C1P have a mechanism where it will not import an image file if the file is already in the catalog?
5) What is the best way of completely deleting a an image file from the catalog, so that C1P will not object to re-import it?
6) Some of my test catalogs give the following console messages when they start "Wrong Browser Cache Content" and then "Data integrity Check failed" - after that I have import difficulties with them. I have tried "verify Catalog", but that doesn't find anything wrong. Is there anything else I could try?
0
-
I am also looking for a mechanism to delete some temporary Catalogs. Can anyone help? 0 -
I have found that if I first I first delete all the images in the Catalog using C1P, then stop C1P and use finder to delete the Catalog file xxxxxxx.cocatalog then I don't have any problems.
I have also found that it seems to be helpful if each catalog has a separate folder for external files, and separate folders are used for files before import and after export. Files are easier to manage for me, and there are no messages from C1P after deleting files and Catalogs.
~/Pictures/CaptureOne/Catalogs
~/Pictures/CaptureOne/CatalogFiles ... /Catalog1Files ... /Catlog2Files ... /Catlog3Files
~/Pictures/C1P/CatalogImports
~/Pictures/C1P/CatalogExports0 -
Thanks Eric - will give that a try.... 0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare