MuseScore 2.0 Beta 2: Broken arpeggios on PDF
In Beta 1, the tempo marking in a PDF file was broken, and that seems to have been fixed in Beta 2. But now there's a new problem: arpeggios (rolled chords) are not showing up properly in PDF files. I have tried deleting and re-inserting the arpeggio on MuseScore and re-exported to PDF, but it still did not show correctly.
Now I can't use rolled chords in any of my compositions without rolling back to Beta 1, something I don't want to do and which had issues of its own.
I've attached pictures of the offending arpeggios. I am running 32-bit Windows 7.
Also, please notice how the PDF file spaces the text further apart. This was not an issue in Beta 1.
Is there any fix I can do to solve these problems, especially the broken arpeggios?
| Attachment | Size |
|---|---|
| Good arpeggio.png | 9.52 KB |
| Bad arpeggio.png | 11.64 KB |
Comments
See http://musescore.org/en/node/41956 - we are the vitctims of a known Qt bug on Windows. Unfortunately it looks like we have to live with this a little while. Meanwhile, you can use a third party PDF printer like PDF Creator.
If your experience is like mine - using 64-bit Windows 8.1 u1, and having the exact same problem - you will not be able to roll back to Beta 1 any files that you've saved in the Beta 2.
Instead, you'll get a 'Load Error' message informing you as follows: 'Cannot read file [filename].mscz. This score was saved using a newer version of MuseScore. Visit the MuseScore website to obtain the latest version.
Everyone potentially affected by this bug should be aware of this!
In reply to If your experience is like by [DELETED] 448831
@stevebob is installing a third party PDF printer a temporary workaround solution for you?
In reply to @stevebob is installing a by Thomas
Yes, Thomas, it is. Thank you for asking!
In reply to Yes, Thomas, it is. Thank by [DELETED] 448831
Just FYI - It turns out PDF Creator is less than perfect in that some symbols are dropped. I realize that this fault lies not with MuseScore but rather the third-party program that generates the PDF (and that other such programs are likely to have their own shortcomings), so I see no point even in trying to document the specific deficits of PDF Creator. I'll just be sitting tight until the new version of Qt is released and PDF files can again be correctly exported from MuseScore instead of 'printed' by using an external PDF writer.
In reply to Just FYI - It turns out PDF by [DELETED] 448831
This is a workaround, I agree. I'd rather stay in MuseScore environment because: 1) the PDF export is faster 2) it would avoid some download sites more or less doubtful.
My fear, unjustified, perhaps? That the next version of Qt (and when?) corrects this issue but introduces another - as happened recently - or others issues, and so on ... :(
Finally, a question: Can you be more specific when you write: "some symbols are dropped" with PDFCreator? Which ones? Thanks
In reply to This is a workaround, I by cadiz1
It turns out I was wrong - or half-wrong, at least. I believed that parentheses around a note had been dropped - but when I re-checked my MuseScore file, the parentheses weren't present after all. Apparently I was mistaken about this, and I should have double-checked the MuseScore file first before assuming that PDF Creator dropped those symbols.
However, another symbol definitely was dropped by PDF Creator - but it's obscure, and I've already found a workaround that I should have been using all along. It's the little curved line used to indicate finger substitution in keyboard music, and I have always created it via a font I've had around for years called WPPhonetic:
(The actual fingering numerals are in the MScoreBC font.)
So yes, this symbol - created with the WPPhonetic font - was in fact dropped consistently by PDF Creator. However, I've since found that the same symbol exists in the FreeSerif font included in MuseScore. It's the last pair of symbols in the Insert Special Characters dialog:
Now that I've discovered this and experimented with it, I've found that PDF Creator handles the FreeSerif symbol just fine:
I honestly don't know the technical term for this symbol, although it was used uniformly by many publishers in the pre-digital era. I have guessed it's an 'elision'. Nowadays, it seems increasingly common for finger substitution to be indicated by a plain hyphen - but I like the old-fashioned look for the Classical and Romantic era scores that I re-typeset. And, in any case, the symbol in FreeSerif is actually equally functional and considerably more attractive (with tapered end points).
In summary, everything's good after all - so far as I'm presently aware.
as another workaround: for arpeggios you could use the straight ones. Sound the same on playback and should convey the same meaning to the musician
I found this problem in MuseScoreNightly-2014-12-23-1606-bf97799 too. (WINDOWS)
In reply to I found this problem in by kanakomoerer
Yes, of course. We need Qt-5.4.1 for the real and final fix
In reply to Yes, of course. We need by Jojo-Schmitz
I haven't been on here as much as I wanted, but I keep seeing Qt and Qt 5.4.1 being thrown around here. How do I get Qt 5.4.1 on MuseScore 2.0 beta 2? Is that even possible, or do I need to wait for the final release of MuseScore 2.0?
In reply to I haven't been on here as by dlee1
You need to wait, if not until the final release, then at least until a nightly build becomes available that uses Qt 5.4.1.
For all users,
If you can create PDF-Version,
1.Please export 'PNG' file-format
2.and use any convert-software,
3.and merge these files.
thx.
4.
or please use this symbol (attention! bravura font!)
this symbol is no error.
In reply to 4. or please use this symbol by kanakomoerer
Or use MuseScore 1.3, it's working perfectly there.