musescore / musescore/MuseScore

Copy/pasting tied notes in chords using selection filter is buggy

Open
#31,922 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2 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
Symptom 1 (in video, 0:00–0:07)
  1. Create a single note tied to the the top note of a chord in the next beat
  2. Select the measure. In the selection filter, select only 'Top note' (and have 'Include single notes' on)
  3. Copy and paste the selection into the next measure
  4. See the notes are not tied together
Image

Note that this is not broken for individual notes in chords where all notes are tied (in video, 0:08–0:22).

Symptom 2 (in video, 0:23–end)
  1. Create a two-note chord tied to a three-note chord, where the three-note chord has an untied note at the bottom of the stack
  2. Select the measure. In the selection filter, select 'Top note' and 'Bottom note' (and have 'Include single notes' on)
  3. Copy and paste the selection into the next measure
  4. See that an invalid slanted tie is between the two chords
Image
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/27c34e40-14c8-4287-b7bf-a8c62ed61a67

In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

No.

Operating system

macOS 15

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.

Research direction

Reproduce the issue in MuseScore Studio 4.6.5 using the two chord-and-selection-filter scenarios described in the report. Trace the copy/paste handling for filtered chord selections; done means single-note ties are preserved and no invalid slanted tie is created when only the top and bottom notes are copied.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.