FreewayTalk

64 replies to this thread. Most Recent

Jeremy Hughes

4 Mar 2019, 12:42 pm

Re: [Pro] Freeway 8

Hi Bob,

We are working on a 64-bit version of Freeway. Unfortunately, Apple have abandoned many of the (32-bit) APIs that Freeway uses (rather than providing 64-bit versions) so we’re rewriting Freeway from scratch. This is a major undertaking, but we’re making good progress.

Jeremy

Alvaro de Regil

6 Mar 2019, 9:53 pm

Hi Jeremy, You’ve been stating this for a long, long time!

Can you tell us if by the time the next OS 10.15 is released this coming September you will have, at the very least, a beta to be tested, or, better yet, a new FWP8?

I am sure that this will help a lot people to plan ahead, because FWP7 will no longer be useful with the next OS, as you well know. Thanks

Jeremy Hughes

6 Mar 2019, 11:56 pm

Apple will presumably release a new version of macOS this fall, and our plan is to have a public beta available before then.

But you should definitely plan ahead.

We’ve said that we are rewriting Freeway from scratch, and that this is a major undertaking in comparison with all previous versions.

We’re making good progress, and development speed is much faster than it was for the previous version of Freeway (which was held back by legacy code) - but it may take a while before the new version is a complete replacement for the current version.

So, if you’re using the current version of Freeway, it would make sense to keep a partition or virtual machine that runs macOS 10.14 or earlier - as others have suggested.

Jeremy

grantsymon

7 Mar 2019, 8:14 am

Thanks for the update Jeremy.

One big question, that would be useful to have an answer to, is whether or not there will be any conversion process, from FW7 to FW8 files? I can imagine that incorporating such a process, could be a gigantic resources black hole .. but it would be good to know all the same. :)

Grant

Jeremy Hughes

7 Mar 2019, 9:20 am

Reading Freeway-7 files is part of the plan - but there are other features that have higher priority right now, so it might not be there from the start.

Jeremy

Alvaro de Regil

7 Mar 2019, 6:45 pm

Thanks for confirming my assumption Jeremy. That’s exactly what I plan, to have a partition for FW8.

One last question: when you say that “it make take a while before the new version is a complete replacement for the current version”, do you foresee the first complete new version as capable of reading FW7 files, or, since you mentioned that it is not a priority, will it take some updates to accomplish that?

Álvaro

Jeremy Hughes

8 Mar 2019, 1:38 pm

One last question: when you say that “it make take a while before the new version is a complete replacement for the current version”, do you foresee the first complete new version as capable of reading FW7 files, or, since you mentioned that it is not a priority, will it take some updates to accomplish that?

I wouldn’t say that reading Freeway-7 files is not a priority, but it is dependent upon other functionality being implemented first. So the point where the new version of Freeway contains everything (or most of what) currently exists in Freeway 7 is the point where we can usefully read Freeway-7 files.

Jeremy

Alvaro de Regil

8 Mar 2019, 6:50 pm

Well, indeed. But it sounds like the first complete version (FWP 8.0) may not be able to read all FW7 files. Am I right? I hope I’m wrong.

Álvaro

waltd

8 Mar 2019, 11:34 pm

I don’t know if they would release such a thing, except maybe as a technology preview. If all you could do was build new sites with it, and not read in existing ones, it would have limited viability for upgrading customers, which would probably be the bulk of the market to begin with.

Walter

On Mar 8, 2019, at 1:50 PM, Alvaro de Regil <[email protected]> wrote:

Well, indeed. But it sounds like the first complete version (FWP 8.0) may not be able to read all FW7 files. Am I right? I hope I’m wrong.

Álvaro

Freeway user since 1997

http://www.walterdavisstudio.com

Jim Feeney

9 Mar 2019, 1:08 am

On 8 Mar 2019, 11:34 pm, waltd wrote:

I don’t know if they would release such a thing, except maybe as a technology preview. If all you could do was build new sites with it, and not read in existing ones, it would have limited viability for upgrading customers, which would probably be the bulk of the market to begin with.

Walter

For sure. I would have to stick with Fwy 7 Pro (and OS 10.14) if the upcoming Fwy 8 could not seamlessly open our Fwy 7 files directly into Fwy 8. Since beginning with Fwy 3.5 in 2004 I’ve slowly built a ~450-page website, each page personally written and unique. I could not possibly start over if I had to rebuild my website.

Oregon, USA | 2017 iMac 21.5” | 3.6 GHz Intel Core i7 | 16 GB RAM | OS 10.14 | User since Fwy 3.5 | https://www.jimfeeney.org

vloerengilde

9 Mar 2019, 8:54 am

good to know,

i’ve some new projects with need a website, i will build some small ones so i can build new ones when FW8 is available. I’m waiting in patience.

www.vloerengilde.nl

Jeremy Hughes

9 Mar 2019, 10:56 am

Our goal is to create a new version of Freeway that is a complete replacement for Freeway 7. But some features (such as the ability to read Freeway-7 files) will take time to implement.

We are planning to release a public beta later this year (before the next version of macOS is released), followed by regular updates from then on.

Jeremy

Frank H

9 Mar 2019, 6:24 pm

HUZZAH!

(not the first time I’ve read this, just felt it was time to cheer) Frank Harsh

On Mar 9, 2019, at 2:56 AM, Jeremy Hughes <[email protected]> wrote:

Our goal is to create a new version of Freeway that is a complete replacement for Freeway 7. But some features (such as the ability to read Freeway-7 files) will take time to implement.

We are planning to release a public beta later this year (before the next version of macOS is released), followed by regular updates from then on.

Jeremy

Alvaro de Regil

9 Mar 2019, 8:06 pm

On 9 Mar 2019, 10:56 am, Jeremy Hughes wrote:

Our goal is to create a new version of Freeway that is a complete replacement for Freeway 7. But some features (such as the ability to read Freeway-7 files) will take time to implement.

We are planning to release a public beta later this year (before the next version of macOS is released), followed by regular updates from then on.

Jeremy

Thanks for further clarifying Jeremy. Yet I’m sorry to say that you are not direct enough. If I’m inferring correctly, it would be suffice it to say, for the purpose of planning ahead: “No. the first complete version of FW8 (FWP 8.0) will not be able to read FW7 files”.

Consequently, FW8 will be great for new sites but useless for the thousands of sites using FW7. I just hope that the next top priority would be to make FW8.1 fully capable of reading all FW7 files, which based on the length of your development timeline so far, I envision to be ready some time in 2020.

Álvaro

John Whittaker

10 Mar 2019, 7:27 pm

I have only been a Mac user for 25 years, but I don’t remember a program update that would not open files from the preceding version. To my mind, having to rewrite sites from scratch is a powerful disincentive to continuing with Freeway. Given that my other (already 64-bit) web program imports site folders at the click of a button, and has the longed-for advantage of providing a code window editing option, I know where to go. As I like Freeway, I may well pay for the FW8 update, but doubt I will use it as my main program.

John W.

Jeremy Hughes

11 Mar 2019, 12:56 pm

Thanks for further clarifying Jeremy. Yet I’m sorry to say that you are not direct enough. If I’m inferring correctly, it would be suffice it to say, for the purpose of planning ahead: “No. the first complete version of FW8 (FWP 8.0) will not be able to read FW7 files”.

I think you’re using “complete” in a different sense to how I’ve been using it. Reading Freeway-7 files is part of what I mean by “complete replacement for Freeway 7”.

Jeremy

Carla

11 Mar 2019, 1:59 pm

Thanks Jeremy for all the hard work. Im really looking forward to the new FWP.

so to be clear: all our FW7 websites will open using FW8 so we dont have to go back and forth?

or will we have to wait on that? Thx

waltd

11 Mar 2019, 2:02 pm

I think what Jeremy has said, all along, is that the final release version of Freeway 8 will open Freeway 7 documents (and convert them to version 8 documents). That’s what Freeway has always done. What some people have latched on to here is the notion that a pre-release public beta version may not have that final detail in place, and they are worried that omission may be permanent. Softpress would never be so short-sighted, in my opinion.

Walter

On Mar 11, 2019, at 9:59 AM, Carla <[email protected]> wrote:

Thanks Jeremy for all the hard work. Im really looking forward to the new FWP.

so to be clear: all our FW7 websites will open using FW8 so we dont have to go back and forth?

or will we have to wait on that? Thx

Freeway user since 1997

http://www.walterdavisstudio.com

Carla

11 Mar 2019, 2:04 pm

Thx Walter I thought I was clear on that until the last few threads! ha

Thx for chiming in C

Alvaro de Regil

11 Mar 2019, 4:23 pm

On 11 Mar 2019, 12:56 pm, Jeremy Hughes wrote:

I think you’re using “complete” in a different sense to how I’ve been using it. Reading Freeway-7 files is part of what I mean by “complete replacement for Freeway 7”.

Jeremy

Hi Jeremy, I think that to be completely clear we need to be more explicit. From what you have said so far, my understanding is that the first complete version (not the beta, but the first complete FW8) may not read FW7 files because it depends on other priorities. I assume that all the beta versions will not read FW7 files and that is perfectly alright. So please clarify if the first FW8 that we would have to pay before downloading it, would read FW7 files or not.

Having said that, I want to let you know that my impression is that most of us hold in very high esteem all the hard work that you and your team are doing to bring back FW to life after having closed your business. It is really a great software that I have personally been using since 2003, and it would be hard to imagine finding something else with such a great interface for people who do not write code. So, in my case, even if the first complete FW8 does not read FW7 files, for whatever reason, I would still buy it just to contribute to the further development of the project until it is fully capable of reading FW7 and much more, I assume.

Thank you so much for the great effort!

Álvaro

Carla

11 Mar 2019, 4:27 pm

What he said !

Jeremy Hughes

11 Mar 2019, 7:36 pm

From what you have said so far, my understanding is that the first complete version (not the beta, but the first complete FW8) may not read FW7 files because it depends on other priorities. I assume that all the beta versions will not read FW7 files and that is perfectly alright. So please clarify if the first FW8 that we would have to pay before downloading it, would read FW7 files or not.

You’re asking about financial and marketing decisions that haven’t been made, and which I’m not responsible for.

I don’t know what the next version will be called, or what its version number might be, or when you might have to pay for it.

Our development goal is to create a new version of Freeway that is a complete replacement for Freeway 7 (including the ability to read Freeway-7 files). It will take time for us to reach this goal, and there is likely to be a transitional period before we get there.

Jeremy

Alvaro de Regil

12 Mar 2019, 6:54 pm

On 11 Mar 2019, 7:36 pm, Jeremy Hughes wrote:

From what you have said so far, my understanding is that the first complete version (not the beta, but the first complete FW8) may not read FW7 files because it depends on other priorities. I assume that all the beta versions will not read FW7 files and that is perfectly alright. So please clarify if the first FW8 that we would have to pay before downloading it, would read FW7 files or not.

You’re asking about financial and marketing decisions that haven’t been made, and which I’m not responsible for.

I don’t know what the next version will be called, or what its version number might be, or when you might have to pay for it.

Our development goal is to create a new version of Freeway that is a complete replacement for Freeway 7 (including the ability to read Freeway-7 files). It will take time for us to reach this goal, and there is likely to be a transitional period before we get there.

Jeremy

Well, then I guess we are left with speculation: maybe yes, may be not. Our only choice is then to remain in limbo and to exercise patience.

vloerengilde

14 Mar 2019, 4:04 pm

no matter what, i wait for it, and will use it when it’s there.

www.vloerengilde.nl

Jim Feeney

17 Mar 2019, 6:41 am

Personally, being at best in the mid-level range of tech expertise, I have no professional need to upgrade quickly to the next Mac OS. I just plan to stick contentedly with OS 10.14 until the much-anticipated Fwy8 is working and will open Fwy 7 files. Meanwhile, Fwy 7 Pro works great. Am I missing something and setting myself up to get caught in some technology trap?

Oregon, USA | 2017 iMac 21.5” | 3.6 GHz Intel Core i7 | 16 GB RAM | OS 10.14 | User since Fwy 3.5 | https://www.jimfeeney.org

Robert T

18 Mar 2019, 2:05 am

I’ve been using FW on-and-off for many years, and I just came back to this forum for the first time in a while. I am really glad to hear that they are developing FW 8!

Thanks very much to Jeremy and all for your efforts! If funding is an issue, and you guys were to set up a Indiegogo/Kickstarter style campaign, I would be willing to pitch in (since I’m no good at coding, I can’t offer to help there…) :) Please keep up the good work!

useKJVonly.com

Paul

18 Mar 2019, 9:15 am

Hi, not really, no. MY main working machine is still on High Sierra. Apple are sending through security updates for it, so that’s all good. The only drawback would be if an app I rely on makes the jump to Mojave and requires that OS to run. Then I’d either have to consider carrying on with what I have already, or making plans to run Freeway in an environment that it’s happy running in.

So, yes, you have to consider the ever moving conveyor belt that is OS updates and software obsolescence. Eventually, they will catch up with you.

However, there is no rule that says you have to update you OS the day it drops.

On 17 Mar 2019, 6:41 am, Jim Feeney wrote:

Personally, being at best in the mid-level range of tech expertise, I have no professional need to upgrade quickly to the next Mac OS. I just plan to stick contentedly with OS 10.14 until the much-anticipated Fwy8 is working and will open Fwy 7 files. Meanwhile, Fwy 7 Pro works great. Am I missing something and setting myself up to get caught in some technology trap?

All the best,

Paul

My Actions Site: http://www.actionsworld.com

Actions for Galleries, decorating that text box and many more!

grantsymon

18 Mar 2019, 10:07 am

I see we’re of about the same vintage. I bought my first Mac in ‘89. :)

I didn’t know that the Mac Pro 6,1 was an SSD card. Silly really but if it’s like the MacBook Pros with the same, they can be switched out, but it’s not a simple operation. You can also buy empty drive boxes to put the old one in, or just use a SATA cable and a rubber band.

If you decide to bite the bullet on the drive, I’d re-format and install a clean Mojave, then use Migration Assistant to move your User Account across from a TM backup. I would guess that the problem you had in the past was that newer versions of the OS puts things in different places to the original installs, so moving stuff across doesn’t always work. So I’d prefer in this situation, to not move applications and instead, to re-install them with the latest available installers. The danger is that some apps, that have survived OS transitions, may not have updated installers to handle the process correctly on recent OS’s. I actually use 3 generations of Macs, which cater to current, plus 2 generations of depleted software, which I still use. One for a 90’s imaging app, which runs like lightning on a G5Quad running 10.6 for Classic (MacOS 9) and another with 10.6 for a high-end digital back, which is still producing the goods 12 years on. So, similar to the discussion about FW8 and it’s compatibility for FW7 files … I see no great urgency. If it can do it down the road, it’ll be great, but I’d personally rather that precious resources be spent on features, stability and bug removal. However, I appreciate that people working in video, sound and imaging, tend to have a lot more computers hanging around, than the average pro user. :)

Grant

grantsymon

18 Mar 2019, 10:17 am

Oops! Replied to the wrong thread … although ironically, the last bit was about this thread.

I shall post my reply in the appropriate thread too.

Apologies.

Grant

eus

27 Jul 2019, 9:16 pm

wel what ever and how eer it all happens ( i know, topic is a little out of date) but i am eager to get that new fw8. remember we had to change our way of thinking after the fw6 version got out :D personaly i salute new idea’s, new update, new start! can’t wait!

i’m on a 2.7 quad and loving every moment…

Steve Gunther

31 Jul 2019, 9:29 am

‘Are we almost there dad?’ Its a loooong journey. Any looming time line for FW8? All waiting patiently…….

waltd

31 Jul 2019, 2:41 pm

If you keep asking, I am going to turn this car around! (Every Dad, ever.)

Walter 8-)

On Jul 31, 2019, at 5:29 AM, Steve Gunther <[email protected]> wrote:

‘Are we almost there dad?’ Its a loooong journey. Any looming time line for FW8? All waiting patiently…….

Freeway user since 1997

http://www.walterdavisstudio.com

Carla

31 Jul 2019, 2:58 pm

Ha!!!~ Walter that cracked me up…… thx for all your hard work guys.. I am patient because 7.1.4 FW is still fantastic and you all taught me how to use it right!

Steve Gunther

5 Aug 2019, 3:31 am

Also - feature request: the ability to register users. That would be gold. I got my secretary to build a wordpress site, using LMS Lifter. Awful. Clunky. Have to hire a coder every time we want to add a field. Arrrggghhh.

Bert Green

12 Sep 2019, 10:14 pm

Hey there Jeremy, Catalina is almost here. Do you have any updates on where things are at with the development of version 8? I’m planning to wait to upgrade for now, but at some point in the coming year I will be getting a new MacBook Pro, and am hoping to be able to run Catalina and switch my site over to version 8. LMK thanks.

Jeremy Hughes

13 Sep 2019, 11:55 am

We’re hoping to release a public beta soon after Catalina is released. But (as I’ve said before) this is a complete rewrite and it’s going to take a while before it is a complete replacement for Freeway 7. So it would be a good idea to have a partition or VM with Mojave on it - so you can continue running Freeway 7 when you need to.

Jeremy

Alvaro de Regil

13 Sep 2019, 4:57 pm

Hello everyone,

I followed Jeremy’s advice and created a new volume for FW 7 with Mojave a month ago. I’ve been using it to update several websites without a glitch. Just make sure that all your files that will be used on the website are in exactly the same files in the new volume. This means that you need to copy or transfer them and put them in the files replicating the same path. Of course you can keep them in the original volume, but you run the likely risk that FW won’t find all of them right away. So to save you time just copy them to the new volume if you have the space.

Great to know that the beta version of FW8 is coming soon. Catalina will be released this October.

Cheers!

Álvaro

Bert Green

13 Sep 2019, 5:00 pm

I’ll keep using Mojave for the time being. Will decide what to do if and when I get a new laptop, but Freeway is so crucial to my work that I’m OK to hold off for a while.

agallagher

30 Sep 2019, 9:16 am

Hi Jeremy

I’m working on a large website update and I am wondering if I should hold off until Freeway 8 comes out or not. If I continue with Freeway 7.1.4 will it be much work to transfer into 8?

Cheers

Anthony

Thanks Anthony

waltd

30 Sep 2019, 12:54 pm

If you need to do this now, you should use the tools available now. You should also plan to maintain an environment (see Jeremy’s message this morning with the instructions) so that you can continue to use the tools available now for the foreseeable future.

Predicting how it will go to upgrade from a known app to an unreleased app is a guess at best. I am certain that Softpress will try very hard to make this process as easy and fool-proof as possible, since it’s in their best commercial interest to do so, but nobody has seen the replacement app, or used it, or tried to open a previous-version document with it yet.

Be as conservative about this as your business needs require you to be. Take good care of your pre-Catalina Mac, and wait to upgrade it until you really can’t any more (for real business reasons). If you really have to get a newer version of the OS in order to be compatible with something else, consider getting a new Mac and keeping your old one on Mojave, or buying an older used Mac to run Mojave and any 32-bit apps that you can’t replace. 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

On Sep 30, 2019, at 5:16 AM, agallagher <[email protected]> wrote:

Hi Jeremy

I’m working on a large website update and I am wondering if I should hold off until Freeway 8 comes out or not. If I continue with Freeway 7.1.4 will it be much work to transfer into 8?

Cheers

Anthony

Freeway user since 1997

http://www.walterdavisstudio.com

grantsymon

30 Sep 2019, 1:42 pm

On 30 Sep 2019, 12:54 pm, waltd wrote:

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?

https://twitter.com/gentcoders?lang=en https://gentlemencoders.com

Grant

agallagher

1 Oct 2019, 2:41 pm

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.

Anthony

Thanks Anthony

Arne Gustafsson

1 Oct 2019, 3:13 pm

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 protected]> 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.

Anthony

waltd

1 Oct 2019, 3:14 pm

That’s what I am using here.

Walter

On Oct 1, 2019, at 11:13 AM, Arne Gustafsson <[email protected]> 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 protected]> 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.

Anthony

Freeway user since 1997

http://www.walterdavisstudio.com

grantsymon

18 Oct 2019, 3:19 pm

On 30 Sep 2019, 12:54 pm, waltd wrote:

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:

https://medium.com/@cormiertyshawn895/how-to-run-aperture-and-iphoto-on-macos-catalina-46a86d028b87

Grant

Joe Muscara

19 Oct 2019, 12:17 pm

On 18 Oct 2019, 3:19 pm, grantsymon wrote: I reckon this clever man may have just made a lot of new friends:

https://medium.com/@cormiertyshawn895/how-to-run-aperture-and-iphoto-on-macos-catalina-46a86d028b87

Not for the faint of heart, though! :o

grantsymon

24 Oct 2019, 12:07 pm

On 19 Oct 2019, 12:17 pm, Joe Muscara wrote:

Not for the faint of heart, though! :o

True! … and depending on Catalina feedback, I may wait for 10.15.2 before trying it out.

However, Nik Bhatt (ex-Aperture Lead) has given a helping hand with some simplification: https://gentlemencoders.com/aperture-for-catalina/

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. :)

Grant

Richard Cacciato

25 Oct 2019, 4:52 pm

Will Freeway 8 run on Mojave? I can’t tell for sure from the discussion to date. Thanks.

Jeremy Hughes

25 Oct 2019, 4:54 pm

On 25 Oct 2019, at 17:52, Richard Cacciato <[email protected]> wrote:

Will Freeway 8 run on Mojave? I can’t tell for sure from the discussion to date. Thanks.

Xway will run on High Sierra or Mojave.

Jeremy

Jeremy Hughes

25 Oct 2019, 5:02 pm

Xway will run on High Sierra or Mojave.

… or Catalina (of course).

Jeremy

Richard Cacciato

25 Oct 2019, 5:04 pm

Fantastic (as always)! Thanks!

Joe Muscara

26 Oct 2019, 12:20 pm

On 24 Oct 2019, 12:07 pm, grantsymon wrote:

On 19 Oct 2019, 12:17 pm, Joe Muscara wrote:

Not for the faint of heart, though! :o

True! … and depending on Catalina feedback, I may wait for 10.15.2 before trying it out.

However, Nik Bhatt (ex-Aperture Lead) has given a helping hand with some simplification: https://gentlemencoders.com/aperture-for-catalina/

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?

grantsymon

26 Oct 2019, 2:50 pm

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.

Grant

Frank H

26 Oct 2019, 7:10 pm

I am elated to hear this! Frank Harshbarger [email protected]

On Oct 25, 2019, at 10:04 AM, Richard Cacciato <[email protected]> wrote:

Fantastic (as always)! Thanks!

Tommy

28 Oct 2019, 1:51 pm

Hi Jeremy,

I understand you are busy, may I know approximate date of release for Xway Beta?

Thanks,

Tommy

Jeremy Hughes

28 Oct 2019, 2:28 pm

Hi Tommy,

The approximate release date is “soon”.

We’re making some changes to our web site, and we plan to release b1 as soon as the web site is ready.

We will make an announcement on Freeway Talk when Xway b1 is released.

Jeremy

On 28 Oct 2019, at 13:51, Tommy <[email protected]> wrote:

Hi Jeremy,

I understand you are busy, may I know approximate date of release for Xway Beta?

Thanks,

Tommy

grantsymon

28 Oct 2019, 9:39 pm

On 19 Oct 2019, 12:17 pm, Joe Muscara wrote:

Not for the faint of heart, though! :o

And just a few days later…

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?

(Problem solved Walter!)

https://medium.com/@cormiertyshawn895/how-to-run-aperture-and-iphoto-on-macos-catalina-46a86d028b87

Grant

Richard Cacciato

28 Oct 2019, 10:41 pm

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?

waltd

29 Oct 2019, 1:23 am

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 protected]> 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?

Freeway user since 1997

http://www.walterdavisstudio.com

grantsymon

29 Oct 2019, 8:59 am

On 28 Oct 2019, 10:41 pm, Richard Cacciato 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?

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.

Grant

Joe Muscara

30 Oct 2019, 11:53 am

On 28 Oct 2019, 9:39 pm, grantsymon wrote:

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?

(Problem solved Walter!)

https://medium.com/@cormiertyshawn895/how-to-run-aperture-and-iphoto-on-macos-catalina-46a86d028b87

Wow.

I know he keeps saying “you can check the source code” but all those warnings make me a tad nervous. I’ll get over it. :)

grantsymon

30 Oct 2019, 7:41 pm

On 30 Oct 2019, 11:53 am, Joe Muscara wrote:

I know he keeps saying “you can check the source code” but all those warnings make me a tad nervous. I’ll get over it. :)

Well … call me crazy, but 10.15.1 came out today, so I updated my main Mac and ran Retroactive 1.0.

I had to Open it via contextual menu 3 times, as Catalina seems to be even more cautious about non-app-store installs … but after that, it took about a minute to run and then, as old Jobs used to say ‘Boom!’ There was Aperture sitting open on my Mac. I have gone through a few libraries and done some basic checking, but it all seems fine. The only thing was that I lost my prefs … but I have them on another Mac!

Grant

waltd

31 Oct 2019, 1:28 am

So happy to hear this!

Walter

On Oct 30, 2019, at 3:41 PM, grantsymon <[email protected]> wrote:

On 30 Oct 2019, 11:53 am, Joe Muscara wrote:

I know he keeps saying “you can check the source code” but all those warnings make me a tad nervous. I’ll get over it. :)

Well … call me crazy, but 10.15.1 came out today, so I updated my main Mac and ran Retroactive 1.0.

I had to Open it via contextual menu 3 times, as Catalina seems to be even more cautious about non-app-store installs … but after that, it took about a minute to run and then, as old Jobs used to say ‘Boom!’ There was Aperture sitting open on my Mac. I have gone through a few libraries and done some basic checking, but it all seems fine. The only thing was that I lost my prefs … but I have them on another Mac!

Freeway user since 1997

http://www.walterdavisstudio.com

grantsymon

31 Oct 2019, 4:08 pm

A little update on Retroactive for Aperture:

Today I’ve been poking around a bit more and have come across a couple of little hiccups.

• Full-Screen mode ‘unexpectedly quits’ Aperture, if you use the F key to return to normal view … when using dual-monitor setup. Using the ESC key seems to avoid the problem, but not always. I’m guessing it has to do with Spaces, which Aperture seems to want to use for Full-Screen. I’m not having the problem when there is no second monitor attached.

More importantly, but with an easy workaround:

• Add Adjustments drop-down menu (in the Inspector) is empty unless Aperture is launched via Retroactive.

Workaround:

Add ALL or preferred Adjustments (and/or Quick Brushes) to an Effect, or to several Effects, via the Effects drop-down, which still shows up. From there you can simply choose an ‘Effect’ when you want to edit an image and the associated Adjustments will be added to any Adjustments have already been applied to the image. You could of course, just re-create the Add Adjustment drop-down menu entirely in the Effects drop-down menu. Alternatively … launch Aperture via Retroactive each time, but, that said, I’m getting Aperture wanting to Repair Libraries after launch from Retroactive, although I haven’t had time to really scrutinise this.

Other than that, I have had the long standing issue (for me) of Aperture not making Previews for certain raw image types (RAF and ORF and even struggling with NEF files). I’ve found with this hacked version, that I can choose to Reprocess Originals and it doesn’t help … but if I do it a second time, it works! So I’ve actually improved something with this hack. :) :) :)

Grant

Back to Top

waltd

31 Oct 2019, 4:17 pm

Amazing. I’ve put Catalina on my laptop, but I’m holding off on my Mac Pro for this very reason. I need to evaluate a real replacement, maybe Capture One, maybe the Raw Power app/extension to Photos (written by one of the authors of Aperture), and move along. I’m not sure that swimming upstream like this is more than a curiosity or last-ditch effort. It’s not likely to be sustainable, not through any malice on Apple’s part, just inattention and other priorities.

Walter

On Oct 31, 2019, at 12:08 PM, grantsymon <[email protected]> wrote:

A little update on Retroactive for Aperture:

Today I’ve been poking around a bit more and have come across a couple of little hiccups.

• Full-Screen mode ‘unexpectedly quits’ Aperture, if you use the F key to return to normal view … when using dual-monitor setup. Using the ESC key seems to avoid the problem, but not always. I’m guessing it has to do with Spaces, which Aperture seems to want to use for Full-Screen. I’m not having the problem when there is no second monitor attached.

More importantly, but with an easy workaround:

• Add Adjustments drop-down menu (in the Inspector) is empty unless Aperture is launched via Retroactive.

Workaround:

Add ALL or preferred Adjustments (and/or Quick Brushes) to an Effect, or to several Effects, via the Effects drop-down, which still shows up. From there you can simply choose an ‘Effect’ when you want to edit an image and the associated Adjustments will be added to any Adjustments have already been applied to the image. You could of course, just re-create the Add Adjustment drop-down menu entirely in the Effects drop-down menu. Alternatively … launch Aperture via Retroactive each time, but, that said, I’m getting Aperture wanting to Repair Libraries after launch from Retroactive, although I haven’t had time to really scrutinise this.

Other than that, I have had the long standing issue (for me) of Aperture not making Previews for certain raw image types (RAF and ORF and even struggling with NEF files). I’ve found with this hacked version, that I can choose to Reprocess Originals and it doesn’t help … but if I do it a second time, it works! So I’ve actually improved something with this hack. :) :) :)

Freeway user since 1997

http://www.walterdavisstudio.com