![]() ![]() And after almost two years since Photos' initial roll-out as a part of Apple's Yosemite OS upgrade, I'm pretty disappointed by the lack of progress so far. Terence wrote: "Photos may get better, but do you really think it will ever get feature parity with Aperture?" But of course, I can't count on that forever. And, although I also currently have unlimited Amazon Prime storage, plus a commercial SmugMug account for client-delivery, I want an OS-integrated cloud solution that my GF (who has limited technical knowledge and only takes iPhone photos) can also use.Īll that said, it seems Apple is secretly attempting to maintain some modicum of Aperture compatibility due to the Sierra release notes mention, and as long as it still works in Sierra, I guess I'll keep using it. Google Drive reportedly compresses your files. Among the other cloud services I've used/continue to use: I canceled my iDrive account last Xmas. We own all-macOS desktops, laptops, and iOS devices, so it makes sense. I mainly also want to simply my life and have decided to commit to Apple's iCloud Drive for primary cloud storage. Since Apple has decided that Photos is a key part of their product strategy, its tight integration with the OS is likely a plus for speed, stability, and continued development, plus, I assume its feature set will eventually improve. Only Aperture (and Capture NX-D) showed the camera's actual focus-point (C1 has its focus-mask, but it's not quite the same thing). Of course, Aperture was my favorite, and Imagenomic's Portraiture for Aperture was my most-used plug-in (I think it's probably the best skin-smoothing software available). ![]() Here's some of the photo apps I also own licenses to (with the exception of C1): I already own almost every third-party Photos extension available.īelieve me, this was a hard-fought decision.Capture One Pro doesn't accept plug-ins.Here's a few of the reasons I'm considering the move to Photos: Last night, I did my first edit with Photos, and it actually wasn't that bad. But after more than two years of hemming and hawing after Apple's EOL announcement of Aperture, I haven't been too keen on any of my other options. Why do I want to move to a less-capable photo-editor/DAM? Well, I don't, really. Note that the edge-sharpness on the Nikkor 14mm is nothing to write home about to begin with. A cityscape shot with a Nikon D3s + AF Nikkor 14mm f/2.8D was transformed by DxO with truly impressive results (though not easily seen in this photo, fine detail in the buildings were greatly improved). And DxO's camera- and lens-specific profiles have produced the best images from my Nikon gear of any RAW developer I've tried. One plus is that Photo Mechanic is wicked-fast and is AP-IPTC compliant. Ingest and manually catalog using the Finder with Photo Mechanic. I've tried the C1 demo, but am still far from proficient with the app, and am not looking forward to the learning curve. Since the DAM component is almost as important as the editing component, Media Pro remains a key consideration. Media Pro SE, it its former incarnations was less glowingly received. C1 has excellent colorimetry, especially for flesh-tones and a strong feature-set. ![]() Happily, C1 has launched a brand new point-version of C1 where at least one reviewer states that it's now significantly faster than LR. Okay, sorry about that last one.Īnyone else using Aperture 3.6 on recent-generation iMacs in Sierra 10.12.3?Īgain, I've been wrestling with this dilemma since 2014. On the plus side, Photos is really beautiful to look at, but the disappearance of keyboard shortcuts hinders those in a hurry to get their work done. ![]() Also, pressing the 'Z' key no longer zooms-in to 100% no matter where the slider is set (it did in El Capitan). One really poor implementation with Photos' defaults: The lack of being able to set a default aspect ratio when cropping is really unforgivable, Apple, even in a consumer app (setting "freeform" as the default will only solicit increasingly horrible cropping decisions by neophyte photographers). Since Aperture seems to be running without any noticeable anomalies (thumbnails are correct, full-screen toggling works, etc.), I may forstall my conversion to Photos. I haven't yet tried opening any libraries created in earlier OSs to see if the metadata bug still crashes 10.12.3. Later, I opened Aperture and imported some files from its internal SSD. I re-downloaded and opened Aperture 3.6 and it crashed during an SD-card import. I just installed Sierra 10.12.3 on my late-2015 5K Core i7 iMac (40GB/500GB) with no other apps installed. Since a Google searching the above terms turns up nothing, I thought I d report what I've observed so far: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |