Agreed but on my real CPU not a VM. Everything works; Finale, audio plugins including SoundSource, etc. I have not found anything that didn’t work with Sequoia.

Been running it on a test Volume for months—long before the announcement, in fact. No problems found with Finale over Sequoia. Many issues with 3rd party plug-ins. NotePerformer 4 is fine.

BIAB AUs don’t work anymore but that’s due to PG Music changing things for BIAB 2024 without making them Apple Silicon native. I could run 27 over Rosetta II and test again but I’m not interested in the outcome. I have about 10TB of 3rd party VIs. Many like Native Instruments have stated that they are not yet macOS 15 compatible.

Please give any system info, operating system version number, plug ins, etc. you can to help all of us tackle any forthcoming issues.

Pass — I’d have to write a book. I’m running a Sequoia APFS Volume on my M2 Studio Ultra. Unlike a VM, it’s the same as running at the root level—they are “real CPU”s. My other Volume boots into Sonoma 14.7. My signature gives all the info that needs to be shared.

I'm currently running Finale on Mac OS Sequoia with my Mac Studio.  So far I have not experienced an issue.  Really wondering what this "Not compatible" thing is. 

It’s just CYA.

Really wondering what this "Not compatible" thing is. 

 

It’s just CYA.

Simple: If you have any issues in Finale over Sequoia, don't even think about official Tech Support.

I know we've had this minor disagreement before, but you can indeed clone a mac. I do it with Carbon Copy Clone

The only disagreement is that you don't understand that one cannot "clone" a Mac anymore. A clone is an exact copy and you can boot from it. That has not been possible for many years because Apple shut that down. In fact, even using Migration Assistant as outlined below will not result in an exact copy if done to an external drive—to another Mac, yes, but some applications will not work if booted from an external drive and there is no known workaround for this.

CCC is a script for backing up the Mac using tools built into the Mac and that is all. From the source:

Hi folks, this is Mike, developer of CCC. I wanted to clear up some misunderstandings here …. You absolutely can restore applications from a CCC backup. My goodness, if you couldn’t restore apps from the backup, we’d have a pretty serious problem. ... It really boils down to whether you’re “restoring some stuff” vs. “recovering your entire Mac to a clean installation of macOS”. Let’s pick this apart:

• If you need to restore just an application, then the procedure is pretty straightforward. You can restore it via CCC, or simply drag and drop in the Finder. Both methods are supported.
• If you need to restore all of your applications (but still just your applications), then same as above – you can use CCC for this, or drag and drop (I’d prefer CCC for a task this large).
• ...

... If you’re trying to recover your entire Mac from a backup, i.e. to a clean installation of macOS, that is when we recommend using Migration Assistant to migrate data from your CCC backup. This recommendation does not vary among backup products now. Whenever you’re migrating user accounts to a clean installation of macOS, Migration Assistant is the only game in town. The user accounts have to be “adopted” by macOS, and only the macOS Installer or Migration Assistant can do that. If you wanted to choose to not migrate your apps, you could certainly restore them via CCC later, but personally I think that starts to make things more complicated.

Please change the channel.

I think this supports what I said, that you can boot from a clone. On a different topic, namely restoring a Mac from a clone (which is not what I addressed), you can use MA to do that from a clone. I’ve done it.

I carbon copied the 1Tb HD on my iMac to an 8Tb SSD.  At first the unit would not boot and provided a no-entry symbol.  I had to take it to Apple to get it "unlocked" which they claimed to be a security provision. Once I had it back home, plugged in the SSD and booted, it worked fine. Opened to the screen to set preferred boot disk, I chose the external SSD and (fingers-crossed), it booted and I have been using it ever since.  Unfortunately, Apple obsoleted the unit and it cannot have an operating system higher than Ventura.  It has finale on it in the last iteration and will stay there until I finally junk the unit.  My back-up for Finale and a bunch of other programs I can't move onto higher Apple OPs.  Meanwhile, I replaced it with a MacBook Pro that cost a bundle, but is the "state of the art" in chips, onboard memory, etc.  It is currently in under Sonoma and runs Finale with a smoothness and lack of issues that the iMac never got passed.  I always wondered why Finale had all the glitches that plagued my earlier Macs.  It seems like a huge pool of memory (128Gb) and fast chips is at least part of the answer.  I have had a couple of crashes with reopen and no lost material (I backup often) when moving back and forth from AUB&E to Score Manager.   This is a problem that two+ years ago, Tech support at Finale told me they were working on and hoped to have a solution soon.  Frankly, while it presents a dozens small pains in the neck, have no more "evolutions" of Finale is one less pain.  

A true clone is an exact copy of a System drive. We're still speaking English and that is what it means. This has not been possible in the macOS since 10.5. It would be nice if CCC et all would stop spreading misinformation on this but that isn't going to happen. The only things that "cloning" apps bring to the table are some advanced scripting options for Disk Utility/Time Machine and some of them are nice—otherwise, you'd have to write them yourself. If you want those, the money is well spent. Even making a boot drive from a TimeMachine backup is easy and Apple has support docs on how to do this.

Some apps and utilities cannot be run on Apple Silicon Macs if booted from external drives (if these were true clones, this would not be an issue) and there is no known workaround due to Apple not allowing certain .kxt files to load unless from System drives. Fortunately, Finale 27 does run from an external but if you have, say, a MOTU audio unit requiring drivers, it will not run from an external. I have one and tested this after someone complained. The Apple Developer boards have complaints going back five years on this and Apple isn't budging.

I will post how to make an external that will boot any Mac made from 2012–2025 and run 27.4.1 in a separate thread but I want to write a set of clear, concise instructions on how to do so. I've been extremely busy with companies not believing that I am retired and the money has been too good to ignore. In any case, it is not intuitive and it is possible to waste many hours before certain error messages show up. 

Finale 27.4.1 runs over Mojave–Sequoia. Except for startup times, I have found little difference in Finale performance from my 2012 MacBook Pros to my M2 Studio with one exception: There are some 3rd party VIs that work over Apple Silicon only if Finale is running over Rosetta II which I don't recommend because it's pretty slow if you do—slower than my 2012 over Mojave. 

MakeMusic solved the Ventura issue a couple years ago. Sonoma dropped a number of Intel Macs and Sequoia dropped even more.