musescore / musescore/MuseScore

MIDI Real-Time "Advance to next note on key release (MIDI)" Preference not working in MuseScore 4

Open
#18,890 0 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Aug 4, 2023.

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

Description

Issue type

Other type of issue

Bug description

I am having a problem using real-time (foot pedal) for note entry in MuseScore 4. MuseScore automatically advances to the next note when the foot pedal is released, creating a note of twice the desired duration. This means that I can't enter one note per pedal press/release combination.

This behaviour is what I would expect if "Advance to next note on key release (MIDI)" is checked. However, this behaviour occurs whether the option is checked or not.

Steps to reproduce
  1. Uncheck Advance to next note on key release (MIDI) in Preferences > Note input.
  2. Press a note (say a quarter note) on the MIDI keyboard. It appears in the score.
  3. Depress the foot pedal. The note is entered into the score and the cursor advances to the next beat.
  4. Release the foot pedal. A second quarter note tied to the first one entered into the score. The cursor moves to the third beat.
    Similarly, depressing the foot pedal with no note pressed on the keyboard and then releasing it enters two rests rather than one.

Note entry works as expected in MuseScore 3. Pressing a note on the keyboard and then depressing and releasing the foot pedal enters a single note.

Screenshots/Screen recordings

No response

MuseScore Version

4.1.1

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

MacOs 12.6.7

Additional context

Problem also occurs in MuseScore 4.0 and 4.1.
This seems similar to Issue #17549.

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.