See soon to be released tip … Pete
?? can you expand?
Hi to all still Aperture users.I'm getting tired waiting for Joseph to publish my tip about apHUB, which I've submitted some weeks ago. I've inititally posted this thread as a teaser but removed the initial post, when Joseph promised to release the tip because I didn't want to spoil the news.It is sad to read posts every day from people switching from Aperture, because they see no future in further using it. Maybe they had made a different choice, if they had known about apHUB before. For me it is the best thing since the invention of sliced bred and I have no more intention to move my Aperture library to anything else since I use apHUB. But I am biased because I made apHUB.I won't go into the details about what apHUB is and whether it is good for you. If you are interested, head over to www.aphub.de, watch the videos, read the intro or manuals and if you really want to test it, register as a beta-tester.Or wait for Joseph to release my tip.Pete
Interesting. As one who has not yet migrated to an Aperture replacement, I look forward to reading the published tip. I have been cleaning up my library and studying alternatives–Lightroom, Capture 1, Perfect Photo Suite 9. (Been reading manuals and watching tutorials).
Perhaps this is the right place to ask this question. If folks don’t mind saying, WHICH alternative are Aperture users choosing. Lightroom, C1 ,On1 other? If you choose to answer and have an extra moment, perhaps a word on why you made your selection and how that choice is working for you.
I tried them all and none did work for me.Capture One nice for edits but DAM is very basic. Read my comment at https://photoapps.expert/comment/30676#comment-30676Lightroom: Terrible UI, no Raw+Jpeg pairs support.On One: No DAM at all.Maybe there will something coming from Serif, the maker from Affinity Photo.But it must be very good to convince me to switch from my current Aperture, apHUB, Capture One workflow.Pete
Thanks, Pete. The work-flow you have developed with “scripts” is very impressive. What happens when a future operating system “obsoletes” Aperture and users can’t afford a 2nd computer to use for Aperture? Your work-flow does require an Operating System that does not finally “obsolete” Aperture–is that right? In other words, your work flow requires Aperture to be able to run?
No interest at all depending Aperture as part of the hub.
I spent a casual 2 years looking for a DAM replacement for Aperture. One thing I learned is neither Aperture or iPhoto are all that reliable a database. I started by making sure Aperture was a pristine as possible with the tools provided. Missing images 0, reprocessed all files, made sure all filed images were reported as imported, ran all the maintenance scripts.
Each time I imported either Aperture’s library or imported direct from the folders Aperture was referencing, I ended up with more images than Aperture could account for. iPhoto was worst. But Aperture was missing somewhere in the neighborhood of a 1,000 images that it should have picked up. Digging into some of the missing images I recognized all of them and while they should have been in Aperture, they were not. Anyone who’s used Aperture in referenced mode knows images go missing all the time.
Not to mention the fact that depending on an unsupported app for DAM raises some concerns in my mind.
I think this would be an OK way to carry on with Aperture until you decide where to move to or to wait for Photos 2.0 and see if it would be enough for you. However, I have to agree with Ray, the Aperture database is outdated and now unsupported and I am afraid the roundtrip solution with scripts may eventually lead you to a number of problems.
Good luck with the project. It is a shame Apple does not appreciate how good user interface and program they had and how faithful we Aperture users are/were.