Edit with Capture One from Photo Mechanic
I've set up Photo Mechanic Plus to Edit photos (Image/Edit Photos) with Capture One. When Capture One is already open, this triggers the import dialog within Capture One just fine. When Capture One is not yet open, Command-E starts up Capture One, but stalls at the dialog that asks which Capture One catalog to open. When I select the proper (and only!) catalog, I have to go back to Photo Mechanic Plus to run command-E once more, to start editing with Capture One. Am I missing a setting somewhere? I'm on a Mac, running Photo Mechanic Plus build 5560 and Capture One 20 (build 13.1.2.37).
The same behaviour is seen when dragging a file, either from Photo Mechanic Plus or directly from a Finder window, onto Capture One in the dock. When I start Capture one from the dock normally, it bypasses the dialog and opens the recent catalog. Is there a setting I can change so that editing a file from Photo Mechanic or dragging and dropping a file from Photo Mechanic or the Finder onto Capture One in the dock bypasses the dialog which catalog to open?
-
Can you try calling C1 from PM when having a C1 session open?
In Windows, when you copy the below string to the search box, then C1 creates a new album holding the image (or images) and you can edit them.
e.g. one image:
C:\Program Files\Capture One\CaptureOne.exe "C:\User1\Pictures\Capture\12345.NEF"
e.g. two images from different folders:
C:\Program Files\Capture One\CaptureOne.exe "C:\User1\Pictures\Capture\12345.NEF" "C:\User1\mybestimages\Capture\P9070001.ORF"
Can PM call C1 using these parameters? Or can you configure PM to do so?
But I think there is much more on PM side to implement e.g. stacking raw+jpg+tiff variants, or showing the preview file from C1 instead of an (I assume) unedited raw/embedded jpg etc.
Also interesting:
0 -
Thanks. So, you say stacking raw + jpg works in PM+, and you can make the jpg being the preview in PM+? Then, you can select the stack (or the raw) and send it to an open C1 session? Or you cannot, and that's the reason for your feature request?
0 -
I voted for your request though I want to edit multiple images not only one by one, and I also think it would need an enhancement in PM not in C1.
0 -
@EtMRS: Great. Can you also select multiple raws in PM+ at once and "send" them to an open C1 session?
Regarding EIP, be careful, e.g. tiff files cannot be packed into an EIP. But you can export Originals including Adjustments. This creates the sidecar folder "Capture One" and "Settings" beneath. Once you access the folder with any arbitrary session the Cache folder is also created.
But don't have a session open at the time when you export from the catalog, see also
0 -
@EtMRS
When I select various picture and drag to CO1, CO1 opens a new session album with all the pictures
After drag&drop, when you right-click on such a picture in the new album in C1 and select "Show in Explorer/Finder", does it open the folder you'd expect?
If drag&drop works as you described in the Windows version too I might give PM+ a try...
0 -
EtMRS, Thank you. That sounds very promising.
One question. When you say
In W10 only, in contextual menu, you have "Edit Selected pictures". CO1 edit only the last one.
do you mean that when you select many images in PM+ on Win10 and then click "Edit Selected pictures" in the context menu of PM+, then the dummy C1 session only shows one image instead of all which were selected in PM+?
0 -
Thank you.
BeO0 -
Yes, both users would update the same settings and mask files (unless maybe if they use different versions e.g. folder Settings131, Settings130). The later write to these files would win, you just don't know exactly when this write action occurs.
I don't know what happens if both users have their session open at the same time, and what happens when one closes it, I think this should be avoided by any means (unless maybe, they would work on different images - but who knows...).
Catalogs have a write lock file, session don't.0 -
As you can set permissions on the NAS, you might be able to control access to the folders per user hence avoiding such potential conflicts.
0 -
@EtMRS
EtMRS:
First, a little tip : After developing RAW and edited metadata in CO1, export it in jpg with same name as the original RAW. Save this JPG in the same path as the RAW. Now, when you open PMp you shall see a RAW+jpeg with a preview like the RAW with CO1 adjustment ant metadata available in CO1.
The disadvantages I see with this:
- If you delete a raw from disk, you do this from within the C1 session (which you should do rather than in PM+ in order to get rid of the C1 sidecar files), then the jpg is still there since it is not stacked in C1
- C1 will automatically create all sidecar files for this jpg too. Not always but e.g. if you preview the jpg in C1. A lot more files (which you would not really need) just for this jpg preview in PM+
It would be sooo nice if PM+ could directly read the .cop preview files (i.e. (1) the file format and (2) from a different, relative location, the CaptureOne/Cache/Proxies folder) and stack them with the raw.
0 -
@EtMRS
C1 doesn't delete sidecars if the images are deleted from external.
If I delete the original image file from the file system with Windows Explorer (RAW and / or jpg, whatever is in folder Capture), the respective sidecar files (.cos .cop .cot .cof) remain in the CaptureOne sub folders. Same should be true if not Explorer but PM+ would delete the raw+jpg.
So I would want to write a cleanup script to delete such orphan sidecar files once in a while.
Metadata:
I understand you use the jpg to transfer the metadata from C1 to the raw+jpg stack in PM+. But you cannot transfer back metadata from PM+ to C1 for the raw file via the jpgs, right? Unless you use xmp, which is possbible in both directions.
I think I understand your approach. This gives the jpgs a very important role, more than I want it to be. Currently, I consider jpgs as obsolete, I can delete them without headache, I don't include them in my backups, etc.
But I see, you use this approach anyway because of the geolocalisation app, so it is consistent for you.If C1 would create .jpg instead of .cop for the previews, and PM+ could stack them to the raws with the same name though they are not in the same directory, this would be ideal (for me), as the previews are built anyway automatically with every edit in C1. I also prefer xmp (or .cos) nearby my raws instead of jpgs as the container for the metadata of my raws, they are deleted and they are moved together with their raws in C1, and are smaller. I think my hesitation is due to my self-imposed disregard for jpgs in comparison to raws:-)
0 -
Hi EtMRS,
Understand. It seems a very good solution to have PM+ as the DAM in the center of your workflow, especially if you are working with 80k images.
How does PM+ know if a jpg (or any other file) which is already in PM+ catalog has changed, e.g. by C1? Do you have to do anything in PM+ (re-import or so) or is it recognized automatically?0
Post is closed for comments.
Comments
12 comments