Are you using any workarounds or other solutions to achieve your goals in Capture One?
As a workaround I am exporting pictures from Mylio (= creating a copy of the original files) to a new specific folder, which I am importing into CO for editing. At the end I have 2 copies of the same file, 1. original at the original location, 2. CO-edited copy of the original in the separate folder. Finally I need to manually find 1. in the library and delete, and move 2. to the location inside CO to keep the CO-edits.
Hi Christian, sounds good.
Cheers
BeO
Hi BeO,
Yes, I keep both. But I anyhow generally have a 2nd copy of all RAW files in an archive (never touched, just the "photo negative locker").
So, I have the RAW in my photo library (drive), with CO edits covered by the CO library.
And I have an additional exported EIP copy in the "locker/shelter".
No, Mylio cannot use/show EIP, which is OK for me, they are anyhow just backups in case there might be a database issue. Exported TIFFs/JPEGs of edited RAWs are stored together in the same folder inside my photo library drive, and shown staggered inside Mylio (= I have a visual representation of my edits in Mylio).
Best
CV
Hi Christian,
The EIP is a zip file containing the raw file and the edit files (you can change the extension to .zip and open it with any unzipper). Mylio cannot use the EIP, I assume. Do you now keep both the raw and the EIP file?
Cheers,
BeO
Hi BeO,
I am doing now both, exporting (in catalog mode) as EIP (= keeping the edits) and doing the "_display" for the edit exports. Works nicely so far.
Thank you very much for pointing me to it!
Best
CV
From that linked article and video, the representative file for display must have an appendix "_display", e.g. image001_display.jpg (which can easily be done in an export recipe), then it is automatically stacked with image001.raw.
At one time there was a tool that did exactly this, using a Capture One Session as an external editor for Apple Aperture- The Capture One Export was imported into Aperture as the next version.
The tool has disappeared as Apple Aperture has long since disappeared as well.
Hi Christian,
Q1
Well, edits/adjustments need to be stored somewhere. If you use Photoshop as an image editor for example, the edits are stored in the PSD or TIFF file. If you use DXO Photolab, the edits are stored in an .dop file in the same folder as the image, if you use C1 then the edits are stored in a .cos file but in a sub folder of the image folder. And you need a C1 session. This does not automatically disqualify C1 as an editor or "external editor", although it certainly was not a design goal. I think neither Photoshop nor DXO consider themselves as "external editors" either, but it is a bit less complex than with C1.
Q2
The point I was trying to make is that you edit your raw in C1, the edit instructions (tool values, layers, styles etc.) are stored in the .cos / .comask file, then you export to a jpg which will look identically to the preview in C1 including your edits. Then, "import" or whatever needs to be done in your DAM (e.g. Mylio) and show it instead of your raw file, the raw and jpg are stacked.
Let me refer you to an article about Mylio:
https://photofocus.com/software/stack-edits-with-originals-in-mylio-photos/
which I haven't fully read yet but it looks promising.
Presets in C1 and copy/apply are possible, not sure I fully understood your question though.
Keep asking, I will find some time to answer.
Thank you both, I learn a lot, and it also helps me to optimize my workflow.
I have already used lots of your time, and if it is OK, I would just like to ask 2 - perhaps stupid - questions, to be sure that I am not accidentally missing something.
Q1
Regarding your feedback to point #1, BeO, I now much better understand, thank you. For explanation, what I factually want to do is to use CO as an external editor by another application. Similar to the "edit with"/"open with" in CO itself. But the other direction. Being inside Mylio (or another software), selecting a picture there, and an "open with" allows to hand-over to CO for doing edits. My impression is that this is just not how CO is designed, that it simply can be used in that way, and that this is no specific Mylio issue.
So, is my assumption right, that CO can generally not be used as an "external editor" for pictures by other applications?
Q2
As I recall, it has always been clear that working with either a library or sessions is a very fundamental decision, as both follow different logics. Your feedback provided me with clarity of what this means in detail, thank you.
In a case where I am very happy with the edits I have done in a session (and stored only with the session), but I would like to keep the look also in a library beyond the (temporary) session ... is there a way to achieve this? (=copy&paste the edits from a picture in the session to the same item representing the same picture in the library)
For a series of pictures being edited the same way, I could create a preset and apply this in the library to the same files. Clear. But for individual edits, file by file?
The simple answer might be "no way!", just want to be sure.
Best
Christian
You are right, Ian, thanks.
369260519517
To clarify... edits (in a session workflow) are ONLY stored in the subfolders you mentioned and not in .cosessiondb file (unlike a catalog workflow, where the are only stored in the catalog database, and not in the subfolders).
Ian
It does not work on Windows with v16 because they killed this function (in v16) and don't see a priority to bring it back. I have an open ticket for 6 months now (since I detected this regression defect).
Hi Christian,
You're welcome.
Regarding point 1)
"pictures are opened for editing in the CO session"
Not sure where exactly you see this in C1, but if you use the library tool in a session and go to a "system folder", the library tool in a session is actually reflecting your systems folder at real time (that is different to a C1 catalog), then this C1 session will show you all images in that folder.
Regarding point 2)
"any CO edits are stored in the CO session only,"
Edits to images are actually not stored in the session (i.e. cosessiondb file) but in small files under the CaptureOne sub folder "Settingsxxx". Maybe they are stored in the cosessiondb file too, but the point is you can throw away this file and the edits are still in the .cos and .comask files, waiting for any new session to be picked up...
"the corresponding catalogue representation is not updated"
Here I think you mean the Mylio catalog? (but it is not automatically updated/synced in a C1 catalog either). That is normal, usually catalog software (aka DAM) shows the small jpg preview embedded in the raw file. C1 adjustment instructions can only be read by C1.
What some DAM applications offer is to stack (group) image files, e.g. image001.raw and image001.jpg, and show the jpg as a representative of that stack. Most DAM apps require the jpg to be in the same folder as the raw file.
Whether or not this is possible in Mylio I don't know. If it is possible, then you could create an export recipe in C1 which exports your image to the same folder, e.g. with the QuickProof format (which is blazingly fast because it is basically the C1 preview image in jpg format). The downside is that you also see the jpg in the C1 session, unless you set the Global Filter in the View menu to exclude jpgs. (But be aware, as soon as you show them in the C1 session it will create .cos files, preview files etc.)
Hi BeO,
Checked it, d&d (still) doesn't work on Windows 10.
I found a bit of a workaround. When first opening a (new) session in CO (not the library), and then I do an "open with" to CO out of Mylio ... pictures are opened for editing in the CO session, which is good!
But ...
Anyhow, thank you for investing the time and providing the background, BeO. Really appreciated.
Ok.
If you were on Mac, you could try to drag&drop your selected images from Mylio to a C1 session, passing "links" to the image files to C1 thus enabling C1 to edit them. However, I don't know if Mylio supports this (not every catalog software does).
The C1 Windows version supported the drop action from external apps to a session album in the past but they broke this functionality in version16.x.
https://support.captureone.com/hc/en-us/community/posts/12947780188317-Drag-Drop-files-from-Explorer-or-DAM-onto-a-session-album-no-longer-works-in-v23
Hi BeO, Windows 10.
Which operating system (macOS or Windows) do you have?