Compatibility of tranposing scores from 0.9.5 (0.9.6 regression)
Steps to reproduce bug
1. Open a transposing score created in 0.9.5 or earlier (see "Transposing score from 0.9.5.mscx")
2. Click on the "Concert Pitch" button
Expected behavior: The D in the transposed score should display as C in the concert pitch score
Actual behavior: The D displays as D double flat in the concert pitch score
Discussion: We need to have a way to migrate old MuseScore files which contain <transposition>-2</transposition>
to the new format.
MuseScore version: r. 2659 nightly
(Operating System: Windows XP)
Attachment | Size |
---|---|
Transposing score from 0.9.5.mscx | 4.27 KB |
Comments
The old "transposition" equals to the new "transposeChromatic" value. Whats missing is to calculate a suitable "transposeDiatonic" value to determine a valid interval for the new scheme.
The following table comes from an earlier unpublished draft of the non-lossy transposition article . It maps maps each semi-tone with its most likely interval.
implemented in rev. 2661
It works well for transposition of an octave or less. However there are a few instruments that transpose by more than an octave.
To test this:
Expected behavior: The note displaying after step 4 should be the same as the note displayed after step 2.
Actual behavior: The transposition loosing the correct pitch spelling.
Discussion: Tenor sax transposes by 14 semitones. This a major ninth (equivalent to a perfect octave (12 semitones) plus a major second (2 semitones).
EDIT: added attached file
Is this the same problem I just had in 0.9.5 when I transposed a piece from G to F and what should have been Bb were all shown as A#? If so it doesn't need raising as an issue.
fixed in rev. 2716.
#5: yes, i believe the current version behaves better
Automatically closed -- issue fixed for 2 weeks with no activity.