Musescore 4 messes up parts when inserting measures in score
Every time I insert new measures between existing measures in a score parts are going messy. I tried to work on different computers and every time i got the same problem as in attached file. Is there any solution to this issue?
| Attachment | Size |
|---|---|
| test1.mscz | 35.04 KB |
Comments
No idea. But if I but notes in the bass part in the score, it seems to straighten out the individual part. FWIW, I don't work in parts. Only in the score because of problems like this.
i have the same issue. ive spent the last three days on correcting corruption errors in the parts and now i see none of the corrections is actualised in the full score.
In reply to i have the same issue. ive… by anlepo
There is a half-solution to this problem. You can save the score as an uncompressed MuseScore folder. After inserting the bars, save as uncompressed MuseScore folder and reopen the file, then save again as .mscz . You can continue to create the score. It worked for me. Maybe someone knows how to report such errors to the developers.
In reply to There is a half-solution to… by klejdonut
I forgot to add that the problem with this solution is that it resets the styles in parts
Is there some way to escalate this issue or see if it's been reported elsewhere? It's been almost a year and I just ran into the exact same problem (and the single instrument part was truly bizarre--double barlines and text above the staff and so on behaved as if the measures had been inserted, but the actual notes were shifted over from the double barlines because the notes in the allegedly inserted measures were skipped)
In reply to Is there some way to… by procrastinator427
As I didn't say very well above. It can be a mistake to work on a score with parts open. It just doesn't always work. Should it? MuseScore isn't the only software that has problems. I learned long ago to not worry about parts until the score is done.
In reply to Is there some way to… by procrastinator427
procrastinator427 wrote > Is there some way to escalate this issue?
This forum's Issue Tracker is largely ignored since MuseScore 4 so it's best to log MS4 issues on Github.
If you don't have a Github account you'll need to open one to post to Discussions or Issues. Afterwards, once a pull request is made, you can track its progress in Pull Requests.
In reply to The Issue Tracker is largely… by scorster
Indeed, it is the purpose of this forum to enable discussion of a problem that someone is having. Often the problem is user error. If the discussion can determine an actual software problem, then Github comes into play. Otherwise, they could be flooded with erroneous requests.
In reply to Indeed, it is the purpose of… by bobjp
Exactly. Once a problem is identified and we have steps to replicate, then's the time to post to Github.
Well... the recommendation back in the day was this:
"Do not create parts until you are happy with the full score"
The software is fragile, however many versions we go through. So why make life even more difficult by creating parts early on?