Some characters do not print from Leland on certain printer drivers on Mac

I would say if the symbol appears on screen with the PDF but not in the print, that sounds like an issue with the printer driver - MuseScore isn't involved in printing the PDF.

However, I note this is kind of similar to an issue one user reported with margins not being respected on print - see #315915: Printed staves cut off on left using v3.6. Maybe it's the same issue. What OS? I note you are both using HP LaserJet Pro models, that could be relevant too.

It is conceivable that something is wrong in how the clef and some other symbols get represented that some printers don't recognize as expected. Do you see the same if you create a score and change the music font to Emmentaler in Format / Style / Score?

I am experiencing exactly as described with the new update on a MacBook Pro. Thank you for bringing attention to this!

So, @pauldrewa , similar printer?

same problem here. MacBook Pro running Mojave. HP Color Laser Jet Pro MFP 477fdw. Leland font. Works OK using Bravura and Emmentaler, but not Leland.

I am having the same issue since upgrading today (1/24). I would like to simply revert to the previous version but can't find how to do that.

Same questions - - what OS, what printer?

Marc, I have an HP Color Laser Jet M254dw.

Same here! Works great once I use either Bravura or Emmentaler, but not Leland.

What? How would the font you use be related to whether printing works?

My guess is something in the font metadata is presented in a way that the driver for that printer on macOS doesn't understand even though everything else seems to understand it. Like, I don't know. the widths of the characters are given as not integers and that driver can only handle integer widths. Not I'm saying I think it is that specifically, it's just an example of the sort of thing that seems plausible given the data we have - the font appears to work everywhere except printed on one particular series of printer models on one particular OS.

Great minds and all that...

Worarounds:

• Don't use Leland, but Emmentaler, Gonville or Bravura
• Export to PDF and print that
• Don't use AirPrint, but print using the HP driver

Had the same issue with my HP LaserJet Pro 200 colorMFP M276nw (see #315706: On macOS Several Symbols Don't Get Printed Correctly when using AirPrint). The workaround that worked for me was to use the HP printer driver instead of using the macOS default AirPrint.

For me the PDF export workaround does not work.

Interesting, this suggests the bug is with Apple and not HP. Still would be good to see if we can fix something in the font to workaround it. But hopefully someone can report this to Apple.

I had this problem until I installed the latest HP driver on my Mac. Then I also deleted and re-added the printer. Then I also did as the previous poster suggested and deselected "Airdrop". Finally it all prints correctly again.

Same problem, different fonts suggested Emmentaller and Gonville are not on our drop down menu and other suggestions don't work. I'm on a brand new HP Laser Jet Pro but went back to Sharp printer and there's no problem so I'd say the problem is HP not Mac, I'm on Catalina.

It is AirDrop and HP printer and Mac and Leland. Only all 4 in combination show the bug.
And Emmentaler and Gonville (and Bravura, MuseJazz, Peteluma) very surely are in the list of Musical fonts to choose from, as they are built into MuseScore

The font selection in Format / Style / Score, right at the top.

Same here. Running macOS 10.15.7, HP Laserjet Pro printer

Laser Jet Pro M281fdw here.

Using a non-AirPrint printer looks to work correctly. There is a minor collision between three-plus digit measure numbers and the clef:

That said, if an exported pdf is converted to PostScript (pdf2ps), reimported to Preview and saved/printed, the missing/misplaced glyphs reappear in the correct locations, including measure numbers:

I don't know if the double conversion changes fonts offhand.

Could anyone having this issue test whether the artifact from https://github.com/musescore/MuseScore/suites/2428014151/artifacts/5184… still has it? (GitHub account needed)

Actually it might even be sufficient (or even needed in addition) to remove Leland.otf from the 3.6.x installation, to force the use of the build-in version of that font.

If that is a build that simply places fonts in different locations, I kind of doubt that will help. So far we've managed to narrow things down to specific issues in with a handful of glyphs in the font - "missing points at extrema", I think it was, as reported by FontForge. It can't be coincidence that the symbols that fail to print are exactly those with this particular issue. So the fix should be to fix those characters in the font. I was under the impression there was already a version of the font floating around with those fixes, and perhaps someone could try installing that.

Well possible that this change of mine does slove this proble, I'd still like to get it checked and tested, for this particular issue and for any other.
I'm not aware of a Leland font that had been modified to fix those "missing points at extrema", else I'd create a PR with it.

I recall it being discussed on Telegram, and either Martin or Simon said they had already made the fix in their copy.

I don't see anything in the Leland repo on GitHub

This? https://github.com/MuseScoreFonts/Leland

The clef is still shifted nearly off the page. Time signature missing. Dot missing on dotted-half note. "4" missing over the (merged) multi-measure rest. I forgot to add a tempo to see if the note is missing.

Yep

So basically the same list as in the initial post

Discussion on Telegram started at https://t.me/musescore_design/4449
And name the affected glyphs shortly after:
Marc Sabatella, [06.02.21 18:44]
the glyphs reporting missing extrema points are all the treble clefs variants (except double), the timesig 3, 4, and 7, double/triple/quadruple/sexctuple dot, single & double flags, parentheses, and then a bunch more you can see for yourselves :-)

Marc Sabatella, [06.02.21 18:48]
but it includes eighth & sixteenth rests, which were also specifically mentioned. so yeah, I think the missing points at extreme seems to be the key here

Is that all still the case with 3.6.2?

I encounter exactly the same issue
using MuseScore 3.6.2 with OS X Catalina 10.15.7
and my printer HP MFP M277dw via Wifi network.

I had to change font-family from Leland to Bravura as a workaround that works.

Or don't use AirPrint/AirDrop, but the HP Printer driver directly

I have a problem with clefs, time signature and other items not printing correctly on my LaserJet Pro MFP M148fdw. I am using the manufacturer's print driver, printing via USB connection, not wireless and not AirPrint. This problem started between 14 and 19 June I I I have a problem with clefs, time signature and other items not printing correctly on my LaserJet Pro MFP M148fdw. I am using the manufacturer's print driver, printing via USB connection, not wireless and not AirPrint. This problem started between 14 and 19 June 2021, with MuseScore 3.x. It persists with MuseScore 3.6 and Mac OS Catalina. The problem appears to affect all of my MuseScore files, regardless of creation date. A workaround I have found is to export from MuseScore to PDF, then re-export the PDF as .png. The .png prints OK.

Platform: LaserJet Pro MFP M148fdw, Mac OS High Sierra, MuseScore 3.x (possibly 3.2 or 3.3). Also Mac OS Catalina, MuseScore 3.6

Chronology: a) June 14 - printed OK with Mac OS High Sierra, MuseScore 3.x; b) June 19 - printing incorrectly, Mac OS High Sierra, MuseScore 3.x, the same file but with changes made; c) June 24 substituted new Mac OS Catalina, MuseScore 3.6 - printing incorrectly on newly re-installed printer. Also printed incorrectly now for a separate file created on the Mac OS High Sierra, MuseScore 3.x platform that printed OK on June 11.

Examples attached (4 files):

1) Current problem score that printed OK on a previous iteration but prints poorly now;
2) PDF export of current problem score , prints wrong
3) Previous score that printed fine from MuseScore on June 11 but prints poorly now
4) Image of the paper printout made directly from MuseScore, of a part of the current problem score - the PDF generates these same errors when it is printed, though the PDF looks fine on the screen

Thanks. Please advise.

Prior to 3.6 there was no Leland font, so whatever problem you're having with versions prior to that is unrelated to the issue at hand here.
Both scores you attached are created with 3.6.2 and using Leland though

Thanks. I hadn't realized that I was already using Leland and 3.6 with the earlier file. What are the steps to convert to another font?

Format > Style > Score > Musical Font

Aha! I finally found Font under Format > Styles > Font. Selected Bravura Font for the most recent score and saved it. Like magic, printing appears to be ok now. Bravo for Bravura! Many thanks to all.

See https://github.com/musescore/MuseScore/pull/8578

Those affected by this issue please test the artifact from GitHub (I'll add the links to it later) and report whether it really fixes the issue

Please give https://github.com/musescore/MuseScore/suites/3188235696/artifacts/7357… a try (needs a GitHub account, IIRC)
Edit: this link is no longer valid (it has expired meanwhile). Instead use the artifacts from PR #9000 (which is a moving target)

As per https://musescore.org/en/node/315706#comment-1087433 it does indeed fix the issue

Marc Sabatella wrote:

> specific issues in with a handful of glyphs in the font - "missing points at extrema", I think it was, as reported by FontForge

Ouch! I invested over a person-day to fixing all sorts of FontForge warnings, default or extra (need to specifically look for them) ones, when doing the new version of MScore because I knew they could lead to all kinds of trouble. (It’s also why MScore is .ttf at an em height of 1024 u now.)

happy to report that it fixes the problem printing on my HP Color LaserJet Pro MFP M477!

Thanks for the report

Glad to hear, that this nasty problem is fixed, thanks to everyone. Is there a forecast, when we will see this ifx in an official MuseScore release?
TIA, Wolfgang

As there so far no further 3.x release is planned, it should hopefully be fixed in 4.0, expected by the end of the year

Given the number of duplicates of this issue, the number fo affected users seems to be non- negligible, so IMHO you should consider releasing a minor 3.6.3 update.
Best Regards, Wolfgang

I'm all for it, but hit with resistance from the in-house team

Might still be useful to collect targetted patches for the last 2.x and 3.x each on a branch. While inofficial, it’s clear they will still see use in years to come, what with each newer release changing the layout engine fundamentally, and you can always point people to those builds.

For 3.x you'd find a pretty exhaustive list in https://github.com/musescore/MuseScore/issues/7449

Relates to #311175: [EPIC] Engraving issues and suggestions

Fixed in branch master, commit 868069c4c3

_Merge pull request #8853 from Jojo-Schmitz/leland-update-master

[MU4] Fix #316152: Some characters do not print from Leland on certain printer drivers on Mac_

I'm having this problem but can't figure out how to download the Fix via GitHub, any help is appreciated

That link is no longer valid (it has expired). Instead use the artifacts from PR #9000 (which is a moving target...)

Automatically closed -- issue fixed for 2 weeks with no activity.

I was successfully using the Emmentaler font workaround on September 14, 2021, but that workaround appears not to be working as of October 20, 2021. Mac OS 10.15.7, HP LaserJet Pro MFP M148FDW. The files I created on September 14 still print fine today. But when I now create a new file and change the font to Emmentaler as I did in September, the printing omits clefs and accidentals in the chord names, as it did earlier this year.

I created a Template via saving one of the working files into the Templates folder, in the uncompressed .mscx format as recommended on another posting about templates. However, the printout of the file I created using the template has printing errors. The following files are attached:
1) the working file I used to make the template - "twinkle Jazz interp M"
2) the mscx Template I created from the working file - "Accordion template ref. twinkle jazz interp M"
3) the mscz test file I created from the Template - "Satin Doll Study using Template"
4) Scan of the printout from the test file - "Scan of Satin Doll Study printout"

Please advise.

That scan does not seem to be of the same score, you can tell by the shape of the bass clef and the rests that it isn't Emmentaler at all. Is that a print directly from MuseScore, or did you export to PDF first? And if the latter, did you do that using File / Export. or did you use some sort of third party PDF printer?

In any case, nothing changed in MuseScore recently, so it may have been an update to macOS or the HP printer driver that broke this. I'd contact those two companies and report this.

Interesting that the scan does not appear to be from the same score. It was printed from MuseScore, not from a PDF. As a check today, I re-printed the file I sent in my previous post from MuseScore, and also from an exported PDF, and both print OK today! Not sure what could have changed.

I then went back to my original problem score not created using a template but changed to Emmentaler Font from the default. This font change was the only change I recall making for the file that was OK and that I used for the working template (.mscx, sent in my previous post).

I ran a few tests: a) I tried printing the original problem score again from MuseScore - still not good. b) I started a new score from the working template, entered two measures and then entered a single measure between them copied from the original score problem score -The symbols in all three bars then failed to print correctly. c) Removed the copied measure - the file now prints OK. It appears that a copied measure added between two measures created within the working file built upon the good template resulted in a change in the file.

I'm attaching the following files:
1. The original problem score that continues to print wrongly "Problem File SD-#,b"
2. File created from the working template, with a single measure copied from Problem File "Test 3...."
3. File created as a copy of Test 3 file, with the copied measure deleted "Test 4..."
4. Image A - printout of original problem score (not good)
5. Image B - printout of Test 3 (not good)
6. Image - printout of Test 4 (good)

Yes, changing to Bravura from Leland fixes the problem without messing with print drivers. FINALLY!

I should probably add that this is a "workaround" as indicated. The best solution is to fix the Leland font so that it works universally. There is a bug in how it is defined if so many other fonts work.

That's why that workaround is listed above
And why the Leland font indeed has been fixed, that's why this issue is closed. Only there's no new release yet containing the fix(ed Leland font).
Only the Artifacts from https://github.com/musescore/MuseScore/pull/9000 (needs a GitHub account) and the nighly builds for the master branch.

I downloaded the hp driver for my printer, went through the install and when it asked me to switch to their driver I did, now everything prints fine.
By the way, Dorico had a similar issue with printing some characters.