Playback Scrubs crash
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Randomly
Status
active
Regression
No
Workaround
Yes
Project
When MuseScore is open and the output is switched from an external DAC, the program's I/O crashes after the first playback request. This can be from selecting a note or selecting play. The main solution is to restart MuseScore's audio drivers every time the output is switched. Alternatively, the output can be switched before launching MuseScore.
To be clear, this occurs when using PortAudio. Each API deals with the soundcard/DAC as a single output. In specific, the switcher goes between dedicated speakers and headphones. This issue is only seen in MuseScore, every other program is not affected by the DAC's internal switcher.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548021803, revision: 3224f34
Comments
Changing the switcher before launching Musescore no longer works. Every launch requires a subsequent audio restart on Musescore's end. It should be noted that Musescore crashes more often than in the previous post; specifically when stopping playback, switching to another spot in the score, and starting playback immediately.
After further research based on large-score works taking longer than usual, I have found that the issue stems from Musescore's usage of RAM. Large works (either long or with many parts) will use roughly the same amount of RAM as typical works, which will cause longer wait times in Musescore's processing. My smaller and shorter works perform better than my large-scale works.
That said, the scrubbing features will crash Musescore consistently on these large and long works. Since these issues seem to be related to the prior issue, it would be handy to have Musescore dynamically allot RAM based on what is loaded in the program. A temporary fix is to change the priority the OS gives to Musescore.