The flat-7 chord bug
With MS 4.0.1.230121751, I'm finding that flat-7th chords appear too widely spaced (see screenshot). On my system, at least, any flat-7 appears this way. Other chords appear normally.
I'd attach an example score—but as it's occurring in every score here, I didn't see the point. Let me know if there's anything else I can do to help. 👋😏
| Attachment | Size |
|---|---|
| ms_chord_bug.png | 25 KB |
Comments
The point is that maybe we can compare your settings to ours. On my system that same thing is spaced properly and the chords use a serif font. Perhaps change the font somewhere in Format > Style...
![sample.png]( "sample.png")
That happens when not using Edwin or FreeSerif as the text font, many other fonts, like Times New Roman have a bad kerning for the flat glyph
In reply to That happens when not using… by Jojo-Schmitz
Yikes, you're right! I'd switched to Calibri, and forgot. Obviously that's the culprit.
The lead sheets we use for studio work have always used sans-serif chord symbols, as certain parties around here consider it a cleaner, less-cluttered look. Does MS include a sans-serif font that would work well for this? I could experiment with others, but just thought I'd ask.
In reply to That happens when not using… by Jojo-Schmitz
Okay, I've experimented—and every other font on my system behaves the same way, serif or sans serif, including those I've installed myself (even Sibelius' Opus Chord Symbols font, which you'd think would know better).
There's something about that "flat" symbol that prevents proper rendering. Is there any working sans serif option?
And shouldn't this be added to the bug list? There's not much point in letting people choose other Chord Symbol fonts if they won't work.
In reply to Okay, I've experimented—and… by Andy Fielding
It is a bug on those fonts, and not one of MuseScore, the fonts that come with MuseScore don't have that bug
In reply to Okay, I've experimented—and… by Andy Fielding
Back in the day of MuseScore 1 and Times New Roman as the default font I've created my own version of stdchords.xml to work around that issue
$ diff -u stdchords-orig.xml stdchords.xml --- stdchords-orig.xml 2013-01-30 16:32:50.000000000 +0100 +++ stdchords.xml 2023-03-01 10:57:04.131141000 +0100 @@ -58,8 +58,8 @@ :a accidental --> - <renderRoot>:n m:0:-1 :a m:.5:1</renderRoot> - <renderBase>m:0:2 / :n :a</renderBase> + <renderRoot>:n m:1:-1 :a m:0:1</renderRoot> + <renderBase>m:0:2 / :n m:1:-1 :a</renderBase> <chord id="1"> <render></render>Not sure whether that'd still work