musescore / musescore/MuseScore

Add option to paste over existing content without erasing it

Open
#20,048 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

I advocate for an add-functionality.
The notes that are copied onto the clipboard, should be able to be add to a bar, without the notes that already are in that bar, being deleted.
So if you have The Notesequence C B A assigned to the flutes and for example E E C, to the oboes, but later decide you want both to be played by the flutes, you just copy the E E C sequence and add it to the C B A sequence.
So The flutes play C and E together, then B and E and then A and C.

Problem to be solved

If you want to copy notes to a bar that is already filled with notes, you can't do so without deleting the notes that are already in that bar.
This means that there is a need to either create another flute section in the score or go through the effort of adding the notes manualy.

Prior art

No response

Additional context

You could further add on that feature and give the option off adding an octave higher or lower.
This way, the effort of for example writing melodies which are doubled in another octave, much easier.
You could just:

  1. Copy the melody
  2. Right click the start of the melody
  3. Click on "Add an octave lower/higher"

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

Start by reviewing the proposed workflow in the issue: copying a note sequence, selecting the destination bar, and choosing an add action. Define the expected behavior for combining existing and pasted notes, including the optional octave shift, then add coverage for the completed behavior; no files or tests are identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.