Re: LilyPond 64-bit version for a Mac
On 03/02, Carl Sorensen wrote: > We cannot use our regular build system to create LilyPond binaries due to > Apple’s restrictive licensing on the OSX SDK. Could you explain briefly or link to why this is? I understand that the App Store's restrictions would violate the GPL, and that Apple avoids distributing anything under GPLv3, presumably to avoid the tivoization clause, but I was not aware of any restrictions on what developers could independently build for macOS and distribute. signature.asc Description: PGP signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: \RemoveEmptyStaves
Thank you!
This should definitely be in the Lilypond Docs for keyboard-specific notation.
-Original Message-
From: lilypond-user
On Behalf Of Malte Meyn
Sent: Monday, March 4, 2019 2:39 AM
To: lilypond-user@gnu.org
Subject: Re: \RemoveEmptyStaves
Am 04.03.19 um 03:17 schrieb Richard Gress:
> Hi all,
>
> Why is \RemoveEmptyStaves not working the way I'm using it? The output
> still shows blank staves in a ten-page document. Uncommenting the
> global command doesn't work, either.
PianoStaff contains the Keep_alive_together_engraver. This means that
individual staves aren't hidden, only the PianoStaff as a whole when all staves
are empty. This makes sense in orchestra music but not for piano solo. You can
use a GradStaff instead or remove the
Keep_alive_together_engraver:
\new GrandStaff <<
\new Staff ...
\new Staff ...
\new Staff ...
\new Staff ...
>>
\new PianoStaff \with {
\remove Keep_alive_together_engraver
} <<
\new Staff ...
\new Staff ...
\new Staff ...
\new Staff ...
>>
In fact, the Keep_align_together_engraver is the only difference between the
two contexts, so both solutions are equivalent.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ties and cross staff beaming
I am putting a score into Lilypond, and I can’t figure out how to
replicate the tied notes in the screenshot below. I am using the
command \change Staff = “bass” to move notes to the bass clef, but I
am not sure how to keep the cross staff beaming and create ties to the
quarter note.
Is there a different way I could create the cross staff beaming, as
then I could insert the notes normally in the appropriate clef and add
ties?
It's possible to use tieWaitForNote if you make sure the notes are in
the right Voice contexts:
\version "2.19.82"
\new PianoStaff <<
\new Staff = "treble" \relative c' {
s1
}
\new Staff = "bass" \relative c {
\clef bass
\set tieWaitForNote = ##t
c8[~ \change Staff = "treble" ] \change Staff = "bass"
c,4
}
>>
In your example, this is going to be a bit more involved, since you need
ties in both hands simultaneously (to be precise, the beamed eights are
going to be in one voice, but the tie-destinations in both hands are
going to be in two different voices).
You might have to resort to invisible notes in one of the systems.
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ties and cross staff beaming
Dear Rachel,
<< {
\change Staff = "bass" c,4
}
\\
{
\up
4
}
>>
Please always give a _compilable_ [and, if possible] minimal example of
LilyPond code to facilitate helping you.
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
ties and cross staff beaming
I am putting a score into Lilypond, and I can’t figure out how to replicate the
tied notes in the screenshot below. I am using the command \change Staff =
“bass” to move notes to the bass clef, but I am not sure how to keep the cross
staff beaming and create ties to the quarter note.
Is there a different way I could create the cross staff beaming, as then I
could insert the notes normally in the appropriate clef and add ties?
Rachel
<< {
\change Staff = "bass" c,4
}
\\
{
\up
4
}
>>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
G'day.
On Mon, Mar 4, 2019 at 1:40 PM Richard Gress wrote:
> Why is \RemoveEmptyStaves not working the way I’m using it? The output still
> shows blank staves in a ten-page document. Uncommenting the global command
> doesn’t work, either.
Because it's not a Staff, it's a PianoStaff. It took me a while to
work this out, too.
It's a similar story for ChoirStaff. I use this:
\layout {
\context {
\Staff \RemoveEmptyStaves
}
\context {
\ChoirStaff \RemoveEmptyStaves
}
\context {
\PianoStaff \RemoveEmptyStaves
}
}
Andrew Bromage
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
