Bug report: strange behavior when changing time signatures

• Oct 11, 2009 - 22:46

I believe the attached example speaks for itself.

Attachment Size
bug illustration.mscz 1.31 KB


In reply to by David Bolton

You're absolutely right, of course, sorry. Anyway, I can't seem to reproduce this from scratch this morning, yet neither can I fix the bug illustration, nor the same bug in my as-of-yet only-slightly-more-complicated original score. Is the data used to represent the score internally decipherable using a text editor? I'm going to try to compare the innards of the valid and the defective to try to see what's going on. And, FTR, I'm using MuseScore 0.9.5 R2012 on Windows Vista Home Prem. SP2.

In reply to by OlyDLG

Well, seems all I needed to do to fix it was remove the second time sig, then add it again - clearly a re-eval isn't getting triggered, and then is, but unfortunately I'm not sure of the exact order of doing things that created the bug in the first place, so I'm not sure what action should have triggered the re-eval but didn't. However, my piece will require more time sig changes, so I'll try to keep track of the order in which I do things in case the bug creeps in again. Thanks.


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