MIKE HALLORAN
Finale 27.4,1, SmartScorePro 64, All of the Garritan Libraries, NotePerformer 5.0.1, 10TB other VIs ... 2023 M2 Mac Studio Ultra 192GB RAM, 8TB, macOS Sequoia 15.7.2 / Tahoe 26.1; Overture 5. Notion 6, Dorico Pro 6, MuseScore 4.5.x, Encore 5.0.7 over Mojave—2012 MBP, DP11, Logic Pro, BIAB Audiophile 2025… Conductor, Singer, Arranger, Composer (former bassist), Retired ASCAP. 40+ years experience solving Mac problems; spent years in Windows and UNIX support
- Total activity 7457
- Last activity
- Member since
- Following 0 users
- Followed by 5 users
- Votes 1343
- Subscriptions 2325
Comments
Recent activity by MIKE HALLORAN Sort by recent activity Recent activity Votes-
It could be the graphics card not keeping up. All systems prioritize tasks. If this is a chronic issue, it could be a sign that something needs to be upgraded—but what? CPU? GPU? Drive? RAM? All? ...
-
Have you filed a support case with MM? What do they say?
-
As long as you are the registered user, you can log into your account and upgrade from there. Some of us had problems upgrading in the Chrome browser (myself included)—best to use Safari or Firefox...
-
Does that even work? If I remember, the manual is in .pdf form on your disk. The earliest one I find online is for 2009. The instructions won't be that different.
-
Log into your MakeMusic user account.
-
On a Mac, fonts compiled before Apple's 2012 compatibility guidelines (or those that ignore it) can have major issues. The only way to fix it is to update the font(s). Being that the 15 year old, i...
-
I like that idea and can see how it would save time and clutter.
-
> What is more important would be to hear from others (Mac users particularly) who are or are not having similar experiences.< I am not having the same experience. I skipped 2012 but 2011, 2014,...
-
Really... go back to 2011 in El Capitan? Good luck with that.
-
Thanks for the link. I'm glad they finally released a fix for the FinaleScript issue. Glad it worked for you. Perhaps I got lucky. Interesting that we both encountered the problem after updating ...