captureone and aperture workflow anyone?

[dchalfon]

Advertisement (gone after registration)

i've been using aperture for quite some time, but sometimes the raw files do not seem to have as good results as the ones processed with captureone.

 

but all my dngs and jpgs are already in aperture, with all the tagging + ipad and flickr integration, so i don't want to switch. i just want to use captureone as my raw processor and aperture for everything else.

 

should i keep the dngs in captureone and export jpg for aperture? any other suggestions of workflow?

[nggalai]

Morning,

 

as Aperture can’t deal with CaptureOne’s processing information, you basically have two approaches to keep on using Aperture for your image management needs:

 

1) Keep DNG in Aperture, open with CaptureOne, stack processed TIFF/JPEG file with DNG original.

 

In this case, you’ll keep your workflow pretty much as-is with the exception of stacking the final CaptureOne export with the DNG original. If you “pick” that processed version inside Aperture this will be the one ending up on your iPad, flickr etc.

 

Advantage is you don’t have to touch your backup scheme, and can keep on using Aperture for those so-so shots that won’t benefit from intensive processing in CaptureOne. Approach would be to do your “common” shots in Aperture and only process those that you think will look better through CaptureOne, then stack the exported, processed version, keeping metadata in sync. Disadvantage is you’ll pretty much have all your images in double in your library should you end up preferring CaptureOne’s results more than not which can be confusing and a problem if you use smaller SSD or the like.

 

2) Store DNG in the file system, process in CaptureOne, import processed TIFF/JPEG file in Aperture.

 

Advantage is you won’t have double images in your Aperture library and thus less chance the wrong version ends up on either iPad or flickr. In this case, you’d copy the images from the SD card using CaptureOne, process all images in CaptureOne, then export all of them to either TIFF or JPEG, then import the processed versions to the Aperture library. Disadvantage is your original DNGs won’t have any of the metadata you later add in Aperture (say, keywords) and backup/recovery is more complicated as you’ll need to keep track of where you keep the originals and their development settings.

 

 

Personally, I’d go with 1) if I wanted CaptureOne for individual shots, not per default, or if I was heavily vested in Aperture’s image management features. I’d go with 2) if CaptureOne was supposed to be my new default RAW processor but couldn’t ditch Aperture.

 

I was in a similar situation a while ago, just with Lightroom instead of Aperture. In the end, I kept my “old” images in Lightroom and made a clear break with the new ones, using MediaPro for media management with my “new” images only. i.e. I didn’t try to move my whole library to MediaPro/CaptureOne, but built up a fresh library with new photos only.

 

Cheers,

-Sascha

[dchalfon]

this is why i am considering the move...

 

the images are print screens from what i have in each app:

 

aperture 3

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

and c1

[Tinchohs]

I use Aperture myself. I'm surprised at the difference of the two images. Do you consistently get such differences? I at times work with Lightroom and the raw processing differences with Aperture are not as visible as what you show. Have you tried having someone else open that file in Aperture? Are the results the same? Thanks.

[esquire53]

maybe you could provide the DNG files.

looks like some pre sets are far off maybe?

[jaapv]

Positively meant: looking through your Flickr stream, I think there is quite some gain to be had from brushing up your processing technique. The results are quite uneven, and that is not due to the processing software.