PDF Creation
I appreciate that the current windows nightly builds are experimental and have been using it to test the new flexible chord rendering system by Marc Sabatella. I have found the build to be fairly stable and the rendering of chord symbols excellent. However I have noticed an increase in the size of documents generated by the PDF creation engine - sometimes as much as 3 times the size. These are purely 1 line leadsheets with an average saved size of 45KB in Version 1.3, whereas when generated in the current published nightly build can be as high as 150+KB. Is this an expected behaviour? Thanks.
Comments
It's not expected per se. Nightlies and current stable version uses the same Qt libraries I believe. Are you using the same font?
In reply to It's not expected per se. by [DELETED] 5
Thanks lasconic - but not that I am aware of. The only thing I see that is different is the inclusion of the WYSIWYG style files provided by Marc.
In reply to Thanks lasconic - but not by steelman1991
I did copy and paste on the two versions (1.3/Nightly 24b9101);
Saved and exported as a PDF, it may be useful, respectively 19.2 KB - 50.9 KB
-------------
The same procedure but score ex novo 10.8 KB - 26.4 KB
In reply to @lasconic by Shoichi
So basically same behaviour I'm witnessing in size terms - thanks Shoichi
In reply to So basically same behaviour by steelman1991
Anyone been able to have a look at this - behaviour still exhibiting in the most recent nightly build MuseScoreNightly-2013-06-28-2207-8eb93db
In reply to Anyone been able to have a by steelman1991
Fwiw, in case anyone was wondering, I can't think of anythi about the chord symbol changes themselves that could be causing this. The changes are purely at the UI level. The actual mechanisms used to render chords hasn't changed a bit. I could easily imagine differences in PDF size depending on the font you use, but that's about it. I assume you'd find the sme size difference even in in a score without chord symbols. But if that turns out not be true - if PDF's of files with no chord symbols also turn out bigger on your system - let me know.
In reply to Fwiw, in case anyone was by Marc Sabatella
Hi Marc - sorry if I clouded the issue, but I wasn't suggesting that the inclusion of the new chord rendering system was the actual cause of the increase in size, merely pointing out the difference in saved file sizes between 1.3 and the nightlies. This happens with all scores irrespective of with or without chords, there is a slight reduction in file size without chord symbols, but this is relative, as the same file rendered in 1.3 is still 1/3 of the size of the same score saved to a PDF file in the nightly build..
Clearly something has changed the behaviour of PDF sizing, but I, like you doubt it is the inclusion of the new chord rendering system - Are you seeing similar results or are your results the same as in 1.3?
Thanks again for the assistance and reply.
In reply to Hi Marc - sorry if I clouded by steelman1991
Just tested quickly with Promenade example from the nightly build
1.3 - 38kb
2.0 - 255kb
quite a difference?
In reply to Hi Marc - sorry if I clouded by steelman1991
I hadn't checked, but just did, and indeed, I see a very large increase in PDF size from 1.3 to 2.0 - on the order of 5X in the case I just tried.
In reply to I hadn't checked, but just by Marc Sabatella
I think the difference comes from the fact that in version 2.0 text is converted to path during pdf export.
Indeed, if you save the same file in 1.3 and in 2.0, you can select the notes of the 1.3 pdf file as text, while you can't do the same for the 2.0 pdf.
Conversion to path was introduced to preserve shapes for svg export.
Since pdf embeds the proper subset of the font, this extra step is not probably necessary in this case.
Ciao,
ABL
In reply to Texts and paths by ABL
In fact converting text to curves causes problems if you ever want to edit the text directly in the PDF
In reply to In fact converting text to by ChurchOrganist
Most of the text is not converted to paths and it's not linked at all with the SVG export. Let's not mix things...
The musical elements are indeed not exported as text anymore and it's due to the fact that Musescore development version is using an OTF font. Apparently, Qt can't embed OTF fonts while creating PDFs. We will roll back to TTF asap and that will solve the PDF size issue.
In reply to Wrong by [DELETED] 5
Sorry for having created confusion.
I tought that the conversion to path for pdf was related to the same thing happening for svg (I searched about text to path conversion through the forum and the svg behavior was what looked more similar to what was happening here).
Next time I will try to perform a deeper search through the forum posts before wild-guessing :-)
In reply to Wrong by [DELETED] 5
Thanks lasconic for having a look and remedying. Its appreciated.
In reply to Thanks lasconic for having a by steelman1991
Should be done in 762ef8544f
Tests are welcome!
In reply to Should be done in by [DELETED] 5
Hi lasconic - initial testing indicating that the problem has been resolved - many thanks for resolving this. Will keep an eye on it and report back any issues.
Thanks again.
In reply to Should be done in by [DELETED] 5
I'm getting larger PDF files with 2.0 Nightly d6d0b1a on a Mac running Mavericks 10.9.1.
PDF file size in 1.3: 109 KB,
PDF file size in d6d0b1a: 1.8 MB.