Chord changes made in transposed part are copied verbatim back to main score instead of being transposed back
Hi! I've found what I'm pretty sure is a bug. I'm writing for a jazz combo, so am mostly editing on the main score with all instruments in concert, then I look at the individual transposed parts occasionally to format and fix up any enharmonic issues.
However, when I modify chords in the transposed parts (e.g. saxes), I've noticed that they do not get transposed "back" in the main score - they are instead copied back verbatim! So if I write say a C chord in the main part, it shows up initially as Eb in the Alto Sax part (correct) - but if I open the alto part and change it to D#, the main score will now also show D#! Instead of staying as C, or maybe B# which would also be acceptable.
This is with the MuseScore-4.1.1.232071203 on OS X.
Exact steps to reproduce this:
- New score with cmd+N
- Create from template -> jazz combo
- Tick "concert pitch" button in bottom right
- Add chord to piano part e.g C^ Am G#^#11 Gsus in first 4 bars
- Parts -> open all
- Go back to main score, select all four chords, copy, then paste into Alto Sax stave
- Open Alto Sax part - it's transposed. Change the E#^#11 to F#^#11
- Go back to main score - the "concert" Alto Sax part now shows C^ Am F^#11 Gsus - the F^#11 hasn't been tranposed "back" to G#^#11
- (even worse: Edit the F^#11 (i.e. double click to change the text), but make no changes - just press escape - now in the Alto Sax part this will have changed to a D^#11!)
I've attached the main score and alto sax score generated by doing the above (minus the last step).
Any help with this would be much appreciated - thanks!
| Attachment | Size |
|---|---|
| test-Score_and_Parts.pdf | 39.04 KB |
Comments
Maybe a bug. Maybe not. MU4 is not the only software that has this kind of thing happen. But it is an ongoing thing that not all changes made in a part are always reflected in the score.
In reply to Maybe a bug. Maybe not. MU4… by bobjp
Thanks for the reply!
I think this is a separate issue - the changes in the part are reflected immediately in the score, but incorrectly (they are not transposed back to concert).
In reply to Thanks for the reply! I… by butterybiscuitpbass
In your score I suspect you have the concert button set, so you see it in concert in the score, but in the part (which does not have concert set) it is properly transposed.
In reply to In your score I suspect you… by xavierjazz
Yep - I have concert ticked in the main score but not in the parts.
The issue is that if I edit a chord in a part, say changing an Abb to a G, the main score would then also say G - when it should have been transposed back to concert so should say Bb (I.e. G up a minor third in the example I used with an Alto sax).
In reply to Yep - I have concert ticked… by butterybiscuitpbass
I don;t understand that, but the point I'm making is that if you want the 2 to match they both have to be set to concert. If you want the alto to be played by a human, it will need to be transpose, as is happeningd.
Double flat/sharp as accidentals will not be grasped by the program (I believe).
In reply to Yep - I have concert ticked… by butterybiscuitpbass
I don't understand that, but the point I'm making is that if you want the 2 to match they both have to be set to concert. If you want the alto to be played by a human, it will need to be transpose, as is happening in the part.
Double flat/sharp as accidentals will not be grasped by the program (I believe).
I've just tried this on Linux, with two different AppImage versions.
The issue is not present with MuseScore-4.0.1.230121751-x86_64.AppImage
The issue does occurs with MuseScore-4.1.1.232071203-x86_64.AppImage
In reply to I've just tried this on… by butterybiscuitpbass
Please report on GitHub, https://github.com/musescore/MuseScore/issues/new/choose
In reply to Please report on GitHub,… by Jojo-Schmitz
Thanks! I've reported it here: https://github.com/musescore/MuseScore/issues/19834 with a simpler reproducer too.