How do you edit with Capture One on Mac?
My current workflow with my mac and fujifilm xt30 camera is: I import images from the
camera to the Photos app for storage. I edit with Capture One and
export for storage and sharing.
I noticed that when I have raws in Photos, there is an option to
"Edit with" other applications, like Capture One or Photoshop. However,
when using this option Photos exports the raw .raf file as a .tiff,
which Capture One then doesn't recognize as an xt30 raw image. I need
to first manually export the .raf from Photos, import to Capture One,
export from Capture One, and re-import to Photos.
So I wanted to see how others are working through this- is anyone
else using Photos for keeping and sifting through your pictures and
Capture One for editing? Other recommended workflows? Thanks!
-
To be frank, I don't see any advantage in doing what you're doing. Capture One is a far more powerful editor than Photos, and is a satisfactory asset manager.
As to C1 not recognising a TIFF file as a raw, it's because it's not a raw file. I've never done a test, but my guess would be that a TIFF file is much less capable of recovery of detail than your Fuji raw (.RAF) file. What's more, a TIFF file from one of my Nikon raw files is much larger than the original Nikon raw file!
The answer your final question:
- I import my image files into C1 - as referred files
- Keyword the files as appropriate in C1.
- Edit in C1 - as a minimum, crop and levels for each file.
- On the rare occasion there's a repair that C1 can't handle I use "Edit with" in C1 and do what needs doing in Affinity Photo. I do that maybe 1% of the time.
Hope this helps.
Shane
0 -
Let's use the same language.
- RAWs are not images but data files. Jpg, Tiff… are images.
- Capture One is not an editor but a powerful multiple files converter
- Affinity Photo is an editor but a "single file at the time" converter
Shane Baker said:
"I don't see any advantage in doing what you're doing." — I share that!Shane Baker said:
"On the rare occasion there's a repair that C1 can't handle I use "Edit with" in
C1 and do what needs doing in Affinity Photo. I do that maybe 1% of the time". I share that too!
My Workflow — as I teach it to my students- After a shoot, files are transferred to the desktop — where everything is faster.
- Launch CO and target the RAWs folder and — since RAWs can't be altered…
- Cull your files and apply via sidecar files tweaks of all sorts that are needed to
get to your final rendition. -
a) If the resulting view on the screen is to your liking… do nothing, just enjoy!
b) If more work by an editor is needed, "Edit with" will convert the file to an e-
ditable format of your choice and proceed. — The converted image will be
along side the parent RAW in the folder, opened in the chosen editor, then
you can perform edits and save the image. - Now that it is (almost) all done, transfer the folder to your archive and backup.
From there, more work may be done or conversion to images for publishing. - Only keep Raws files and edited images but none of the converted images as
they can be republished at will at any time with a mouse click.
0 -
"Photos" is usually, I mean by most of Mac users, considered as a DAM. But it is also a RAW converter, in such a way that if you ask "Photos" to open a RAW, it will do it using the Mac RAW converter (which is by far worse than the one of Capture One). Accordingly, if you try to "Edit with...", it will just send to the 'Editor' the image (as Nikon shooter said), and not the RAW to Capture One, i.e. a TIFF. Capture One does the same when you "Edit with...".
So, I can't understand why you use "Photos" rather than Capture One and its catalogue, for instance, unless you have a huge catalogue (above, say, 50,000 images). And in that case, a real DAM would be better than "Photos". I agree, however, that "Photos" is free....
My workflow is just using Capture One from the beginning to the end (except for printing, where Capture One is not that good). I import, process, heal and clone when necessary, and exporting in any format using Capture One.
0 -
Thanks for sharing the logic behind the "Edit With" functionality. Sounds like a feature request to have a "convert with" function then. I like using Photos as the single program that archives all my pictures from various devices (phone, fuji, older cameras). It's integrated well with the apple ecosystem. Wish it were simpler to use Capture One as a raw converter/editor with Photos. I think I'll import my raws directly into Capture One then export results to Photos, letting Capture One be the archive of the raws and Photos for the jpgs. It works, but just adds another folder/program to care about for backing up etc.
0 -
Gidday Dylan
Your comment "I think I'll import my raws directly into Capture One then export results to Photos, letting Capture One be the archive of the raws and Photos for the jpgs" still has me a little puzzled.
Unless you're doing a heavy cull at the front of your process, it means (as I understand your process) that you'll have masses of duplicated files - as raw and as JPEG. Using a recipe in C1 takes a moment to export to JPEG (or pretty much any other format), so I only convert a raw if I have a particular need (email, blog, whatever).
Also, while I'd be the first to agree that the C1 DAM could be improved, I can still find in a minute or two that image of my wife in Berlin or my great grandfather or a drone shot at a particular location or all my shots made with my iPhone 8.
It's your gear so of course you must do what works best for you, but I can't help but feel you're doing it the hard way. :-)
Anyway - all the best.
Shane
0 -
Sorry for re-opening this thread.
As an Apple user myself I can see where Dylan is coming from and why he would want to still use Photos at the beginning or the end of the workflow.
For one I think it's a major gap that CaptureOne doesnt have a cloud service nowadays, and to that matter a mobile app. One big advantage of Photos (or Lightroom) is that you always have access to all your photos, you don't have to be at your desktop.
Secondly, and less important but still nice, is that Photos does a good job on personalization, creating memories and albums based on location/time/people etc...It's amazing how many old photos I've found myself looking back because they were prompted to me that I would have never taken a look otherwise.
Ok so now on workflow. I am still trying to find the best workflow for myself since I just started using CaptureOne, but please share any feedback:
- Import onto CaptureOne; folder on external SSD that I can move between workstations and keeps me "mobile" (backup onto iCloud Drive)
- Cull and tag/rate all "keepers"
- Edit (at least crop/levels etc)
- Personalized recipe that exports from CaptureOne onto a folder on my desktop the full quality JPG
- Script that is monitoring that folder and automatically imports onto Photos app to a folder called "CaptureOne"
- From there I share with family/friends/instagram etc etc
I still don't have access to all photos but i also don't need the "rejected" ones.
The only flaw here is that if I am traveling just with my iPad there is nothing I can do and in that situation is where I see myself keeping my Mobile subscription to Lightroom.
Thoughts?
0 -
I agree with Paulo and Dylan. I have seen software programs come and go over the years. I know several users that have created their own servers and placed a database on their servers for the best way to keep RAW information organized. I have also seen breaks with updates to software programs that disrupted workflows that was working great for the user. Starting from Apple Photos is not such a bad way to score a workflow that is not going to just change on an update. Well not most of the time anyway, I have seen some Photo editing software declare bankruptcy. What would be the promise of converting all of that info that is on your computer which the images are relying on for organization The only way I I know that you would never have to do that is to build a database for .DNG and .TIFF files on a database and open the files from your own database that you have invented for yourself for search options in your own operating system. Am I correct?
0
Post is closed for comments.
Comments
7 comments