Playback not using pedal if started too far from the start of the pedal line.

• Jan 7, 2022 - 09:25
Reported version
S3 - Major

To reproduce bug, just have a score with a pedal line longer than 10 measures, and some notes in each measure.
Attached score is a tailored example.

Steps to understand the bug:

1) Start playback anywhere after measure 10.
Pedal will be absent.
2) Start playback from the top (Or anywhere within the first 10 measures)
Pedal will be present.
3) Start playback from after measure 10 again.
Pedal will be present.
4) Change literally anything in the score, and start playback after measure 10 again.
Pedal will be absent.

The starting point of the pedal line does not matter.

Workaround example:
If I want to listen to a new change I made in measure 30, with the pedal present, I would have to start and
stop the playback from the top (anywhere in the first 10 measures), and then start the playback for measure 30.
(Invisible overlapping pedal lines creates unintentional pedal lifts. It isn't a good workaround.)

Unsure about regression.
Could not find any other reports on this.

To sum it up, after starting the playback from the top, it applies the pedal to the first 10 measures, and then
just remembers that it goes on after that, so applies it to the rest of the score as it should. As soon as any
change is made, the playback changes (even if it doesn't actually change), and forgets that the pedal goes on
after 10 measures. This results in the pedal not working after measure 10, until you start it from the first 10 measures again.
This bug makes it extremely difficult to work on pieces that hold the pedal indefinitely.

If this was fixed, the playback would either apply the pedal to all measures that have the pedal line, or it would simply do what it does now, but regardless of where you start the playback.

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit):, revision: 3224f34

Attachment Size
(Pedal_Bug).mscz 14.8 KB


My guess is that this relates to the way the playback system breaks up a score into "chunks" before playing, so it only has deal with a small set of information at a time. And the problem then occurs if the start of the pedal is in a different "chunk" from the start point.

I'm not sure the MsueScore 4 playback system - which is still under development - uses the same concept, so this bug might already be fixed, or might end up coming back in a different form. Definitely something to test with development builds of MuseScore 4 as the playback system stabilizes.