Instrument change to different transposition after creation of parts results in incorrect octaves

• Apr 2, 2020 - 13:21
Reported version
S3 - Major

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit):, revision: 148e43f

  1. Create a score with a non-transposing instrument - e.g. flute
  2. Enter a chromatic scale extending over more than one octave
  3. Create parts
  4. In the score right click on first measure and select score properties
  5. Change instrument to a transposing instrument - e.g. Bb clarinet

Result - all occurences of Bnat and Bb concert are shown in the part an octave too low, but are shown in the correct octave in the score. The playback pitch is correct however in both the score and the part. See attached score. Test.mscz

If a differently transposing instrument is selected at step 5 different note are affected. For example if Eb clarinet is selected D Db and C concert are shown in the part an octave too high, but again sound at the correct pitch.

Similar things happen if the change of instrument is made in the part rather than the score, but then the score shows the incorrect octave while the part shows the correct one. i.e. the score or part shows the correct octave if that is where the instrument change is made, but the other element (score or part) where the instrument change was not made shows the incorrect octave.

Workaround is to make instrument changes before creating parts.

Attachment Size
Test.mscz 5.87 KB


I originally added a comment under #301540. @SteveBlower pointed out that this is the correct bug for my problem. I cannot reattach the score because I already corrected it. Below is a summary of my original comment. The score shows transposition from Eb to Bb and from Bb to Eb.

In the score attached to #301540 (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 on Windows 10.

In reply to by Jojo-Schmitz

Apparently transposing a staff on either the score or in a part doesn't handle all 12 half-tones correctly in the other (score to part or part to score). Some (most?) are handled correctly, but what appears to be a contiguous group are in a wrong octave. For example, E in any octave transposed correctly, but any F was transposed an octave higher than it should have been.

The linked trouble report, #301540, has two other cases of problems with some properties not being synced from the score to the parts.