Input caused time signature issues (corrupt score, unknown cause)

• Jul 10, 2015 - 22:46
Type
Functional
Severity
S2 - Critical
Status
closed
Regression
No
Workaround
No
Project

I am a new MuseScore user, so I thought I'd take something I already had, and use it to learn the input interface. I am a long-time user of other music software, so this seemed quite simple to do. I did not import anything, copy anything from another source, or do anything that wasn't already in the MuseScore user interface.

The file is attached.

I had completed entering the Bari Sax part, and was working on the other sax parts when measure 38 started giving me fits, unable to input four beats into a 4/4 measure.

I tried several things:

• Copy and paste from another 4/4 measure, which only put the fourth beat in the next measure.

• Change the value of the beat 1 note to a whole note, but it separated the note into a 3-beat plus 1 grouping, utilizing the following measure.

• Add a new 4/4 time signature at that measure, but it didn't make any difference.

At this point, everything from the problem measure disappeared (even the completed Bari Sax part), and I am left with weird measure lines that are empty of everything, including the standard issue rests.

I don't really care about this score, since it was just for practice. But I thought you should know. I have a history of using software beyond their expectations, and often find bugs like this. However, I thought I should report it.

GIT commit: b25f81d

Attachment Size
Birdland.mscz 41.05 KB

Comments

Well, your score reports as corrupt when I load it, so that's not a good sign, and that surely explains the problems you are seeing. The question is, how did I get like that in the first place? Anything unusual you can think that you did starting in measure 38 that might have triggered this? What was the last thing you remember doing before seeing problems?

For now, the best thing to do is to delete everything from measure 38 to the end. Click the rest in measure 38 top staff, then shift+ctrl+end to select to the end of the score, then ctrl+delete. Then you can add new measures and try again.

As I stated, I'm not concerned about recovering this file, as I was just using it for input practice. Since I am new to this software, I could have something strange (like a carry-over keyboard from a different software program). However, I was being really careful not to do that.

My best guess is that the last thing I did was copy and paste a section of the Bari Sax part into the Tenor Sax part, and then edit it. The time signature crash happened when changing the note value. Perhaps that helps?

I don't know the cause for now.
By exporting the file in MusicXML format: Birdland.xml , a warning appears at the opening, but the corruption is fixed.
fichier xml.jpg
There is a lot of "invisible" rests from the measure 38. By repairing a single invisible rest (->to visible) eg in the Alto sax staff (measure 38), this warning disappears after save-reload. 2 Birdland Alto.mscz
To finish, as mentionned in comment #1, by deleting measures 38 -> to the end, and adding new empty measures, the file is as new, in main score and parts. 3Birdland parts.mscz