[Feedback Form] Collisions between systems possible if bottom staff of upper systems is invisible

Bottom lyrics margin still exists, and in fact I always have to decrease (to at most the 3.0 default) it when importing 2.x scores, for closed score SATB staves to be too far apart

Thanks Jojo. You are correct in that the bottom lyric margin is overall functional (and I love the auto-spacing approach adopted in the new version, even though I have to reduce my margin value as you mention). My application, however is a bit more specific. I'm creating a lead chart with only one staff line and am looking to see if there is a way to attain variable system spacing in the chart to be more efficient with space. For O Come All Ye Faithful for instance, I have multiple level of text below the staff for the verses (think hymnal), but in the refrain is the same each time, requiring less vertical space. I'd like to find a way to get variable spacing such that the verses have enough room but the refrain uses no more margin than needed.

It may seem like a minor issue, but in many cases for me it is the difference between one or two pages for the musicians, which becomes significant when doing songs back-to-back.

I've attached two files to highlight the issue, made with Versions 2.3.2 and 3.0.

You shouldn't need to change any settings to get that - this should happen by default. If you are finding otherwise, can you attach your score?

My pleasure; the score is attached. And, as a sidenote, thank you for all you have done, Marc, in bringing the vision of Musescore to reality. So many have benefitted from your work, myself included.

The score is attached. Here is the process:
1) Open Score in M3
2) Go to 'Instruments" and uncheck the bottom Music XML part (which is effectively the bass clef; I do it this way to make lead sheet creation simpler).
3) The spacing issues should be immediately apparent (another file attached to show what I see). The lyrics butt up against the bottom of the staff and ignore the chords, causing an unsightly overlap of text. This is the point where I used to be able to adjust the spacing via the bottom lyric margin to get the results depicted in my last post. This no longer seems to work. I may be ignorant, however of another way to accomplish the same thing, (Note also how the ending from the second part remains in the , but this is a separate issue).

I'm happy to provide further information if needed or to learning a new way to do the same thing. Happy New Year.

If you delete the voltas in the second staff, they will look better when you follow my instructions. They are not normally shown in conductors scores on all staves.

If you create parts, use file->Parts then click New All and OK both parts will look good.

There is however a bug that needs fixed, and the Min Bottom Margin for the lyrics seems to be trying to take into account the invisible bass staff.

Thanks mike320, I will note the matter on the voltas and am familiar with the parts system, which I use for larger scores. I hadn't thought of using it for a two-part score; this should be a fine workaround for the time being. Good suggestion.

I haven't tested other margins, but from experience I suspect this isn't the only margin being ignored if the adjacent staff is invisible.

I plan to look at this, if anyone can think of other cases where we fail to consider invisible staves properly, let me know. There is #280458: Autoplace allows collisions between systems with invisible staves which may well be a duplicate of this (need to investigate).

For the record, the problem does not exist within systems, only between systems. So as I understand it, it's the system skyline we aren't getting right. And, it's not just lyrics, but even a note far below the staff will be allowed to extend into the system below if the bottom staff of the system is invisible.

And what info do you need?

Sorry, thought at first I couldn't reproduce until I understood the issue was with systems, not staves.

https://github.com/musescore/MuseScore/pull/4693

We were checking for "hidden" staves (hide empty staves) but not "invisible" ones (edit / instruments). Trivial fix.

Fixed in branch master, commit 80a68ce51a

fix #280561: invisible staves cause collisions

Fixed in branch master, commit 423873d1e5

_Merge pull request #4693 from MarcSabatella/280561-invisible-staff-skyline

fix #280561: invisible staves cause collisions_

Fixed in branch 3.0.x, commit b2a5ff9bdb

_Merge pull request #4693 from MarcSabatella/280561-invisible-staff-skyline

fix #280561: invisible staves cause collisions_

Automatically closed -- issue fixed for 2 weeks with no activity.