Arpeggio and multi-measure rest
When you have an arpeggio that ranges into two chords located in two staffs (A grand staff) and press "m" to toggle multi-measure rest, the distance between those two staffs increases ruining the score appearance completely
| Attachment | Size |
|---|---|
| Captura de Tela 2022-09-14 às 9.57.00 PM.png | 276.47 KB |
| Captura de Tela 2022-09-14 às 9.57.22 PM.png | 278.28 KB |
| Captura de Tela 2022-09-14 às 9.57.28 PM.png | 270.83 KB |
| Captura de Tela 2022-09-14 às 9.57.35 PM.png | 262.64 KB |
| Captura de Tela 2022-09-14 às 9.57.40 PM.png | 262.11 KB |
Comments
It's hard to tell from just pictures, but I'm guessing you didn't add the arpeggio correctly - you might have just dragged it to look like it covers both staves. Instead, add to the top staff, then select the bottom handle and press Shift+Down to extend it properly. If I do that, I don't see any change. If I don't do that, then not just toggling multimeasure rests, but any full relayout will trigger extra space. Unless you disable autoplace for the arpeggio, which works, but isn't as good as adding correctly. only adding it correctly will allow it to adjust automatically if the staff distance changes later as you add more notes etc.
In reply to It's hard to tell from just… by Marc Sabatella
I actually did add to the top staff, selected the bottom handle and pressed shift+down
In reply to I actually did add to the… by Fábio Henrique3
IN that case, as mentioned, we really can't diagnose form just pictures, we'd need you to attach the score.
In reply to IN that case, as mentioned,… by Marc Sabatella
Both the Timpani clef bug and this Arpeggio bug I am talking about are related to the Musescore 4 (4.27.0 to be precise) which I am currently testing, I tried to report the bug on the button there which didn't work. Shall so I continue those reports in GitHub as you have said in the Timpani comment? I will attach the score so you can see what I am talking about.
In reply to Both the Timpani clef bug… by Fábio Henrique3
I've opened that score in the current nightly build of MuseSocre 4, pressed M, and there is no change. Are you perhaps using an older build? I'm not sure what "4.27.0" represents. There have been many bugs fixed over the past several weeks.
If you can still reproduce using the current nightly build, then yes, please post it to GitHub with precise steps to reproduce the problem. But, simply pressing "M" doesn't seem to be it.
BTW, this score is in continuous view; it's to be expected that staff distances won't reflect reality there, because you only have one long system and no page boundary to measure against. Still, in this example, I can't reproduce an issue.
In reply to I've opened that score in… by Marc Sabatella
It is weird nothing happened to you, I will see if there is another update. And yes, I know it is in continue view, but even though if those problems don't get fix it gets very frustrated to work, especially with really big ensemble. I will post it on Github