Hello,
did you even try what Urs suggested?
\new Staff <<
\spacers
\one
>>
means that \spacers and \one are simultaneous <<>>, not sequential {}.
So you can just fill in the example Urs gave and it will do what it
seems you want (that hasn’t been easy to understand).
Yours, Simon
Am 10.10.2014 um 22:23 schrieb ViniWolfling:
Hello,
Thank you dearly for your help. Unfortunately I don't think starting
every staff with spacers and writing the music afterwards won't do...
I should have given an example like you did. I apologize. My bad.
Suppose we have 30 measures written in one part. When the other part
has only 2 measures, we put a s1*28 in the end so that it will have
blank measures in until 30.
One = { \repeat unfold 30 c'1 }
Two = { d1 e1 s1*28 }
\score {
<<
\new Staff <<
\One %music up to measure 30
>>
\new Staff <<
\Two %2 + 28 whole spacer rests
>>
>>
}
Now when we write 2 more measures, making it a total of 4, we have to
change that 28 into 26, so that it will still stop at 30, right?
Otherwise, part two will end at measure 32, which is not intended.
One = { \repeat unfold 30 c'1 }
Two = { d1 e1 f1 g1 s1*26 } % !!!!!
\score {
<<
\new Staff <<
\One %music up to measure 30
>>
\new Staff <<
\Two %2 + 26 whole spacer rests
>>
>>
}
So whenever we add music to any part that's not the longest one, we
have to subtract spacer rests. Is there an auto-subtract?
Like, instead of saying "I want 28 spacer rests here, now I want 26,
now I want 20, now I want 14..." there could be a goal-oriented
statement like, "Fill this part with spacer rests up until measure 30,
regardless of how many measures I've written as of now"
That way, as long as the goal doesn't change (which it will, but much
less often), Lilypond would guarantee all the parts end at the same
point with blank measures. Part two could have 4 implemented measures
and 26 spacer rests, while part three would have been written until
measure 10 and filled up with the remaining 20 measures automatically.
Not sure if this exists, though. Could be a feature request, but I'm
not sure others would benefit from it. I totally see how I would.
Thanks again for helping out. I really appreciate it. :)
-Vini
On Oct 10, 2014, at 3:26 PM, Urs Liska [via Lilypond] <[hidden email]
</user/SendEmail.jtp?type=node&node=167399&i=0>> wrote:
I *think* this is what you want to achieve:
write one music variable containing spacer rests for the whole piece (or
for the longest part that you already have) and then include that on
each staff. Say:
spacers = {
s1*20
}
one = {
\repeat unfold 20 c'1
}
two = {
\repeat unfold 12 c'1
}
\score {
<<
\new Staff <<
\spacers
\one
>>
\new Staff <<
\spacers
\two
>>
>>
}
That way the \spacers part keeps the staves alive.
HTH
Urs
Am 10.10.2014 16:22, schrieb ViniWolfling:
> Hi everyone,
>
> I was playing with spacer rests for a multi-part, partially-blank
score, and
> it occurred to me to put them in every unfinished staff until the
empty
> measures “catch up” with the one staff that is already finished.
Like this:
>
> • Shinobue (Japanese flute) part consists of 30 measures, for the time
> being.
> • Shime-, Kumi- and Oo-daiko parts (all Japanese drums) are either
mostly or
> completely empty.
>
> I'd like to save a pdf with all the still-unwritten drum measures
as blanks,
> so that I can doodle on them on an iPad or any other tablet, or
even paper
> (not the most eco-friendly solution, so nope). This is pretty easy
since I
> know the number of measures I've already written, but updating the
remaining
> number in the s1*XX statement all the time is very annoying.
Especially when
> I forget to, upon adding music, which makes the spacer rests
overflow the
> end of the score.
>
> Now on to the point: is there a way to ask Lilypond itself to kindly
> calculate the remaining measures and decide how many whole spacer
rests to
> put in each distinct staff?
>
> I think what I'm trying to say here is... Is there a way to say “Hey
> Lilypond, no matter how many measures have already been written on the
> shime-daiko staff, whether 0 or 29, you just make sure to put
spacer rests
> up until there are 30 measures”? Then I can change that number much
less
> often than every time I run the typesetting command for every
single new
> measure.
>
> Or is this just plain lazy of me to even think of such a feature? :(
>
> Thanks in advance for all the support. I sometimes come here just
to read
> the topics, and solutions posted here often inspire me. <3
>
>
>
> --
> View this message in context:
http://lilypond.1069038.n5.nabble.com/Automatic-multimeasure-spacer-rests-tp167387.html
> Sent from the User mailing list archive at Nabble.com
<http://Nabble.com>.
>
> _______________________________________________
> lilypond-user mailing list
> [hidden email] </user/SendEmail.jtp?type=node&node=167394&i=0>
> https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
[hidden email] </user/SendEmail.jtp?type=node&node=167394&i=1>
https://lists.gnu.org/mailman/listinfo/lilypond-user
------------------------------------------------------------------------
If you reply to this email, your message will be added to the
discussion below:
http://lilypond.1069038.n5.nabble.com/Automatic-multimeasure-spacer-rests-tp167387p167394.html
To unsubscribe from Automatic multimeasure spacer rests?, click here.
NAML
<http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
------------------------------------------------------------------------
View this message in context: Re: Automatic multimeasure spacer rests?
<http://lilypond.1069038.n5.nabble.com/Automatic-multimeasure-spacer-rests-tp167387p167399.html>
Sent from the User mailing list archive
<http://lilypond.1069038.n5.nabble.com/User-f3.html> at Nabble.com.
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
