Global Time Signature Is Broken
When right clicking into the time signature properties menu and setting the actual and text value both to 7/4 and clicking OK and re-entering the same menu my global value has multiplied. This also causes anomalies where the bar lines go out of sync with the given time signature. However, this visual anomaly does not affect the score when it is reopened after being saved but playback IS affected with the score going out of sync. This example is of 7/4 time.
OS: Arch Linux with qt5 used for building the gui.
Revision: Musescore 2.0 rev. 7761.c6d6c4b (built from aur)
| Attachment | Size |
|---|---|
| Global Time Anomaly.mscz | 7.64 KB |
Comments
Hi artofmusic
Thanks for the report.
Do you intend to provide a fix? If not, could you de-assign yourself?
It appears this score is already corrupt - it is showing 49/16 as the time signature in measure properties. Can you provide steps to reproduce the problem in a score created from scratch?
Also explain what you were expecting to happen. If you were simply trying to add a 7/4 meausre, this is not the way to do it. Instead, you should add it from the time signature section of the master palette. The properties you were playing with are not meant for this purpose. But without knowing what exactly you were trying to do, it's hard to say for sure if it's working "correctly" or not.
It Works through the master palette. Maybe making it harder to break by going to the master palette menu instead to edit time. Just like 1.x
Well, it *shouldn't* break. I'd still like to see steps to reproduce the problem from scratch so we can see what specifically isn't working, so I'm leaving this open until we understand it fully. We do know about one bug having to do with this, perhaps what you were seeing is the same: #42341: Local time signature change results in corruption. if so, we can close this again as a duplicate.
Yes This Is The Same Error.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.