musescore / musescore/MuseScore

Some notes aren't played when under a slur

Open
#30,309 2 comments 0 reactions 3 assignees View on GitHub

@bkunda is already working on this.

Since Oct 14, 2025.

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

Description

Issue type

General playback bug

Description with steps to reproduce

Use Muse Sounds

Flutes and oboes (and possibly more) in all dynamics:

  1. write melody
  2. double an octave up/down in the same voice
  3. add slurs
    actual behaviour: the lower note is much quieter if it's even played at all at the end of the slur
    expected behaviour: both notes should follow the given dynamics (as well as the instrument can) and the last note under the slur should not disappear

Violin section (and possibly more):

  1. write melody with slurs
  2. set dynamic to piano (this happens less with louder dynamics)
  3. apply "Classic Phrasing" flag
    actual: the last note is sometimes very quiet
    expected: the last note should follow the given dynamic
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/9256db7a-1235-43a2-ace6-a5b08dab6173

https://github.com/user-attachments/assets/f9bc3204-7ea3-4b18-97b8-6dba57829a2e

slur bug score.zip

While making this minimal file I checked MS Basic and it doesn't have the issue
The violin section example had the problem when I initially put it in the score but it magically fixed itself when switching sounds to violins 1 and back to violins 2 (the screen recording is of violins 1 in a different score)

In which versions of MuseScore Studio is this issue present?

4.5.2-4.6.0

Regression

Choose option...

Operating system

Windows 11

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.