Export as pdf cropped

• Jan 5, 2019 - 23:54

Hello Musescore Developers,

I found a problem which is propably a bug.

When I do File->Export the resulting .pdf is cropped - (the music starts on the top of the page, the border is not respected).

Presumable Reason:
My pdf-Viewer says the paper format is "US-Letter, Hochformat (216 × 279 mm)", even though in Layout->Page Settings it says "A4, 210,06mm x 296,93mm".
I assume the problem is that the exporter doesn't respect the page settings.

How to reproduce:
1. create any score, e.g. start with an empty score and add lots of empty bars (Ctrl + B).
2. choose File->Export
3. Voila

OS: Arch Linux, Arch.: x86_64, MuseScore version (64-bit): 3.0.0., revision: 3543170

It's an annoying bug, which renders the exporter almost pointless.
Can it be reproduced?
Is it difficult to fix?


In reply to by Shoichi

On your system the export seems to work. Where do you set the "pdf print properties"? If there is such a thing the problem is obvious. When I select "File -> Export" there is no such options, just the "Save As..." dialog.
Yeah, in my case changing the page settings to "216 × 279 mm" helps.

In reply to by Jojo-Schmitz

I want A4, thats why in "Format->Page Settings" I chose "A4". But "File->Export" doesn't respect this, but seems to exports as "Letter ..." (without giving me an option to change that). And in the end the result is cropped.

(choosing "Letter" in "Format->Page Settings" is just a workaround to at least get a usable .pdf File)

In reply to by EsGeh86

That score is in A4, created with MuseScore 3.0.0 on Linux. The PDF seems broken, Adobe Acrobat Reader DC can't open/display it properly (here on Windows 7), it reports error 14 and shows an entirely empty page. Chrome shows it though.
See https://forums.adobe.com/thread/2351596, which here shows "Expected a dict object." as the detailed error. After that all bets are off I'm afraid.

Adobe then reports the page size to be 0x0mm. I guess your PDF viewer stumbles accross this (and ingnores the error Adobe complains about, just like Chrome does) and shows some internal default format instead?

The revision you report, 3543170, got to be wrong, this is a commit from 2013!
But esp. with Linux we've been seeing this a lot, some maintainers seen to forget to run the 'make release' step in their build process.

Do you still have an unanswered question? Please log in first to post your question.