Mike, you can also find the info posted here https://makemusic.zendesk.com/hc/en-us/articles/360054240594 

We will continue to update the article as more info becomes available, so feel free to follow this to get updates.

What about timeline for native AppleSilicon (+multicore support)? I don't dare to even guess. If Mac version of Finale stays in development, then conversion seems inevitable. Can we expect it in 1-2-3 years perhaps?

0

I am expecting m1 Apple computer next month so I want to know if Finale 26 is actually usable through Rosetta?
It would be really helpful if we got a list of issues or functionalities from Finale developers on M1 platform.

I find it hard to believe that Finale would ignore the chance to configure their products to work with the new Apple architecture. When a new update will come out to address this, I have no idea; but I expect it is under study at Finale.

Adrian, I also hope that MakeMusic will give us Finale 26 update for new architecture, not like they did with previous versions, otherwise many will be forced to switch to Windows.

...not to windows! Switch to a competing notation product like Dorico.

Is there any update regarding the compatibility of M1 macs with Finale 26? My ageing computer is groaning and with the possible release of M1X MacBook Pros in June/July I am hoping to upgrade. Dorico and Sibelius have had Rosetta 2 compatibility for a while now, and I notice the makemusic article above hasn’t been updated since early January. 

Finale 26 works fine on my Mac mini M1.

Thanks, that’s good to know!

I have tested F26 and NotePerformer on M1 mini. The sad thing is- it works much faster under Rosetta 2 than on my latest Intel mini with i7 processor.
The most awkward thing is- it is 2021 and the notation app that can also host VI-s can utilise only one porcessor core. Gosh. Time stands still.

Andrew,
I am also eager to know what are the plans for the m1 architecture. It looks like we have to wait for full compatibility till next Finale 27 and of course we have to pay for the upgrade.🤔

>the notation app that can also host VI-s can utilise only one porcessor core. Gosh. Time stands still.<

No. You don’t understand how this works. Finale doesn’t “play” Virtual Instruments — it triggers players that host the VIs and most of them use one core per instance. An instance can host multiple VIs but they are all using a single core when you do that. For VIs to use multiple cores, you need to run multiple instances of their players, easily done, Aria, UVI, SampleTank, Kontakt and so on are all single-core players. There are a few specialized instruments that have proprietary multi-core players—Finale can trigger those, too. Mac/Win/Linux — makes no difference.

Ok. What I see is that FINALE has 3 instances of NotePerformer playing and only one core of 6 is used for Finale, all 3 instances together. But that doesn't change things - Finale is so slow with bigger files. Even without playback.

I now really dare to say that this is incorrect. Aria player hosts Garritan instruments. I do not have Aria player installed. NotePerformer has its own player and Finale hosts it as a plugin. For MacOS there is only one process visible - FINALE. All plugins that run inside Finale are running inside Finale's process. Finale's process can use only one core. Because all the plugin instances run inside Finale's process, they are also restricted to the single core. To end this dispute, please open Activity Monitor and see processes and core usage.