musescore / musescore/MuseScore

Piano sustain pedal has issues in playback/MIDI with tempo changes.

Open
#24,425 2 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Sep 3, 2024.

P2 playback regression MS3
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’m not sure if this issue has been posted before, but I’ve encountered a problem that mainly occurs when there’s a tempo change, usually after more than 30 bars.

In bar 33, the issue persists, and starting at 185 BPM, the sustain pedal playback shows unusual behavior. It might be related to tempo markings, but I’m not certain. The problem only happens during tempo changes. (The rit. markings are disabled and are just text, as are the fermata markings.)

This song was created entirely from scratch using MuseScore 4.4, but the issue also occurs in MuseScore 4.2 and possibly in the first version of MuseScore 4.0. This inconsistency can affect playback quality. Deleting and re-adding pedal markings does not resolve the issue.

I have attached the video and the link to the file for download.
https://musescore.com/user/69102031/scores/20451373/s/g5FvuE

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/f91fd1b8-93f2-4e1b-83de-64ec8ff03e94

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

MuseScore 4.4

Regression

I was unable to check

Operating system

Windows 11, MacOS Sonoma

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.