Export as PDF
I understand (from wording that implies "still under development" or similar) that development of Export PDF is still not final, but have the following two issues:
1. Producing a PDF copy of music for one instrument (of 18 in the full score) gives different results for (a) using the "Export as PDF" (selecting the particular instrument in the drop-down list and de-selecting the "whole score" item), and (b) selecting the instrument (in the main, normal score display) only by hiding all of the "unwanted" instruments ("closing eye" within the "instruments" menu) and then printing to PDF. I attach the two results. The "normal" (with non-wanted instruments hidden) PDF now (compared to previous versions of MuseScore) seems to have a rather random incorporation of the multi-rests. I prefer the "Export PDF" version.
2. The drop-down list of instruments selectable within "Export PDF" has a selection of "instrument types" as originally selected from the available lists. This presents a problem where several instruments of the same "family or type" are selected (e.g. solo cornet, #1 cornet, etc). I believe the list should be from the user's names as given under "instrument - long name". Leading on from this, the PDF copy has one sub-title near the top left which states the "instrument type. This should be the "instrument - long name" or other as selected by the user, but there is no way of entering a name for this field on the output.
Regards,
Noel Hall
| Attachment | Size |
|---|---|
| Concerto for Bass Tuba.mscz | 113.37 KB |
| Concerto for Bass Tuba_15a.pdf | 78.98 KB |
| Concerto for Bass Tuba_15b.pdf | 252.49 KB |
Comments
Exporting to PDF isn't experimental at all, that works fine. It's import of PDF that is still experimental AI technology.
The names of the parts are taken from the part names (in the Parts dialog), not the instrument names. That's an important distinction, between a Part can contain multiple instruments. So there will be just one part name but potentially multiple instruments with it. That's why ti's important you can select by part name.
Not sure why you'd by hiding instruments in the main score, though. Unless maybe you haven't found the Psts dialog yet, which generates the parts automatically?
Regarding the rests, it's not totally clear what is going on, but if you can give precise steps to reproduce that issue we can understand and assist better. When I generate the parts normally via the Parts dialog, the solo tuba parts shows a 16 measure rest as I expect.
In reply to Exporting to PDF isn't… by Marc Sabatella
Hi Marc,
I started to reply but lost the text. My task was to produce copies of brass band music from (often photocopied hand-written originals) - 18 instruments, and scores totaling over 50 pages.
I have an issue with multi-measure rests. Two of the PDF versions (15a and 15b) of the score for "Tuba Soloist" were previously attached. One was taken as a MuseScore program "front page" view and which was then printed to PDF. This version had, in its first line, 3 bars of multi-measure rests (2, 3 and 6) with other vacant bars between. The same score, when then taken, through File-Export-PDF (and selecting the "Tuba unspecified" part) produced the single multi-measure rest (16) up to the first Rehears am Mark (1). My question is therefore why does the multiple number of multi-measure rests appear? This problem did not seem to exist in MuseScore3, and there does not appear to be anything different in the first 16 (empty) bars to warrant this anomaly.
I have used the "hiding" partly because, as I enter music, I want less confusion from the other lines.
The other point I made was in the PDF version created from File-Export-PDF, in which the Part name "Tuba (unspecified)" was included. This means nothing to anyone playing the music, and in my requirement for producing separate copies for each instrument, it would be better to have this "Part name" replaced by the "Instrument long name", and the "instrument names deleted from appearing on any of the lines of music. However I don't know how this name can be changed - can't find it in the on-line help.
Because I have used the same "part name" several times in the total score, prints for different instruments with the same part name are also confusing (and unnecessary).
Regards, Noel
In reply to Hi Marc, I started to reply… by Noel Hall
You can use the Parts system to enter parts individually - no reason to resort to hiding instruments in the score.
Anyhow, again when I generate the tuba part, I see a 16 measure rest. So in order to understand why you are seeing something different,t w'ed need you give precise steps for us to reproduce the problem. But here are mine:
Result: just what I expect - a sixteen bar rest up front:
In reply to You can use the Parts system… by Marc Sabatella
Thanks, Marc.
I have never used the "Parts" system before, and I will have to get used to doing it this way. I can see that I can rename the "Part" through this system. While showing the Part name within the title block of the output, how can I temporarily hide the Part (long name) and Part (short name) - so that these names do not end up taking up space on the printout when the whole page is of that part anyway?
As a supplementary comment/issue, and related to forum issues from others, I am finding that some of the slurs which I have entered throughout the total score seem to randomly get deleted between my MuseScore sessions. So far I have not found any particular actions which may have prompted this - usually just one or more slurs which existed at the end of my last session but are not there when a new session is opened.
Noel
In reply to Thanks, Marc. I have never… by Noel Hall
I'm not understanding your question about hiding names. Do you mean, in the part, you don't wish to see the staff names? By default, you won't. The only reason the long staff name is appearing here is that for some reason you turned off the option "Hide instrument name if there is only 1 instrument" in Format / Style / Score.
As for slurs not appearing in parts, yes, there are a few scattered reports of this occurring, but so far no has succeeded in finding steps to reproduce the problem, so we're a bit stuck in terms of understanding how it happens.