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
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
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
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
___
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
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
