New post
Avatar
0

I have Finale 26 on my Apple Silicon Mac running macOS 12.  I tried Finale 27 for 30 days.  The only improvement I noticed was that HyperScribe worked again.   (It had been broken in Finale 26 in macOS 12.)  But a major regression is that, presumably because of the new Apple CPU architecture, all of my plugins are gone.  So I no longer had JW Meter and Rhythm, JW Lua, JW Lua Lyric Baselines Up/Down,  Patterson Copy Page Layout, etc.  So I decided to uninstall 27 and revert to 26.

I understand that the Plugins are from third party developers, but I think that MakeMusic needs to step up and either pay these deveopers to recompile their Plugins, or buy them and integrate them into Finale 28.  Also, for God's sake, please automatically migrate my preferences and stuff automatically from previous Finale versions, as all other apps do.  That is some time-consuming and annoying to need to re-make everything manually.

7 comments

Date Votes
Avatar
0

The problem with the JW plug-ins (and other ones) is that they are not native (M1). But you can make them work if you launch Finale in Rosetta mode.

Comment actions Permalink
Avatar
0

Thank you, Michel.  Yes, I realize that the Apple Silicon "M1" is the issue.  I'd forgotten about the workaround of launching in Rosetta mode.  Yes, that will work for a few years.  Ultimately, though, MakeMusic needs to get these Plugins working on Apple Silicon.

Comment actions Permalink
Avatar
0

Since the plug-ins (those not already included in Finale) are the responsibility of the plug-in authors, it is not Finale's role to make them work. We can hope the plug-in suppliers feel it worth their time to update them.

Comment actions Permalink
Avatar
2

Adrian, I agree it is not their responsibility.  But it is in their interest, assuming they want users to continue purchasing upgrades to Finale.  I get far more value from plugins than I do from the minimal improvements in recent new Finale upgrades.  So, out of the box, an upgrade is one step forward and five steps back.  I shall consider running in Rosetta.

Comment actions Permalink
Avatar
1

As you say: Rosetta will work for a few years, but is a stop-gap. There may well come a time when Apple deprecates and eventually removes support for Intel code altogether.

 

This is the inherent danger in relying on third-party individuals for core functionality; (some of them, like Jari, doing it for no financial reward in their spare time). In the event that RP, TG, JW, et al are unable or unwilling to continue, there are no other 'staff' familiar with the internals to take over. 

 

Ironically, Finale 27.2 is amazingly fast on my M1 Pro  MBP when running natively -- it's the most responsive I've ever seen Finale!  I haven't seen any comments about this, which suggests that everyone's running Rosetta -- and it seems a shame to hobble it, given the manhours spent recompiling it.

Comment actions Permalink
Avatar
0

Good thoughts, Ben.  As far as Finale 'staff' (contractors or employees) being familiar with the third-party plugins, yes, but multitudes of software engineers in this world quit their jobs every day, and thus the world is full of software being maintained by engineers who did not write the original code.  I wonder though, if MakeMusic has access to the plugins' source code.  MakeMusic might need to buy it from the authors.

As far as the lack of reactions to Finale 27 being fast when run on Apple Silicon, I think the reason for the lack of cheering is that it has not been perceived as an issue.  Other than initial launch and the interminable "Loading library…", I'm never waiting for Finale.

Comment actions Permalink
Avatar
0

Yes, but when one person joins a team from somewhere else, there's another team member to show them the ropes. If someone is just handed the code, with no comments, and no ability to ask questions, then that's not as straight forward.

 

Avid found that out when they sacked the entire Sibelius dev team -- in one of the most commercially short-sighted backfires ever. 

 

Finale has definitely had phases of sluggishness -- particularly scrolling issues. It's demonstrably faster than F26 on my 2018 Mini, which is no slouch.

Comment actions Permalink

Please sign in to leave a comment.