Maestro fonts (Wide & Regular)
Moderators: Peter Thomsen, miker
- castellanos
- Posts: 15
- Joined: Tue May 16, 2017 3:57 pm
- Finale Version: 27.0.0.710
- Operating System: Windows
Hi there!
I'm trying to change a score font, but I'm having problems trying to set Finale to Maestro "Wide".
When I select Maestro "Wide" and apply it, Finale does not change anything and stays in "Regular". No problem with the other options: Bold, Oblique etc...
Is this an issue or I'm doing something wrong?
Cheers!
I'm trying to change a score font, but I'm having problems trying to set Finale to Maestro "Wide".
When I select Maestro "Wide" and apply it, Finale does not change anything and stays in "Regular". No problem with the other options: Bold, Oblique etc...
Is this an issue or I'm doing something wrong?
Cheers!
Finale 27.0.0.710
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
There was an old bug that might still be there. Even MakeMusic was intrigued with how I was able to trick Finale despite the bug.
Instead of choosing Maestro and then selecting Wide, type Maestro Wide into the slot.
Zuill
P.S.: Yep. Bug still there, and my workaround still works. Funny that MakeMusic acknowledged the bug and that my approach works, but they haven't fixed it. I think they should put my workaround in the manual. Then they won't need to fix the bug (ha ha!).
Instead of choosing Maestro and then selecting Wide, type Maestro Wide into the slot.
Zuill
P.S.: Yep. Bug still there, and my workaround still works. Funny that MakeMusic acknowledged the bug and that my approach works, but they haven't fixed it. I think they should put my workaround in the manual. Then they won't need to fix the bug (ha ha!).
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- castellanos
- Posts: 15
- Joined: Tue May 16, 2017 3:57 pm
- Finale Version: 27.0.0.710
- Operating System: Windows
Where should I type "Maestro Wide"? In which slot?
Normally I go to Document/Document Options/Fonts/Notation/Set Fonts
There are three slots: Font, Typeface and Size.
Normally I go to Document/Document Options/Fonts/Notation/Set Fonts
There are three slots: Font, Typeface and Size.
Finale 27.0.0.710
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
Whether there, or in the Default font window, it doesn't matter. To the left side you see Maestro in the slot. Click the mouse there after the word Maestro, type a space, then add Wide. Then click okay.
Zuill
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- castellanos
- Posts: 15
- Joined: Tue May 16, 2017 3:57 pm
- Finale Version: 27.0.0.710
- Operating System: Windows
Neve mind!
I got it. Directly to Document/Set Default Music Font...
I typed Maestro Wide into the Font slot and worked.
Thanks a lot!!
I got it. Directly to Document/Set Default Music Font...
I typed Maestro Wide into the Font slot and worked.
Thanks a lot!!
Finale 27.0.0.710
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
Glad you got it. Pretty amazing they know about this, and yet refuse to fix it or let anyone know. Now 2 of us know. Maybe others will read this and know as well. Let's not keep it a secret.
Zuill
P.S.: Here's a link to the old MakeMusic forum where this was discussed once in the past: https://forum.makemusic.com/default.aspx?f=5&m=401649
Zuill
P.S.: Here's a link to the old MakeMusic forum where this was discussed once in the past: https://forum.makemusic.com/default.aspx?f=5&m=401649
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
In my last post in another thread, I reported that MM claimed it started with Windows 7 and that they fixed it in a Finale 2011 update.
So, you can see that it is also with Windows 10 and long past finale 2011.
https://forum.makemusic.com/default.aspx?f=5&m=468590
Zuill
So, you can see that it is also with Windows 10 and long past finale 2011.
https://forum.makemusic.com/default.aspx?f=5&m=468590
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- castellanos
- Posts: 15
- Joined: Tue May 16, 2017 3:57 pm
- Finale Version: 27.0.0.710
- Operating System: Windows
Yeah, tell me about it... MM and it's updates...
I've realized that trackpad gestures (zooming and scrolling) that work with Finale and Mac computers since years, do not work on Windows yet... Go figure!!
I've realized that trackpad gestures (zooming and scrolling) that work with Finale and Mac computers since years, do not work on Windows yet... Go figure!!
Finale 27.0.0.710
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
- elbsound
- Posts: 196
- Joined: Wed Aug 03, 2016 10:06 am
- Finale Version: Finale 2014.5
- Operating System: Windows
Here is a blog entry about font names in Finale with a few more tricks.
For example sometimes Finale only recognizes the PostScript font name instead of the standard name.
Typing the font name without blanks can also be an option.
https://elbsound.studio/font-names-in-finale.php
At the end of the article there is a "Finale Font Name Troubleshooting Guide":
https://elbsound.studio/font-names-in-f ... leshooting
For example sometimes Finale only recognizes the PostScript font name instead of the standard name.
Typing the font name without blanks can also be an option.
https://elbsound.studio/font-names-in-finale.php
At the end of the article there is a "Finale Font Name Troubleshooting Guide":
https://elbsound.studio/font-names-in-f ... leshooting
- N Grossingink
- Posts: 1786
- Joined: Mon Dec 19, 2016 2:50 pm
- Finale Version: 27.3
- Operating System: Mac
Jan, thank you for posting the link to your web page with your valuable information on using fonts in Finale.
Your information applies to Windows, but some of us Mac users have been plagued by Finale's faulty font handling also. I'm thinking of the phenomenon of opening older Finale files (2010 and before) in Finale 2014 or 25 and having certain text fonts labeled as "missing" in the font lists and displaying in a system default typeface. The fonts are indeed installed correctly and do display properly in Finale 2011 and 2012. As mentioned, the errors started appearing in 2014 and continue in 25.
Have you heard anything from others on how to deal with these problems and how they came about in the first place?
Thanks,
N.
Your information applies to Windows, but some of us Mac users have been plagued by Finale's faulty font handling also. I'm thinking of the phenomenon of opening older Finale files (2010 and before) in Finale 2014 or 25 and having certain text fonts labeled as "missing" in the font lists and displaying in a system default typeface. The fonts are indeed installed correctly and do display properly in Finale 2011 and 2012. As mentioned, the errors started appearing in 2014 and continue in 25.
Have you heard anything from others on how to deal with these problems and how they came about in the first place?
Thanks,
N.
N. Grossingink
Educational Band, Orchestra and Jazz Ensemble a specialty
Sample: https://drive.google.com/file/d/1pFF5OeJDeLFGHMRyXrubFqZWXBubErw4/view?usp=share_link
Mac Mini 2014 2.6 Ghz, 8Gb RAM
OSX 10.15.7
Finale 2012c, 25.5, 26.3, 27.3
Educational Band, Orchestra and Jazz Ensemble a specialty
Sample: https://drive.google.com/file/d/1pFF5OeJDeLFGHMRyXrubFqZWXBubErw4/view?usp=share_link
Mac Mini 2014 2.6 Ghz, 8Gb RAM
OSX 10.15.7
Finale 2012c, 25.5, 26.3, 27.3
- elbsound
- Posts: 196
- Joined: Wed Aug 03, 2016 10:06 am
- Finale Version: Finale 2014.5
- Operating System: Windows
Yes, I have heard of this. I work mainly on Windows. So I haven't tested if the problems that I describe in the blog also occur on MacOS, but maybe they do.
So my suggested solutions may also apply to MacOS (e.g. typing the font name without blanks or adding a font weight like "Wide" to the font name).
Just test it - it shouldn't do any harm.
One general problem is that true type font files hold several names and that MacOS may access different name than Windows. And probably even OS version-dependent. As Finale always was cross-platform, they probably had the idea (back in the 80s or 90s) to access the fonts on Windows in a more MacOS-style. That's why Finale behaves so different regarding fonts than standard Windows programs. The MacSymbolFonts.txt is one of these things.
So my suggested solutions may also apply to MacOS (e.g. typing the font name without blanks or adding a font weight like "Wide" to the font name).
Just test it - it shouldn't do any harm.
One general problem is that true type font files hold several names and that MacOS may access different name than Windows. And probably even OS version-dependent. As Finale always was cross-platform, they probably had the idea (back in the 80s or 90s) to access the fonts on Windows in a more MacOS-style. That's why Finale behaves so different regarding fonts than standard Windows programs. The MacSymbolFonts.txt is one of these things.
I seem to remember that at a certain point MM changed the Engraver font name from 'Engraver Font Set' to 'EngraverFontSet' which screwed things up royally (indeed using the PostScript name). Part of the problem may have to do with Finale's implementation of support for Unicode. I still have situations with older files in which I have to point Finale in the right direction so that it can find a font which has always been installed on my system. I've created macros which take care of this relatively quickly and painlessly but it still shouldn't be necessary.
Vaughan
Finale 3.2 - 26, Sibelius 4 - 7, Dorico 2.2
Tobias Giesen's plugins, full version, Robert Patterson plugins, Jari's plugins
MacOS 10.14.2
MacPro (2016) 16 GB, MacBookPro (2018) 16 GB
Amsterdam
Finale 3.2 - 26, Sibelius 4 - 7, Dorico 2.2
Tobias Giesen's plugins, full version, Robert Patterson plugins, Jari's plugins
MacOS 10.14.2
MacPro (2016) 16 GB, MacBookPro (2018) 16 GB
Amsterdam
-
- Posts: 1297
- Joined: Fri Aug 20, 2010 8:59 am
- Finale Version: Finale 27
- Operating System: Mac
As Elbsound points out, the issue with Maestro Wide is confusion between:
1. Name: "Maestro Wide"; Style "Regular"
2. Name: "Maestro"; Style "Wide".
I think it's a Windows-only problem, due to the different way that font selection is done.
As for the Mac issue of 'missing fonts': This is actually the result of a fix! Finale had previously specified font names and styles incorrectly, which caused a variety of other problems. As a result, documents created in those years need to be corrected by re-specifying the font and style correctly.
Re: Engraver family: PostScript fonts can't have spaces in the name they use in font menus. TrueType fonts can. So the Type 1 versions of Engraver are called "EngraverFontSet"; but for some reason, the TT format versions use "Engraver Font Set" (though internally they do also contain the PostScript name without spaces!). Needless to say, computers (and users) can get confused between the two when different formats are installed from those set in the document.
MM has revealed publicly that they intend to move towards SMuFL compatibility: that would imply new fonts which would hopefully correct these issues. I very strongly doubt that MM 'refuses' to fix any issue; but with limited resources, it may be that a quick fix now is not worth doing if the same components are part of some grander scheme later down the line.
1. Name: "Maestro Wide"; Style "Regular"
2. Name: "Maestro"; Style "Wide".
I think it's a Windows-only problem, due to the different way that font selection is done.
As for the Mac issue of 'missing fonts': This is actually the result of a fix! Finale had previously specified font names and styles incorrectly, which caused a variety of other problems. As a result, documents created in those years need to be corrected by re-specifying the font and style correctly.
Re: Engraver family: PostScript fonts can't have spaces in the name they use in font menus. TrueType fonts can. So the Type 1 versions of Engraver are called "EngraverFontSet"; but for some reason, the TT format versions use "Engraver Font Set" (though internally they do also contain the PostScript name without spaces!). Needless to say, computers (and users) can get confused between the two when different formats are installed from those set in the document.
MM has revealed publicly that they intend to move towards SMuFL compatibility: that would imply new fonts which would hopefully correct these issues. I very strongly doubt that MM 'refuses' to fix any issue; but with limited resources, it may be that a quick fix now is not worth doing if the same components are part of some grander scheme later down the line.