High tempo marking crashes Musescore 2.02
I think there should be some way to "idiot proof" tempo markings so they don't play beyond a certain speed, because it is possible to hang Musescore by creating a high tempo marking and attempting to subsequently play the file.
Loading the attached file and playing it will hang Musescore 2.02 running under Windows 10.
Attachment | Size |
---|---|
chun dao xiang jiang.mscz | 27.43 KB |
Comments
I couldn't load the file in 2.02 or the nightly until I manually changed the tempo marking (in the MSCX) to something more reasonable.
I can't even open your score on my arch linux x86-64 labtop...just hangs after I press the Open button.
What order of magnitude tempos crash your machine? 1000bpm, 10,000bpm, 100,000bpm, ...?
EDIT: while I can't load your score, I can manually open it. I see you've set tempo to 1.66667e+94. That is quite large indeed! :)
Maybe something like 1,000,000 bpm should be a max? Even on a score of whole notes, that will be very fast. (I realize there will always be someone who desires to exceed the limitations).
How did you create this score?
Musescore 2.02 running under Windows 10.
In reply to Musescore 2.02 running under by brettvachon
are you even able to open up this score you made? Also crashes on my Windows 8.1 machine on 2.0.2.
In reply to are you even able to open up by ericfontainejazz
No, I can't open it. Nobody can. This was an unintended consequence of increasing the tempo marking and saving the file.
In reply to Musescore 2.02 running under by brettvachon
How did you create it in MuseScore 2.0.2? How did you increase the tempo?
In reply to How did you create it in by [DELETED] 5
Here is the original file I was working on when I got the idea for this bug. There's nothing special about it except that it was the file I was working on at the time. Just take the first tempo marking and increase it with the number 9 until the 9s run off the first page and into the second. Then attempt to play the file. It will crash Musescore.
I think arbitrary tempo increases should be capped, regardless of whether this causes a crash or not, because there's no point in having such a high tempo marking anyway.
I've filed a bug report.
https://musescore.org/en/node/85836
In reply to I've filed a bug by brettvachon
and it has been fixied a month ago in the nightly builds (18d0fa9e)
In reply to and it has been fixied a by Jojo-Schmitz
Cool thanks