Wrong key signature for new instruments
Submitted by lasconic on June 3, 2010 - 3:51pm.
| Project: | MuseScore |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Windows XP pro
Nightly R 3121
Create a new score with a concert instrument, e.g. flute. Finish with only that one instrument.
Now choose Create - instruments - add a Bb clarinet - OK.
The clarinet does not come with two sharps. Same problem with Eb-instruments.
(if you choose all instruments from the beginning, there is no problem.)
Corrolary bug:
Actual result : The key signature is different for both staves
Expected result : The key signature should be the same
Playing with this bug, I often got a crash when closing musescore. I put in on critical. Will try to find step to reproduce the crash.
The variant in #1 is fixed by duplicating the key signature of the existing staff to the new staff (r3131).
I would like to see the original report more of an feature request. In the new wizard you can explicitly specify a global key signature for the score. This information is not available anymore when you later add a new instrument. The score key must be reconstructed/guessed from existing instruments taking into acount any transposition. I would like to postpone this to the next version after 0.9.6.
After some thoughts (and testing in sibelius), I'm not even sure the feature request is worth. Somebody else would like this behaviour?
I would expect that the new instrument had the same (concert pitch) key as the all the other instruments.
I still get different key signatures when I follow lasconic's instruments in comment #1 above. (Tested using r. 3137 nightly build, Windows 7)
This is going to come up in the next tutorial video I'm making, in which I add a bass guitar to the vocal parts in the score. At this stage it seems as though I need to add the key signature in manually into the bass guitar part when it gets added to the score. Is that correct?
Katie
Katie, I guess so. The issue is also present in version 0.9.5 but no one noticed until a few days ago.
That's OK - I'll just plan to include an extra step in the video (ie. manually add in the key signature for the new instrument). Thanks.