Skip to content

(marching?) Percussion input does not respect the selected input voice. #34152

Description

@duck57

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

I'm unsure whether this applies to all percussion inputs or only to the marching percussion.

Steps to reproduce

  1. Enter percussion notes to the default voice 1.
  2. Change to voice 2 and add other notes in the same measure.

Expected behavior

The voice 2 notes appear in the same measure as the existing notes.

Actual behavior

Voice 1 is overwritten by the new notes. None of them enter on voice 2.

Inconvenient workaround

Enter your voice 2 notes first (on voice 1), then select them and change them to voice 2. Now, enter your voice 1 notes. This workaround does not function properly when editing voice 2 after voice 1 has been added.

Supporting files, videos and screenshots

Screen.Recording.2026-07-10.at.16.52.07.mov

In which versions of MuseScore Studio is this issue present?

OS: macOS Sequoia (15.7.7), Arch.: arm64, MuseScore Studio version (64-bit): 4.7.4-260706075, revision: github-musescore-musescore-7688c00

Regression

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

Operating system

mac OS 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

Metadata

Metadata

Assignees

Labels

UX/interactionneeds reviewThe issue needs review to set priority, fix version or change status etc.regression MS3Regression from MS3 (3.6.2)

Type

Fields

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions