musescore / musescore/MuseScore

Lyrics: Extender lines go too long (after saving file / editing another note)

Open
#26,416 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving needs review
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

Lyrics extender sometimes extends beyond its place into the next text.

Put down three notes, where we want the first word to extend the first two notes, and the second word of lyrics to start on the third note. Putting in an extender "_" on the middle note usually works fine, but sometimes, after either saving the file or editing a different note, the extender changes size, becoming so long that it overlaps the second word of lyrics, on the third note.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/43edeb9c-fe89-41fc-b337-2d356d3220f6

If you rename be_still_and_know.zip to .mscz you can see there are examples where MuseScore handles it fine and other places where it consistently goes wrong.

2361_be_still_and_know.zip

What is the latest version of MuseScore Studio where this issue is present?

OS: Ubuntu Core 18, Arch.: x86_64, MuseScore version (64-bit): 3.6.2, revision: github-musescore-musescore-3224f34

Regression

I was unable to check

Operating system

only checked on Ubuntu 22

Additional context

No response

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.