musescore / musescore/MuseScore

Wrong placement of grace note after when followed by a repeat sign

Open
#28,435 2 comments 0 reactions 1 assignee 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. Add a note on the last beat of a bar and add a grace note after
  2. Add a left repeat sign at the end of that bar

Actual behaviour: The grace note is placed correctly in step 1 but moves to before the note when the repeat sign is added in step 2. If steps 1 and 2 are reversed, the grace note is placed incorrectly (before the note and not after) right away, see the video below.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/4ae960d4-e52e-4a78-99b4-52ae99957437

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

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

No (same all the way back to at least 3.6)

Operating system

Windows 10

Additional context

Deleting the repeat sign restores the correct position of the grace note. Also, the issue did not occur when adding a right repeat sign instead of a left one.

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.