This ditching of 32 bit support is going to keep me from adopting new the new OS for as long as possible. I have a significant number of old apps critical to various professional workflows that do critical tasks but that are no longer supported. I've never appreciated Apple's periodic enforced software obsolescence policies but this round is going to be especially painful.
DxO’s claim to fame is their camera/lens database and how they use that for specialized image corrections. Their perspective correction module isn’t bad either. It’s capable, and I sometimes use it for editing individual images, particularly architecture. They also have a series of “film packs” that are essentially filters to make your image look like various analog film types if you’re into that. It’s been a generation or two since I’ve tried using it for library management, but at the time it was more awkward to use than Aperture for sure.Hi, does anybody know of a photo editing suite that is pretty much an easy one click import, (retaining structure and notes, metatdata etc), from Aperture that isn't Photos.
I don't need anything that powerful at all really and don't mind a little bit of cost.
Thanks.
DX O Optics Pro looks nice and cheap....
I’ll admit, I’m still confounded by the sessions versus catalog split. I went catalogs. What made you choose sessions? Best I could figure from the vague documentation was that sessions were tuned for tethered capture in studio?i switched to Capture One (v10) - initially it wasn't great - didn't really know whether to go with Catalog's or Sessions; workflow not as straightforward as Aperture, but most of the fundamentals in the software were good. Now CO is on to version 12 - am using Sessions and used to the workflow, it's been very very good. RAW processing outstanding; very fast; professional UI etc etc. Photographers like Thorsten van Overgaard have published some excellent training materials for CO as well, so the eco-system is expanding and seems vibrant - plug-ins etc now available.
Did you check the Apple support document re the Aperture announcement? it has instructions on how to move to Adobe's Lightroom Classic. It has an Aperture import plugin. Some metadata will have issues, and you might want to use keyword hierarchies instead of Aperture's album/folder setup as this will impart the same organizational info, but be much more portable into any other subsequent DAM program. Not sure what "notes" are in Aperture; don't remember those.Hi, does anybody know of a photo editing suite that is pretty much an easy one click import, (retaining structure and notes, metatdata etc), from Aperture that isn't Photos.
I don't need anything that powerful at all really and don't mind a little bit of cost.
Thanks.
DX O Optics Pro looks nice and cheap....
Such ********. Why do they support final cut but not aperture? Really really annoying
I’m pretty sure Apple has burned that bridge. I’d be surprised if Apple could convince professional photographers to trust them with their work again.I loved Aperture but Lightroom just got too far ahead and Apple needed to reboot it, perhaps with a professional app based on Photos but with more in depth tools.
My guess is that Apple has plans for Photos as a modular and scaleable DAM/photo editor to replace Aperture. Like Final Cut, it’s always been a long term plan, starting with the basics and iterating it up from there.
The Photos app already works exceptionally well for those ranging from non photographers to amateur photographers to maybe even prosumers. It’s when you get to professionals that it breaks down due to the lack of a workflow capable of handling thousands of photos per shoot and archiving.
But the foundation is there. With non destructive editing extensions, you can perform very sophisticated edits in the Photos app. It needs a way to separate your personal photos from your work.
I think that a second Photos app with a different UI could be built that has complex editing tools built in but that runs on the same underlying infrastructure. The fact that they’re ending support for Aperture after Mojave gives me a bit of hope that we might see the next step up for the Photos app in the next version of macOS.
I think that a second Photos app with a different UI could be built that has complex editing tools built in but that runs on the same underlying infrastructure. The fact that they’re ending support for Aperture after Mojave gives me a bit of hope that we might see the next step up for the Photos app in the next version of macOS.
I've still not forgiven Apple for pulling the plug on one of the best apps they've created, especially since there's just no good alternatives…
(Hoping that Affinity eventually will create a descent DAM but that does not let Apple off the hook.)
Such ********. Why do they support final cut but not aperture? Really really annoying
Apple and Nikon killed my love of taking pictures.
I’ll admit, I’m still confounded by the sessions versus catalog split. I went catalogs. What made you choose sessions? Best I could figure from the vague documentation was that sessions were tuned for tethered capture in studio?
My guess is that Apple has plans for Photos as a modular and scaleable DAM/photo editor to replace Aperture. Like Final Cut, it’s always been a long term plan, starting with the basics and iterating it up from there.
The Photos app already works exceptionally well for those ranging from non photographers to amateur photographers to maybe even prosumers. It’s when you get to professionals that it breaks down due to the lack of a workflow capable of handling thousands of photos per shoot and archiving.
But the foundation is there. With non destructive editing extensions, you can perform very sophisticated edits in the Photos app. It needs a way to separate your personal photos from your work.
I think that a second Photos app with a different UI could be built that has complex editing tools built in but that runs on the same underlying infrastructure. The fact that they’re ending support for Aperture after Mojave gives me a bit of hope that we might see the next step up for the Photos app in the next version of macOS.
Because they they have sold two million copies of Final Cut Pro X and they sold no where near that many of Aperture.
Thanks for the pointer. I think I’m still the catalog type, Aperture sold me on that workflow. I do find the Capture One catalogs are limited in their size though, and I have to break them up into a collection of smaller catalogs— which Defeats the purpose to some extent. Sessions would require me to remember which session a give image was in— it think that works well for events, but not when you visit a favorite site multiple times...There were a few factors: - catalogs were less stable (i think size of library was an issue); scaleability (i have 150k+ photos, one catalog gets quite large and creates issues for backups, Time Machine backs up entire Catalog, even with one small edit; I used sessions to record events, holidays etc and it provided a natural division into smaller file groupings); my photos are stored in a Finder folder hierarchy so no software lock-in, future proofing access to the underlying photos. I use a folder naming convention Job# YYYY-MM-DD EventName/description so very easy to recall/sort. Inside main folder were Capture, Selects, Output, Trash folders set up by C1P - which seemed logical, whether to not it was a tethered/studio shoot or out in the field with subsequent import
An article on topic worth reading...
https://www.dtcommercialphoto.com/catalogs-vs-sessions-epic-battle-times/
If you think Aperture is a pro application, you are not a pro.
I've never used it to be honest, but I thought it was. Same for Final Cut.