3.5 Freezes When Specific Actions Are Taken On Scores with Larger Instrumentation

• Aug 8, 2020 - 15:49

The minimum number of staves on the score I've seen so far for the freezes to take effect is 25. I've seen this occur with two separate files, including one that I had just recently created so I can likely say that this is not the case of a corrupted file.
Such actions include:
1. Using the rewind button near the top of the interface to return to the first page of the score (workaround includes pressing the Home key on Windows and clicking on the first measure)
2. Using playback on part scores
3. Using playback on full score


In order to investigate, we would need you to attach one of the scores for which you are seeing a problem, and give us precise steps to reproduce the issue.

Do you still have an unanswered question? Please log in first to post your question.