Grand staff distance variable rather than constant; Style > Page setting has no effect
Reported version
3.0
Priority
P1 - High
Type
Functional
Severity
S2 - Critical
Status
by design
Regression
No
Workaround
No
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 26ad655
See attached score (carulli_anglaise.mscz). This looked fine in MS 2.3. Now big gaps have opened up within the staff/tablature systems – except for the first system on page 2.
Note: Selecting all and and pressing Ctrl + R seems to restore the correct spacing. But not sure why.
| Attachment | Size |
|---|---|
| carulli_anglaise.mscz | 27.13 KB |
Comments
I observe a change on last September 6.
As expected with: 0e6e208
Not with: 8035689
I guess an undesired effect of : https://github.com/musescore/MuseScore/commit/92e37502a8b4e987cb1e2bfa0…
See attached file. A related issue:
Expected result: Just a change to the text-line
Actual result: The system distance decreases.
Expected result: No change.
Actual result: The system distance increases but not to the original width.
The distance is changed correctly when resetting positions which is expected.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4191, revision: d9ccbb1
(BTW, please ignore the 25 Sep entry—posted by mistake).
The nominal "Grand staff distance" (in Format > Style > Page) is unchanged. But the actual grand staff distance in the 3.0-dev document window is still larger than it was in 2.x.
In the attached score (use the reset option), you can see that "Grand staff distance" varies from system to system, rather than remaining constant.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4839, revision: cf1f5ce
Referring again to "Chansonette". The Grand staff distance (GSD) should be constant. But it is being affected by score objects such as lines. For example, if you delete the hairpin in measure 8, the GSD shrinks for that system. If you move the hairpins in measures 14 and 15, down, the GSD increases for that system.
that distance is a minimum setting now in 3.0, more space as needed to avoid collisions
This score looks badly laid out in 3.0-dev compared to 2.3. Grand staff distance needs to be fixed. And there is another problem. Go to Format > Style > Page. Try adjusting the "Grand staff distance." It has no effect.
In reply to This looks so bad in 3.0-dev… by geetar
With two exceptions it looks fine and consistent to me. The "TAB" at the beginning of the Tablature staff is fubar. The final system looks like the staves are closer than all of the other systems, but it's not a terrible difference.
I don't see any significant differences in the score provided in the opening in 2.3.2 vs 3.0
And a linked nieten and tab staff is not a grand staff, so its setting isn't relevant. "Open issue" is not a valid status either BTW
In MS 2.x, Grand staff distance applied to all staves linked to a single instrument. The fact that it does not apply to staff/tab in 3.0-dev is a bug.
Or it was a bug in 2.x...
Does staff distance make a difference (if grand staff distance doesn't) ?
Yes, "Staff distance" does affect staff/tab in 3.0-dev, but it didn't in 2.x (and shouldn't in 3.0-dev). "Grand staff" doesn't just refer to keyboard staves but to any system with staves sharing the same instrument. That covers staff/tab, so it should be governed by "Grand staff distance."
In reply to Yes, staff distance does… by geetar
I disagree. Grand staff refers to independent staves for the same instrument, not (necessarily also) to linked staves, which is an entirely different concept.
But whether staff distance or grand staff distance, not being constant but autospacing as needed definitely is by design
Deleted.
If they are not linked, then grand staff distance doesn't apply at all, they are totally independent instruments. Just by coincidence with the same name and sound, but different channels in the mixer.
In this context, the term "linked" refers to the fact that two staves are mutually updating; and the term "unlinked" means that the staves are not mutually updating (e.g. the example score, Chansonette). In both cases the staves go throught the same instrument.
OK, I see you can add a (non-linked) staff to a Guitar and turn it into tablature, but does this make any sense?
Still, this issue is about "Grand staff distance variable rather than constant" which is by design.
But indeed adding a 2nd staff to any instrument doesn't seem to make it a grand staff, irrespectively of staff type (and it is still debatable whether in the case of different staff types this is to be considered a grand staff, even if it was in 2.x), this IMHO is a bug and should be dealt with separately.
Seems not even for a 3 staff organ this is working properly, it seems to only consider the top 2 staves a grand staff.
see #281127: Grand staff distance excludes tablature and organ pedal staff
"OK, I see you can add a (non-linked) staff to a Guitar and turn it into tablature, but does this make any sense?"
IME, linked staff/tab is not flexible enough to cope with the full range of notation required: You cannot notate most harmonics, or ottavas; you have to hide duplicated symbols, you cannot vary the notation in one staff from the other. Non-linked staff/tab is not limited in this way.