musescore / musescore/MuseScore

Pedal at end of section is sustaining through into the next section

Open
#27,280 1 comment 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Mar 21, 2025.

P2 playback regression MS4
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
  1. Open score
  2. Select anything before measure 392
  3. Play
  4. Hear that the pedal that is supposed to end at the section break is sustained through it

Expected behaviour:

Pedal stops at the section break and the next section doesn't sound pedaled until it's marked as such.

Supporting files, videos and screenshots

Muse Sounds:

https://github.com/user-attachments/assets/49ebf1bc-0a00-4994-8cce-9d3199fc911b

MS Basic:

https://github.com/user-attachments/assets/24a9565b-59bd-433c-b971-632d651ae1bb

I tried reproducing the problem in a simpler score than this Beethoven sonata I noticed the issue with, and I couldn't, so here's the score of the Beethoven sonata:

Piano Sonata no. 5 in C minor Op. 10 no. 1 (Little Pathetique).zip

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

MuseScore 4.5.0

Regression

Yes, this used to work in MuseScore 4.3.2

(can be rechecked on MS4.3_Piano.Sonata.no.5.in.C.minor.Op.10.no.1.Little.Pathetique.zip)

Operating system

Windows 10

Additional context

Score was originally made in MuseScore 4.2.1 in case that matters at all.

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.