Crash on Insert Measure command
Writing a cadenza for a concerto, I created a 60-beat-long irregular measure, but then wrote more material than would fit. In order to get it all in one measure, I intended to insert a new blank measure, then set that one as irregular and for the number of beats needed, then copy/paste the material into that single measure.
However, everytime I right-clicked on a measure--even a regular one--and then clicked on INSERT MEASURE, the application crashed.
Here is the text of the error detail:
Problem signature:
Problem Event Name: APPCRASH
Application Name: mscore.exe
Application Version: 0.0.0.0
Application Timestamp: 512df23e
Fault Module Name: mscore.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 512df23e
Exception Code: c0000005
Exception Offset: 00041ab8
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt
Has anyone had this happen; and does anyone know of a solution or work-around? I am using MuseScore 1.3.
Thanks
Comments
Can you attach the score?
It's not a whole score, just one of the parts derived from the score. I was unable to complete the work I was doing on it, but the latest version is attached.
The problem area is at the end. The cadenza starts at measure 35, and I wanted to make the entire cadenza an irregular measure so it wouldn't count in the measure numbers. Unfortunately, the cadenza is 81 eighth notes long, and the measure properties won't let me specify more than 63/8.
Hopefully I fixed the file and didn't break anything else. See file attached.
I inserted measures 2 measures before the cadenza and copy paste carefully.
Since we don't have information to fix the bug, and there is no fix on MuseScore 1.3 while MuseScore 2.0 is being worked on, I close this bug.
For support question, it's better to use the forum http://musescore.org/en/forum