Gonville 2.2 SMuFL -- files -- OTF & JSON

• Jan 9, 2014 - 05:42

So... - version ALPHA (HOT :D) of Gonville font - contains basic symbols only. I created a few new symbols - schleifer, a few accidentals, missing letter "n" in dynamics. More symbols - coming soon :p

Gootector

Follow my topic for more updates for this font.

P.S.
Jazz font will be after Gonville - maybe.

Marc - a task for You - list of the most neccessary musical symbols in jazz font.

Attachment Size
Gonville.zip 38.97 KB

Comments

• Jan 9, 2014 - 15:41

Why not making this your Pull Request?
Just add more commits to your https://github.com/Gootector/MuseScore/tree/patch-1 doing this.
Theres's no real need to have a single PR for every single change, one PR can contain multiple commits.
Although in this case I see no reason to have single commits for delete gonville.otf. glyphnames.json etc and add then their replacements.

There's some more work needed to be able to select that font.
Maybe like this: fe6c7216? (I don't want to steal your work, so I don't intend to submit this as a PR, unless you want me to)

BTW: your metadata.json causes some white-space damage, unneeded blanks between a comma and a linefeed, causing the diff to be larger and harder to read than needed.
(I fixed that in 1b1ef225a)

Reply

• Jan 9, 2014 - 15:39

Personally, I'm actually more interested in chord symbols than the notation itself. We have MuseJazz, but it is only so-so (and the glyphs I created myself are considerably worse than so-so). The reason I find chord symbols significant is that they need to be readable in dimly lit bars, yet not take up much space horizontally., This calls for a relatively a heavy line thickness but a narrow overall character width, with capital letters much bigger than lower case so the roots jump out at you. These are some very specific attributes that few fonts ordinarily shoot for. The same font - or a variant of it - needs to work for ordinary text too. Maybe the variant would have relatively larger lower case letters.

Anyhow, regarding music characters - which I think others care about more than I do - the most obvious candidates would be the ones that get used the most, particularly in jazz charts: noteheads, stems, flags, beams; clefs, the numbers used in time signatures, accidentals; barlines (especially repeats), brackets, articulations, coda, segno. If everything else were simply borrowed from Gonville, I doubt anyone would complain.

Reply

• Jan 9, 2014 - 17:30

Ok, I understand. The very first will be clefs - treble, alto, bass; next - flags (8-128th) and others elements of notes (noteheads will be from Gonville); next - numbers (0-9) and letters (f, m, p), accidentals (sharp, double sharp, natural, flat, double flat), coda, segno and "common" fermats (up and down).

Reply

• Jan 13, 2014 - 11:57

I updated Gonville on github. The file glyphnames.json is wrong. Whats needed is a list of bravura glyphnames with the corresponding code points in the font. This is needed bc. bravura codepoints may change until they reach version 1.0. If you are compatible with latest bravura version this may be a simple copy from bravura/gyphnames.json.

Reply

• Jan 14, 2014 - 07:59

Shouldn't we then, for the time being, hide Gonville behind the -e switch, as being experimental?
It currently doesn't work properly, that's for sure (I tried changing the font from Emmentaler to Gonville on the promenade example: no clefs, timesigs, noteheads, just stems and beams)
Or is using a nightly experimental enough in itself?

Reply

• Jan 14, 2014 - 19:56

Anyone can test the development builds - no need to PM anyone. Just click the Download link at right of this page and scroll down to the "Nightly versions" section. As changes get merged into the main development trunk, builds are made available. Lots of people have been testing these already. Sounds like Gonville is not ready for use yet, but is close.

Reply

• Jan 29, 2014 - 01:02

Gonville 2.2 SMuFL alpha2

Please add otf file to repository.
Changes:
- added all clefs from palette
- fixed bug in displaying articulations and ornaments
- fixed bug in displaying brackets
- 1 new notehead
- 2 new accidentals
- and more symbols from palette...

Missing (will be in beta):
- sori and koron
- noteheads for percussion
- mordents and pralls

Greetings,
Gootector

...How to add binary file to repository, for example otf file?

Attachment Size
Gonville.zip 33.67 KB

Reply

• Jan 29, 2014 - 04:23

I don't *think* anything special is required to add to the repository aside from the normal "git add" one would to make it part of your local commit. When you push that commit to your fork on GitHub, it comes along for the ride, and when you issue the Pull Request for that branch, the new file should get merged in like any other change.

Reply

• Feb 8, 2014 - 23:02

I find the GitHub app to be pretty buggy. I see that error from time to time, and usually just closing the program and restarting fixes it.

But if it doesn't this time, see the Git Workflow document in the developers' handbook for info on how do things from the command line.

Reply

• Feb 9, 2014 - 09:20

Looks like your master branch is way behind upstream. Also you still have a bunch of old branches that could get deleted, only the last 2, patch-5 and patch-6 are still needed, as not be in merged into upstream yet.
I also don't understand why using 2 branches and PRs to get 2 changes files updated and still missing the 3rd (the font itself), one branch, one commit, with all 3 files and one PR is the way to go IMHO.

Reply

• Feb 9, 2014 - 21:23

If it's any consolation, we pretty much all went through this kind of thing when first getting started with Git. Well, I did anyhow. The advice above to start over is good, I think. Several times I've had to delete a branch, my local repo, or even my whole fork on GitHub, and recreate it to recover from some mistake I had made along the way. I more or less have the hang of it now so this doesn't happen often, but I don't understand things well enough to know better ways of solving these sorts of problems when they do come up.

Reply

• Feb 8, 2014 - 15:48

Changes:
- fixed bugs in displaying fermats and articulations
- fixed bug in displaying letter 'f' in dynamics (kerning) - sfz, rfz, etc.
- added a few basic percussion noteheads
- added sori and koron symbols
- added thumb symbol
- added ottavas numbers: 8, 15, 22
- added trill&glissando line element, arpeggio up&down arrows
- added brackets for accidentals
- ...and more useless and strange symbols :D
- ...and more small changes...

In final:
- elements for mordents and pralls ("swirls")
- more noteheads for percussion

Greetings,
Gootector

Attachment Size
Gonville.zip 40.42 KB

Reply

• Feb 21, 2014 - 15:05

I though Werner did that, but apparently not this one. Be aware that it might conflict with resp. revert your recent 2d6d0b8

Edit: no it does not, it's the font only

Probably needs a chage in metadata.json:
{syntaxhighlighter brush:cpp}
@@ -1,6 +1,6 @@
{
"fontName": "Gonville",
- "fontVersion": "2.2 alpha2",
+ "fontVersion": "2.2 SMuFL 0.8 beta",

"engravingDefaults": {
"arrowShaftThickness": 0.16,

{/syntaxhighlighter}

Both in PR #711

Reply

• Feb 24, 2014 - 17:42

* Barline dots are the same than augmentation dots.

* regarding flags, I'm not questioning the choice and vertical position of the flag. I'm talking about the horizontal position. With the current glyph we have a note like the right one. The glyph would need a bit more "stem" in order to be positioned correctly. See the left one where I moved the glyph artificially 0.12sp on the right.

shot_140224_183244.png

If you check the flags in Bravura they have a bit of stem on the right. Left bravura, right gonville.

shot_140224_184202.png

Attachment Size
shot_140224_183244.png 12.08 KB
shot_140224_184202.png 33.33 KB

Reply

• Mar 3, 2014 - 12:06

It would be great if you can provide a screenshot again with all the symbols. The MuseScore community on the social networks love great screenshots ;)

Reply

• Mar 3, 2014 - 22:04

Jazzy will be ONLY for open-source programs, not for use with commercial software as Sibelius, Finale etc. For commercial programs will be special, commercial version of Jazzy. I respect my work and I don't want to company as Avid use my products for free.

Reply

• Mar 5, 2014 - 15:22

Thank you!
Any reason why you don't add the font in your pull request?

I don't see the dot in the font. glyphnames.json suggests that it should be at U+E1C7

Flags and dynamics looks better. The connection between stem and notehead when the stem is up is still not good.

shot_140305_161804.png

Attachment Size
shot_140305_161804.png 37.01 KB

Reply

• Apr 15, 2014 - 12:51

Great, thank Jojo. In order to spare the git history a bit, I will not merge the PR right away, if you are ok with updating it from time to time. We already commited several version of Gonville, which is not really nice for the history either...

The tests also shows that the alignment of articulations is not right https://github.com/Jojo-Schmitz/MuseScore/blob/gonville-vtest/vtest/gon…
From SMuFL 0.85 "Articulations to be positioned above a note or chord should be positioned such that they sit on the baseline (y=0), while articulations to be positioned below a note or chord should be positioned such that they hang from the baseline."

Reply

• Apr 15, 2014 - 13:05

OK, I will.
one test is still missing, I tried to take bravura-mmrest and make a gonville-mmrest from it, this failed miserably as it resulted in a corrupt score. Trying to generate the png from it gave the following error message:
Debug: Score::readStaff(): missing measure! (...\MuseScore\libmscore\scorefile.cpp:257, void Ms::Score::readStaff(Ms::XmlReader&))

Reply

• Apr 15, 2014 - 16:40

Ok. Thanks, Jojo and lasconic. Hmm... I see that the trill line is displaying incorrect. Next update coming soon.
And question - where are the newest nightly for windows? Fortunately, schepers has one of yesterday... :P

Thanks,
Gootector

Reply

• Apr 27, 2014 - 13:29

PR redone, but still open issues:
•bad alignment of some trills in gonville-4,
•bad alignment of the 'thumb' articulation in gonville-5
•bad alignment of some trills in gonville-8,
•missing noteheads in gonville-10

Not sure my change to metadata.json is correct but it prevents an error/debug message about
"ScoreFont: symId not found "

Reply

• Apr 27, 2014 - 20:01

There are still other outstanding issues with Gonville:

1. In #24763: [Gonville] Move note flags on X=0 Y=0, dealing with stem positioning on up-stem notes. I don't know if this is exclusively a font issue as imported 1.3 scores show a greater degree of bad stem positions, and mostly on Windows 8.x. Why would a 1.3 score make a difference from a native 2.0 score?

2. The difficulty of selecting note stems on flagged notes when using Gonville. This would seem to be a font issue with flag positioning, where they covering too much of the stem.

Reply

• Apr 29, 2014 - 23:02

Update coming soon.
PR redone, but still open issues:
•bad alignment of some trills in gonville-4,
•bad alignment of the 'thumb' articulation in gonville-5 - fixed
•bad alignment of some trills in gonville-8,
•missing noteheads in gonville-10 - fixed

metadata.json - try file from Bravura SMuFL 0.9. I'll send this file with the next update.

Gootector

Reply

• Sep 5, 2014 - 12:08

Gonville 2.2 - SMuFL 1.02

Changes:
- updated to Bravura 1.02 templates and SMuFL 1.0
- added missing notehead(s)
- added and redesigned a few new symbols
- fixed a few bugs
- added GonvilleText.otf file
- added readme.txt file
- added *.json files

Please add/change ALL files to the repository.

Greetings,
Gootector

PS
Possible fixes on Monday or Tuesday.

Attachment Size
Gonville_2.2_SMuFL_1.02.zip 393.6 KB

Reply

• Sep 5, 2014 - 13:24

Ok, add this to my PR #838 , along with added/updated vtests.
Comments:
gonville-3-ref.png
the articulation of the 4th note, to staff, seems to far up, compared to Bravura, but Emmentaler has the same issue, not sure who's right
gonville-4-ref.png
most articulations (trills) are missing a part, they show a rectangle instead, compare with Bravura/Emmentaler. Alignment looks OK though
gonville-5-ref.png
articulation 1st note, top staff has an entirely different position compared to Bravura/Emmentaler, above rather than below
gonville-8-ref.png
bottom stave, 1st measure, missing trill below staff, 2nd measure,, 2nd trill much longer than Bravura/Emmentaler

Reply

• Sep 9, 2014 - 11:20

Ok, but I found a few critical bugs:
- wrong kerning for letter f in Gonville.otf and GonvilleText.otf
- displaying second segno - glyph is cut; metrics are adjusted on 2012; in size 400%-1600% segno is displaying correctly...
- size of GonvilleText.otf
- notes and dot for tempo are missing - which glyphs are necessery?

Kerning and size are easy to fix, but I don't know how fix the displaying of segno.

And second tab clef - is necessery?

I don't found more bugs.

Reply

• Sep 9, 2014 - 14:38

The note and dot for tempo use the Unicode versions of those glyphs, aligned at the baseline instead of "mid staff" like the SMuFL versions. And these too are from the text version, I believe. Repeats, dynamics, and all the symbols at the top of the F2 symbol palette come from the musical text font (everything up to the space, which is a special version of space used for tempo markings, 0.5sp wide I think but don't quote me on that. The rest of the glyphs in that dialog come from the regular current text font (eg, FreeSerif or whatever you are using).

Reply

• Sep 11, 2014 - 09:27

That explains the slight change in layout (and yes that does look better, and indicates that the other vtests need to get regenerated too), but not the huge difference in the width of the PNGs it generated. There's also a variation in height.

OK, seems to be a GitHub issue

Reply

• Sep 11, 2014 - 10:52

Jojo-Schmitz - you didn't do (v)test for Gonville Text font - kerning and changes of sizes for letters are dedicated for Gonville Text font. Never mind, I see that fonts were updated :D

In my opinion - vtests are "semi-good" way to how the fonts are displaying. Download a few scores - for example - from musescore.com and see effects "in action".

Reply

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