Saving PDFs often shows heads and stems separated
I have made a short example Entchen.mscz and also attached the resulting pdf.
The other pdf shows that sometimes the result is good, and sometimes it isn't - the lute seems to be good, but not the notation.
GIT commit: 7f9585a
Built with qt-creator on Linuxmint 18
| Attachment | Size |
|---|---|
| Entchen.mscz | 4.84 KB |
| Entchen.pdf | 9.8 KB |
| NYPL11-page1.pdf | 25.89 KB |
Comments
Doesn't seem to be an issue in Windows (7 Enterprise, 64bit)
Which Qt Version? (I'm using 5.6.2, the latest and greatest as of a couple days)
Related to some fonts being installed that shouldn't be?
I think I have 5.6.0:
Qt Creator 3.6.1
Based on Qt 5.6.0 (GCC 4.9.1 20140922 (Red Hat 4.9.1-10), 64 bit)
How can I check the font problem?
do you habe mscore font installed?
My Qt 5.6 is using GCC 4.9.2 (and did evers since Qt 5.6.0). Maybe ugrading to the latest Qt 5.6.2 and maybe eben to QtCreator 4.0 (be aware that the project config works differently there) helps already?
The nightly builds for Mac do use 5.6.2 since a few days, not sure about the Linux builds, but maybe you could give those a try too?
Didn't know that I should install anything while using qtcreator ...
But I see also some error messages in qtcreator like: read failed:
Should I also copy these files to the searched dir read failed: /usr/local/share/mscore-3.0/styles/ ?
you should not have any musescore fonts installed (it leads to trouble if you have), but you need to run the 'make install' step
There doesn't seem to be any musescore font installed. So this shouldn't be a problem.
But did you do the "make install"? That step is not optional if you want things to actually work correctly. And you need to run the copy that "make install" installed, not the copy you built. If you have done that and still have these font issues, what are the read errors you are seeing?
I have now compiled another version under linux by using make directly and also installed it. But it is the same again.
I attach two files: the musescore and the resulting pdf-File, where after measure 3 in the 2 lower systems (notation) the view isn't correct.
Now, with the newest version compiled, it even seems worse.
There are really small heads and other symbols in the pdf - printing out a pdf with cups is perfect btw.
With the newest version, it seems to be good again and fixed!
But anyway there are two other problems I see currently (cf. the exported pdf):
- The first measure, the anacrusis is far too wide away from the bar line - it seems to have get worse ...
- Currently I cannot delete measures, as it was possible before (with CTRL-DEL) and also the menu entry seems to be missing.
Should I begin two other issue topics or are this problems already known?
073fcdc (linuxmint)
the 2nd issue is known and not really an issue, the function has been enhanced and the shortcut renamed, see https://musescore.org/en/node/126586, you'd need to set the shortcut manually or revert to factory settings
So let's mark this fixed and report that other issue
OK, needed some time - it seems, as if this shortcut was deleted ... It now works!
Thank you!
Automatically closed -- issue fixed for 2 weeks with no activity.
Problem is still present in the newest build: 6a0fb3f
There's an output of Treble Clef Template with some notes.
No style change has been made.The staff space (sp) has been reduced (to 1.5mm).I'm trying to find a pattern when the problem occurs. But I can't... I created a simple score (using A5 paper) and it was rendered wrongly 1_before_save.pdf ; then I saved the file and reopened and everything was OK 2_after_save.pdf .
Another fact, common for all wrongly-generated PDFs, is that the separation happens only to the stems heading up.
I will still try to find a way to get this bug reproducible.
Still exists on Windows 10, MuseScoreNightly-2018-04-06-2019-master-8bb019c.
See the attached pdf exported from the score attached by TS.
Well, it's not so easy to reproduce but it seems I found the pattern.
So, to reproduce this you need:
1. A score (at least the attached one)
2. Any pdf file with a score (the attached files would work but you may want to try it with any other pdf).
Steps to reproduce:
1. Open the attached score (asdf.mscz).
2. File→Export
3. In the export dialog click on a pdf file so that a preview appears. You may use any of the attached pdf files including the correct one (asdf1.pdf), the result would be the same.
4. Click Save, confirm replacing the file.
Result: you get something like this: asdf.pdf.
In my tests the pdf preview step was important, if I skip this the resulting file is correct, see asdf1.pdf.
Tested on
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 5ad448c
Dimitri, the scaling of some items are off in the generated PDF. Noteheads, time signatures and clefs (among other things) are a little too small relative to the rest of the objects. The opposite problem exists when printing: Noteheads, time signatures and clefs (among other things) are too large. I reported it here.
See https://github.com/musescore/MuseScore/pull/4060
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.