multi measure rests break in parts for unknown reason.
Reported version
3.0
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Once
Status
needs info
Regression
No
Workaround
No
Project
Why?? The multi measure is set to minimum 4 bars and the measures are empty... Idk why this is happening...
| Attachment | Size |
|---|---|
| Capture.PNG | 115.49 KB |
Comments
Please share the score, from just images it is impossible to diagnose
the score
It seems that hard system breaks cause all of the parts to have multi measure
rest breaks.
The more I test, the more elusive this problems seems to be.
I add the cello and violin parts, that's where the problem is on my laptop
In reply to I add the cello and violin… by Christophe Magnan
When I delete the parts and make parts again, all of the parts have the short multi measure rests. I tried several things to make it stop, but none of my theories panned out. For anyone else testing the problem, I tried
changing the minimum measure for a multi-measure rest
changing the system breaks
changing the measure numbering
Also
No system items forcing the breaks
No double bar lines
No key signatures (that I can see)
I haven't looked at the .mscx file, I'll leave that to someone who's more familiar with it.
In reply to When I delete the parts and… by mike320
Thx so much for your time, that's a weird problem...
What is the source of this file?
Created with Musescore (what version?), otherwise in another format (?)
If you turn mmrests off, you see some odd barlines too. I feel we've seen this before - the rests in part breaking where line breaks are in the score, and the strange barlines. And I feel the was fixed already. But a search isn't turning up anything.
If this score was imported form 2.x using an older beta, I'd be kind of inclined to guess, it's a bug already fixed that will require reimporting
found the issue I was remembering: #278891: Adding system breaks in imported score causes system breaks to act like section breaks. There was no real specific fix for that issue, I just made a leap of faith that this was connected to other 2.x import issues that were fixed, because in this case I did have access to the original 2.3.2 score and verified no issue existed importing it anymore. So, again, if this was a 2.x score and you still have access to it, try re-importing. If it works better, let's consider this issue closed as well. If not, please attach the score and we can set the status to "active" if we can reproduce. Otherwise, we'll leave it here as "needs info" until someone comes up with a reliable way to reproduce from scratch or by importing a score created in a released version.