Retroactive is discontinued?! Wish I'd known that before I upgraded! I've been using Aperture forever via RetroA. Guess I'll hold on and see what the Pixelmator aquisition brings although I'm not keen for another subscription and that seems the way of the world these days.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Aperture, how I miss thee - is Apple still listening?
- Thread starter vjl323
- Start date
- Sort by reaction score
They're not advancing iPadOS, they're stripping macOS. Look at the recent debacle where macOS couldn't reliably use PCI-based storage on Mac Pro systems - the likely culprit looks to be the new mass storage architecture and mount timing, which has been homogenised to macOS from iPadOS. The entire Sonoma release was effectively broken.
I was new to Mac shortly before iPhoto became Photos. I hated the new one. I couldn't even buy Aperture then. But got a copy from somewhere to try it. What I of course deleted later. I am not so into photo editing anyway.
I remember when Affinity photo came out and everyone was so excited about that as alternative for Aperture and Photo Shop. I didn't find a single mention in this thread.
I only have Darkroom an Infltr because I got them for free in TestFlight. Don't know if those are even real photo editing apps for Pros.
What about Gimp? I have installed it since forever but somehow never use it. It's also not mentioned here. But should do anything for free. Why does nobody like it?
I remember when Affinity photo came out and everyone was so excited about that as alternative for Aperture and Photo Shop. I didn't find a single mention in this thread.
I only have Darkroom an Infltr because I got them for free in TestFlight. Don't know if those are even real photo editing apps for Pros.
What about Gimp? I have installed it since forever but somehow never use it. It's also not mentioned here. But should do anything for free. Why does nobody like it?
I just sent them a feature request to release the old version for free and only convert it to 64bit and Apple Silicon.
Retroactive no longer works on my M3 MBP using Sequoia. Pretty sure I had it installed previous to the upgrade.
Last edited:
I stuck with Mojave for ages mainly for Aperture and iPhoto, a great combination. And I could use external editors if needed. My wife still uses Mojave, for iPhoto and iTunes. And Firefox ESR, but eventually she'll have to upgrade.
I upgraded yesterday, to Sonoma. My phone use .heic images and hevc videos, and it was just too much hassle not being able to use them in iPhoto.
I had tried Photos in Monterey, didn't use it much but just tested all images were transfered ok from iPhoto library, and I got the impression I could use external editors by "dragging" images from Photos to, say, GraphicConverter.
But in Sonoma I can't find ANY way to edit images from Photos without an automatic conversion to .tiff, and when I try to "drag" to another app, the images are sometimes automagically and randomly (?) converted to jpeg first! Either way I lose metadata or quality. I want to use an external editor to edit the original file, is that impossible or am I just a Photos noob?
I have Pixelmator Pro (Photos converts to .tiff), Affinity (Photos converts to .tiff) if I open in external editor.
If I "drag" an image from Photos to Affinity or Pixelmator Pro I sometimes get the full image opened in .heic. or jpg, sometimes I get a lower resolution image opened in .jpg. Same camera, same album. I'm bewildered.
Anyway, If they could integrate Pixelmator into Photos it might work out... Photomator seems to be interesting, but I haven't tried it yet, it's expensive (already paid for Pixelmator Pro) and I'm not sure how it integrates with photos.library.
I upgraded yesterday, to Sonoma. My phone use .heic images and hevc videos, and it was just too much hassle not being able to use them in iPhoto.
I had tried Photos in Monterey, didn't use it much but just tested all images were transfered ok from iPhoto library, and I got the impression I could use external editors by "dragging" images from Photos to, say, GraphicConverter.
But in Sonoma I can't find ANY way to edit images from Photos without an automatic conversion to .tiff, and when I try to "drag" to another app, the images are sometimes automagically and randomly (?) converted to jpeg first! Either way I lose metadata or quality. I want to use an external editor to edit the original file, is that impossible or am I just a Photos noob?
I have Pixelmator Pro (Photos converts to .tiff), Affinity (Photos converts to .tiff) if I open in external editor.
If I "drag" an image from Photos to Affinity or Pixelmator Pro I sometimes get the full image opened in .heic. or jpg, sometimes I get a lower resolution image opened in .jpg. Same camera, same album. I'm bewildered.
Anyway, If they could integrate Pixelmator into Photos it might work out... Photomator seems to be interesting, but I haven't tried it yet, it's expensive (already paid for Pixelmator Pro) and I'm not sure how it integrates with photos.library.
Last edited:
Like all the Affinity suite, Affinity Photo feels like a windows app ported to macOS. Almost every feature and element of it, you brush up against metaphorical sharp edges where the designers haven't put effort into polish. In the v2 era, you can't have more than one document window open at once, because Windows doesn't allow it. None of the measurements units boxes label whether they're width or height, you can't edit a vector mask and see what is actually being masked at the same time.
They're apps made by people trying to figure out a way to monetise a file format they invented. What they are not is apps made to be the best possible tools for the task, by people who actually do the task the app is supposed to fulfil.
Anyone who would make a publishing layout app, that doesn't support document-wide layers is unfit to make a DTP app.
In summary, Affinity demonstrated why you wouldn't want a DAM / RAW developer from Affinity.
Does it offer native support for AdobeRGB colour space? That's the first thing to check if it's "for pros".
Like most free / open source software, the people who program GIMP are not UI designers, and like most open source developers, they're generally quite defensive / possessive of their (often uninformed) UI choices. Attempting to suggedt better solutions is usually met with "get the source and fix it yourself".
GIMP, lke Blender, isn't (or at least hasn't been) a Mac app when used on a Mac.
Yeah, the website says it is discontinued and no longer supported. Last macOS it runs on is macOS 14. It will not run on macOS 15 unless someone forks the project and finds a way to make it work.
For me, migrating off of Aperture will take 6+ months and a lot more money to get drives to use as holding spots for library exports. It's been a process I've been putting off for years since the app still runs great on all but one version of macOS.
So just dealing with some Aperture Strangeness - needed to look at an older shoot managed by Aperture on my Trash Can currently running Monterey with a bunch of RAM. i was getting the dreaded "Unsupported Image Format" dialog box when trying to open pictures., I could usually look at the previews I tried rebuilding the database and permissions but nothing seemed to work. if i tried to open or export I got the dreaded black box. Library is on an Ext.
Then tried on an older MBP that is still on Mojave and Aperture is running natively and everything seems fine albeit a lot slower, am able to open images and export as either Jpgs or full size Originals. On the Trash Can Retroactive is active.
Any Thoughts ?
Cheers.
Then tried on an older MBP that is still on Mojave and Aperture is running natively and everything seems fine albeit a lot slower, am able to open images and export as either Jpgs or full size Originals. On the Trash Can Retroactive is active.
Any Thoughts ?
Cheers.
I was never able to get retroactive modded Aperture to open .nef RAWs on Ventura, with much the same issue. I think it's really only a usable tool for Catalina and possibly Big Sur.
Hey Mattspace - thanks I''ll try on a newer MBP that I think is still on Big Sur, and or try the Mojave partion on my Trash Can.
SO..... As an exercise I tried Importing some Aperture Library's into Capture One and was pleasantly surprised by the results! Only thing really needed was to remove a "Locale.pid" file from the Container package before starting the import there is a handy Alias that point the way.
SO..... As an exercise I tried Importing some Aperture Library's into Capture One and was pleasantly surprised by the results! Only thing really needed was to remove a "Locale.pid" file from the Container package before starting the import there is a handy Alias that point the way.
Last edited:
I told nitro to look at my „Pictures“ folder. So anything that gets added there shows up in Nitro. When I drag new images in to a session folder within „Pictures“, they are there. No need to tell Nitro again.
BTW, the Import feature is on the roadmap. (But no eta)
Affinity is the most capable alternative. The development isn’t as fast as some users would like to. But compare the two companies and the decades of headstart. Still, I neither liked nor trusted the Adobe apps so I went with affinity from the beginning when I had to make the decision. It has been my work horse for several years. No regrets.
Thanks for the info - I just updated my OS so I can now give Nitro a try, I'll also look at Affinity. I've also just discovered I can import Aperture Projects into C1 - so maybe a way forward for me to save all those older Aperture Raw Files.
That one person whose job is to continue monitoring Steve Jobs’ inbox wishes we would stop doing this. 😂
Are these RAW files or jpgs? If they're RAW, I'm curious if the color profiles relate well between Aperture and Capture One. The most significant issue I had was everything imported in from Aperture had a unusually warm white balance. That may have been an error on my part though. This was quite some years ago so I don't remember the specifics.
Hey, you actually CAN split and merge catalogs in Capture One Pro! I just discovered this the other day.
The way you do this is you go into your Library tool panel and right click on any of your collections. You can "Export Collection as Catalog" for anything that counts as a collection: album, smart album, collection by date, recent imports, and so on. Any grouping that's within the Library navigator can be exported like this.
The nice part is that when you do this, it'll also export any metadata associated with the images so your adjustments, tags, and ratings are transferred too.
I have large ongoing projects that are difficult to split off and my catalogs were getting massive. I setup a smart album to group together all images that were older than a certain date that weren't rated highly enough to stay within my active catalog. Every now and then, I export that to a new catalog and choose to include copies of the image in the exported catalog.
Normally, I don't store my source images inside the catalog package, but when I'm creating archive catalogs, I want them all bundled together.
Once I have my exported archives, I may then import them into a larger parent archive catalog.
The one thing that I messed up on the first time doing this was I didn't delete the images in the original catalog before I deleted the smart album I used to group my older images. Removing the smart album before I sent the actual images to the trash caused Capture One to lose the links to all of the images and I couldn't undo it. I had to manually find the images I wanted to delete from my filesystem.
I need to go back and check, The one odd thing i noticed was that within this was one project thats broken up by days. Some days exported as .Nef and others as DNG so yeah confused.