3.7 Evolution - Early Music
Ben Byram-Wigfield (aka benwiggy) created a SMuFL font "Valerio" for notating early music. (SIL Open Font License)
See Dorico forum:
https://forums.steinberg.net/t/valerio-a-16th-century-music-font/941064
This font can be used in 3.7 Evolution
Edit: New screenshot after fix by Jojo.
Howto: see https://github.com/Jojo-Schmitz/MuseScore/wiki/Musescore-3-Evolution-Fe…
Remember to rename (copy) Valerio.json to metadata.json.
Musescore 4 users are left in the cold.
Comments
Thanks, added to the WIKI page
In reply to Thanks, added to the WIKI… by Jojo-Schmitz
Additionally, maybe we could get the 3.7 code to handle the font specially so that stem positions were centered? That'd require a particular handling though, which means it'd make sense to bring the font in as an internal resource. Plus all the "code work"
In reply to Additionally, maybe we could… by worldwideweary
Isn't the point to attach the stem defined in metadata.json?
In reply to Isn't the point to attach… by Jojo-Schmitz
That may be, but according to the OP's image: it doesn't show correctly, whereas the 'fotos' shown on the Dorico forums do. Does that mean MuseScore is not interpreting the data properly, misapplying it, or that the data is not in the correct format? Hell if I know (...yet).
In reply to That may be, but according… by worldwideweary
I do suspect a bug in MuseScore. Looking at the MuseScore image it can be seen that the barline tips y alignes with the note head center, but not the x
In reply to I do suspect a bug in… by Jojo-Schmitz
In the moment of excitement, i didn't even notice this yesterday...
Looks like a nice project (and learning opportunity) to look into.
In reply to I do suspect a bug in… by Jojo-Schmitz
Hmm, maybe not: looking at, for example, a quarter note, in the metadata there is no
noteQuarterDown
(down stem), just anoteQuarterUp
, so there may be stuff missing?OTOH: changing it's
bBoxSW
andbBoxNe
doesn't seem to have any effect, neither has changingnoteheadBlack
(which might be the one used here for quarter notes, at least it looks right in the master palette's symbols palette)In reply to Hmm, maybe not: looking at,… by Jojo-Schmitz
More appropriate setting would be this (in Valerian's metadata.json):
Which looks correct. But changing the x-values there doesn't seem to have any effect, while changing the y-values does take effect.
So this does indeed point at MuseScore to be ignoring the x-values.
Looking at the code:
seems to confirm this
In reply to More appropriate settind… by Jojo-Schmitz
Looks good with Valerio
with some code changes
But then looks bad with Leland
No idea why, that change doesn't touch the y-values at all
In reply to Looks good woth Valerio … by Jojo-Schmitz
Ah, it isn't the y-value, the stems now end up at the wrong side, so it is the x-value
In reply to Looks good woth Valerio … by Jojo-Schmitz
Seems a) a bad copy/paste error for downstem, b) some flawed logic, and c) issues with various fonts' metadata. Back to the drawing board
In reply to Seems a) a bad copy/paste… by Jojo-Schmitz
This seems to work properly for all fonts
At least with quarter notes... others yet to be tested
In reply to This seems to work properly… by Jojo-Schmitz
Other durations look good too, feel free to test the artifacts of https://github.com/Jojo-Schmitz/MuseScore/pull/672
Will try to port it to master too
In reply to Other durations look good… by Jojo-Schmitz
This build works fine with Valerio and with other fonts as well. (Linux appimage)
Thank you for the fix!
In reply to Other durations look good… by Jojo-Schmitz
FWIW: Export/Import to musicxml (with an old MU3.7 version) loses everything Valerio, and I see no ref. to ‘font’ or ‘Valerio’ in the musicxml file.
In reply to FWIW: Export/Import to… by elsewhere
Not sure, but is the name of the musical fonts exported to MusicXML in general? Or are only the internal ones exported, or is it just Valeria that is mssing?
In reply to Not sure, but is the name of… by Jojo-Schmitz
Not sure either. A 'usual' musicxml file mentions 'font' in:
EDIT: In the Valerio musicxcml file there is not a single mention of font (?!)
In reply to Not sure either. A 'usual'… by elsewhere
These are all text fonts
Valerio comes without a text font
In reply to These are all text fonts… by Jojo-Schmitz
Never mind. All is well after I use
Format/Style/Score/Musical Symbols Font/Valerio again
In reply to This seems to work properly… by Jojo-Schmitz
Oh boy, this is a holy mess for many fonts and upstem notes with a some notehead types/durations)
In reply to Oh boy, this is a holy mess… by Jojo-Schmitz
OK, not as messy as initially though, I'm now quite happy with it for all fonts I checked this with, PR updated, so pick the new artifacts to check
There's one remainining issue though with Valerio: beams.
In reply to OK, not as messy as… by Jojo-Schmitz
I found this problem with the AloisenGrooveU font.
I guess (almost) nobody uses this font, and it can be ignored?
The 'beam' problem also exist in Dorico. But are beams needed in 16th century printed music?
Any suggestions about a good companion text font?
In reply to I found a problem with the… by graffesmusic
I don't have these AloisenU and AloisenGrooveU Fonts, so can't check or comment. `Maybe you can sent it to me for testing?
Thanks for the info that beams (for Valerio I assume) don't work in Dorico either, but stems do?
If so I wonder why they didn't fix Bravura and Petaluma...
In reply to I don't have these AloisenU… by Jojo-Schmitz
Oeps, sorry.
The beams do work in Dorico.
Were beams used in the 16th century?
In reply to Oeps, sorry. The beams do… by graffesmusic
No idea, but it means that I'd need to look into this. Which I did suspect before anyway.
In reply to I don't have these AloisenU… by Jojo-Schmitz
OK here's how the Aloisen fonts look (with my PR in its current form)
Seems to be bad metadata for
noteheadBlack
andnoteheadHalf
'sstemUpSE
, very bad (on the wrong side of the heads) for AloisenGrooveU, only a stemwidth off for AloisenU, similar to Bravura.Actualy the Aloisen fonts don't have a
stemUpSE
at all!?!In reply to OK here's hai the Alloisen… by Jojo-Schmitz
Fixed in the latest version of my PR...
In reply to Hmm, maybe not: looking at,… by Jojo-Schmitz
The glyphBBoxes stuff bBoxSW and bBoxNE seems to be Finale specific.
https://w3c.github.io/smufl/latest/specification/glyphbboxes.html
This data is provided primarily for MakeMusic Finale, which requires bounding box data for certain graphical and spacing calculations performed by the software.
Deleting this complete block doesn't change anything.
I also noticed that the x values do not have any effect, while the y values do work
In reply to The glyphBBoxes stuff … by graffesmusic
I believe MuseScore uses the
bBoxNE/bBoxSW
data too and for the same purpose. But for attaching stems it is the wrong thing anyhow, it'd be thatstemUpSE/stemDownNW
, it that exists