Free Elbsound Finale Fonts Package v1.12
The Elbsound Music Fonts Package is a free package with 25 music fonts for Finale.
(Download 25 Free Music Fonts for Finale)
The fonts are 100% compatible with Finale's Maestro font and are available under the OFL or GNU GPL license.
1-click usage in Finale: To apply the fonts simply select "Document->Set Default Music File" in Finale and ... done.
All fonts from the font package:
How to swap fonts in Finale? With the Elbsound font package it just takes 5 seconds.
The original fonts used are:
Bravura, Beethoven, Cadence, Emmentaler, Euterpe, FreeSerif, Gonville, Gootville, Gutenberg, LV-GoldenAge, Haydn, Improviso, JazzyBasic, LilyBoulez, Leipzig, LilyJazz, Musica, Noto Sans Symbols, Profondo, Paganini, Ross, Scorlatti, Sebastiano, Symbola, Unifont Upper.
The version 1 . 11 update includes:
- SymbolaFIN: updated tremolo symbols and corrected tremolo metrics in FAN file
The version 1 . 1 update includes:
- four new fonts: Gonville, Musica, Noto Sans Symbols and Symbola
- 16 new composite glyphs (e.g. all notes for tempo marks, grace notes and quarter-tone accidentals are now composed from the same font and not taken from a fallback font anymore -> a more unified look).
- many minor fixes (e.g. unified ledger line and staffline symbols, better arpeggio centering, improved sffz kerning and white spots caused by inverted line directions were removed).
All fonts were transformed fully automatically (!) by a computer program through a process I developed called "Automatic Font Conversion". More technical information on that can be found in this article and in the ReadMe.
It's also possible to use these fonts in Sibelius through the "Maestro" style (see below).
Free DownloadDownload Elbsound Music Font Package (v1.12) (full symbol availability in Windows only, in MacOS 129-159 are missing)
Update 2017-11-08: v1.12 now includes an updated Aruvarb font based on the SMuFL 1.25 reference font implementation.
Deprecated version: Elbsound Music Font Package (v1.0) (fully symbol availability for MacOS AND Windows)
Download the SIL OFL font "Nepomuk" for text expressions like
Why only limited MacOS support in v1.1?
MakeMusic has confirmed on 2016/10/19 that there is a bug in Finale's font handling which prevents the symbols in the slots 129-159 to be shown in any (!) unicode font on MacOS. According to notation product manager Mark Adler this will be fixed in an upcoming point release. When the bug is fixed, it's not necessary anymore to have separate Finale fonts for Windows and MacOS.
Until then I decided to drop an extra version for MacOS which required duplicate testing and only offered limited font features (no unicode symbols!). If you still want to use the limited non-unicode font for MacOS, you can download the version 1.0 below or use v1.11, but cannot access the symbols from the slots 129-159 through Finale's font dialogs.
If you like this project and would like to see more fonts, please support us with a donation:
All SymbolsAll Maestro-compatible symbols (created with "Document->Set Default Music Font"):
Download in higher quality as a PDF
Usage in Sibelius with the "Maestro" font style: switching back and forth between Helsinki and HayFIN
-> Step-by-step tutorial on how to setup the fonts in Sibelius (Thanks to Robin Walker for providing this!)
On this subpage you find a comparison of the commercial MTF-Beethoven-Fin font for Finale from Music Type Foundry and BetvnFIN from the Elbsound Music Font Package. Both are based on the glyphs from the original Beethoven font for LilyPond.
Image: Comparison of Maestro, MTF-Beethoven-Fin and BetvnFIN
(click on the image to read the full comparison)
1-Click Arpeggio with the Elbsound Music FontsThe Lilypond based fonts in the Elbsound Music Fonts Package have an extra single length arpeggio element in the upper unicode area (symbol U+E15B). If you use this symbol instead of the standard Maestro-compatible double length element (symbol 103), it's possible get a good arpeggio positioning in Finale with one click.
You can download the Elbsound Arpeggio Articulation Library which includes the new arpeggio definitions for 12 fonts.
To use the library simply assign one of the articulations to an articulation meta tool (Select articulation tool and hold shift and press the meta tool key, then select the articulation definition and hit ok). To assign the articulation to the note key-click on the note at the bottom border (!) of the note.
The horizontal position of the arpeggio only fits quarter notes, but not whole notes, additional accidentals or chords with noteheads on both left and right of the stem.
To also manage the latter with one click, you could create more articulation definitions with slightly bigger horizontal offsets.
This trick only works if the fonts are not added to MacSymbolFonts.txt! Otherwise the unicode symbol area is not visible.
FAQ/Troubleshooting1.) Problems with FAN files in Finale
Finale changes the font annotation format regularly in its updates. Should you encounter any problems with font annotation, it's also possible to auto-create these files from within Finale.
Just go to Preference->Font Annotation, select the font, click on "Auto-annotate all" and then on "Save".
2.) Why is the MacSymbolFonts.txt used on Mac OS only ?
The MacOS and Windows fonts in the font package are not compatible.
Since Finale 2012/MacOS it's not possible to have unicode fonts that are compatible to non-unicode fonts like Maestro (a "confirmed bug"). So to have full compatibility with Maestro, you must add the font to the MacSymbolFonts list and thus can only access the first 256 characters of the font.
On Finale/Windows it's possible to access all unicode symbols AND the Maestro-compatible symbols.
I.e. the Aruvarb font includes all (!) symbols from Bravura.
The only Windows limitation is that the unicode symbols from the unicode blocks above 0xFFFF can't be accessed, if the font is set to Maestro-compatibility.
3.) Installation on older Finale version on Windows
If you are using the fonts on an older Windows installation of Finale, please use the fonts from the MacOS/Fonts folder and also add the font names to the Windows MacSymbolFonts.txt.
The fonts for Finale were not tested on older installations, so they might not work. Especially the "upper unicode block" fonts (FreeSerifFIN, Unifont UpperFIN and EuterpeFIN) might not be available in versions before 2014.
4.) Inconsistens symbols ?
All Finale fonts were created fully automatically from the original fonts.
No new symbols were designed, but a few composite symbols were derived automatically from existing symbols (e.g. marcato-staccato, tenuto-staccato, ottava clefs, composite dynamics, arpeggio etc.).
If a symbol doesn't match the style of the font (e.g. the niente 'n' in LijazFIN), it is because a matching symbol was not available in the used fonts.
5.) Combining the Maestro-compatible symbols with the characters from the unicode blocks
On Finale/Windows you also have access to the unicode symbols from these fonts (not on MacOS -> see 2. above).
For example the full Bravura range is available in Aruvarb, or all Lilypond symbols are available in CadncFIN.
But don't forget: these unicode symbols were not rescaled or repositioned, so they might require some fine-tuning if you want to integrate them into your score or match the Maestro-like symbols.
6) Why these abbreviated font names for the SIL OFL fonts ?
Because the full font names are reserved in the SIL OFL and may not be reused.
7.) Some flags in the musical example Berg look different than in my own scores.
Yes, flag settings were optimized for some of the Finale fonts. Especially those fonts that have very different metrics than Maestro require a tiny flag optimizaton.
Those are mainly the handwritten fonts. To fine-tune the flag settings go to Document Options->Flags or use the upcoming House Style Changer plugin which already includes the correct flag settings.
8.) Why are the quarter-tone accidentals different than in Maestro ?
The quarter-tone accidentals in Maestro are very buggy: compared to the standard accidentals they have a different size, a different design and a different baseline which makes them more or less unusable (another "confirmed bug").
To have quarter-tone accidentals that can actually be used, I decided to have them match the standard accidentals in size and baseline, so that they can be easily used in Finale.
Unfortunately some original fonts do not have these "digit 4"-quarter-tone accidentals (e.g. the Cadence font).
In these cases a quarter-tone accidentals from one of the fallback fonts (Bravura, Musica and Symbola) was used which slightly differs in design.
9.) Why does the MacOS font folder not include an OTF font like the Windows folder ?
As MacOS has a very smooth handling anyway, it's not necessary to have an OTF font on MacOS.
10.) Known Bugs
-The rests in SbstnFIN still look a bit squeezed -> will be updated in the next release
-The two-bar repeat in LeipFIN doesn't connect to the top barline -> will be updated in the next release
-The 16th note flag down in EuterpeFIN has a white dot caused by merging overlapping symbols-> no automatic fix possible
-The space symbol (character 32) in GotvlFIN is not visible (i.e. no distance between two characters if the space is added in between) -> will be updated in the next release
11.) Systems tested
Finale's font handling depends on the current OS (Mac/Windows), its version and Finale's version.
Make sure you have the correct font file and font annotation file installed, updated the MacSymbolFonts.txt if necessary and restarted Finale.
The fonts were tested on Windows 10 with Fin 2014, 2014.5 and 25 and MacOSX El Capitan Fin 2012, 2014.5 and 25.