I am seriously wondering what I am going to use instead of Aperture
Walter,
I mentioned this on another thread and I remain hopeful.
The Apple Developer conference produced a surprise, in that Apple have granted developer access to the Photos database. This has some big implications for Photo software, which has always been able to access certain parts of Photos and run as ‘plugins’. Now, developers will be able to access the database and presumably build more than just a plugin. Whichever way it works out, the crux for Aperture users, is that Photos and Aperture shared libraries to start with and when you open an Aperture library in Photos, it is converted by Apple’s own software and so, all those things that were not available to the likes of Adobe, are available to Photos, it’s just that Apple chose not to use a lot of them, such as keywording, but they’re all still in there.
So the big deal for us Aperture users, is that Aperture’s main man and former lead, Nik Bhatt, looks to be using this newly found access to build DAM features into his RAW Power app, It’s already very similar in style to Aperture and there’s a big demand for a DAM of the same quality (Lr trails badly) so there is hope. It’s obviously a big job so who knows for timing, but I’m hopeful to see something by the spring. Perhaps worth giving him some encouragement?
Thanks for the as always sound advice, I will continue to work on the Freeway 7.1.4 and just go for it. I’m personally not to bothered about upgrading OS for some time I was just hoping to see what 8 has to offer to maybe make work faster and see if it has some new features.
Really not sure what to expect and I update a few large websites about this time every year so was kind of hanging back a bit.
Thanks for your time responding once again Walter.
Anthony
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Talk about upgrade…, can I work just as good on my
new iMac with Mojave OS, using Freeway 7.1.4?
Arne
On 1 Oct 2019, at 16:41, agallagher email@hidden wrote:
Hi Walter
Thanks for the as always sound advice, I will continue to work on the Freeway 7.1.4 and just go for it. I’m personally not to bothered about upgrading OS for some time I was just hoping to see what 8 has to offer to maybe make work faster and see if it has some new features.
Really not sure what to expect and I update a few large websites about this time every year so was kind of hanging back a bit.
Thanks for your time responding once again Walter.
On Oct 1, 2019, at 11:13 AM, Arne Gustafsson email@hidden wrote:
Talk about upgrade…, can I work just as good on my
new iMac with Mojave OS, using Freeway 7.1.4?
Arne
On 1 Oct 2019, at 16:41, agallagher email@hidden wrote:
Hi Walter
Thanks for the as always sound advice, I will continue to work on the Freeway 7.1.4 and just go for it. I’m personally not to bothered about upgrading OS for some time I was just hoping to see what 8 has to offer to maybe make work faster and see if it has some new features.
Really not sure what to expect and I update a few large websites about this time every year so was kind of hanging back a bit.
Thanks for your time responding once again Walter.
I am seriously wondering what I am going to use instead of Aperture, which is similarly marooned, even though it is already 64-bit.
Walter,
my previous message may have been overly hopeful about Aperture’s adjustments still being present in Photos. It seems that Apple have removed that over time. However, I reckon this clever man may have just made a lot of new friends:
To be honest … it could enable Aperture to run for years, unless for some reason Apple decide to block it. It should also be understood though, that Aperture is stuck, for RAW processing, at about 5 years ago. But if you use it essentially as a DAM (which I do) then it should be fine. I remain hopeful that Nik will be able to add DAM features to the excellent RAWPower app and all will be good again.
To be honest … it could enable Aperture to run for years, unless for some reason Apple decide to block it. It should also be understood though, that Aperture is stuck, for RAW processing, at about 5 years ago. But if you use it essentially as a DAM (which I do) then it should be fine. I remain hopeful that Nik will be able to add DAM features to the excellent RAWPower app and all will be good again.
Thanks! I should keep an eye on his blog (I’ve added it to NetNewsWire so I will be). It’s good and bad that this “fix” will allow me to put off deciding on what I want to use a little longer.
When you say Aperture is stuck as far as RAW processing, what do you mean? Is it the cameras that it works with or stuff it does with those files? I presumed it worked with whatever RAW files the OS supports, but since I haven’t upgraded my camera in many years, I haven’t checked. If it’s the other, what do you use to process your files?
Aperture’s RAW support stopped being updated after MacOS 10.12 in 2016. Remember those updates … ‘Digital Camera RAW Compatibility Update’? Well Aperture required those for new cameras to be added.
If you’re camera was supported, then it’s still fine, but if you buy a new one, it won’t be supported and if that’s the case, I’d recommend using Nik Bhatt’s RAWPower, which taps into the MacOS RAW processing, which I personally think is excellent. That is of course, if you are using software other than the manufacturer’s own, which is often absolutely horrible, but usually produces excellent RAW conversion for their own cameras.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
What a hero is Tyshawn Cormier. Not only did he fathom a truly great hack, to help us hop over an Apple hurdle, but now he’s turned his complex trick into a free app!!!
Question … if Tyshawn Cormier could do it … why couldn’t Apple and does this mean that, as suspected, the post Jobs Apple, is not at all the same place?
So the article says that it modifies “some internal 32-bit components”. Any idea if this will work on other 32-bit applications, such as Photoshop CS5 or MS Office 2011?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
No idea, but there’s enough hate out there for the new Adobe business model that I would not put it past someone to try to figure that out.
The reason that Aperture proved so fix-able was that Apple already did the hard work of making it mostly 64-bit many years ago. They did that for performance reasons, and also to serve as an example of the kind of speed gains you could get (as a developer) from investing that effort. As you’ll recall, Aperture 1 was a real pig, performance-wise. But as with many music production apps, the devil is in the libraries and plug-ins. Many of those are written in 32-bit C or C++, and are not maintained at the same pace as the rest of the app. They are faceless, and silently do what they do without any modification, year after year. Up until Catalina, Apple’s architecture allowed them to run in a separate thread, in 32-bit compatibility mode, without slowing down the main 64-bit application thread.
Walter
On Oct 28, 2019, at 6:40 PM, Richard Cacciato email@hidden wrote:
So the article says that it modifies “some internal 32-bit components”. Any idea if this will work on other 32-bit applications, such as Photoshop CS5 or MS Office 2011?
So the article says that it modifies “some internal 32-bit components”. Any idea if this will work on other 32-bit applications, such as Photoshop CS5 or MS Office 2011?
Extremely unlikely.
As Walter says, Aperture is a 64bit app, so it was a surprise for many, that it wouldn’t run in Catalina. In fact, it turns out that the obstacle to Aperture running, essentially, is down to 2 video frameworks, which are included in Aperture. For users that don’t use Aperture for video, these can be removed without a problem and that is what this hack does.
