Unable to get a complete print-out of score
Reported version
3.6
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
Yes
Project
I spent the afternoon entering a score into MuseScore (v3.6.2.548020600). I set the page size to "Letter" and when I printed from my iMac running macOS Catalina (10.15.7) on my HP LaserJet multiple aspects of the score were missing. I exported it to .pdf and tried again with the same results. Both MuseScore and Preview looked perfect on the screen. What can be done to get this fixed? I've attached the file for reference use only.
| Attachment | Size |
|---|---|
| LIKE_A_FLICKERING_FLAME.mscz | 30.75 KB |
Comments
On Mac, HP printers have known issues with the default music font. See #316152: Some characters do not print from Leland on certain printer drivers on Mac for more info, workaround is to use another font than Leland (Change font to Bravura in Format -> Style...). If that doesn't work then please let us know.
Switching to Bravura fixed MOST if the problem. Apparently the "flat" symbol still doesn't print in the chord symbol text. (Should substitute for a lower case "b" after a chord tonic character. Only shows a tiny dot.) What do I need to do to correct this? I'm also disappointed that I can't make Bravura the default setting when I start a new score. I have to make this change each time apparently. Is there a reason Leland cannot be fixed to work properly? If several other fonts work, it seems the error is in how Leland is defined in postscript.
Try whether changing Format > Style > Text styles > Chord Symbols > Font from Edwin to FreeSerif helps here
Leland has been fixed already (and possible Edwin too). But no official release with the fixed Leland is yet available
Changing the chord symbol font to FreeSerif worked! I'm a bit frustrated and perplexed about these little workarounds. To be completely clear, I think MuseScore is AMAZING software for open source code!! It's very powerful and goes up against the "big guys" charging hundreds of dollars every time the come out with an major revision. I just expect you'd "ship" you code as universally compatible as possible with a list of possible substitutions to get "better" capability in an accompanying text file with appropriate caution notes. Alternatively, it would be nice if we could make the default blank score keep the hacks we need to put in for it to work on our system. THANKS for the rapid and helpful support!
As per @oktophonie, Simon Smith, this issue should be fixed in Edwin 0.53 too, but he could never reproduce it, so we're not 100% sure.
Try the artifacts from https://github.com/musescore/MuseScore/pull/9000 to check (needs a GitHub account to get at them, then you'd find them under "Show all checks")
See #323561: Chord notation won't print correctly when using Edwin on a Mac and an HP printer for the 2nd part of the issue
I appreciate the reply regarding Edwin 0.53. I'm really not going to be as heavily engaged is using MuseScore as most of you, and I definitely am not ready to be assisting in writing/editing/debugging the code. I do have a small background in this, but it's ancient at this point and I just have too many other interests in my life that would make me a nearly useless member of your team. I'll be patient and wait for formal releases as long as you're OK with me notifying you when I see anomalies along the way. Again, thanks for the very excellent response time addressing my issues.
Hello,
I ran into this as well and the workaround still works. I looked through the notes, work in progress, and the related item and sounds like this will be fixed when the updated Edwin font gets into master and is released. Let me know if you need a tester! Excited for this fix.