musescore / musescore/MuseScore

Stem direction of close invisible notes in other voices changes spacing for visible elements

Open
#22,784 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Engraving bug (incorrect score rendering)

Bug description

When you have a note in one voice, and an invisible note in another voice at the same time that is close to the visible note, the stem direction of the invisible note changes how the visible notes look. It can add extra space if the stems are not going in the same direction. This is especially apparent with accidentals. If the invisible note is lower, it will add extra space after the note, and if it is higher or in the same space, it will add extra space before.

Steps to reproduce
  1. Add a note in voice 1, along with another closeby note in voice 2 on the same beat
  2. Make the note in voice 2 invisible
  3. Change the stem direction of the invisible note with "X"
  4. Observe changes in the distance between notes even though the thing you are changing is invisible
Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/21023353/92be4a49-6f9c-45ff-917d-0f974bba3d14

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.0-241231433, revision: github-musescore-musescore-5f36e74

Regression

No.

Operating system

Reported on Windows 11

Additional context

It seems like the algorithm is trying to make the stems line up even though the element is invisible and should be completely ignored by the spacing. The distance where the invisible notes affect the visible ones seems to be .5 sp

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.