Hello Aaron,
> Tags might be a reasonably simple option here.
Yes, that really looks promising! I'll try that as soon as I can.
Thank you!
--
Markus Grunwald
https://www.the-grue.de/~markus/markus_grunwald.gpg
___
lilypond-user mailing list
On 06/27, Ben wrote:
> Mason,
>
> Does that mean for every piece of yours you have separate dynamic contexts
> for every single instrument? I'd imagine that could possibly clutter up your
> score a bit, no?
>
> To have many dynamic context variables mapped to all their appropriate
> instruments,
On 6/27/2018 1:20 PM, Mason Hock wrote:
On 06/27, lyuser.theg...@spamgourmet.com wrote:
But I have one issue with the reuse of my work. My last score e.g. has
four voices (T1, T2, B1, B2). I assign music and lyrics for each voice
to a variable and combine them info a choir staff. So for our
On 06/27, lyuser.theg...@spamgourmet.com wrote:
> But I have one issue with the reuse of my work. My last score e.g. has
> four voices (T1, T2, B1, B2). I assign music and lyrics for each voice
> to a variable and combine them info a choir staff. So for our
> rehearsal, everybody can see all the
Hi Markus,
\tags are, as Aaron said, the way to go.
I'd just like to mention the way I often handle this, perhaps this is on any
help:
Instead of tagging each and every single dynamic element, I often completely
\omit certain stencils of a voice, if applicable.
The following example, while not
On 2018-06-27 04:08, lyuser.theg...@spamgourmet.com wrote:
What I would like to have is a simple switch in lilypond that
hides the duplicated markup, so that I can use the same variables for
both use cases.
You mentioned finding some proposed solutions already, so I hope I am
not just
Hello,
This time, I have a more general question:
I've set some scores for my men's choir using lilypond - and I love it
:) With the help of this list, these scores look just like I would
like to have them and our singers like to read them.
But I have one issue with the reuse of my work. My
