musescore / musescore/MuseScore

Can't copy notes when selected via "Select -> Similar"

Open
#28,584 2 comments 0 reactions 1 assignee View on GitHub

@bkunda is already working on this.

Since Jun 27, 2025.

needs review UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Intention:
If I want to merge two staves, the common sense approach would be to select only the notes on one stave (not the rests in between them, just the notes), then copy them to the other stave. I would expect this to effectively copy the notes (the pitches and durations) from stave 1, without altering the notes already written on stave 2.

Behaviour:

  1. Write a bunch of notes on a new score (or open a score with notes), with at least two staves
  2. Click on the first note in one of the staves
  3. From the context menu (right click) select "Select", then either "Similar" or "Similar on this stave"
  4. COPY the notes (either ctrl+c, or context menu "copy", or Edit menu "copy")
  5. Select another stave, then PASTE (either context menu, Edit menu, or shortcut)
  6. NOTHING HAPPENS!

Expected behaviour:
We should be able to copy paste ONLY the notes (not the rests) in order to merge two staves onto one.
I am aware of the "Implode" command, which work as expected. This, however, involves a few extra steps, as the notes of each stave are merged onto a separate voice, so now I need to convert all notes to the same voice and do some clean-up.
If copy-paste doesn't work when selecting only the notes via Select-Similar, then what is the purpose of this command, when applied to notes?

Supporting files, videos and screenshots

Image

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

4.5.2-251141402

Regression

Choose option...

Operating system

Windows 10 x86_64

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.