in a 1400 bar score with 9 flows I’ve done parts first. to be able to see and correct each line before I get into the score with condensing etc.
Is there a recommended order ?
in a 1400 bar score with 9 flows I’ve done parts first. to be able to see and correct each line before I get into the score with condensing etc.
Is there a recommended order ?
yes, put in all the notes articulations, slurs, dynamics, etc… in your score, then let Dorico take care of the parts.
As for condensing, don’t do that until the very last note has been entered.
I always do parts first. Then score.
When you say “done parts first”, do you mean layout, or note entry?
Are you transcribing an existing set of parts into Dorico, or composing/arranging something yourself?
Typically, I do the layout of the Full Score before I tackle the parts. But I don’t think it matters. The important thing is to get all the notation in before starting any layout work.
Thank you all !
Ok, so it’s possible to do both.
Yes all notes, dynamics, articulations, texts etc. then the layouts. And I do the parts first. Because once you put on the condensing, with a score of this size it becomes really slow.
I was really scared about the condensing but I’ve run into only two things up to now.
One was a Condensing grace note a2 thing, easily fixed.
The other thing is a div. unis. problem, in the strings in the score.
It’s perhaps best to do that problem as separate post.
Thank you for answers !!
Very sincerely,
Joakim
Remember to check your local/global properties settings.
Jesper
true!
In what sens ?
would globally locally be the technique to solve this ? :
I just meant that if you do the parts first, then in the score, having set local properties globally would change any property edits you made in the part. So be careful.
Jesper
yes. I’m doing it like that. locally now in the score.
thanks !!
do you have a solution for this also : this is the part
but in the score I would like “2 soli”
but since it’s a condensed score I can’t put another text…
ah you can change the player label text…
yes.
so I hide “solo”.
and change “div.” into “2 soli”.
the first thing that happens is
since there is now '(apparently) a difference between first and second divisi.
But I can hide the other texts also. a little tricky but
got there.
thank you jesper !!
but how do I do with this :
if I do like this in galley view and in the part:
I end up with this in the score:
what’s the method ??
Time to eat, I’m sure (hope) someone else has an answer. Haven’t used condensing very much myself.
Jesper
thanks for all jesper !
Is the problem that the unis. label is over the empty bar, and not snapping to the notes a few bars later?
If so, that’s unfortunately how it works for now. Divisi labels snap to notes in uncondensed staves, but when the staves are condensed, the labels above the staff are actually condensing player labels, which unfortunately don’t snap to notes/entrances. You can fake it with a playing technique or staff text.
I’m not sure what this toggle is doing. Under Layout Options→Staves and Systems.
Jesper

extremely valuable info.
so how do I do that ?
in write mode:
•putting a “unis.'“ text in the part.
•hide that text in the part in properties locally
in engraver mode:
•hide the first “unis.” in the score
or a better way ?
thanks!!
j
I already have that, and it doesn’t do anything.. thanks jesper !! /j
I believe that option refers to automatic divisi/unison labels on uncondensed divisi staves, when set to show above the staff.
The unis. shown above the empty bar in the score isn’t one of those, it’s an automatic player label, generated by condensing. Player labels don’t snap to notes.
Yes that’s a good way to do it.
Thanks @Stu_M
Jesper