MuseScore 3.0 prints and exports some elements in the wrong size
Printing a score natively from 3.0 causes some elements (e.g. clefs, braces, noteheads, keysigs, timesigs, rests, but not barlines, text, staves or volta lines) to be printed too large. See attached .mscz file and jpeg of the hard copy printout.
Exporting to PDF causes the opposite to happen: some elements (the same elements that printed too large) renders too small on export. See attached PDF of the same .mscz file as before.
Steps to reproduce:
Create a new .mscz file in a 3.0 nightly or open a .mscz file created in a previous version in a 3.0 nightly.
Press Ctrl+P to print the file
Export the file to PDF format
Compare the printed and PDF output to the original file
OS: Windows 7 SP 1 (6.1), Arch.: i386, MuseScore version (32-bit): 3.0.0, revision: e223087
Maybe a reappearance of
https://musescore.org/en/node/124351
https://musescore.org/en/node/124166
https://musescore.org/en/node/125431
https://musescore.org/en/node/123506
?
Also, is there any known workaround to get MuseScore to behave properly in this regard? The previous "export to PDF first, then print" workaround doesn't seem to work any more :-(
EDIT: initially forgot to attach files.
| Attachment | Size |
|---|---|
| Aandgesang_3.mscz | 32 KB |
| Aandgesang_3.pdf | 152.79 KB |
| IMG_20180521_163902[1].jpg | 2.6 MB |
![IMG_20180521_163902[1].jpg](https://musescore.org/sites/musescore.org/files/2018-05/IMG_20180521_163902%5B1%5D.jpg){kind=link}
Comments
edit: forget ;-)
SVG export also does weird things, but PNG export works as expected. So it seems to be at least three possibly, but not necessarily related issues here:
Certain elements print too large
The same elements that print too large, are too small in PDF exports
SVG export exports elements in the right size, but erases staff lines for all but the first bar of a system
Should I open separate issues for each of the three, or keep them together here?
Can you still reproduce this?
Attached the file converted to the new file format, so it opens with the latest development builds.
I can't reproduce on my HP OfficeJet Pro 8620
It looks like this with cc84a61.
Not for me. So what is the difference?
My system: OS: Windows 7 SP 1 (6.1), Arch.: i386, MuseScore version (32-bit): 3.0.0, revision: cc84a61
Maybe 32 bits vs 64?
Also, the printer is HP LaserJet P1005
And the output from a Canon Inkjet iP3600 series
32bit? Where did you get that from? The downloadable development builds surely are 64bit.
(but I build a 32bit version myself and still couldn't reproduce)
Should have said it was self-built with mingw_32.
EDIT: latest version self-built. I first observed the issue in a nightly build.
Which Qt version? I'm using the new 5.9.7 for my (MinGW) 32bit build currently (and the equally new 5.12.0 beta2 for my (MinGW and MSVC) 64bit builds)
Qt 5.10.1 (i386-little_endian-ilp32 shared (dynamic) release build; by MSVC 2015)
Maybe the bugs is there? 5.9 is (and 5.12 will be) an LTS (Long Term Support) release.
The developers' handbook pretty clearly states to use 5.9.
I've looked into 5.12, as that finally will allow for MinGW 64bit builds and as that will be the next LTS release (planned for end of November), hopefully timely enough for MuseScore 3.0
Only MSCV 2017 64bit supports WebEngine, which we need for the Startcenter.
See https://github.com/musescore/MuseScore/pull/4060
When I think about it, I don't think the problem is with my Qt version. I first observed the issue with a nightly build before migration to MSVC was even considered. Presumably that would have been built with a correct Qt version?
But there indeed has been such a bug in a previous MuseScore version IIRC, just is it has been fixed a while ago.
I can't reproduce any more on OS: Windows 7 SP 1 (6.1), Arch.: i386, MuseScore version (32-bit): 3.0.0, revision: 417d89e, so it would seem to be fixed!
Even without that PR... well, as I said, I couldn't reproduce it, but looking that the PR indicates that it may happen when found the print and export in a certain order and during the same session.
So I believe that PR has it's merit, it fixes a real bug, so lets wait till it is merged
Fixed in branch master, commit 27ac99551d
fix #137766, fix #272598, fix #277404: correct font size setting when rendering a score in pdf printing mode
Fixed in branch master, commit 707d033ea2
Merge pull request #4060 from dmitrio95/fix-printing-pdf-issue
fix #137766, fix #272598, fix #277404: correct font size setting when rendering a score in pdf printing mode
Automatically closed -- issue fixed for 2 weeks with no activity.