MuseScore
MuseScore copied to clipboard
Better Copy/Paste: Measure Linking
Your idea
I wanted to flesh out the idea made in https://github.com/musescore/MuseScore/issues/20918
My flow would greatly benefit from a feature that allows for dynamic measure linking across different parts and sections in the score.
Benefits from a measure linking system:
- Reduces editing time to standardize dynamics, articulations, rhythms, notes
- Allows for rapid editing of melodies that are shared between multiple instruments
- Ensures that the intention of harmonies are clear and consistent
- Ensures that individual note changes from another instrument are clear and consistent
A link would consist of the following:
- source part name/id
- measure/beat number
- duration (number of measures/beats)
- modifications (transposition, individual note changes, articulations, dynamics)
Problem to be solved
These are common examples that I wish could be sped up and include some form of verification:
- The 1st oboe part copies an 8-measure section from the 2nd clarinet part, but then I changed the the 2nd clarinet part, and now I need to remember to update it in the 1st oboe part.
- The 2nd trumpet part should always copy the 1st trumpet part, but should be transposed down two diatonic steps.
- The piccolo part should always be in unison with the 1st flute part, but should have occasional individual notes that are up an octave.
Currently, in MuseScore, when you copy and paste material from one part or section to another, the pasted material is static. If you later edit the original, the copied sections remain unchanged, which can lead to inconsistencies, especially in large scores. This becomes cumbersome when editing recurring musical phrases or orchestrating similar harmonies for multiple instruments.
A measure linking feature would save significant time for composers and arrangers by reducing the need for repetitive manual updates, making it easier to maintain consistent thematic material across an entire score.
Prior art
I don't know if other notation apps allow this, but basically all DAWs support this in some capacity. Also, I am used to the software world, in which DRY code is the norm.
Additional context
I am a computer chip engineer, and the number one thing that is clear is that humans constantly make mistakes. Having bugs in software is fine, because you can just release an update. However, a bug in a computer chip usually cannot be patched, and is often a several million/billion dollar mistake. Similarly, many composers likely cannot afford to mass-reprint a part/score if mistakes are found. Therefore, I believe that notation software should introduce methods to verify that your intent matches the sheet music.
Since this is a fairly large change, maybe this feature should start as a plugin that could be incorporated later? I am happy to hear thoughts on this.
Thanks!
Checklist
- [X] This request follows the guidelines for reporting issues
- [X] I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
maybe this feature should start as a plugin that could be incorporated later?
Implementing this with a plugin is not really possible with the current plugin API, and would be very error-prone. A better idea might be extend MuseScore's existing logic for linked staves and linked parts (and linked "system objects").