PDF export problems with High Sierra 10.13.4 Beta 2
Hello
I don't know if this is a problem with Musescore or with High Sierra - since installing the newest beta of High Sierra (10.13.4 Beta (17E150g)) the export doesn't work correct anymore: it shows the staves but the are empty , no notes. Print to PDF shows the same behaviour ( but print to PDF works fine with other apps I've tested...)
I tried to test with the nightly build of musescore - but it failed to open my latest .mscz files ! opens a new tab with the title but nothing more shows up. older mscz files ( pre February) open regularly...
| Attachment | Size |
|---|---|
| Imperial_March old export.pdf | 34.28 KB |
| Imperial_March with MacOS beta.pdf | 25.22 KB |
Comments
Don't use print to PDF, use export. And don't install MuseScore's fonts.
In reply to Don't use print to PDF, use… by Jojo-Schmitz
I tried export FIRST , I always use export
Print to PDF I tried as a workaround
And - both worked really fine before....
The fonts that are shown in the Style menu are
Emmentaler
Bravura
Gonville
for musical symbols
exported with each of them - same result
Are any of these fonts installed on your Mac (rather than just built into MuseScore) If so: delete them, so MuseScore uses its own builtin ones.
See also https://musescore.org/en/node/269369, where this topic came up the other day
In reply to Are any of these fonts… by Jojo-Schmitz
No - I searched fonts in my user/library/fonts directory as well as in the systems font directories - none of them is there to find
Workaround: upload them onto musescore.org and then download them as a pdf.
ok - that might be a workaround - but somewhere there is an error, should be fixed...
thanks for the tip, didn't think of that
See also #269361: MuseScore does not print clefs or note heads on osx 10.13.4 (beta), not sure which to mark as a duplicate
Please report the problem to Apple. You are using a beta version of their OS and a stable version of MuseScore. The problem appeared when you installed the Apple upgrade. Hopefully, Apple will fix the problem on their side.
The problem seems to be gone with the High Sierra 10.13.4. Developer Beta 4 from March 6th...
In reply to The problem seems to be gone… by taptptb
I can confirm.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.