I like to take low-light photos and have very seldom found the need to use DxO OpticsPro for noise reduction recently.
#CAPTURE ONE PRO 7 PLUGINS ISO#
Having said that, the ability of modern sensors to take pictures at ISO 6400 (or ISO 3200 if you are a pixel-peeking perfectionist) with few noise artifacts, means the need for noise reduction has reduced considerably in the last few years. Noise Reduction in Capture One is reasonable but if you have very noisy images then you will need to reach for something else: either Photo Ninja or DxO OpticsPro in my experience. If anyone has an idea, I’d be glad to hear it. Round-tripping to the OnOne suite from Capture One also has some issues as I have found out: it works for jpgs but not for tiffs and despite support enquiries to both Phase One and OnOne I have not solved this issue. So it remains a round-trip I can’t avoid but it is an infrequent one. However, cloning and healing wasn’t great in Aperture either and I used and still use OnOne for this.
There is new functionality in Capture One v8 but it’s still not close to what you can achieve in Photoshop or OneOne. This was weak in Capture One 7 when I moved over. Double-clicking any slider resets it to its default value. For a proper compare to original, you have to right-click and create a new original version for comparison purposes and then delete it (or not) once done.Ĭapture One’s Exposure and HDR tools with reset buttons highlightedĬlicking and holding the Revert button with Option/Alt resets the tool until you click off. I’ve since learned that you can use the Option key with the Revert button to do a quick backwards compare for each editing tool but this is fiddly and prone to error. I’d much prefer a history tool or a single key ‘compare to original version’ shortcut.
Creating compare versions is possible in Capture One but this is clumsy in my view. Aperture doesn’t have a history tool either but it does have a very handy compare to original version with a single shortcut (‘m’). This is a major miss and a big argument for Lightroom. Hooray! Officially, this new feature is just for Photoshop, but many other apps also work including my beloved Color Efex Pro! No History Tool
Since version 8.1 Capture One supports round-tripping with automatic file re-import from third-party applications. This was for me the biggest stumbling block about moving to Capture One.īut, you will notice the last two paragraphs have been written in the past tense. OK I could export a file to it and use my favourite filters, and maybe the Capture One Clarity slider reduces the need a bit, but this situation was not fantastic, especially as I had to manually import the TIFF file back to Capture One. In particular, I really missed Color Efex Pro 4 from Nik. For the most part it succeeds with this all-in-one approach but there are functions where it is not best of breed (cloning, healing and noise reduction spring to mind).Īs an Aperture user you were almost obliged to use third-party apps to achieve specific results and this led to familiarity and love in some cases. The Phase One philosophy has historically been to do everything in the one program and thus it had no support for third-party plug-ins. So what’s missing? Capture One is/was a Standalone Program Phase One has stated that will now release some major functional upgrades in dot releases rather than waiting for a major new release. As an aside, this also reflects a change in release philosophy. The Yosemite 10.10.3 beta has dashed many of these hopes so my analysis made at the time has been adapted here to focus on why you might not choose Capture One and maybe use something else.Ī more recent consideration in this analysis is that Phase One has introduced a major new feature with its 8.1 release late last year that radically changes its prior ‘standalone’ program stance and in my view addresses one of its biggest disadvantages. At the time there were also quite a few reasons I identified for staying and waiting it out for Photos.app. My initial post on Capture One looked at all the positive reasons I identified for moving to Capture One alongside some of my experiences in using the program from an ex-Aperture user’s perspective.