Undesired Chord Font Changes

• Oct 14, 2012 - 02:07

musescore 1.2
windows 7
no font selection made. i use the default font for everything.

place chord names in the score by selecting a note on a staff, then either using the pull down menu or typing ctrl-k. that works beautifully.

go work on some other part of the score.

go back to a previously entered chord name,, double click on a chord name to correct a mistake, i.e., change Ab7 to Abm.

place the cursor to the right of the "7" and backspace, then type the "m" on my keyboard.

the resulting "m" appears in a different font, usually the jazz font, sometimes in something that looks like arial, not in the default font.

to get the right font for the 'm" i have to backspace over all the characters in the chord name, then reenter the entire chord name.

while not a major bug, it is a nuisance.

iowaplayer


Comments

It would help if you posted a sample score and mentioned which specific chord demonstrates this behavior. What you describe is not the normal behavior, but I suspect what you are seeing has to do with the fact that MuseScore treats chird shmbols it doesn't recorgnize differently than ones it does. I amguessing you have a mistmatch between the font you selected for the chordname text style and the font used by the chord descriptorfile ifypu haveselectedu der the chordnma egeneral style, and that recognized chords are showing up in one font and unrecognized chords other. But without seeing the score, I can only guess.

Btw, the "default font" depends on how you created your score - different templates use different fonts. But if you didn't uses templte, and didn't specifically change fonts or apply a style, chordnames would default to Times New Roman on Windows.

In reply to by iowaplayer

Hmm. That's not a jazz font; it is "mscore1", the font used for certain music characters. In this case, the "m" is the same "m" that is used for dynamics like "mf" or "mp".

As far as I can tell, this is happening because of the flat sign in the chord symbols, which is rendered in that font. Normally, you type a "b" into a chord symbol and MuseScore automatically turns it into the flat sign, but then if you go back to edit the chord, it turns back into a "b". For some reason, though, your flat signs have become permanently embedded into the chord symbols - they aren't changing back to b's when you edit the chords. I've never seen this happen before, and am not sure what might have caused it. How did you create these chords? You didn't by chance type these chords by using the "flat" sign from the text symbol palette rather than simply typing "b" and letting MuseScore do its job, did you? That would have this effect. So might importing the score from a poorly constructed MusicXML file.

As it is, your chords are all showing up as being unrecognized, and you can verify this by right clicking a chord and choosing Harmony Properties. If a chord is recognized, the Harmony Properties dialog will show you relevant information about the chord - the root, what type of chord, what extensions / alterations are present. But your chords are all showing up as generic "C" chords - except for the few chords that do not contain accidentals, like the chords that happen starting around measure 17.

So if you have an idea as to how these chords all got into this unrecognized state, then I'd say, don't do that again - but let people know what it was, so others can avoid the same mistake, and perhaps MuseScore can be updated to prevent that from happening. If you don't know how your score got into this state, could you explain in more detail how you created it, and specifically, how you entered the chords?

In reply to by Marc Sabatella

marc,

btw, the reason that the piece i attached is noted in the key of c is that i copied it from a score for this song.

when i do a score for harmonica ensemble, i usually put in the chords by name, and put all the notes in the chord on the staff so i can play them back.

when i want to just get a chord harmonica chart, i put in single notes to define the time of the chord, and the chord name over head.

the reason for keeping the staff in c is that if i put the chord staff into the key of the song, entering the individual notes of the chords gets very confusing because of how musescore automatically shows notes based on the key of the staff. in c i feel like i have much better control over the notes i input to the chart, without getting tripped up by the auto-note functionality.

trying to put a b major chord into notes on a staff marked in the key of b is a LOT different than putting the same chord in on a staff marked in the key of c.

for my purposes, when i send out the parts, the chord harmonica players don't much care what key the song is in as they simply play the chord names. the other harmonica players don't care what the chord staff says because they don't play that staff.

iowaplayer

hi marc!

i create the chords by selecting a note, then using the pull down menu, create text, chord name or by entering ctrl-k and then entering the chord name.. and yes, i use the palette to put in the flat symbols. i've never tried to import any files into musescore. all my work has been hand-entry.

i'm not real sure why i shouldn't enter chords the way i have been, other than this font problem. what are the benefits? the musescore handbook doesn't identify any benefits for doing it either way. as a matter of fact, i thought i WAS entering chords the way the musescore book says to do it, other than using the palette. if i put a chord in a piece, i'm already aware of the info that that Harmony Properties would tell me.

if there is a better way to do it, i'd love to know what it is and what it can do for me!

when i want to use the playback facility in musescore i actually put all the notes of each chord on the staff, with the name of the chord above it (using the above method).

i'm a bit confused, but i love using this proggy. its a gas, and it is SO useful! i get tons of work done with it!

thanks for your help!

iowaplayer

In reply to by iowaplayer

Ah, then all you need to do is stop using the flat sign from the palette. Just type a lower case "b" where you want a flat sign to appear, and MuseScore will take care of the rest. It will automatically display as a flat, and if you go to edit it later, it will turn back into a "b".

Not sure what you mean about other ways of entering chords. There *are* other ways, but there are no benefits. Keep doing exactly what you are doing; just use "b" instead of the flat sign. Otherwise, you will see the problems like you are seeing. And many more besides - like the chords won't transpose properly if you try transposing the score, chords won't export to MusicXML properly if you try that, chords won't change to a different style if you change chordname style, chord playback won't work if that ever gets implemented, etc. All those problems and more go away as soon as you start using "b" instead of the flat sign.

Do you still have an unanswered question? Please log in first to post your question.