Entering any note in one frame causes beach ball / Unresponsive

General notation questions, including advanced notation, formatting, etc., go here.

Moderators: Peter Thomsen, miker

dallascomposer
Posts: 26
Joined: Sat Feb 18, 2017 8:37 pm
Finale Version: Finale 26.3.1.643
Operating System: Mac

Post by dallascomposer » Thu Jan 27, 2022 2:11 pm

I am going nuts - There is one measure on one staff of my score that causes the program to freeze when I try to enter a note. I get the spinning beach ball and the program will stay "Unresponsive" in the activity monitor until I force quit.

This is happening in one measure on one staff. Any attempt to enter a note in that measure causes this. I have deleted the contents of the temp folder and all my preferences.

I have switched to "Play Finale through MIDI" and I have tried switching every staff to SoftSynth. It doesn't seem to be related to Audio or Midi.

Any ideas? My computer (2019 iMac) well exceeds the minimum computer requirements
Finale 27.3.0.160
MacOS 13.3
iMac 2019; 3 GHz 6-Core Intel Core i5
Graphics: Radeon Pro 560X 4 GB
RAM: 8 GB 2667 MHz DDR4


dallascomposer
Posts: 26
Joined: Sat Feb 18, 2017 8:37 pm
Finale Version: Finale 26.3.1.643
Operating System: Mac

Post by dallascomposer » Thu Jan 27, 2022 2:17 pm

So further experimentation: I was incorrect. It happens only in this one measure, but in ALL other staves as well.

I tried making a new staff and copying the existing data into it, but I couldn't enter any notes into the same measure, in any staff.

Finale leaps to 100% CPU usage as soon as I enter the note.
Finale 27.3.0.160
MacOS 13.3
iMac 2019; 3 GHz 6-Core Intel Core i5
Graphics: Radeon Pro 560X 4 GB
RAM: 8 GB 2667 MHz DDR4

dallascomposer
Posts: 26
Joined: Sat Feb 18, 2017 8:37 pm
Finale Version: Finale 26.3.1.643
Operating System: Mac

Post by dallascomposer » Thu Jan 27, 2022 2:21 pm

Okay who knows what caused it, but I finally worked around it by inserting a measure stack.

Just to be safe I didn't copy the existing notes over. Manually re-entered them all and then deleted the faulty measure stack. No idea how this happened.
Finale 27.3.0.160
MacOS 13.3
iMac 2019; 3 GHz 6-Core Intel Core i5
Graphics: Radeon Pro 560X 4 GB
RAM: 8 GB 2667 MHz DDR4

Post Reply