The Long Goodbye to Aperture and the Start of a New Adventure with Capture One Pro 8
This article originally appeared on Lee’s Photography Blog.
Well, we finally got the confirmation recently that Photos.app from Apple would not be any kind of new Aperture; it’s aimed squarely at iPhoto users and a lot of them might be unsure if it’s even fit for purpose for some of their workflows.
Apple, it would seem, is no longer interested in real pro software, and prefers to cater for a kind of “beige” demographic.
Quite a few apologists/optimists argue that it's still early days, and maybe with upgrades more features will be added. All well and good, but I for one do not want to dedicate more time than I have to learning new software, and I don’t want to start using several things, incorporating a bunch of temporary workarounds, with the hopes that I can ditch them later.
I have been trying Lightroom but I just don’t want to go there; the interface seems wrong and perhaps a little out of date, furthermore I don’t want to aid Adobe in its monopolising of all things creative.
So I have started playing with Capture One Pro 8 and after an initial “whoah! That looks complicated!” I am starting to really like it; aesthetically (to a degree it follows Apple’s new “flat” GUI, in terms of looks), but more importantly it just is so capable… it seems to surpass Lightroom in so many ways; seen from my experimenting, and also from reading what other people say. And when I look at Aperture now, it looks like a relic—a sketched-out beta!
One issue is Capture One is way over-priced, especially these days, and they are certainly missing out on a lot of possible clients because most will just blindly go to Lightroom once they compare prices.
Right now I will keep using Aperture because it is easy to have Capture use its library, so I can experiment and learn on the same images in Capture one that I have to process quickly for clients in Aperture.
Editor's note: This final statement about letting Capture One use Aperture's library prompted me to reach out to Lee to expand on this option. He's written a post about it, which will go live later this week!