transpose doesn't work with linked staves
1. open attached score (note the C major scale)
2. transpose whole score to D major
Expected result: The pitched staff schould show a D major scale and D major key signature.
Actual result: The pitched staff shows an E major scale and a D major key signature.
Analysis:
Both staves get transposed up by a major second. But beeing linked staves, the actual notes are transposed twice.
Since the tab staff has no key signature, the key signature of the pitched staff is transposed only once.
Using 2a0c8de on Ubuntu 12.04
| Attachment | Size |
|---|---|
| LinkedStaffTransposeBug.mscz | 2.26 KB |
Comments
Hi heuchi
I think it's generally better to do a 1.3 score and then provide the steps from there. Scores saved in 2.0 currently aren't guaranteed to open correctly and I suspect that to be the case here.
Are you still able to reproduce?
I can reproduce it in df3b4a2
The original demonstration score does no longer load correctly indeed.
However, it's not easy to show the problem exactly the same way using a score created in v1.3, because v1.3 doesn't have the 'linked staves'-feature.
Attached is a file created in v1.3:
1. Open it
2. Go to the Instruments dialog and add a new guitar instrument and a linked TAB staff for it.
3. Copy the notes from the first instrument to the pitched staff of the newly created one.
4. Transpose whole score to D major.
After step 4 the new instrument behaves as described in the original report.
Reproduced - thanks :).
There is more to list with a 1.3 score (due to it being quite different to 2.0), but it's better in the long run. Hopefully, it will be less necessary when 2.0 and beyond is released :).
Actually, I wonder about this. My impression is that scores imported from 1.3 are special cased in a number of ways. I would think that where possible, it would be best to reproduce problems with a fresh 2.0 score to be sure a bug isn't just in the importing. Not that imported scores aren't important too, but I would think it better to demonstrate problems in the main code paths where possible. I think worries of incompatible changes to format should be largely behind us by now?
The problem can be reproduced in 65af8f7 under Windows 8 64-bit
For a testcase created in MuseScore 2.0 see the attached file.
To reproduce:
1. Open attached file.
2. Select all (Ctrl+A)
3. Press up arrow to transpose the score on semitone up.
4. Transposition is wrong. Notes are transposed twice as described before.
Temporary solution: Do not use ctrl+a to select everything. Select only standard staff, not a tab staff.
Fixed in bdc7ec245c
Automatically closed -- issue fixed for 2 weeks with no activity.