Some properties are not synced correctly between parts and score

• Feb 23, 2020 - 21:04
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
MuseScore

Steps to reproduce: (Using version 3.4.2.9788 148e43f on Windows 10)

Case #1

1) Create a new score and add one instrument (eg. Bb trumpet)
2) File->Parts->All Parts
3) Go to the score view
4) Add some notes in a measure
5) Select the measure, inspector->Select notes->Chord->Small
6) Copy the measure and paste it into the measure after
7) Look at the Bb trumpet part (The attached file "Case1" was saved at this stage)

Result:
*) Only the second measure has small notes

Expected result:
*) The notes in both measures should be small

==========

Case #2

1) Create a new score and add one instrument (eg. Bb trumpet)
2) File->Parts->All Parts
3) Go to the Part view
4) Format->Style->Text Styles-Expression: Change the font to Arial Black and the colour to red
5) Add some "expression text" in the part view
6) Add some "expression text" in the score view

Result:
*) When text is added in the score, the text style of the score is used in the parts
*) When text is added in the part, the text style of the part is used in the score

Expected result:
*) When text is added in the score, the text style of the parts should be used in the parts
*) When text is added in the part, the text style of the score should be used in the score

7) When the files is saved and reopened the text appears as expected. Also notice that switching between using multirests using "M" in the part, seems to update the font properties.

Attachment Size
Case1.mscz 5.46 KB

Comments

• Apr 25, 2020 - 18:50

I have encountered a third case. In the attached score (Benny Goodman's "Let's Dance"), the five reed parts were originally Clarinet, Alto, 2 Tenors, and Bari. On the score page, I changed instrumentation to Clarinet, 2 Altos and 2 Tenors - first Tenor became second Alto and Bari became second Tenor. The transposed parts looked correct on the score. However, in the respective parts (still named Tenor 1 and Bari), the transposition moved many notes up an octave. The whole notes in measures 2 and 4, among other, show the problem.

I had first tried this by changing the Bari part to a Tenor and the same problem happened, except the part was correct and the score was not. I reverted this change, then tried making the changes from the score page. Because of this, I believe this is always reproducible. I'm using MuseScore 3.4.2.9788 on Windows 10.

I have also experienced both of the above problems.

Attachment Size
Let's_Dance-CAATT.mscz 147.49 KB

Reply

• Apr 25, 2020 - 19:32

I think that last one (third case) is the same as #303274: Instrument change to different transposition after creation of parts results in incorrect octaves. I'm not sure if this is related to the other issues you raised, even though they involve differences between score and parts. I recall there were some earlier different problems where instrument changes could result in odd octave shifts. Those were fixed but may have similar underlying causes. Unfortunately I don't understand what goes on "under the hood" to say for certain.

Reply

• Oct 7, 2020 - 20:00

I've found another case:
Steps to reproduce: (Using version 3.5.0.13199 43c553 on Windows 10)

Case #4:

1) Create a new score and add one instrument (eg. Bb trumpet)
2) Enter some quarter notes
3) Drag a dashed barline from the barline palette to any note (which is not on beat 1)
2) File->Parts->All Parts
3) Go to the Part view

Result:
*) The dashed barline does not appear in the newly created part

Notice that the dashed barline will show up in the score if it is entered in the part.

Reply