Chord symbol elements as exponent type?
Is there a way chord symbols could use the standard font, but show chord embellishments as exponent type, like the way the jazz option works? I've included an image example of what I'm looking for.
| Attachment | Size |
|---|---|
| Screen Shot Klaus.png | 46.61 KB |
Comments
Use menu item: Format -> Style -> Chord Symbols and adjust 'Extension scaling' and 'Extension vertical offset'.
![superscript.png]( "superscript.png")
In reply to Use menu item: Format ->… by Jm6stringer
Thank you! I did not know this. I appreciate your help.
In reply to Thank you! I did not know… by HotChocolateJazz
It was only just added, for MuseScore 3.3 :-). Note "7" is the "extension", "(#11)" is the "modifier", in "D7(#11)".
In reply to It was only just added, for… by Marc Sabatella
Great, thanks for the clarification Marc!
In reply to It was only just added, for… by Marc Sabatella
I now have another question. Could the code be modified to be a little bit smarter? My following example shows what happens when I use the modifier 'add2'. I think because the word 'add' contains three chord letters, the code doesn't see this as a modifier and displays them without extension or modifier formatting. However, the 2 in 'add2' is seen as a modifier and is formatted as such. An idea for code modification would be to flag when the chord has been named, therefore indicating that any subsequent text becomes automatically extension and/or modifier. As a side note, I do know that indicating 2 is supposed to be the same as 'add2'. However, some people like to differentiate that a 2 chord can be a chord where the 3 is replaced by 2, as in a 4 chord (C4). In that case, indicating 'add2' becomes valid and is clearer in such a case.
In reply to I now have another question… by HotChocolateJazz
You must define "add" as a modifier in "chords_std.xml".
Then you should show it to the software in the "Custom" field from "Format => Style => Chords Symbols".
I made one for you. (chords_std.xml) Put this in your user "Style" directory.
see : "addChord01.png"
It looks like this:
![test-chordext.png]( "test-chordext.png")
Note: If you use the predefined "Jazz" style (Format => Style => Chords Symbols => Appearance) , it is already defined there.
In reply to You must define "add" as a… by Ziya Mete Demircan
Maybe this should make it into the MuseScore repository?
In reply to Maybe this should make it… by Jojo-Schmitz
Perhaps, but actually, I think this was deliberate, modifier was really meant only for the b9 etc. These text indications are more often not superscripted in my experience, so I think I excluded them on purpose. Realistically, more controls would help, but ultimately we need a chord symbol editor.
In reply to Perhaps, but actually, I… by Marc Sabatella
Since it is already superscript in jazz style, it didn't seem strange to me.
But yes, it is possible to come across different styles in different places.
In reply to Since it is already… by Ziya Mete Demircan
Well, yes, but lots of things are typically superscripted in the jazz style that aren't otherwise - in MuseScore and in the world at large. Although I occasionally see things like the 7 in C7 superscripted outside the jazz world, I've never see "add2" superscripted outside the jazz world. A good exhaustive study of published literature could be useful in tweaking the defaults and deciding which elements should respond to which settings in order to give the most flexibility and best ability to match published norms. My sense is there would no way of really getting there without more settings still, and/or a chord symbol editor. But if people show enough published evidence to justifying simply changing the XML file, I'm certainly open to that.
In reply to You must define "add" as a… by Ziya Mete Demircan
Very interesting, thank you! After reading Marc Sabatella, and noticing that 'add' isn't used standardly as superscripted, then maybe the image I attached previously is correct. After all, 'sus' is used the same way, and now I notice the smaller number isn't awkward, as it makes sure the number doesn't go above the height of a lower case 'a', or 'sus' for that matter. Maybe Musescore is programmed that way?
In reply to Very interesting, thank you!… by HotChocolateJazz
I'm noticing size of number after 'add' is actually the scaling I choose for the modifier. So I'm realizing I'm liking 0.75, as it's a good superscript size, as well as good match for lining up with 'sus' or the 'a' of 'add'. Example follows, using scalings of 0.75 and vertical offsets of -4.00 for both extensions and modifiers. Don't mind the chords, it's just a test.