Program will not show courtesy key signatures. Courtesy key signatures have been selected in "Inspector" and "Style". When creating one in the Master Pallet, it will not appear in the key signature pallet window to be selected.
Which version of MuseScore exactly (and for good measure on what OS) and can you share the score shoing this behavior along with a step by step procedure to reproduce?
(and please don't assign to yourself, unless you plan to fix yourself too, actually it might have been better to ask in the forum first before entering an issue)
I am using Musescore 2.0.2 on a PC Desktop with a Windows 7 OS. I attached the chart I am working on. The issue arose when I changed keys at measure 64. I checked both the "Styles" and "Inspector" menus and the "Courtesy Key Signature" boxes were selected. I then went to the Master Palette and created the key signature I wanted. I then went to the "Key Signature" pull-down menu to select the key signature I created, but the newly created signature was not shown. The problem has appeared in other charts that I have worded on recently, but I did not think to send a bug report.
Again: please don't assign to yourself, unless you plan to fix yourself too...
Why should there be a courtesy accidental? This is in the middle of the system, courtesy signatures (usually?) appear at the end of a system, if in the change is on 1st measure of the next system. And it does here too, if you apply a line break to measure 63
Indeed, a courtesy key signature is one occurs at the end of a musical line if a key change occurs at the beginning of the next line. That is not the case here, so courtesy key signatures are not relevant.
I am guessing you were actually hoping for a natural sign to appear in the key signature to indicate that one of the previous flats is being cancelled. That's a otally different thing, and it is controlled by a different option. See Style / General / Accidentals; the options there control the appearance of these naturals.
In the future, it is best to use the Support forum to ask for help using MuseScore, and don't file a bug report until it has been confirmed that what you are seeing is actually a bug and not just a misunderstanding
Comments
Which version of MuseScore exactly (and for good measure on what OS) and can you share the score shoing this behavior along with a step by step procedure to reproduce?
(and please don't assign to yourself, unless you plan to fix yourself too, actually it might have been better to ask in the forum first before entering an issue)
I am using Musescore 2.0.2 on a PC Desktop with a Windows 7 OS. I attached the chart I am working on. The issue arose when I changed keys at measure 64. I checked both the "Styles" and "Inspector" menus and the "Courtesy Key Signature" boxes were selected. I then went to the Master Palette and created the key signature I wanted. I then went to the "Key Signature" pull-down menu to select the key signature I created, but the newly created signature was not shown. The problem has appeared in other charts that I have worded on recently, but I did not think to send a bug report.
Again: please don't assign to yourself, unless you plan to fix yourself too...
Why should there be a courtesy accidental? This is in the middle of the system, courtesy signatures (usually?) appear at the end of a system, if in the change is on 1st measure of the next system. And it does here too, if you apply a line break to measure 63
Indeed, a courtesy key signature is one occurs at the end of a musical line if a key change occurs at the beginning of the next line. That is not the case here, so courtesy key signatures are not relevant.
I am guessing you were actually hoping for a natural sign to appear in the key signature to indicate that one of the previous flats is being cancelled. That's a otally different thing, and it is controlled by a different option. See Style / General / Accidentals; the options there control the appearance of these naturals.
In the future, it is best to use the Support forum to ask for help using MuseScore, and don't file a bug report until it has been confirmed that what you are seeing is actually a bug and not just a misunderstanding