Wht good is all this speed if I have to relaunch Finale every three minutes

[blueshift]

Just a vent. I don't expect much help, and besides, we need world peace. Please don't answer.

[N Grossingink]

Try replacing Finale's preferences:
https://makemusic.zendesk.com/hc/en-us/ ... inale-etc-

There never will be Finale peace if someone doesn't do something.

[Bill Stevens]

Re-launch every three minutes? I re-launch about every three months. Let's figure out your problem.

::: Bill

[MikeHalloran]

I'll guess it's this:

version 27.1…
MacOS 12.2.x Monterey

27.2 is running smoothly on both my iMac Pro and my M1 MacBook Air over Monterey 12.3. Hasn't crashed once on either machine once I got it running.

If there are plugins and VIs in your system that Finale doesn't like, it might crash during authorization and that happened to me after updating to Monterey 27.1. Finale 'sandbags' them so they won't try to load later.

The fix was to keep opening 27, letting it sandbag more plugs till it was done (I have over 500 plugins and libraries). When Finale finally found them all, the crashing stopped. MakeMusic Support couldn't figure it out; Wallander Support told me what was happening but said there was no way to know which plugins and VIs were the culprit.

If using non-Native plugs or VIs such as NotePerformer on an M1, Finale must be run in Rosetta 2. Otherwise, 27.2 is Native.

[blueshift]

GPO5, GCPO, a couple up to date SFZs from active publishers, and Aria

I go through this after every update and it takes weeks (months) to debug. Any theoretical gain in speed from my older quad core x 16 gb ram machine is not even recoverable.

But I am getting far better audio...waaaay better. I can hardly believe the difference.

[blueshift]

The extra speed really comes in handy when frequently needing to restart Finale.