I wonder in the C1 folks have already decided to do or not do plugins in the future. I wonder what they are saying to their user community about the future.
Not at all - Using it in a single catalog mode and not flagging, organizing a more complex set, etc, etc is just right for your workflow.
I work with someone who has 30 plus collections in each of 5 catalogs, publish to Smugmug, Facebook, and uses the hell out of the flag/star system to cull thousands of travel images before returning to a desktop system - repeat the cull of 20 to 40 thousand images from a single tour 3-5 times a year. Almost 200 pins on a world map - you get the idea.
I have 1 catalog with perhaps 2500 images for my entire life. She has 150,000 and seems to know precisely where everything needs to be in all the various collections. I'm thinking somewhere between us is the average
I'll stick with Aperture until it's deprecated, it does everything I need it to.
I'll stick with Aperture until it's deprecated, it does everything I need it to.
I shoot Canon, and right now, I am seriously considering going with an all-Canon workflow. That would mean replacing Aperture with Canon's Digital Photo Professional, and replacing my Epson R1900 ink jet printer for a Canon model, probably the Pro-10.
After thinking about it for a while, this is a good solution for me. I'm impressed with DPP 4.0, and especially that it uses all the information from my Canon .CR2 files to produce very high quality images. I can also easily apply picture styles to RAW images (could not do that with Aperture!), and it has lens correction data available (also not available in Aperture). It's also free, and you don't have to buy a subscription. The only downside is that I will miss the integration into the Apple ecosystem, which was one of the main reasons I was using Aperture in the first place. It remains to be seen how I can connect the images in DPP into Apple's new Photo app so they can be shared via iCloud, etc. It may be possible through a proper folder setup, but I'm just not sure yet.
Although I use Aperture (referenced), all shots worthy of distribution are sized and imported into a managed iPhoto library. iPhoto, or Photos in the future, supports iOS sync's, web distribution, using the library in multiple Mac's, books, etc. That approach would give you the integration you're looking for with one extra step.
How does DDP invoke a plugin (like Aperture or LR), send the plugin a TIF or PSD file, receive the processed image back from the plugin and store it along side the raw original?
Can you rephrase this? I can't follow.
Thanks. I know all this. What I was referring to was a more automated approach to the import step. Right now, what I'm conceiving is to do all the sorting, edits, resizing, etc. in DPP, manually exporting those images in a selected format (JPG, Raw, etc.), then manually importing the images into the new Photos app. I want to exchange the word "manually" in the previous sentence to "automatically" and do it in one step.
How do you move images from your reference Aperture library into your managed iPhoto library? Are you using the Unified Library feature?.
Good chance it will run just fine on the next few gens of Macs and OS.
Unless there's some shiny new feature you gotta have, why not
I shoot Canon, and right now, I am seriously considering going with an all-Canon workflow. That would mean replacing Aperture with Canon's Digital Photo Professional, and replacing my Epson R1900 ink jet printer for a Canon model, probably the Pro-10.
After thinking about it for a while, this is a good solution for me. I'm impressed with DPP 4.0, and especially that it uses all the information from my Canon .CR2 files to produce very high quality images. I can also easily apply picture styles to RAW images (could not do that with Aperture!), and it has lens correction data available (also not available in Aperture). It's also free, and you don't have to buy a subscription. The only downside is that I will miss the integration into the Apple ecosystem, which was one of the main reasons I was using Aperture in the first place. It remains to be seen how I can connect the images in DPP into Apple's new Photo app so they can be shared via iCloud, etc. It may be possible through a proper folder setup, but I'm just not sure yet.
With digital asset manager (DAM) and editor programs like Apple Aperture and Adobe Lightroom, the vendors know that they can not and will not, code into their apps all the filters and effects that users will need and want. Hence, both Aperture and LR users can purchase plugin programs such as Photoshop, the Nik Collection, Topaz Labs filters, OnOneSoftware's Perfect Photo Suite....etc.
In Aperture or LR you basically send a TIF or PSD version of the image to the selected plugin app. In that app you do the editing you want and save the image. The plugin app brings the edited image back to Aperture or LR where the edited version is stored alongside the original version.
So the question is...how to have such an integrated workflow from DPP to a plugin app and bring the file back to DPP? I think this has to be a manual process. DPP does not seem to know plugins exist or how to invoke them. I think the same limitation applies to Nikon's CaptureNX program and many others. They don't seem to have a "larger picture" in mind. Instead of a wide-angle pano, they are doing narrow FOV macro.
This is already an issue. Not sure if a legacy raw engine (non updated) is present in macOS. But it’s evident Aperture doesn’t have access to the current raw engine or updates for modern camera raw files.2. RAW support - as this is handled by OSX it will reply on Apple not making the RAW support incompatible with legacy Aperture
It wasn't as much of an issue five years ago... which is when the post you replied to was made.This is already an issue. Not sure if a legacy raw engine (non updated) is present in macOS. But it’s evident Aperture doesn’t have access to the current raw engine or updates for modern camera raw files.
Oh wow. My first necro reply. Thanks for catching that.It wasn't as much of an issue five years ago... which is when the post you replied to was made.
I feel like WabashSphinx should have either made a new thread or could have joined one of the numerous, more recent posts about Aperture instead of reviving this thread...
It wasn't as much of an issue five years ago... which is when the post you replied to was made.
I feel like WabashSphinx should have either made a new thread or could have joined one of the numerous, more recent posts about Aperture instead of reviving this thread...