Transfer C1 catalog managed photos to Photo Mechanic managed
Because of an existing performance bug of C1 13.1 (very very slow file actions) I am thinking about changing my workflow.
I will try to manage my complete photo library with PhotoMechanic ... still using C1 to develop my raw's.
So I have to transfer C1 catalog managed photos to Photo Mechanic managed. Is there someone who has experience with this transfer and Tips to do this in the best way?
Thx!
-
When you say catalog managed photos, do you mean that your images are stored within the Capture One catalog, rather than in the regular computer file system? If so, then you will want to move them out of the Capture One catalog into folders on your computer. (I assume that PM doesn't actually store images inside a catalog, like C1 can.) You can do that by creating the folders you want to use in Finder, adding them to the C1 catalog, then dragging files as required from the Inside Catalog part of the Library tool into the folders you want/
How many managed files do you have in your Capture One catalog? Does that number have anything to do with the slowness?
Ian
0 -
The files are still in my regulär filesystem only managed by C1 (not stored in C1).
I have several C1 catalogs between 5.000 to more than 100.000 photos. The number of files does not have something to do with the slowness. It's a bug inside current C1 Version 13.1 (ticket is accepted and still open) , 13.0.x was and 12.x was ok. All file transaktions (e.g. importing 1.000 takes around more than 1.5 hour -> unaccepable slow)
0 -
So in that case, perhaps the strategy you need for now is to select the photos you want to work on using PM, and move the selected ones to a different folder, which you can then import to Capture One (without being slowed down by importing the rest). Or you could work on them in C1 using a session, which could add the image folder as a favourite. No importing as such is required, although C1 still has to generate previews, so that could be a bottleneck, I suppose. You can always add them from the session to your catalog later when you have resolve this issue.
Ian
0 -
Thx, yes. I will try you use PhotoMechanic as my only DAM and C1 only for developing the raw's.
My question is now: How can I get all photos with their individual keywords, ratings, color marks I assigned in C1 available in PhotoMechanic, without touching original raw files?
0 -
Transferring the photo's keywords, ratings, color marks assigned in C1 to PhotoMechanic is not trivial.
You should of course store these thing in an XMP sidecar file, and CaptureOne will write the XMP for you. However the contents of the XMP are not intereted the same way by Capture One and Photomechnic.
Check the PhotoMechanic forum for some interesting posts.
The most obvious problem is that Capture One has two colors that Photo mechanic does not. Another one is that no two applications handle and descibe hierarchical keywords in the same way.
Most likely EXIF Tool can be used to massage the XMP from Captoure One format to Photomechanic Format. I've done this before in transferring Metadata from Aperture to Capture One (not as complicated, most issues with hierarchical keywords) but it is a great help if you can write a little Applescript to coordinate and deal with the more complicated changes.
The simplest to handle hierarchical key words during a transfer is to combine the entire hierarchy into one string, so that keyword B which is a child of keyword A becomes keyword A_B. Once on the other side you then creat a new hierachy by first creating keyword a, then selecting all images witth keyword A_B, and assigning a keyword b which is the child of keyword a. Finnally delete keyword A_B.
0 -
Hi I P
I'm thinking of buying Photo Mechanic 6+ to use as my DAM with CO but have the same question - how do I create a PM catalog that recognizes all the edits I have done on my CO images (these are stored in an external drive as individual files not in CO itself)?
I'd be grateful if you could respond as they have a promotional price which I believe ends tonight. Thanks
0 -
The only way edits made in Capture One can be seen outside of Capture One is to export (process) the edited variants. You will have two (or more) copies of the image, the original unedited image and processed copies. It makes no difference if you use a catalog or session. It makes no difference if the images are stored inside or outside of a catalog.
I'm ignoring the Capture One previews... I don't believe there is an easy way to access those files assuming they are files that can be displayed by other programs.
0 -
Thanks, Where do I export them to and in what format (I'm guessing JPEG)?
0 -
I have been considering the same thing and have an evaluation copy of PM6.
First thing is that PM will not recognise the Edits made by CO. (I think this kind of coordination is very rare, I'm not aware of any two tools that will share their edits, about the best I've ever seen is CaptureOne and Aperture)
IMO The only way that really works to share an edit between two tools from different vendors is to output and share the resulting image.
Another question is DAM settings of each tool. You don't want both tools to be trying to manage assets. .
PM6's real strength is injestion, culling and assigning Metadata, and the speed with which it operates. Its DAM function is very new - although likely exteremely reiliable given the 6 month beta period, it seems a little short on features. In my opinion, Capture One's Catalog is superior to that of PM6+, as PM6+ doesn't do Smart Albums, and I find their whole catalog interface very clunky.
If you are using Capture One for DAM, and PM6 for ingestion, then it is only necessary to transfer color codes, ratings, keywords and IPTC metadata from PM6 to CO. If the both tools are set to use XMP sidecar files, then for RAW image files this works great. For JPEGs, there is a small problem. PM6 always writes the metadata inside the JPEG file. Capture One will read the JPEG's metadata, but never write or change it. Capture One will only change an XMP file. Thus with Capture One, keywords and other Metadata of the JPEG file can be changed, but will persist only as long as you do not resynchronise the image. The keywords in the JPEG file will be in the catalog keyword library forever. This could be remediated by clearing the JPEGs IPTC and XMP metadata after it has been read by CaptureOne. Exiftool will do that, and you can also do it with PM6.
if you are using PM 6+ for DAM, then you don't want CO to also try to perform DAM, so the best configuration will be for CO to use a Session and PM6+ to use its catalog. As mentioned above, tools don't freely share their edit settings, so after editting an image in CO, the result will have to exported (8 bit TIFF? DNG? PSD?), with edits and metadata, and then ingested into the PM 6+ catalog.
I am not sure what I'm going to choose. I do have quite a large number of JPEGs.
My initial thoughts were PM6+ and let it do the DAM. But I'm not fond of its DAM, and I notice that Image Alchemist also hasn't devised a two way workflow between PM and CO. So perhaps not this option.
I could just use PM6 for ingestion and culling. PM6 is cheaper than PM6+
Or just stick with CO21.
I do have the CO21Beta, although I may not state my comparison of PM6+ and CO21Beta.
0 -
Thanks for your detailed comments. I have CO20 (I’m a refugee from Aperture, which I still long for, but which would not support my Olympus RAW files and now of course has been completely phased out) and the trial version of PM6+ but given all the issues of coordination especially with regard to retrospectively looking at older images, the answer may indeed be to just stick with CO or perhaps PM6 for ingesting and culling going forward. Maybe one day CO will beef up its DAM features...
0
Post is closed for comments.
Comments
10 comments