


I have the same issue, and I had it as well with both previous versions AND previous computers, so the good news is: There IS a solution. Bad news is: I forgot how, and now I'm searching here and find your post.... unanswered. Thats such a pity.
Finale gods should give us a hint - at least how and where to search.. Or have you found out?
I'm on an iMac 2017 i5 (retina), as mentioned: same issue. Maybe we find out..


Any entry method.
It’s a noticeable difference between vanilla 26 and the “updates”. I’ve heard back from makemusic but they say there isn’t an issue. I’ve asked to “roll back” but they said they don’t have it anymore (which I don’t believe). No, I am using Noteperformer 3 but the bug from 25 was fixed for 26. But I don’t think that is related as it worked perfect with plain 16.

Same issue here. It lags about one to two seconds after just about every click. I have an extremely fast system so it is not on my end and I o only noticed it started doing this with the latest update. It is most prevalent on speedy note entry and when you click on certain tool icons. Also it is even worse when trying to copy and paste (almost 5 seconds sometimes). It did not start doing this until version 26.2.1.468. They better fix this...and fast...
If Makemusic will contact me I can record what it is doing so they can see it first hand.
Windows 10 Pro
Intel Core i7 3.2 GHz
16 GB RAM
NVIDIA GeForce GTX 1060 6GB


I read this comment a few weeks ago and didn't think about it. But yesterday I was trying to update and correct a year-old score and there IS a terrible time lag. Add to that the still unresolved screen re-draw messes and Finale is really hard to use and impossible to recommend right now.




Suddenly I remembered: If you're on a retina Mac, you could LOWER THE FREAKING RESOLUTION, as described here:
https://makemusic.zendesk.com/hc/en-us/articles/217557808-Slow-performance-on-Mac-Retina-displays
Looks are beyond awful. Welcome to 1999. But as long as I can enter notes in simple or speedy entry, I am OK with it. (means on a scale 1-100 at around ±60)
Edit: Now I changed it BACK, and it also works flawlessly. Would be a shame for makemusic, but you can try and have less hassle, WHILE MAKEMUSIC IS WORKING ON A SOUTION! In'it..?

I opened a ticket and was able to show MakeMusic the problem and they duplicated it on their end. The development team is now working a fix. No timeline. They agree turning off auto update layout and music spacing and using scroll view when manually inputting notes is a temporary work around.



I've discovered the issue is 100% the automatic note spacing. When I turn that off everything goes VERY fast.
It is not an issue of graphics card or display drivers. My computer is an 8th generation i7 PC that uses a SSD. The problem only started happening with version 26.2
There was no issue with 26.1
I am frustrated with the lack of response and communication by MakeMusic as my workflow has grinded to a VERY slow speed due to this. It takes quadruple the time to enter in runs, whether it's with mouse/click or a midi controller. It's incredibly irritating.


Hi Brooke,
You are correct that there was a bit of speed difference in the v26.2 release for Windows users from the previous release. This is something that we addressed in the v26.2.2 hotfix released in March. You can read about it here for more details. If you have not yet, please install the update and see if this helps with the performance slowdown you are seeing.



Sooooooo, the Finale 26.3 update recently made me do some re-instaling. I completely deleted prior versions of finale, and by doing so I found several folders in ~/Library/Preferences (something like the registry for windows) named makemusic or Finalev26 that I deleted, and there were folders of older versions I suspect causing problems, also I did reinstall my MIDIkeyboard. My issues have been solved.
It all seems to go back to the old saying "there is nothing like a clean install"
So if I experience that kind of problems again, I'll likely make a clean install of the OS, the Soundcard, the MIDI Keyboard and so forth (along with all the other stuff I use). It will be a pain, but there is another saying: No pain no gain...
I doubt that it's any different for Windows, as programmers will likely have a cleanly-installed-computer to test the software on, everything else would be just plain stupid.
I know this answer is not narrowing down the problem but you could try just updating prior to reinstalling, also see if deleting and reinstalling music related apps and drivers works before you setup a new OS. That's what I wanted to point out.
Please sign in to leave a comment.
19 comments
Date Votes