musescore / musescore/MuseScore

Incorrect playback volume and note duration for long bass notes

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

@miiizen is already working on this.

Since May 27, 2026.

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

I am not sure how to reproduce this, I have tried to create e new score with just the bass track, but that didn't work, so, instead, I have isolated the problem on a project I was working on. The problem appears in every long note in the whole project, so I have included the whole project as well, as well as a video recording of how it plays back on my end. The issue crops up in both musesounds and MS basic, and it doesn't have to do with MIDI velocity (all notes register as 64), and if I delete the long note, and replace it by a short note, the problem disappears, but if I press any number on my numpad larger than a measure on a otherwise fine note, the problem comes back.

Supporting files, videos and screenshots

Nightmare.zip

In which versions of MuseScore Studio is this issue present?

recorded in 4.7.0-260513133, but it was present in the latest 4.6 version before updating

Regression

I was unable to check

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.