Time signatures and adding measures

• Jul 14, 2009 - 13:43


I write music with many time signature changes. When I insert new measures in the middle of ready-made scores, the time signatures of the measures after my insertions get scrambled and the score becomes un-editable.
I suspect that this is because the command to insert a certain number of bars is not linked to any time signature, so after an insertion of new measures in a many-time-signature-sequence, the code can no longer decipher which measures have which time signatures.

I will suggest a new feature on the Feature Request forum.

John Overton


In reply to by David Bolton

So this bug still exists in 0.9.5. then?
I have a file where the same thing happened, and I have not been able to fix it by following your advice in the bug report. What happens in this scrambling process is also that you lose notes. Is there another way to save my file, or do I have to rewrite the whole composition from scratch, hoping I'll remember the notes that have disappeared? (Sorry if I sound frustrated - I am of course, but I don't mean to come off as rude. )

In reply to by julipanette

julipanette, I don't think you problem is related to the original post.

It sounds like you are loosing the last few notes of each measure when you change time signature. You can copy the notes, change the time signature then paste the notes into the new time signature. That way you don't lose any notes.

In reply to by David Bolton

Thank you for your quick reply. So what you're saying is that the procedure you describe should generally be used when changing time signatures? I'll remember that! It's strange though, because I have been working with several MS versions without encountering this problem before, although I change time signatures all the time in everything I write.

Anyway, thanks for the help!

In reply to by julipanette

The procedure is only necessary if you change a time signature and the score has notes after the time signature change. This has been the behavior since at least 0.9.2 (when I first started using MuseScore). I agree it is not optimal but at least a workaround exists.

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