October 2013 - Prospect Park Brooklyn, NYC
From Dave Caolo on TUAW:
Finally, the message delivered by the iPhone 5s camera is clear: Apple is becoming a serious imaging company. They spent a lot of time on that camera. You don't need a point-and-shoot camera anymore. There's no need to find a cable or a memory card reader. This is your camera.
This is why it's so frustrating to serious photographers that on the other side of the serious imaging equation -- ie. serious image processing -- all we're getting from Apple is crickets.
I remember being all excited and diving in to the Aperture 3.0 update just as my wife and I were leaving for a vacation in Paris. We took that vacation in February 2010. The current version of Aperture is 3.4.5. In contrast, Adobe Lightroom version 3.0 was released in June of 2010. Lightroom 5.2 release candidate is available now on Adobe Labs.
On the other hand, during the keynote, Phil Schiller did say that the new camera system is "for the rest of us", though - for the folks that just want to get take a picture, and let their cameraphone do the work.
Feel free to check out the photo in larger sizes and poke around in the metadata over on Flickr.
I don’t know if I’m pointing out something everyone already knows, but one of the features of Aperture 3 that I really like is the ability to run it on my two machines at the same time, using the same license, on the same network. In previous versions, when Aperture was launched, it would detect that the same serial number was already in use on another machine on the network, flash you a dialog box alerting you to this, and quit immediately.
Joseph Linaschke over at ApertureExpert.com has an excellent article that goes over in detail one of my favorite new features of Aperture 3: the ability to not only manage multiple libraries, but to synchronize them as well. If you work with Aperture on both a desktop and a laptop, it is now possible, for instance to have a pared down version of your library that goes on the road with you, and can be synced back to the main library once you’re back home. You can also export any project (or album or book, etc.) as a Library, move it to another machine, and open it up with no fuss. Changes made to the project — including metadata, adjustments, etc. — on either machine are applied when you sync, and Aperture does a great job handling conflicts between the two, allowing you to specify which library’s changes should take precedence. Head on over to the article for more details on how it all works.
Aperture users: Are you using Metadata Presets? If not, you should consider it - they’re really handy for entering metadata on large numbers of images, particularly at the point of import. I have one fairly generic preset that just has my copyright info, country, and name, which I use for everyday shooting, and come up with others depending on the shoot (travel, events, etc). What I realized when the new year rolled around was that my copyright still said “©2009 Simon Abrams. All Rights Reserved.”, and that I had no easy way of changing it, due to Aperture’s woefully spartan interface for managing or editing metadata presets. In Aperture’s current incarnation, all you can do is add, rename or delete a preset; you can’t edit any of the text within it.
So what to do? Well, a little poking around in the Application Support folder (specifically ~/Library/Application Support/Aperture) reveals that Aperture’s metadata presets are (quasi-)conveniently contained in an XML document. Simply opening up the file in your text editor of choice enables you to make changes to the metadata content, save it, and voila, you’re in business. Of course, ideally, you’d be able to make these simple edits in Aperture itself - maybe we can add this to our wishlist for (the increasingly vaporware-ish) Aperture 3.