Setting PDF resolution to 2000 DPI has strange effect on braces, not spanning the entire range
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
When you export into pdfs a score with harp or piano, the key that lash the two systems ends up short, like on the fourth line of the treeble clef and the note heads and stems appear not perfectly in line. all of this appears in the pdf file, not in the editor.
Comments
Sounds like you are having some sort of problem using MuseScore, but it isn't clear what just from the description. Something where a specific score when exported to PDF looks wrong? Please attach your score and give precise steps to allow us to reproduce the problem you are seeing. Also say what OS you are on and what version of MuseScore (Help / About).
In reply to (No subject) by Jojo-Schmitz
As you can see, the systems are not properly lashed together, and in the first G# the note head is not aligned with the stem. Im sorry if I myspell something, i speak spannish as a my mother language.
thanks!
Please share the score too
Also say what OS you are on and what version of MuseScore (Help / About).
Edit: the PDF got created by MuseScore 3.6.2, and not in a Mac, as far as I can tell. (so we still need to know your Operating System).
For some reason uses Bravura and Leland, the former probably because of a fallback for some glyphs not available in Leland.
And here's an image showing the mess:
![foo.png]( "foo.png")
In reply to Please share the score too by Jojo-Schmitz
Im running windows 10, ill attach the score and the pdf, the errors appear when i create the pdf thats the poblem because i cannot fix it in the editor. in adition to the lashing of the two systems i have some beams and steams out of alignment here and there with no clear reason ( this happenned on the second G# for example )
That score and the PDF don't show any issue, they do look identical and correct. But quite different from the PDF in the inital post
yes its a different score but the problems are there, its happening everytime I export something in pdf format. i find note heads out of alingment and the brackets dont cover the two staves.
What PDF viewer are you using?
In reply to What PDF viewer are you… by Jojo-Schmitz
foxit reader or adobe acrobat reader, I see the same on both
And you are using File > Export > PDF?
I don't understand why I don't see this if I use this on that sample score, nor see it in the 2nd PDF you provided
yes of course. so, if you do that in the score that i submit you dont see the things i marked on th png?
In reply to yes of course. so, if you do… by nehuen251
the pdf resolution is set to 2000 dpi i dont know if thats the default setting
See this, in MuseScore:
![Un_calido_azul_(1).png]( "Un_calido_azul_(1).png")
![Un_calido_azul_(2).png]( "Un_calido_azul_(2).png")
And this in Acrobat:
2000 DPI certainly is not the default setting, I'm pretty sure 300 DPI is, but that matters only for images embeded in a score.
Tada! That is it, much to my surprise!
Workaround: set it to 300 DPI, the default setting
Another workaround, at least for the brace (I don't see that other issue in any case), is to use Emmentaler or Gonville, only Leland, Bravura, MuseJazz and Petaluma seem to have that issue
im beyond happy and grateful hahahaha thanks a lot for your attention and help, i was going mad trying to solve the issue!
once again, thank you !
Nehuen,
In reply to im beyond happy and grateful… by nehuen251
360 (5*72) should be the default, has been since quite a while IIRC
IIRC that default changed, from 360 to 300 to match the default for PNG
AFAIR it was the PNG default that changed, which I only noticed due to a comment from you some time ago stating so ;) when updating the manpage…
So, 360 for both.
Ah, this way round then. I only remembered to have them made identical