Musescore 3 FreeSans bold text rendering
Just downloaded version 3 and all my boldfaced freesans titles are rendered very poorly when zoomed out, see the attached image
| Attachment | Size |
|---|---|
| musescore3 tekst.PNG | 66.47 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
I can confirm. I move the title down and it was still chopped off at the same spot. Can you enter this into the issue tracker at https://musescore.org/en/node/add/project_issue?pid=1236. Also mention which Operating System (OS) you use, mine is windows 10. This may be a factor.
In reply to I can confirm. I move the… by mike320
If so, make it Suggestion (to iincluse a Bold and BoldItalic verson of FreeSans), as otherwise it is by design ;-)
The reason most probably is that we don't package a Bold (nor Italic or BoldItalic) version of FreeSans (but do for FreeSerif) and that converting a normal font to Bold generally gives rather bad results (not so much for Italic, IIRC)
In reply to The reason most probably is… by Jojo-Schmitz
As per https://www.fontspace.com/gnu-freefont/freesans, https://en.wikipedia.org/wiki/GNU_FreeFont and https://www.gnu.org/software/freefont/ there is a FreeSans Bold and a FreeSans Oblique and a FreeSans BoldOblique (Oblique rather than Italic, but seems to be the same thing), and also a Free Mono family.
Now in the issue tracker as #281601: Musescore 3 FreeSans bold text rendering is bad
In reply to The reason most probably is… by Jojo-Schmitz
Thanks for the answer! I've downloaded and installed all the fonts from https://www.fontspace.com/gnu-freefont/freesans but this doesn't help. Do I need to point musescore to these fonts?
In reply to Thanks for the answer! I've… by Polbeer91
Should not be needed, IIRC MuseScore takes the external ones over the internal? Maybe not here though, in which case a code change would be needed to embed them inside MuseScore
It is not just Freesans. All Sans-fonts set to bold are rendering bad when zooming out, but when you zoom in, the font is rendered the correct way. Tested fonts are: "EngraversGothic BT" "Freehand591" and "Arial"
In reply to It is not just Freesans. All… by webfischi
Hi all,
is there any solution for this problem available? It's a really poor look in Musescore3 software. In Musescore2 all is fine. See files Musescore2.png, Musescore3.png.
But I've another problem: Exporting to PDF works wrong in Musescore3. Bold texts (Title, subtitle in my example) are printed out in regular in PDF. In Musescore2 it was pefect. See *.pdf.png screen shots.
Any idea?
Many thanks!
dan930
In reply to Hi all, is there any… by dan930
Which font is that? I can't reproduce any such problem using the font being discussed in this thread (FreeSans). Also, can you attach an actual score, not just a picture?
In reply to Which font is that? I can't… by Marc Sabatella
As webfischi wrote: "It is not just Freesans..." That's the reason for my question in this thread :)
However, I'm using "Linux Libertine O" font (Windows 10, otf font file). In Musescore2 it works fine. The problem is only in MS3. Enclosed you will find the MS3 example.
Many thanks!
dan930
In reply to As webfischi wrote: "It is… by dan930
Hello
![Espana-MS3.JPG]( "Espana-MS3.JPG")
I don't have a problem displaying your partition in MS 3.4.2 on Windows 10 v 1909
In reply to Hello I don't have a problem… by Papibois
But this is not "Linux Libertine O" font, what Musescore is using in your screen shot. Maybe you don't have installed thin font, and MS3 replace it by a system's default font?
In reply to But this is not "Linux… by dan930
Yes you are right but no problem either after installing the Linux Libertine O bold font (LinLibertine_RB.otf on Windows) :
![Espana-Libertine.JPG]( "Espana-Libertine.JPG")
In reply to No problem either after… by Papibois
Maybe that's the beginning of an explanation here:
This is most probably the same issue as in #281601: Musescore 3 FreeSans bold text rendering is bad and #284218: Broken on-screen rendering of synthetically emboldened fonts.
However, I couldn't find a real solution in this case, it appears to be a bug of Qt, which affects all systems using freetype engine for font rendering (Linux and Windows, in which we forced freetype in qt.conf).