musescore / musescore/MuseScore

Calculation of odd lyrics line height and starting point doesn’t take font size and line height of even lyrics lines into account and vice versa.

Open
#33,978 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P2
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)

Description with steps to reproduce
  1. Enter four verses of lyrics (one note is enough)
  2. In Format > Style > Text styles > Lyrics even lines, increase the font size to ~16 pt
  3. Verse 2 lyrics are now overlapping verse 3 lyrics and the distance between verse 3 and verse 4 is disproportionately large

Expected behaviour: equal distance between all verses

Supporting files, videos and screenshots
Image

Lyrics line height.mscz.zip

Image

098. Hark! the Herald Angels Sing.mscz.zip

In which versions of MuseScore Studio is this issue present?

3.6.2 – 4.7.3, 4.7.4 latest nightly, main latest nightly

Regression

No.

Operating system

Windows 11, macOS 26.5

Additional context

Came up and was discussed in https://musescore.org/en/node/393558

Original poster was using odd lines for pinyin (set in Microsoft Himalaya) and even lines for Chinese (set in PingFang SC). The behaviour is the same for any font that uses different sizes for odd and even lines, but the inherent size of Chinese characters aggravates the problem.

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

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.