Skip to content

Unexpected space increases between staves when applying second voice icon, non-reversable #32372

@mskutsch

Description

@mskutsch

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. When converting a two-note chord with single up-stem to two voices (with one up-, one down- stem), using the 1st and 2nd voice icon
  2. Sometimes, but not always, this causes the stave below to move down one step, increasing distance beween staves unnecessarily, Changing the next chord in similar way causes stave below to move down one more step, etc. so that first two, and eventually only one (4-stave) system fits on each page (rather than 3 systems fitting nicely).
  3. This cannot be reversed by using the un-do icon; if you do this, the stave below just moves even further down.
  4. This can be seen in attached screenshots. On first page the operation has been successful, many chords have been split into two voices, but the problem starts if you try doing this in first bar of second page.
  5. Screenshot 1 shows correct behaviour on page 1, and up-stem for the chords in Bar 18, page 2. Screenshot 2 shows what happens when the lower notes are is given a down-stem in Bar 18, and please note the gap between staves, which only increases as more notes are treated with down-stems

Supporting files, videos and screenshots

(screenshot 1)
Image

(screenshot 2)
Image

(screenshot 3)

Image

In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Windows 11

Additional context

I first checked in the Forum and was advised that this must be a bug and should be reported (HildeK)

I hope you can access the screenshots from the link pasted above. I would have preferred to send the Musescore file itself but your system evidently cannot read 4.6.5 yet, at least it could only identify files from earlier versions, on my computer.

My email contact is mskutsch@ciga.unam.mx if needed for contact.

Checklist

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions