Re: Hiding empty staves
Hello Andrew,
From a previous thread:
%%%
\version "2.19.25"
%{
\RemoveEmptyStaves does not work primarily because \PianoStaff has the
Keep_alive_together_engraver. You should remove that one (or not use
\PianoStaff) and then invoke only the second Staff as
\new Staff \with { \RemoveEmptyStaves } { ... }
I have a harp score where there are a lot of lines that require only the upper
staff. How can I suppress the lower staff in lines where it is empty
If you don't want to retain the upper Staff with rests only when the
lower Staff has notes, things are a bit more tricky.
Basically, you'll
arrange to have your whole PianoStaff removed on demand, give it a
remove-layer of #0 but put _another_ copy of the first Staff (better
though a rest-only variant of it) in parallel with the PianoStaff,
giving it a remove-layer of #1. That way it will only survive into the
final score when both staves in the PianoStaff will die.
%}
%\new PianoStaff
<<
\new Staff \relative c' {
\repeat unfold 5 { c4 e g c }
\repeat unfold 12 { c2 a }
\repeat unfold 20 { R1 }
\repeat unfold 10 { c2 a }
\repeat unfold 8 { c,4 e g c }
}
\new Staff \with { \RemoveEmptyStaves }
\relative c {
\clef bass
\repeat unfold 5 { c4 e g c }
\repeat unfold 42 s1
\repeat unfold 8 { c,4 e g c }
}
>>
\layout {
\context {
%\Staff \RemoveEmptyStaves
}
}
%%%
> Le 3 juin 2016 à 07:54, Malte Meyn a écrit :
>
>
>
> Am 03.06.2016 um 06:39 schrieb David Wright:
>> On Thu 02 Jun 2016 at 21:14:17 (-0400), Andrew Bernard wrote:
>>> I have a two stave piece using a PianoStaff. In some sections I need to
>>> hide the unused lower stave for a number of bars. Using \RemoveEmptyStaves
>>> or \RemoveAllmptyStaves does nothing. There are only spacer rests in the
>>> staff in question.
>>>
>>> The NR in Section A.20 says these functions 'Remove staves which are
>>> considered to be empty according to the list of interfaces set by
>>> keepAliveInterfaces, including those in the first system.’ But what does it
>>> mean for a staff to be considered empty?
>
> This is how keepAliveInterfaces is defined:
>
> keepAliveInterfaces = #'(
>bass-figure-interface
>chord-name-interface
>cluster-beacon-interface
>fret-diagram-interface
>lyric-syllable-interface
>note-head-interface
>tab-note-head-interface
>lyric-interface
>percent-repeat-item-interface
>percent-repeat-interface
>;; need this, as stanza numbers are items, and appear only once.
>stanza-number-interface
> )
>
> A Staff which doesn’t contain items of these types is removed (f. e. a Staff
> only containig rests, spacer rests, but also key changes and some other
> things).
>
>> AFAICT just change PianoStaff to GrandStaff. I think I see the logic
>> in LP's behaviour.
>
> PianoStaff is an alias for GrandStaff except that it contains the
> Keep_alive_together_engraver. So using a GrandStaff should be the same as
> PianoStaff \with { \remove Keep_alive_together_engraver }
>
> This can be found in the Internals Reference and in the file engraver-init.ly.
>
> ___
> 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: Hiding empty staves
Am 03.06.2016 um 06:39 schrieb David Wright:
On Thu 02 Jun 2016 at 21:14:17 (-0400), Andrew Bernard wrote:
I have a two stave piece using a PianoStaff. In some sections I need to
hide the unused lower stave for a number of bars. Using \RemoveEmptyStaves
or \RemoveAllmptyStaves does nothing. There are only spacer rests in the
staff in question.
The NR in Section A.20 says these functions 'Remove staves which are
considered to be empty according to the list of interfaces set by
keepAliveInterfaces, including those in the first system.’ But what does it
mean for a staff to be considered empty?
This is how keepAliveInterfaces is defined:
keepAliveInterfaces = #'(
bass-figure-interface
chord-name-interface
cluster-beacon-interface
fret-diagram-interface
lyric-syllable-interface
note-head-interface
tab-note-head-interface
lyric-interface
percent-repeat-item-interface
percent-repeat-interface
;; need this, as stanza numbers are items, and appear only once.
stanza-number-interface
)
A Staff which doesn’t contain items of these types is removed (f. e. a
Staff only containig rests, spacer rests, but also key changes and some
other things).
AFAICT just change PianoStaff to GrandStaff. I think I see the logic
in LP's behaviour.
PianoStaff is an alias for GrandStaff except that it contains the
Keep_alive_together_engraver. So using a GrandStaff should be the same
as PianoStaff \with { \remove Keep_alive_together_engraver }
This can be found in the Internals Reference and in the file
engraver-init.ly.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On Thu 02 Jun 2016 at 21:14:17 (-0400), Andrew Bernard wrote: > I have a two stave piece using a PianoStaff. In some sections I need to > hide the unused lower stave for a number of bars. Using \RemoveEmptyStaves > or \RemoveAllmptyStaves does nothing. There are only spacer rests in the > staff in question. > > The NR in Section A.20 says these functions 'Remove staves which are > considered to be empty according to the list of interfaces set by > keepAliveInterfaces, including those in the first system.’ But what does it > mean for a staff to be considered empty? AFAICT just change PianoStaff to GrandStaff. I think I see the logic in LP's behaviour. Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Hiding empty staves
I have a two stave piece using a PianoStaff. In some sections I need to hide the unused lower stave for a number of bars. Using \RemoveEmptyStaves or \RemoveAllmptyStaves does nothing. There are only spacer rests in the staff in question. The NR in Section A.20 says these functions 'Remove staves which are considered to be empty according to the list of interfaces set by keepAliveInterfaces, including those in the first system.’ But what does it mean for a staff to be considered empty? Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
hiding empty staves until they are needed
Hello. In lily pond i am creating my final assignment for the semester. Yee! lol! except not. I don't want to write rests and i plan on maybe writing out the repeats. I don't now yet. I want to though hide empty staves until they are needed, then hide the staves again. I saw this in a choir score i was reading for one of our concerts and wondered if that is possible that way i don't have to write out rests. Also how will this effect the parts i will eventually create for each player to turn in to the prof. I have until may 10 probably to complete this assignment and i want to work on a bit at a time so i don't get a headache lol! i'm still using lily pond v 2.16 Thanks. And i'm not looking forward to starting this project. I already have a templet i found on the lily pond manual which is close enough. I can probably remove the staves i'm not going to use so as not to waist paper or what ever the prof will do with it lol! take care all and thanks for your patience. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: hiding empty staves
Am 2007-05-07 um 03:28 schrieb Bryan Stanbridge:
In LP 2.6 I could hide empty staves (also in the first system) with
\layout { \context { \RemoveEmptyStaffContext } }
Can't remember if I also needed
\set Score . skipBars = ##t
In LP 2.10 an empty stave in the first system is only hidden with
\override Score . VerticalAxisGroup #'remove-first = ##t
\layout {\context { \Score \override VerticalAxisGroup #'remove-
first = ##t }}
Should work. (I didn't test it, though)
Thank you!
My problem was: I didn't expect that I'd need \context two times:
\context {
\RemoveEmptyStaffContext
}
\context {
\Score \override VerticalAxisGroup #'remove-first = ##t
}
Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)
smime.p7s
Description: S/MIME cryptographic signature
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: hiding empty staves
Quoting fiëé visuëlle <[EMAIL PROTECTED]>:
Ahoi!
In LP 2.6 I could hide empty staves (also in the first system) with
\layout { \context { \RemoveEmptyStaffContext } }
Can't remember if I also needed
\set Score . skipBars = ##t
In LP 2.10 an empty stave in the first system is only hidden with
\override Score . VerticalAxisGroup #'remove-first = ##t
But that can't go into the \layout block.
Why not? Just use
\layout{
...
\context{
\Score
\override VerticalAxisGroup #'remove-first = ##t
}
}
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
hiding empty staves
Ahoi!
In LP 2.6 I could hide empty staves (also in the first system) with
\layout { \context { \RemoveEmptyStaffContext } }
Can't remember if I also needed
\set Score . skipBars = ##t
In LP 2.10 an empty stave in the first system is only hidden with
\override Score . VerticalAxisGroup #'remove-first = ##t
But that can't go into the \layout block.
It would be rather important to be able to set that as a general
preference (i.e. in the \paper or \layout block) for our ConTeXt
module (similar to lily-book with LaTeX).
If it's possible, please tell me how!
Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Rutger wrote: Dear all, I don't know whether this will be helpful at all, or whether it will just be some silly remark from an inexperienced user, but at least it may prevent future inexperienced users from making the same mistake: I have been struggling with the same problem as Bob, and at first I also didn't succeed in making it work even when reading this thread. It turned out that I had rests at the beginning of the staff I wanted to hide, instead of the \skip command. Apparently (correct me if I'm wrong), rests (as opposed to a \skip) are considered real 'content', which is why they are not hidden. Yes, but the stave will be considered empty if it only contains full measure rests, like R1*3. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Dear all, I don't know whether this will be helpful at all, or whether it will just be some silly remark from an inexperienced user, but at least it may prevent future inexperienced users from making the same mistake: I have been struggling with the same problem as Bob, and at first I also didn't succeed in making it work even when reading this thread. It turned out that I had rests at the beginning of the staff I wanted to hide, instead of the \skip command. Apparently (correct me if I'm wrong), rests (as opposed to a \skip) are considered real 'content', which is why they are not hidden. Best, Rutger -- View this message in context: http://www.nabble.com/Hiding-empty-staves-tf2645020.html#a8441545 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
In message <[EMAIL PROTECTED]>, Manuel <[EMAIL PROTECTED]> writes Am 24/12/2006 um 20:30 schrieb Christopher A. LaFond: "stop" may not seem obvious to all. In America, we use the word "period"; I don't know what is used in other English speaking countries. My recommendation is "Add full stops (periods) for dotted or double dotted notes:" Christopher, may be for non-native speakers the word "period" could be confusing in that context. But if "stop" is not quite clear, a solution could be: "Add full stops (called "periods" in american English) for dotted or double dotted notes" What do you think? For consistency, I'd say "Add periods (full stops) for dotted or double-dotted notes". Seeing as the base language of the manual seems to be American anyway ... Cheers, Wol -- Anthony W. Youngman - [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
In message <[EMAIL PROTECTED]>, Pierre Abbat <[EMAIL PROTECTED]> writes On Sunday 24 December 2006 14:34, Manuel wrote: I'm sure you are right. My English needs you. "fourth", not "quarter", it should be. The duration of a note, however, is a quarter. Not in English it isn't! :-) In American, yes ... Cheers, Wol -- Anthony W. Youngman - [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Manuel wrote: "Add full stops (called "periods" in american English) for dotted or double dotted notes" What do you think? Manuel That is fine, but you need to capitalize "American" as well as "English". -- ° Chris° ° ><°> Christopher A. LaFond [EMAIL PROTECTED] http://www.lafond.us If you're happy and you know it, clunk your chains. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Hello Johan, I'll think another expression instead of "this or that". I mean to say "these, and many other imaginable things" - and since LilyPond doesn't go out to walk the dog... Manuel Am 25/12/2006 um 12:46 schrieb Johan Vromans: Manuel <[EMAIL PROTECTED]> writes: Hi Manuel, I don't understand the "this or that" correction, I meant it in the sense of "something or other". Would you explain, please? I think it's bad english, but I'm not a native english speaker as well. So I would go for just "this" which I'm sure is okay. Is the expression "is very probably" in bad english or are you encouraging more optimism? More optimism. All the things you mention can definitily be done with Lilypond, so why not just say "YES"? Thanks for the good work! -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Manuel <[EMAIL PROTECTED]> writes: Hi Manuel, > I don't understand the "this or that" correction, I meant it in the > sense of "something or other". Would you explain, please? I think it's bad english, but I'm not a native english speaker as well. So I would go for just "this" which I'm sure is okay. > Is the expression "is very probably" in > bad english or are you encouraging more optimism? More optimism. All the things you mention can definitily be done with Lilypond, so why not just say "YES"? Thanks for the good work! -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Am 24/12/2006 um 23:10 schrieb Pierre Abbat:
Whether the wether is out
with the shepherd at night depends on the weather. ;)
Great! But why are we still hiding empty staves?
I'm sure you are right. My English needs you. "fourth", not
"quarter", it should be.
The duration of a note, however, is a quarter.
phma
That's right, I have corrected it. Who is phma?
Any help for the Linux users coming?
Chapter One.
If you are using a Mac, open a new LilyPond window.
If you are working with Linux...
Then write this inside:
{ c' d' e' f' g' a' b' c' ' }
Save the file and then select "Typeset file" from the "Compile" menu.
Manuel
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On Sunday 24 December 2006 14:34, Manuel wrote: > I'm sure you are right. My English needs you. "fourth", not > "quarter", it should be. The duration of a note, however, is a quarter. phma ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On Sunday 24 December 2006 15:10, Manuel wrote: > Johan, > > Thank you! I have now corrected wether to whether (how did this > escape the TexEdit spell check?). "wether" is a valid word, meaning "sheep" (most often in "bellwether", the sheep who wears a bell to lead the other sheep). Whether the wether is out with the shepherd at night depends on the weather. ;) Pierre ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Here is the whole thing again, including Jay's suggestions and other
corrections
Manuel
LilyPond's
Beginners Guide
for the
Very Beginner
Chapter One.
If you are using a Mac, open a new LilyPond window.
If you are working with Linux...
Then write this inside:
{ c' d' e' f' g' a' b' c' ' }
Save the file and then select "Typeset file" from the "Compile" menu.
A small window will open, where you can follow the proceedings, and
then a ".pdf" document will appear, with this result:
(insert graphic here)
It is a little C-major scale. Let us consider it:
The so-called "curly braces"
{
and
}
are essential. You must always write your music inside such brackets.
Also, LilyPond is "case sensitive", which means that in our little
example, "c" (that's lower case) is right, but "C" (that's upper
case) would be wrong.
Then, LilyPond has certain pre-set values, called "defaults", which
will apply whenever you do not ask for something different. In our
present example, for instance: the treble clef, 4/4 time signature,
quarter notes.
You can, of course, change these and all other defaults, indeed you
can engrave old plainchant, contemporary notation, orchestral scores,
do MIDI files, and more. But all that lies further down the road. For
the moment, we will teach you how to engrave a simple melody.
First, we'll give you a very useful tool to input your notes, called
the "relative mode".
In our example, we have written each note with an octave
denomination: one apostrophe:
'
for the so-called "first octave", which is the octave immediately
above and including the central c, and two apostrophes:
''
for the "second octave", the one immediately above the first octave.
But now, using the "relative mode", you will save yourself a lot of
work. Erase what you wrote before in the LilyPond window and write
this instead:
\relative
{ c d e f g a b c }
Save the document again, close the .pdf and select "Typeset file"
from the "Compile" menu. The result will be the same C-major scale.
(insert graphic here)
But now, with the
\relative
command, the first note is automatically engraved as close as
possible to the central c and every further note will be engraved as
close as possible to the previous note. "As close as possible" means
calculating the smallest interval. Thus if you modify your input to
this:
\relative
{ e g c b g f d c }
(Don't forget to always save the file and close the previous .pdf
before compiling)
You will get this result:
(insert graphic here)
You can analyze the exercise and see that a third has been preferred
to a sixth, a fourth to a fifth, etc. Now in this mode, when you add
an apostrophe, it makes the note appear one octave higher as it would
have appeared without the apostrophe. Two apostrophes make for two
octaves, and so forth.
To make a note one octave lower as it would otherwise appear, add a
coma:
c,
or two or more for more octaves:
c,,,
See it here:
\relative
{ c' g e' d c c, d c }
(insert graphic here)
Good. Now let's see how to select the following:
Clefs
Time signatures
Keys major and minor
Rhythmic values
Sharps and flats
Double bars and repeat bars.
These are simple things to do. Write this example:
\relative
{
\clef treble
\key c \major
\time 4/4
c d e f g a b c }
(insert graphic here)
The result is our first example of a C-major scale, but this time you
see the way some defaults are set. Change them easily, like this:
\relative
{
\clef alto
\key cis \minor
\time 2/2
c d e f g a b c }
This should look thus:
(insert graphic here)
Don't worry just yet about the naturals. We'll come to it in a moment.
You change the clef changing the denomination "treble" for
alto
tenor
bass
or other, no less important clefs, like:
french (G clef on the first line)
soprano (C clef on the first line)
mezzosoprano (C clef on the second line)
baritone (C clef on the fifth line)
varbaritone (F clef on the third line)
subbass (F clef on the fifth line)
percussion (percussion clef)
tab (tablature clef)
To set the key, proceed in this way:
\key (name of the tonic) \(major or minor)
like for instance:
\key g \minor
And similarly for the time signature, like this:
\time x/y
For instance:
\time 6/8
Now for the rhythmic values.
You specify these values with a number after the name of the note:
"c1" will make a whole note; "d8" an eighth note, etc.
Add full stops (called "periods" in american English) for dotted or
double doted notes:
g4.
for a dotted quarter note,
a8..
for a double dotted eighth note, and so on.
Insert rests with the letter "r" and specify their duration with
numbers:
r4.
will be a dotted fourth rest.
Once a rhythmic value is entered it remains the same for all the
following notes or rests until you change it. This applies for rests
as well. Lets see this with an example:
\relative
Re: Hiding empty staves
Johan, Thank you! I have now corrected wether to whether (how did this escape the TexEdit spell check?). I don't understand the "this or that" correction, I meant it in the sense of "something or other". Would you explain, please? Is the expression "is very probably" in bad english or are you encouraging more optimism? Manuel Am 24/12/2006 um 21:02 schrieb Johan Vromans: Manuel <[EMAIL PROTECTED]> writes: The exercises you have done so far should enable you to write any simple melody. As you are surely aware, we have not said anything yet about tuplets, lyrics, polyphony and many other things. If you wonder wether you can do this or that with LilyPond, the answer is very probably "YES!" wether -> whether this or that -> this is very probably -> is Good work! -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Manuel <[EMAIL PROTECTED]> writes: > The exercises you have done so far should enable you to write any > simple melody. As you are surely aware, we have not said anything yet > about tuplets, lyrics, polyphony and many other things. If you wonder > wether you can do this or that with LilyPond, the answer is very > probably "YES!" wether -> whether this or that -> this is very probably -> is Good work! -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Am 24/12/2006 um 20:30 schrieb Christopher A. LaFond: "stop" may not seem obvious to all. In America, we use the word "period"; I don't know what is used in other English speaking countries. My recommendation is "Add full stops (periods) for dotted or double dotted notes:" Christopher, may be for non-native speakers the word "period" could be confusing in that context. But if "stop" is not quite clear, a solution could be: "Add full stops (called "periods" in american English) for dotted or double dotted notes" What do you think? Manuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Hello Joe, Am 24/12/2006 um 20:00 schrieb Joe Neeman: At least in my experience, the interval from, for example, G to the C above is always referred to as a "fourth," not a "quarter." I'm sure you are right. My English needs you. "fourth", not "quarter", it should be. Manuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Manuel wrote: Add full stops for dotted or double doted notes: g4. "stop" may not seem obvious to all. In America, we use the word "period"; I don't know what is used in other English speaking countries. My recommendation is "Add full stops (periods) for dotted or double dotted notes:" -- ° Chris° ° ><°> Christopher A. LaFond [EMAIL PROTECTED] http://www.celticharper.net "To communicate with Mars, converse with spirits, To report the behaviour of the sea monster, Describe the horoscope, haruspicate or scry, Observe disease in signatures." (T.S.Eliot) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On 12/24/06, Manuel <[EMAIL PROTECTED]> wrote: Here it is again. I ran it through a spell check in TexEdit and found even more mistakes, now corrected. All of them? You can analyze the exercise and see that a third has been preferred to a sixth, a quarter to a fifth, etc. Now in this mode, when you add At least in my experience, the interval from, for example, G to the C above is always referred to as a "fourth," not a "quarter." an apostrophe, it makes the note appear one octave higher as it would have appeared without the apostrophe. Two apostrophes make for two octaves, and so forth. Other than that, I think that this is a very good introduction. My only complaint is that I'm not sure it's useful to have all three of - a "very beginner" tutorial - a "normal" tutorial - a user manual Could this "very beginner" tutorial just replace the beginning of the current tutorial? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On Sunday 24 December 2006 12:39, Manuel wrote: > I work with Mac OS X. I don't know what Kwrite is (what is your OS?) > I have assumed - perhaps erroneously - than for all OS's it was > possible to just "open a new LilyPond window". I select "new" from > the "File" menu or press "command-n" and that's it... I run Linux with KDE. Kwrite is a plain-text editor in KDE. Any plain text editor will work, as long as it can save the file as UTF-8 if you have anything outside ASCII. I use Ubuntu, which is set up with UTF-8 as default encoding. In Linux LilyPond is a command-line program which takes the .ly file as an argument and outputs the .ps and .pdf files. > Are you in Niue? No, it's just the DNS provider that's registered there. Pierre ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Here it is again. I ran it through a spell check in TexEdit and found
even more mistakes, now corrected. All of them?
Manuel
LilyPond's
Beginners Guide
for the
Very Beginner
Chapter One.
Open a new LilyPond window and write this inside:
{ c' d' e' f' g' a' b' c' ' }
Save the file and then select "Typeset file" from the "Compile" menu.
A small window will open, where you can follow the proceedings, and
then a ".pdf" document will appear, with this result:
(insert graphic here)
It is a little C-major scale. Let us consider it:
The so-called "curly braces"
{
and
}
are essential. You must always write your music inside such brackets.
Also, LilyPond is "case sensitive", which means that in our little
example, "c" (that's lower case) is right, but "C" (that's upper
case) would be wrong.
Then, LilyPond has certain pre-set values, called "defaults", which
will apply whenever you do not ask for something different. In our
present example, for instance: the treble clef, 4/4 time signature,
fourth notes.
You can, of course, change these and all other defaults, indeed you
can engrave old plainchant, contemporary notation, orchestral scores,
do MIDI files, and more. But all that lies further down the road. For
the moment, we will teach you how to engrave a simple melody.
First, we'll give you a very useful tool to input your notes, called
the "relative mode".
In our example, we have written each note with an octave
denomination: one apostrophe:
'
for the so-called "first octave", which is the octave immediately
above and including the central c, and two apostrophes:
''
for the "second octave", the one immediately above the first octave.
But now, using the "relative mode", you will save yourself a lot of
work. Erase what you wrote before in the LilyPond window and write
this instead:
\relative
{ c d e f g a b c }
Save the document again, close the .pdf and select "Typeset file"
from the "Compile" menu. The result will be the same C-major scale.
(insert graphic here)
But now, with the
\relative
command, the first note is automatically engraved as close as
possible to the central c and every further note will be engraved as
close as possible to the previous note. "As close as possible" means
calculating the smallest interval. Thus if you modify your input to
this:
\relative
{ e g c b g f d c }
(Don't forget to always save the file and close the previous .pdf
before compiling)
You will get this result:
(insert graphic here)
You can analyze the exercise and see that a third has been preferred
to a sixth, a quarter to a fifth, etc. Now in this mode, when you add
an apostrophe, it makes the note appear one octave higher as it would
have appeared without the apostrophe. Two apostrophes make for two
octaves, and so forth.
To make a note one octave lower as it would otherwise appear, add a
coma:
c,
or two or more for more octaves:
c,,,
See it here:
\relative
{ c' g e' d c c, d c }
(insert graphic here)
Good. Now let's see how to select the following:
Clefs
Time signatures
Keys major and minor
Rhythmic values
Sharps and flats
Double bars and repeat bars.
These are simple things to do. Write this example:
\relative
{
\clef treble
\key c \major
\time 4/4
c d e f g a b c }
(insert graphic here)
The result is again our first example of a C-major scale, but this
time you see the way some defaults are set. Change them easily, like
this:
\relative
{
\clef alto
\key cis \minor
\time 2/2
c d e f g a b c }
This should look thus:
(insert graphic here)
Don't worry just yet about the naturals. We'll come to it in a moment.
You change the clef changing the denomination "treble" for
alto
tenor
bass
or other, no less important clefs, like:
french (G clef on the first line)
soprano (C clef on the first line)
mezzosoprano (C clef on the second line)
baritone (C clef on the fifth line)
varbaritone (F clef on the third line)
subbass (F clef on the fifth line)
percussion (percussion clef)
tab (tablature clef)
To set the key, proceed in this way:
\key (name of the tonic) \(major or minor)
like for instance:
\key g \minor
And similarly for the time signature, like this:
\time x/y
For instance:
\time 6/8
Now for the rhythmic values.
You specify these values with a number after the name of the note:
"c1" will make a whole note; "d8" an eighth note, etc.
Add full stops for dotted or double doted notes:
g4.
for a dotted fourth note,
a8..
for a double dotted eighth note, and so on.
Insert rests with the letter "r" and specify their duration with
numbers:
r4.
will be a dotted fourth rest.
But know that once you specify a rhythmic value, it will be repeated
for the following notes until you specify a new value. This applies
for rests as well. Lets see this with an example:
\relative
{c4 r8 e g4 c r8 g c r c,4 r}
(insert grap
Re: Hiding empty staves
Pierre, I'm glad you liked it. English is not my mother language, as you can see. So, thank you very much for all spelling corrections! As far as I can see, they are all quite right. Am 24/12/2006 um 18:01 schrieb Pierre Abbat: What OS are you on? I open a Kwrite window and type "lilypond music.ly" in a Konsole. I work with Mac OS X. I don't know what Kwrite is (what is your OS?) I have assumed - perhaps erroneously - than for all OS's it was possible to just "open a new LilyPond window". I select "new" from the "File" menu or press "command-n" and that's it... You can, of course, change these and all other defaults, indeed you can engrave old plainchat, contemporary notation, orchestral scores, do MIDI files, and more. But all that lies further down the road. For the moment, we will teach you how to engrave a simple melody. sp: "plainchant". Or do you mean "plainsong"? Ha ha! Plainchat would be a nice kind of chat, maybe. I meant the medieval monody like Gregorian. How do you name it correctly? for the so-called "first octave", which is the octave inmediately above and including the central c, and two apostrophes: sp: "immediately". "inm-" is Spanish. In English it's called "middle C". I never get that nm-mm thing right. So, "middle C" it is. To make a note one octave lower as it would otherwise appear, add a coma: sp: "comma". A coma is a form of unconsciousness. Let's not get that far and put that extra "m". or other, no less impotant clefs, like: sp: "important" Yes, don't get impotent, get importent. \key (name of the tonica) \(major or minor) sp: "tonic" I would have thought of "Indian Tonic Cunnington" (know it?) But go ahead without an "a". Now for the rythmic values. sp: "rhythmic" Rhight you are again. Give me a moment and I will correct it and then post it again. Are you in Niue? Manuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On Sunday 24 December 2006 08:01, Manuel wrote:
> Chapter One.
>
>
> Open a new LilyPond window and write this inside:
>
>
> { c' d' e' f' g' a' b' c' ' }
>
>
> Save the file and then select "Typeset file" from the "Compile" menu.
What OS are you on? I open a Kwrite window and type "lilypond music.ly" in a
Konsole.
> You can, of course, change these and all other defaults, indeed you
> can engrave old plainchat, contemporary notation, orchestral scores,
> do MIDI files, and more. But all that lies further down the road. For
> the moment, we will teach you how to engrave a simple melody.
sp: "plainchant". Or do you mean "plainsong"?
> First, we'll give you a very useful tool to input your notes, called
> the "relative mode".
>
> In our example, we have written each note with an octave
> denomination: one apostrophe:
>
> '
>
> for the so-called "first octave", which is the octave inmediately
> above and including the central c, and two apostrophes:
sp: "immediately". "inm-" is Spanish.
In English it's called "middle C".
> To make a note one octave lower as it would otherwise appear, add a
> coma:
sp: "comma". A coma is a form of unconsciousness.
> or other, no less impotant clefs, like:
sp: "important"
> \key (name of the tonica) \(major or minor)
sp: "tonic"
> Now for the rythmic values.
sp: "rhythmic"
I think it's a great introduction!
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
> Fine! I have now written the following, and am posting it here for > general criticism. I like it! Thanks for your work. This is indeed a kind of a first-time starter which I would not be able to write. Graham, do you have some time to include something like this into the manual. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Hello Werner,
Am 23/12/2006 um 07:46 schrieb Werner LEMBERG:
I am a professional musician and an experienced music teacher. I
would even be willing to write a first chapter of a User's Guide for
the Very Beginner.
Please go on! Either send patches or, in case you aren't satisfied
with chapter 2, rewrite it.
Fine! I have now written the following, and am posting it here for
general criticism.
Manuel
LilyPond's
Beginners Guide
for the
Very Beginner
Chapter One.
Open a new LilyPond window and write this inside:
{ c' d' e' f' g' a' b' c' ' }
Save the file and then select "Typeset file" from the "Compile" menu.
A small window will open, where you can follow the proceedings, and
then a ".pdf" document will appear, with this result:
(insert graphic here)
It is a little C-major scale. Let us consider it:
The so-called "curly braces"
{
and
}
are essential. You must always write your music inside such brackets.
Also, LilyPond is "case sensitive", which means that in our litte
example, "c" (that's lower case) is right, but "C" (that's upper
case) would be wrong.
Then, LilyPond has certain pre-set values, called "defaults", which
will apply whenever you do not ask for something different. In our
present example, for instance: the treble clef, 4/4 time signature,
fourth notes.
You can, of course, change these and all other defaults, indeed you
can engrave old plainchat, contemporary notation, orchestral scores,
do MIDI files, and more. But all that lies further down the road. For
the moment, we will teach you how to engrave a simple melody.
First, we'll give you a very useful tool to input your notes, called
the "relative mode".
In our example, we have written each note with an octave
denomination: one apostrophe:
'
for the so-called "first octave", which is the octave inmediately
above and including the central c, and two apostrophes:
''
for the "second octave", the one inmediately above the first octave.
But now, using the "relative mode", you will save yourself a lot of
work. Erase what you wrote before in the LilyPond window and write
this instead:
\relative
{ c d e f g a b c }
Save the document again, close the .pdf and select "Typeset file"
from the "Compile" menu. The result will be the same C-major scale.
(insert graphic here)
But now, with the
\relative
command, the first note is automatically engraved as close as
possible to the central c and every further note will be engraved as
close as possible to the previous note. "As close as possible" means
calculating the smallest interval. Thus if you modify your input to
this:
\relative
{ e g c b g f d c }
(Don't forget to always save the file and close the previous .pdf
before compiling)
You will get this result:
(insert graphic here)
You can analize the excercise and see that a third has been preferred
to a sixth, a quarter to a fifth, etc. Now in this mode, when you add
an apostrophe, it makes the note appear one octave higher as it would
have appeared without the apostrophe. Two apostrophes make for two
octaves, and so forth.
To make a note one octave lower as it would otherwise appear, add a
coma:
c,
or two or more for more octaves:
c,,,
See it here:
\relative
{ c' g e' d c c, d c }
(insert graphic here)
Good. Now let's see how to select the following:
Clefs
Time signatures
Keys major and minor
Rhythmic values
Sharps and flats
Double bars and repeat bars.
These are simple things to do. Write this example:
\relative
{
\clef treble
\key c \major
\time 4/4
c d e f g a b c }
(insert graphic here)
The result is again our first example of a C-major scale, but this
time you see the way some defaults are set. Change them easily, like
this:
\relative
{
\clef alto
\key cis \minor
\time 2/2
c d e f g a b c }
This should look thus:
(insert graphic here)
Don't worry just yet about the naturals. We'll come to it in a moment.
You change the clef changing the denomination "treble" for
alto
tenor
bass
or other, no less impotant clefs, like:
french (G clef on the first line)
soprano (C clef on the first line)
mezzosoprano (C clef on the second line)
baritone (C clef on the fifth line)
varbaritone (F clef on the third line)
subbass (F clef on the fifth line)
percussion (percussion clef)
tab (tablature clef)
To set the key, proceed in this way:
\key (name of the tonica) \(major or minor)
like for instance:
\key g \minor
And similarly for the time signature, like this:
\time x/y
For instance:
\time 6/8
Now for the rythmic values.
You specify these values with a number after the name of the note:
"c1" will make a whole note; "d8" an eighth note, etc.
Add full stops for dotted or double doted notes:
g4.
for a dotted fourth note,
a8..
for a double dotted eighth note, and so on.
Insert rests with the letter "r" and specify their duration with
numbers
Re: Hiding empty staves
Werner LEMBERG wrote: With other words, you poor guy have stumbled on a bug in lilypond, and the people who've tried to help you weren't aware of this. Thanks very much, Werner. This version works exactly the way I want it to. Here's hoping it doesn't take quite so long the next time someone posts to the list explaining that yes, (s)he's already read the documentation, and it still doesn't work, (and here's a packaged minimal repro case documenting what's been tried) to get past the RTFM responses. Thanks again and Merry Christmas! -- Bob Kline http://www.rksystems.com mailto:[EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
> Dear Bob, you did give me some hope. I thought that not knowing a
> thing about programming was my problem, maybe being too stupid or
> lazy to understand what should be clear to me. But I see that you
> are indeed a software developer and still can have trouble with a
> programm.
Friends, Mats and Graham both do a great job by answering almost all
help emails. I don't even start to think about the time involved to
do that!
However, we are normally too far involved into LilyPond to recognize
some of the very basic problems.
> I am a professional musician and an experienced music teacher. I
> would even be willing to write a first chapter of a User's Guide for
> the Very Beginner.
Please go on! Either send patches or, in case you aren't satisfied
with chapter 2, rewrite it.
> > Thanks anyway to anyone who was sincerely trying to assist me.
> > Sorry I didn't get it.
Bob, I suggest that you retry it -- with a more recent lilypond
version! Attached is the result of this snippet (which you've already
sent to the list) processed with lilypond 2.11.4. It seems that it
does exactly what you want.
With other words, you poor guy have stumbled on a bug in lilypond, and
the people who've tried to help you weren't aware of this.
Werner
==
\version "2.11.2"
melody = \relative c'' { c1 \break c \break c \break c }
altoMusic = \relative c' { \skip 1*2 e1 e }
tenorMusic = \relative c' { \skip 1*2 g1 g }
bassMusic = \relative c { \skip 1*2 c1 c }
verseone = \lyricmode{ la1 la la la }
\score {
<<
\override Score.VerticalAxisGroup #'remove-first = ##t
\context ChoirStaff <<
\context Staff = women <<
\context Voice = sopranos { \voiceOne << \melody >> }
\context Voice = altos{ \voiceTwo << \altoMusic >> }
>>
\new Lyrics { \set stanza = "1. " \verseone }
\context Staff = men <<
\clef bass
\context Voice = tenors { \voiceThree << \tenorMusic >> }
\context Voice = basses { \voiceFour << \bassMusic >> }
>>
>>
>>
\layout {
\context { \RemoveEmptyStaffContext }
}
}
bob.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Well, well... Dear Bob, you did give me some hope. I thought that not knowing a thing about programming was my problem, maybe being too stupid or lazy to understand what should be clear to me. But I see that you are indeed a software developer and still can have trouble with a programm. Indeed, the didactical quality of LilyPond's tutorials is nowhere near to the program's quality, indeed maybe the best music notation software there is at the moment. I am a professional musician and an experienced music teacher. I would even be willing to write a first chapter of a User's Guide for the Very Beginner. But although I am sincerely sorry that you are giving up because of lack of adequate support, I think maybe there is still hope for the digitally challenged... Manuel Am 22/12/2006 um 22:44 schrieb Bob Kline: Bob Kline wrote: Graham Percival wrote: Have you read chapter 9 as well? If not, could you read that and let me know if it helps? Once you do understand it, could you also propose an addition to the docs to clear this up? I will keep trying and report back results. OK, I give up. I've posted the exact code earlier in this thread showing my attempt to do *exactly* what it was suggested I do. I've read (more than once) all of the sections of the manual to which I've been directed. I've tried everything I can think of to get the empty staff to disappear in the first system, but nothing works. I know from first-hand experience with the software packages to which I've contributed code myself how frustrating it can be to field the same questions repeatedly from users who can't be bother to make any effort to use the tools (including the documentation) which has been provided for them. But I also know that when a user actually tries to solve his/her problems with the software I am more than willing to do whatever it takes to explain how to get it to do what is needed. It's possible that the developers are looking at my attempts with pity and wonder that I'm so feeble-minded that I can't understand what their documentation is explaining so clearly. It's also possible that no one knows how to achieve the result I'm after and for some reason it's more comfortable to say "go read another chapter until you understand it, grasshopper" than to simply say "I don't know." Thanks anyway to anyone who was sincerely trying to assist me. Sorry I didn't get it. -- Bob Kline http://www.rksystems.com mailto:[EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Did you see my answer from November 20? /Mats Bob Kline wrote: Bob Kline wrote: Graham Percival wrote: Have you read chapter 9 as well? If not, could you read that and let me know if it helps? Once you do understand it, could you also propose an addition to the docs to clear this up? I will keep trying and report back results. OK, I give up. I've posted the exact code earlier in this thread showing my attempt to do *exactly* what it was suggested I do. I've read (more than once) all of the sections of the manual to which I've been directed. I've tried everything I can think of to get the empty staff to disappear in the first system, but nothing works. I know from first-hand experience with the software packages to which I've contributed code myself how frustrating it can be to field the same questions repeatedly from users who can't be bother to make any effort to use the tools (including the documentation) which has been provided for them. But I also know that when a user actually tries to solve his/her problems with the software I am more than willing to do whatever it takes to explain how to get it to do what is needed. It's possible that the developers are looking at my attempts with pity and wonder that I'm so feeble-minded that I can't understand what their documentation is explaining so clearly. It's also possible that no one knows how to achieve the result I'm after and for some reason it's more comfortable to say "go read another chapter until you understand it, grasshopper" than to simply say "I don't know." Thanks anyway to anyone who was sincerely trying to assist me. Sorry I didn't get it. -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Bob Kline wrote: > Graham Percival wrote: > >> Have you read chapter 9 as well? If not, could you read that and let me >> know if it helps? Once you do understand it, could you also propose an >> addition to the docs to clear this up? > > I will keep trying and report back results. OK, I give up. I've posted the exact code earlier in this thread showing my attempt to do *exactly* what it was suggested I do. I've read (more than once) all of the sections of the manual to which I've been directed. I've tried everything I can think of to get the empty staff to disappear in the first system, but nothing works. I know from first-hand experience with the software packages to which I've contributed code myself how frustrating it can be to field the same questions repeatedly from users who can't be bother to make any effort to use the tools (including the documentation) which has been provided for them. But I also know that when a user actually tries to solve his/her problems with the software I am more than willing to do whatever it takes to explain how to get it to do what is needed. It's possible that the developers are looking at my attempts with pity and wonder that I'm so feeble-minded that I can't understand what their documentation is explaining so clearly. It's also possible that no one knows how to achieve the result I'm after and for some reason it's more comfortable to say "go read another chapter until you understand it, grasshopper" than to simply say "I don't know." Thanks anyway to anyone who was sincerely trying to assist me. Sorry I didn't get it. -- Bob Kline http://www.rksystems.com mailto:[EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Graham Percival wrote: > Have you read chapter 9 as well? If not, could you read that and let me > know if it helps? Once you do understand it, could you also propose an > addition to the docs to clear this up? I will keep trying and report back results. -- Bob Kline http://www.rksystems.com mailto:[EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Bob Kline wrote: Could one of you have pity on a poor clueless user and give an example showing where these two directives go? There is only one command, which can be entered in two different ways. I have looked at chapter 5 of the docs (I assume we're talking about the chapter 5 in the latest released version of lp, rather than the versions currently shipped with most Linux distros), and my poor brain just isn't getting it, as I don't see the part that says *where* to put the \override command. Have you read chapter 9 as well? If not, could you read that and let me know if it helps? Once you do understand it, could you also propose an addition to the docs to clear this up? Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Isn't the simple answer to your problems that you read the wrong
version of the manual? As far as I can see, you use version 2.6
and if I read the manual correctly for that version, you should use
\override Score.RemoveEmptyVerticalGroup #'remove-first = ##t
If you want to keep this setting in the \layout section, do
\layout {
\context {
\RemoveEmptyStaffContext \override
RemoveEmptyVerticalGroup #'remove-first = ##t
}
}
Your example works without any problems in version 2.10.
/Mats
Quoting Bob Kline <[EMAIL PROTECTED]>:
Erik Sandberg wrote:
The problem above, is that { } have different meanings in different places:
Usually { } means sequential music, but the { } after \score are
special: it
starts with a _single_ music expression, followed by optional \layout (etc)
blocks. So you must make \override part of the music expression, like:
\score {
<<
\override Score.VerticalAxisGroup #'remove-first = ##t
\context ChoirStaff <<
\context Staff = women << >>
\new Lyrics
\context Staff = men << >>
>>
\layout{...}
}
I apologize for being so slow to grok what's going on here, and I
appreciate the responses posted so far on this issue, but I still don't
get it. I have tried doing *exactly* what you're telling me to do here
(except for putting back in the missing ">>" to balance the delimiters
of the \context ChoirStaff chunk), and I'm still getting the blank staff
in the first system. I've read the FAQ (multiple times). I've tried
reading the manual top to bottom to try and get a comprehensive picture
of the lexical grammar at work here, but my brain is glazing over. If
there's a place I should have been reading but missed (or nodded off
when I was trying to read it), I promise I won't be offended if someone
posts something which tells me how lame my efforts were at not finding
the obvious guide which explains how this works, as long as the poster
tells me where that guide is.
I have boiled down the problem to a minimal repro case, and I'm
attaching three tiny files which illustrate my attempt to do what Erik's
telling me to do here: the .ly source, the resulting .pdf, and a cropped
image of the relevant portion of the output.
Thanks for any guidance you have to offer!
--
Bob Kline
http://www.rksystems.com
mailto:[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Erik Sandberg wrote: > Hm, maybe it's the \clef bass; you could try to move it to where the music > starts. (not tested; it's just a guess) Thanks for the guess, but that didn't work: it just prints the empty staff with a G clef. -- Bob Kline http://www.rksystems.com mailto:[EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On Monday 20 November 2006 18:40, Bob Kline wrote:
> Erik Sandberg wrote:
> > The problem above, is that { } have different meanings in different
> > places: Usually { } means sequential music, but the { } after \score are
> > special: it starts with a _single_ music expression, followed by optional
> > \layout (etc) blocks. So you must make \override part of the music
> > expression, like:
> >
> > \score {
> > <<
> > \override Score.VerticalAxisGroup #'remove-first = ##t
> > \context ChoirStaff <<
> > \context Staff = women << >>
> > \new Lyrics
> > \context Staff = men << >>
> >
> > \layout{...}
> > }
>
> I apologize for being so slow to grok what's going on here, and I
> appreciate the responses posted so far on this issue, but I still don't
> get it. I have tried doing *exactly* what you're telling me to do here
> (except for putting back in the missing ">>" to balance the delimiters
> of the \context ChoirStaff chunk), and I'm still getting the blank staff
> in the first system.
Hm, maybe it's the \clef bass; you could try to move it to where the music
starts. (not tested; it's just a guess)
--
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
On Friday 17 November 2006 22:28, Bob Kline wrote:
> Andrew Longland-Meech wrote:
> > Thank you. I've got it now, even though it seems a bit illogical to put
> > one bit of layout in \layout and the other in with the notes, when they
> > both do a similar job!!
> >
> > On Thu, 2006-11-16 at 10:53 -0800, Graham Percival wrote:
> >> Andrew Longland-Meech wrote:
> >>> \override Score.VerticalAxisGroup #'remove-first = ##t "
> >>>
> >>> I don't understand where this should go. Is it in the \score section?
> >>> Or in the \layout section? Or in with the notes? Please can someone
> >>> guide me in the right direction?
> >>
> >> Please see chapter 5 of the docs.
>
> Could one of you have pity on a poor clueless user and give an example
> showing where these two directives go? My attempts always end up with
> the unwanted staff omitted on the second system of the music, but
> included for the first system. Here's an example of what I'm trying:
>
> \score {
> \override Score.VerticalAxisGroup #'remove-first = ##t
> \context ChoirStaff <<
> \context Staff = women << >>
> \new Lyrics
> \context Staff = men << >>
>
> \layout {
> \context { \RemoveEmptyStaffContext }
> }
> }
>
> I have looked at chapter 5 of the docs (I assume we're talking about the
> chapter 5 in the latest released version of lp, rather than the versions
> currently shipped with most Linux distros), and my poor brain just isn't
> getting it, as I don't see the part that says *where* to put the
> \override command.
The problem above, is that { } have different meanings in different places:
Usually { } means sequential music, but the { } after \score are special: it
starts with a _single_ music expression, followed by optional \layout (etc)
blocks. So you must make \override part of the music expression, like:
\score {
<<
\override Score.VerticalAxisGroup #'remove-first = ##t
\context ChoirStaff <<
\context Staff = women << >>
\new Lyrics
\context Staff = men << >>
>>
\layout{...}
}
--
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Andrew Longland-Meech wrote:
> Thank you. I've got it now, even though it seems a bit illogical to put
> one bit of layout in \layout and the other in with the notes, when they
> both do a similar job!!
>
> On Thu, 2006-11-16 at 10:53 -0800, Graham Percival wrote:
>> Andrew Longland-Meech wrote:
>>> \override Score.VerticalAxisGroup #'remove-first = ##t "
>>>
>>> I don't understand where this should go. Is it in the \score section? Or
>>> in the \layout section? Or in with the notes? Please can someone guide
>>> me in the right direction?
>> Please see chapter 5 of the docs.
Could one of you have pity on a poor clueless user and give an example
showing where these two directives go? My attempts always end up with
the unwanted staff omitted on the second system of the music, but
included for the first system. Here's an example of what I'm trying:
\score {
\override Score.VerticalAxisGroup #'remove-first = ##t
\context ChoirStaff <<
\context Staff = women << >>
\new Lyrics
\context Staff = men << >>
>>
\layout {
\context { \RemoveEmptyStaffContext }
}
}
I have looked at chapter 5 of the docs (I assume we're talking about the
chapter 5 in the latest released version of lp, rather than the versions
currently shipped with most Linux distros), and my poor brain just isn't
getting it, as I don't see the part that says *where* to put the
\override command.
Thanks!
--
Bob Kline
http://www.rksystems.com
mailto:[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Andrew Longland-Meech wrote: Thank you. I've got it now, even though it seems a bit illogical to put one bit of layout in \layout and the other in with the notes, when they both do a similar job!! You don't have to put them in separate places. The commands can be put in either place... and if you're just talking about the Score.VerticalAxisGroup, you only need one command. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Thank you. I've got it now, even though it seems a bit illogical to put one bit of layout in \layout and the other in with the notes, when they both do a similar job!! On Thu, 2006-11-16 at 10:53 -0800, Graham Percival wrote: > Andrew Longland-Meech wrote: > > \override Score.VerticalAxisGroup #'remove-first = ##t " > > > > I don't understand where this should go. Is it in the \score section? Or > > in the \layout section? Or in with the notes? Please can someone guide > > me in the right direction? > > Please see chapter 5 of the docs. > > Cheers, > - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding empty staves
Andrew Longland-Meech wrote: \override Score.VerticalAxisGroup #'remove-first = ##t " I don't understand where this should go. Is it in the \score section? Or in the \layout section? Or in with the notes? Please can someone guide me in the right direction? Please see chapter 5 of the docs. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Hiding empty staves
Hi all! I'm using \RemoveEmptyStaffContext to 'French' a piece that I'm typesetting, but the first system still shows the empty staves. In the manual section on hiding empty staves it states "...If empty staves should be removed from the first system too, set remove-first to true in VerticalAxisGroup. \override Score.VerticalAxisGroup #'remove-first = ##t " I don't understand where this should go. Is it in the \score section? Or in the \layout section? Or in with the notes? Please can someone guide me in the right direction? Regards Andrew ps Lilypond is a great piece of software. Many thanks to all involved. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
