musescore / musescore/MuseScore

Problems with "Score and part synchronization" of title frame

Open
#31,802 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce
  1. Create a score for a jazz band (over 16 instruments).
  2. Add the title and composer in the vertical frame.
  3. Create the parts for each instrument.
  4. Go through all of the parts and, in each part:
    a. select the vertical frame and each of its components
    b. disable synchronization of Position, Style/appearance, and Text
  5. Return to the score. At this point the vertical frame and its components should be independent of the parts.
  6. Make changes to the vertical frame that shouldn't appear in the parts, e.g.:
    a. make the frame longer, e.g., height 120.
    b. Add a new text frame that, because synchronization is off, should only appear on first page of the score.
    c. Add an image that, likewise, should only appear on the score (the image I used is attached; for my purposes, it has to be reduced and moved, but I don't think that will affect this test).
  7. Examine all the parts. I found:
    • Some parts had a change in the size of the vertical frame. Using the height adjustment arrows in the properties showed that the frame was incorrectly displayed. An increment and decrement of the height returned the frame to the correct size.
    • The image and the text frame were added to the parts. Note that neither the changed size of the image nor the positions of either of the the additions were copied from the score even though the "Position" and "Style/appearance" toggles were set to "Synchronize with main score" in the parts' copies of those objects.

(optional) Undo changes and repeat steps 6 and 7 to see a different set of parts affected.

  1. Save and reload to see all the parts have the wrong size for the vertical frame.
Supporting files, videos and screenshots

Easy.mscz.zip

Image
In which versions of MuseScore Studio is this issue present?

4.6.3.252940956

Regression

I was unable to check

Operating system

Windows 11

Additional context

When the problem first occurred, I backed out the changes and tried again. The problem recurred except a different, small set of parts didn't have a wrong-sized vertical frame. I started fixing the parts, then decided that this issue should be written.

I have attached a mscz file (with the 'zip' added to allow uploading). This show the effect if the bug on the size of the vertical frame . I started correcting the file so the first 6 parts have been fixed. The rest of the parts are drawn with the wrong height. The properties show a height of 10.

I have just started to try working with a cover page, including an image and text that should not appear on the parts. The severing some widgets is an excellent enhancement. However, only having the selection in the parts may be reasonable on a score with even 6 parts, the effort to sever the parts from the score becomes cumbersome when having to be applied to more that 10 parts. The steps to reproduce this bug point out the need for some enhancements, such as:

  1. Score and part synchronization on the score. For global objects such as the title, breaking the synchronization in one place is much easier that in all the parts. Also, I've had to make some small positioning changes on the score to move staves closer together. Those changes should not be propagated to the parts, but finding the objects that need to be severed in the parts is prohibitive.
  2. I would suggest adding the 'exclude from score' button to more of the widgets, particularly texts and lines. An 'exclude from part[s]' button should be added to those widget on the score.
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.