PDF export of parts - multiple problems
Piano reduction for two hands (piano duet) - two piano parts: Primo and Secondo
https://musescore.com/user/4151271/scores/24834334
- The main score line breaks don't replicate in the parts the PDF exports. Piano duets need to have the score pages sychronised as they are facing pages in a single score with page turns used by both players.
- The exported PDF parts are not given the actual part names Primo/Secondo but Piano 1 and Piano 2 (There's a problem on musescore.com that may derive from this where the keyboard view of the score calls them - even more confusingly - Piano and Piano (1) ).
- The PDF export of Secondo (Piano 2) has roughly one page in the score not drawn properly and spread over three pages:. see screen-shot. There is nothing in the on-screen display of the whole score or parts that shows any issues. The other exported files (whole score and Primo) have no equivalent issues.
KALINNIKOV Intermezzo No.2 (4H)(ms)-Piano_2.pdf - I noticed while creating the score some other strangeness that I haven't been able to replicate. I set up the score with two piano parts and hid the Primo part while entering the entire Secondo, and then unhid the Primo to finish. I discovered partway through the score a few bars I had copy-pasted within the Secondo were had also been pasted into the Primo.
OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.1-250800846, revision: 603eca8
| Attachment | Size |
|---|---|
| Secondo - neasures 100-126.png | 169.17 KB |
Comments
So just do that. Done in the attached for the 1st page of each, the rest left as an excercise to the reader ;-)
Done in the attached
Done in the attached
In reply to That's normal, you've… by Jojo-Schmitz
There seems to be more disconnect betrween score and parts than is documented, belying the advertised sycnhronizations e.g.
a. Page settings like scaling and margins are not replicated from the score to the parts. I had to reset them in each part.
b. multi-bar rests are turned on in the parts despite being disabled in the major score. I have to disable them individually in each part.
In reply to I am surprised that the… by memeweaver
Layout between main score and parts are different by design, this is triu for system breaks (and, for more obvious reasone, page breaks) but also for scaling and paper format.
Multimeasure rests being set to on for parts and off for main score is by design too. And exactly the main reason for system breaks for replicating: they just don't make sense in that case.
The synchronization between main score and parts is about their content, not about their layout. In this respect Mu4 isn't different from Mu2 or Mu3 (Mu1 didn't have linked parts), and this is happening on purpose.
The problem is that in Mu3 (and 2) You had to explicitly generat parts to be able to export them (and many users found that confusing) while in Mu4 the parts are automatically generated on the fly on export (and that does confuses users too), unless you did generat them explicitly.
In reply to Layout between main score… by Jojo-Schmitz
>Layout between main score and parts are different by design, this is triu for system breaks (and, for more obvious reasone, page breaks) but also for scaling and paper format.
I can't see any reason why you would ignore user adjustments to the main page settings when creating subsidiary PDFs like parts.
>The synchronization between main score and parts is about their content, not about their layout.
![Musescort part synch.png]( "Musescort part synch.png")
The UI and documentation speaks to appearance properties, .. and pretty much every property I've had problems with is not included in the umbrella "essentially, all other properties"
Multimeasure rests being set to on for parts and off for main score is by design too.
> Undocumented and there are no parts-sensitive options for it in the settings. It's really annoying picking through all these settings to disable them part by part. Multibar rests in particular as I have to break them open to set system breaks as desired.
In reply to >Layout between main score… by memeweaver
System breaks are not a style setting! Nor a position! Nor are page settings BTW...
Use https://musescore.org/en/project/export-layout-breaks-parts to transfer them
Mulit measure rests being enable for parts by defailt has been the case ever since the intorduction of linked parts in Mu2, and I'm sure this is documented.
You can prevent this from happening by setting up a style file and load that automatically for all parts via Preferences
In reply to >Layout between main score… by memeweaver
When you set a style for a part there is a button at the bottom of the dialogue that says "Apply to all parts". If you want the same setting in all parts that is the one to press after you have adjusted one part to your taste.
Regarding synchronisation between score and parts. Consider an orchestral score - typically one system per page, system length determined by the requirements of the "busiest" instruments, no multi-measure rests shown as there are no multi-measures where all instruments are resting. Compare with an individual instrument part, several systems per page, system length determined by the requirements of that part only, often resting for multiple measures while other instruments do their own thing. The layout requirements for a score and an individual part are very different.
In reply to When you set a style for a… by SteveBlower
As I am making decisions about system breaks - based on space, readability, continuity, recurring figures etc - as I am notating, having them preserved in the parts is of immense benefit.
It's a few seconds work to bulk remove the breaks from the parts than it is to have to manually go through hundreds of measures to recreate them.
In reply to As I am making decisions… by memeweaver
It is a few seconds using that plugin to transfer them.
In 90% of the cases they won't make any sense in parts, and there is of no benefit at all.
In reply to is a few seconds using that… by Jojo-Schmitz
As most of the people advocating for this functionality in the thread that generated it will note, it is of great benefit.
By the logic of features not being of benefit unless they're useful in the majority of scores, then there are plenty of obscure notation features in Musescore that would never have been implemented.
In reply to is a few seconds using that… by Jojo-Schmitz
I tried the plugin on a larger piano 4H score: https://musescore.com/user/4151271/scores/24896425, which is only one movement of a larger symphony project.
Source score has system breaks over 454 measures applied after m6 at every 4-5 measures - thus expecting around 100 system breaks,
Resulting system breaks from plugin
* Primo at m6, m41, m42
*Secondo at m6, m41, m44
So about 3% of the expected system breaks and only one applied correctly; the others not even at matching measures!
I tried clearing the breaks and running it again: aside from m6, I still got only 2 additional breaks in each part: roughly in the same place, but again not consistently.
Just to be sure: I restarted Musescore with part system breaks cleared but just got a rehash of the above.
In reply to I tried the plugin on a… by memeweaver
Well, with very few exceptions (m6 is one of them, m41m and m45 the others) you're using system locks, nit system breaks.
As that plugin is/was for MuseScore Studio 4.4 (and later), where these didn't exist, it doesn't (yet) know about them, hence can't replicate them.
But it does do them at these 3 measures (6, 41 and 45). for both parts, not at m42 or m44, check again
I'll check whether I can fix the plugin to work on system locks too
In reply to Well, with very few… by Jojo-Schmitz
>>you're using system locks, nit system breaks.
I hit enter and sometimes I get locks and sometimes I get breaks. As you say "There's really no point in fighting against what the Program is doing by design." I don't know what the design intent of that is.
>>But it does do them at these 3 measures (6, 41 and 45). for both parts, not at m42 or m44, check again
I did it three times and got three results. I can count and recognise numbers. The different measures stretched out to page width was a huge clue to them being different.
In reply to >>you're using system locks,… by memeweaver
I hit enter and sometimes I get locks and sometimes I get breaks
Enter gives system breaks. Ctrl+Enter gives page breaks. Enter never gives a system lock.
Unless there was a bug in 4.5.0, which what your score stems from. Update to 4.5.2 (released just today)
For System locks you's need Alt+L (to lock all system use Ctrl+Alt+L), it is a toggle.
I can count and recognise numbers
I looked at the score you shared. And counted there...
And tried it myself.
In reply to As I am making decisions… by memeweaver
There's really no point in fighting against what the Program is doing by design.
You'd need to work with the program, not against it.
In reply to There's really no point in… by Jojo-Schmitz
Because of gaps or poor expression in the documentation, it is frequently very difficult to distinguish between "by design" and bug.
In reply to I am surprised that the… by memeweaver
Ad 4.: That'd be a bug indeed, but ISTR to have seen it being reported already. When in doubt, check GitHub
In reply to I am surprised that the… by memeweaver
See also https://musescore.org/en/project/export-layout-breaks-parts