Editing in MasterScore not Always Carried Over to Parts

• Jun 29, 2018 - 08:37
Reported version
2.2
Type
Functional
Severity
S3 - Major
Status
by design
Project

This is being reported as a bug, on the basis that music notation software of the caliber of MuseScore need not present hard-working users with this...

In masterscore in (say) a trumpet part, after inserting a hairpin with required start and end dynamics, the user is often then presented with overlaps (which, other than for phrase marks, are never really permitted in music notation) to remove piecemeal. The laborious task is then to:

  1. Lower the hairpin so that it is not overlapping with tie or phrase marks.
  2. Lower the right-hand dynamic marking by the same amount.
  3. Lower the left-hand dynamic marking by the same amount
  4. Select the hairpin.
  5. Drag the right-hand end of the hairpin horizontally so that it does not overlap with the right-hand dynamic marking.
    1. Drag the left-hand end of the hairpin horizontally so that it does not overlap with the right-hand dynamic marking.

Phew. All done. On to the next set of collisions...

...Except, that having already done this laborious tidying work in the masterscore, the user is then presented in the extracted part, with their tidied work from the masterscore, looking like this:

mess.gif

...Everything has to be done all over again in the part.

To avoid everything having to be done piecemeal, twice, Musescore needs to be programmed to carry-over to the respective part, any programmed removals of overlaps in the masterscore.


Comments

Status (old) active by design
Status active by design

No, not at all: Content needs to get synced between master score and existing linked parts, but layout should not (it does get copied accross if you (re-)create the part though). And the next major version (try a development build from the master branch) will have a better layout with collision detection/avoidance, so these kind of manual tweaks should not be needed anymore.