Pdf rendition and wysiwyg problems
Open the attached score. Use the export command to generate a pdf. Set the pdf to display at 100%. Various elements in the score are not as sharp as they should be.
And much of the text in the final text frame of the score has been lost in the pdf output.
Now install the free "pdf creator" (available from http://www.pdfforge.org/pdfcreator). "Print" the same score using pdf creator as the printer. Set the resulting pdf to 100% and compare the output to the previous pdf. It is noticeably improved in sharpness.
But still, there is the same problem with the final text frame in the score.
| Attachment | Size |
|---|---|
| morley_ the_man_is_blest.mscz | 19 KB |
Comments
If that text uses tabs, this is a know and meanwhile fixed problem
WISYWIG issue solved (there are tabs in the score). That just leaves the issue of differing quality pdfs.
I don't see any issue with the exported PDF on my system. Could a difference in the PDF itself, or in the program used to view it. Could you post the PDF you are getting, and a screen shot showing the issue you see? Also, which PDF viewer are you using? Could also be difference in screen resolution and whether "100%" happens to correspond nicely to an an integral division of pixels or whatever.
As requested here are two comparison pdfs for the score in question.
The Musescore pdf maker produces a file of 42 kb. "Pdf Creator" produces a slightly larger file (56kb) and notes and text are less bold but also sharper. Both viewed using Adobe reader X at 100% magnification.
In reply to As requested here are two by geetar
Can you post a screenshot of what you are seeing? For me, these look identical, except PDF Creator has a few small glitches - the ends of the system backets not quit lining up right.
I'm inclined to think that what you are seieng with the MuseScore version are just ordinary scaling artifacts that are a function of the specific viewer you use, the magnification, the screen resolution, your graphics drivers, etc.
In reply to Can you post a screenshot of by Marc Sabatella
Remarkably, what I'm seeing is that the MuseScore version has the ends of brackets not quite lining up right.
Attached as requested, two screenshots. The differences I mentioned are apparent here also. I have checked the pdfs on two different PCs and the difference is apparent in both cases. The graphics software on the machine that has produced these snapshots is NVidia 7.8.840.0, the latest update. The second machine uses a Mobile Intel 945 express package.
Just to be absolutely sure: are you viewing in the desktop version of Adobe reader, NOT the in-browser version (which does look different). And at 100% magnification.
Re: "End of system brackets." I presume you mean the bar lines at the end of a system? Their absence is due to the fact that most of bar lines have been hidden just like the original here . I thought this was "normal."
In reply to Attached as requested, two by geetar
I think ZackTheCardshark was referring to the system bracket on the left hand side of the clef as highlighted in the attached image.
When the PDF Creator document is viewed in web browser (Chrome 42 on Windows 8) I can also see two additional lines of text on the right hand side of stanzas 2 and 4 (at the very end, below all systems).
In reply to Attached as requested, two by geetar
I am on Linux, no Adobe software at all. But I checked a variety of other viewers, also on iOS. No issue except for the glitch in system bracket for the PDF Creator version (the bracket connections the systems on the left), as shown in another reply).
Your screenshots both look pretty fuzzy to me compared to either it looks on my monitor. I assume that's because your screen resolution is lower than either of the machines I tried, and that even the screenshots look different on your screen.
Anyhow, it's perfectly normally for artificacts like this to appear at particular combinations of screen resolution, monitor resolution, view magnification, etc. Consider, if the font rendering calculations that that a line is to be drawn 3.5 pixels wide for your given resolution / magnification, the software has to decide wheteher to draw that 3 or 4 pixels, and it has to make that same type of decision for every single line it draws. It's inevitable that this won,t always look right. The higher the resolution the device, the less likely to be an issue for any given magnification, which is why you mostly see this on screen not in print.
Some programs provide "anti-aliasing" controls to reduce the effect - I believe most Adobe programs do. It looks from your screenshots like your Adobe program has chosen different anti-aliasing behavior for the two files for whatever reason. You can probably override those defaults if you check the documentation.