Re: arpeggio placement
David Stocker wrote: Any hints on forcing the arpeggio line to the right to make the placement more natural would be appreciated. For the first case, fiddle with the padding. Negative works too, e.g. \override Staff.Arpeggio #'padding = #-0.4 For situations where this doesn't work, see http://lists.gnu.org/archive/html/lilypond-user/2009-03/msg00658.html Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
Hi guys correct me if I am wrong. The g minor chord has two flats Eb Bb which need to be marked as es and bes in Lilypond other wise the Accidental_engraver sees them as naturals in the g minor chord, hence the natural symbol for any unmarked E or B note in your music. Just trying to see if I understand this all correctly? How did I do? Simon On 25/08/2009, at 01:39, Sona wrote: I'm new to Lilypond and the list. So far the code is pretty intuitive, but I am stumped by the way accidentals work. Several posts deal with this subject, but probably are beyond a novice's ability to undertand. I'm transcribing a modern piece with 2 flats in the key signature (I've set \key g \minor). It's rather atonal, though, so it seems Lilypond tries to correct pitch by turning every e-flat and b-flat into a natural. What code do I use to override this? The printed result should have only 4 accidentals. Right now there are 37, and of course the pitches are all off. What do I put where in what part of the code? I can send my page code, if it would be helpful. Thanks in advance! cleo ___ 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: Accidentals: Unwanted naturals
Correct. *ALL* pitches in the input *must* be explicitly given. The key signature assignment tells LilyPond how to display the pitches. For exmaple; 'e' *always* means e-natural no matter what the key signature is. -David Simon Mackenzie wrote: Hi guys correct me if I am wrong. The g minor chord has two flats Eb Bb which need to be marked as es and bes in Lilypond other wise the Accidental_engraver sees them as naturals in the g minor chord, hence the natural symbol for any unmarked E or B note in your music. Just trying to see if I understand this all correctly? How did I do? Simon On 25/08/2009, at 01:39, Sona wrote: I'm new to Lilypond and the list. So far the code is pretty intuitive, but I am stumped by the way accidentals work. Several posts deal with this subject, but probably are beyond a novice's ability to undertand. I'm transcribing a modern piece with 2 flats in the key signature (I've set \key g \minor). It's rather atonal, though, so it seems Lilypond tries to correct pitch by turning every e-flat and b-flat into a natural. What code do I use to override this? The printed result should have only 4 accidentals. Right now there are 37, and of course the pitches are all off. What do I put where in what part of the code? I can send my page code, if it would be helpful. Thanks in advance! cleo ___ 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 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
In response to Graham and others who have expressed frustration about people who have failed to pickup on accidentals. It can be very difficult for fist time novices like myself to understand implicit information about what is a reasonably technical musical concept. I spent four hours last night pouring through web site tutorials and only now do I understand why the tutorial puts so much emphasis on accidentals. Prior to this accidentals and the emphasis in the tutorial on accidentals made no sense to me at all. When I have more time I'll develop this more fully for the sake of others because I know it will help to fill out my understanding further. Simon On 25/08/2009, at 02:02, Graham Percival wrote: On Mon, Aug 24, 2009 at 11:39:37AM -0700, Sona wrote: I'm new to Lilypond and the list. So far the code is pretty intuitive, but I am stumped by the way accidentals work. Several posts deal with this subject, but probably are beyond a novice's ability to undertand. No. Those posts tried a horrible solution which didn't fix anything. This *is* well within a novice's ability understand. Please read chapter 2 of the Learning Manual. Tutorial-Simple notation-Key signatures and Accidentals. (or something like that) I'm transcribing a modern piece with 2 flats in the key signature (I've set \key g \minor). It's rather atonal, though, so it seems Lilypond tries to correct pitch by turning every e-flat and b-flat into a natural. It sounds like your input contained e-natural and b-natural. You probably wanted to write ees and bes in your input file. Seriously, have you read the tutorial? If so, why did you skip over the big warning about accidentals? This is the second person recently to not notice that warning; should we make it bigger, or add a red background, or something? - Graham ___ 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: boxed measures
Dear Mats,
this sounds quite good, but I have no idea how to use the
ly:make-stencil-function for drawing boxes!
2009/8/24 Mats Bengtsson mats.bengts...@ee.kth.se
There are already functions available in LilyPond Scheme, to draw boxes,
that should be useful here, such as box-stencil. To use it, you first have
to create an (empty) stencil of the appropriate dimensions, for example
using ly:make-stencil.
/Mats
Nick Payne wrote:
The box could be drawn with Postscript. Here’s an example of drawing large
square brackets with Postscript. Easily modifiable to draw a box:
\version 2.12.1
#(define lbracket 0.25 setlinewidth
0 setlinejoin
0 setlinecap
0.5 -2 moveto
-2 0 rlineto
0 8.8 rlineto
2 0 rlineto
stroke)
#(define rbracket 0.25 setlinewidth
0 setlinejoin
0 setlinecap
0.5 -2 moveto
2 0 rlineto
0 8.8 rlineto
-2 0 rlineto
stroke)
\relative c' {
c4-\markup { \postscript #lbracket } c c c-\markup { \postscript #rbracket
}
}
Nick Payne
*From:* lilypond-user-bounces+nick.payne=internode.on@gnu.org[mailto:
lilypond-user-bounces+nick.payne lilypond-user-bounces%2Bnick.payne=
internode.on@gnu.org] *On Behalf Of *Stefan Thomas
*Sent:* Sunday, 23 August 2009 5:43 PM
*To:* lilypond-user
*Subject:* boxed measures
Dear community,
I would like to do something like You can see in the attached image.
I don't mean the feathered beams (I know how this can be done) but the
boxed bars, followed by the dotted lines.
I have no idea how to do this in Lilypond.
A hint would be great!
Thanks
Stefan
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.64/2318 - Release Date: 08/22/09
18:04:00
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: mats.bengts...@ee.kth.se
WWW: http://www.s3.kth.se/~mabe http://www.s3.kth.se/%7Emabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 25. August 2009 10:09:53 schrieb Simon Mackenzie: The g minor chord has two flats Eb Bb Exactly. This means that a note that is displayed on the middle staff line without any accidental is actually a B-flat, not a B. In Lilypond you have to enter the real pitches, so you have to enter a b-flat. If you enter only b, then lilypond assumes you really want a b, which means that lilypond needs to print a natural, because the key signature says that without it a note on the middle staff line means a b-flat. If you know the piano, you can think of each key on the piano having one name (b, b-flat, etc.) and if you want one particular key on the keyboard being pressed, you need to use that name. Don't think of okay, that note should be displayed on the middle staff line. The middle staff line means b, so I have to enter b. This is wrong, since the middle staff line can mean either b, b-flat or b-sharp, depending on the key signature. Cheers, Reinhold - -- - -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFKk5/pTqjEwhXvPN0RAsPDAKC+aT0ob7bfPXHYCeZwB82oqfrmMQCgyTWU Roo3cpqCOP6Cb+glBJKS6JU= =e98W -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
As a follow-up, have the people with unwanted accidentals seen this: http://lilypond.org/doc/v2.13/Documentation/user/lilypond-learning/Accidentals-and-key-signatures#Key-signatures ...and is it not clear? The last example on that page shouldn't be any less clear than the example I gave. -David David Bobroff wrote: Correct. *ALL* pitches in the input *must* be explicitly given. The key signature assignment tells LilyPond how to display the pitches. For exmaple; 'e' *always* means e-natural no matter what the key signature is. -David Simon Mackenzie wrote: Hi guys correct me if I am wrong. The g minor chord has two flats Eb Bb which need to be marked as es and bes in Lilypond other wise the Accidental_engraver sees them as naturals in the g minor chord, hence the natural symbol for any unmarked E or B note in your music. Just trying to see if I understand this all correctly? How did I do? Simon On 25/08/2009, at 01:39, Sona wrote: I'm new to Lilypond and the list. So far the code is pretty intuitive, but I am stumped by the way accidentals work. Several posts deal with this subject, but probably are beyond a novice's ability to undertand. I'm transcribing a modern piece with 2 flats in the key signature (I've set \key g \minor). It's rather atonal, though, so it seems Lilypond tries to correct pitch by turning every e-flat and b-flat into a natural. What code do I use to override this? The printed result should have only 4 accidentals. Right now there are 37, and of course the pitches are all off. What do I put where in what part of the code? I can send my page code, if it would be helpful. Thanks in advance! cleo ___ 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 ___ 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: Accidentals: Unwanted naturals
Sorry but as a first time user to lilypond and music in general this section in the tutorial was about as clear as mud to me. Not wanting to offend anyone just stating how I felt the fist time I read this section in the learning tutorial. As I said previously when I have time I'll have a shot at articulating this more fully to aid my learning further and help others who have been tripped up Accidental(ly). Simon On 25/08/2009, at 15:34, David Bobroff wrote: As a follow-up, have the people with unwanted accidentals seen this: http://lilypond.org/doc/v2.13/Documentation/user/lilypond-learning/Accidentals-and-key-signatures#Key-signatures ...and is it not clear? The last example on that page shouldn't be any less clear than the example I gave. -David David Bobroff wrote: Correct. *ALL* pitches in the input *must* be explicitly given. The key signature assignment tells LilyPond how to display the pitches. For exmaple; 'e' *always* means e-natural no matter what the key signature is. -David Simon Mackenzie wrote: Hi guys correct me if I am wrong. The g minor chord has two flats Eb Bb which need to be marked as es and bes in Lilypond other wise the Accidental_engraver sees them as naturals in the g minor chord, hence the natural symbol for any unmarked E or B note in your music. Just trying to see if I understand this all correctly? How did I do? Simon On 25/08/2009, at 01:39, Sona wrote: I'm new to Lilypond and the list. So far the code is pretty intuitive, but I am stumped by the way accidentals work. Several posts deal with this subject, but probably are beyond a novice's ability to undertand. I'm transcribing a modern piece with 2 flats in the key signature (I've set \key g \minor). It's rather atonal, though, so it seems Lilypond tries to correct pitch by turning every e-flat and b- flat into a natural. What code do I use to override this? The printed result should have only 4 accidentals. Right now there are 37, and of course the pitches are all off. What do I put where in what part of the code? I can send my page code, if it would be helpful. Thanks in advance! cleo ___ 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 ___ 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: arpeggio placement
Works perfectly. Thanks Robin! David Robin Bannister wrote: David Stocker wrote: Any hints on forcing the arpeggio line to the right to make the placement more natural would be appreciated. For the first case, fiddle with the padding. Negative works too, e.g. \override Staff.Arpeggio #'padding = #-0.4 For situations where this doesn't work, see http://lists.gnu.org/archive/html/lilypond-user/2009-03/msg00658.html Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
On Aug 25, 2009, at 3:50 AM, Simon Mackenzie wrote: Sorry but as a first time user to lilypond and music in general this section in the tutorial was about as clear as mud to me. Not wanting to offend anyone just stating how I felt the fist time I read this section in the learning tutorial. I'm not sure why this is difficult. In the code you must write the note you want. If you want a B flat, you must write bes (if using the default language for LilyPond). If you want B you write b and if you want B# you write bis. LilyPond cannot guess whether you want B, Bb or B#. It seems to me that by the end of the text under the two examples about accidentals, this should be straightforwardly clear. Is there some way of phrasing this that would have made it clearer for you? BTW, doing it this way is what allows LilyPond to transpose music to different keys cleanly and accurately. This makes life so much easier for the user when arranging for horns and other transposing instruments, doing orchestral music, jazz, transposing for singers, etc. For the developers, I think that something is confusing here for English speakers: the use of -es and -is for flatted and sharped notes as the default. I was initially bewildered by this, not knowing that the default conventions are Dutch. This seems odd given that the default language for the Web site and documentation is pretty much English, so I think some confusion on the part of newbies when Dutch is used in the code can be forgiven. If the user is new to music in general then they have set themselves a daunting task trying to score music with LilyPond. There is no way for the documentation to make up for the user's lack of knowledge about the structure of music. My condolences there but I see no responsibility for the LilyPond documentation to tutor users in music, only in the use of the program. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
On Tue, Aug 25, 2009 at 4:34 AM, David Bobroffbobr...@centrum.is wrote: As a follow-up, have the people with unwanted accidentals seen this: http://lilypond.org/doc/v2.13/Documentation/user/lilypond-learning/Accidentals-and-key-signatures#Key-signatures ...and is it not clear? The last example on that page shouldn't be any less clear than the example I gave. I do have a suggestion: I would add two examples to the section that shows this clearly. Warning: key signatures and pitches Please take a close look at the following examples: Example a: c d e f g a b Example b: \key cis \major c d e f g a b To determine whether to print an accidental, LilyPond examines the pitches and the key signature. The key signature only affects the printed accidentals, not the note’s pitch! This is a feature that often causes confusion to newcomers, so let us explain it in more detail. [...] -- Leonardo Herrera mailto:leonardo.herr...@gmail.com http://leus.epublish.cl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
It is actually perfectly reasonable for a person completely new to notating music for this to not make sense. The purpose of the documentation is to provide information about how lilypond prints music. Other resources are necessary to provide information about the difference, both written and sounded of a note and the various accidentals that can change a note. One big (in my opinion, reasonable) assumption made by the LilyPond documentation is that anyone using the program will be familiar with musical terms and what they mean. Hopefully in english, but there's even a glossary for foreign language speakers. On 25.08.2009, at 10:50, Simon Mackenzie wrote: Sorry but as a first time user to lilypond and music in general this section in the tutorial was about as clear as mud to me. Not wanting to offend anyone just stating how I felt the fist time I read this section in the learning tutorial. As I said previously when I have time I'll have a shot at articulating this more fully to aid my learning further and help others who have been tripped up Accidental(ly). Simon On 25/08/2009, at 15:34, David Bobroff wrote: As a follow-up, have the people with unwanted accidentals seen this: http://lilypond.org/doc/v2.13/Documentation/user/lilypond-learning/ Accidentals-and-key-signatures#Key-signatures ...and is it not clear? The last example on that page shouldn't be any less clear than the example I gave. -David David Bobroff wrote: Correct. *ALL* pitches in the input *must* be explicitly given. The key signature assignment tells LilyPond how to display the pitches. For exmaple; 'e' *always* means e-natural no matter what the key signature is. -David Simon Mackenzie wrote: Hi guys correct me if I am wrong. The g minor chord has two flats Eb Bb which need to be marked as es and bes in Lilypond other wise the Accidental_engraver sees them as naturals in the g minor chord, hence the natural symbol for any unmarked E or B note in your music. Just trying to see if I understand this all correctly? How did I do? Simon On 25/08/2009, at 01:39, Sona wrote: I'm new to Lilypond and the list. So far the code is pretty intuitive, but I am stumped by the way accidentals work. Several posts deal with this subject, but probably are beyond a novice's ability to undertand. I'm transcribing a modern piece with 2 flats in the key signature (I've set \key g \minor). It's rather atonal, though, so it seems Lilypond tries to correct pitch by turning every e- flat and b-flat into a natural. What code do I use to override this? The printed result should have only 4 accidentals. Right now there are 37, and of course the pitches are all off. What do I put where in what part of the code? I can send my page code, if it would be helpful. Thanks in advance! cleo ___ 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 ___ 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 James E. Bailey ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
how to remove \RemoveEmptyStaffContext up the chain?
Hello all,
I've got a situation where one of my \include files contains a
\layout { \context { \RemoveEmptyStaffContext } }.
99% of the time, I want this to happen. However, in a few
circumstances — especially when engraving/editing, but also for a few
specific pieces in final form — I want all of the functionality of
that \include file *except* the \RESC. Is there some way I can do
that from the main file (i.e., where the \include is called)? I'd
rather not have to define two different files (one with \RESC and one
without)...
Thanks,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
On Tue, Aug 25, 2009 at 08:46:59AM -0500, Tim McNamara wrote: For the developers, I think that something is confusing here for English speakers: the use of -es and -is for flatted and sharped notes as the default. I was initially bewildered by this, not knowing that the default conventions are Dutch. Well, the sentence immediately after the introduction of is/es/isis/eses says This syntax is derived from note naming conventions in Nordic and Germanic languages, like German and Dutch. (although that might have changed after you started using it) If the user is new to music in general then they have set themselves a daunting task trying to score music with LilyPond. There is no way for the documentation to make up for the user's lack of knowledge about the structure of music. Actually, in some ways there is -- the music glossary. And those links are at the top of every section in the Learning manual! So I'd say this: if somebody is new to music in general, doesn't read the Learning manual carefully, and doesn't read about unfamiliar terms in the music glossary, then they'll have a very daunting task. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
On Tue, Aug 25, 2009 at 10:05:45AM -0400, Leonardo Herrera wrote: I do have a suggestion: I would add two examples to the section that shows this clearly. How is that more clear than: In this example: \key d \major d cis fis No note has a printed accidental, but you must still add is and type cis and fis in the input file. The code b does not mean “print a black dot just on the middle line of the staff.” Rather, it means “there is a note with pitch B-natural.” In the key of A-flat major, it does get an accidental: \key aes \major b If the above seems confusing, consider this: if you were playing a piano, which key would you hit? If you would press a black key, then you must add -is or -es to the note name! -- Really, all the info is already there. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals: Unwanted naturals
Graham Percival wrote: On Tue, Aug 25, 2009 at 08:46:59AM -0500, Tim McNamara wrote: If the user is new to music in general then they have set themselves a daunting task trying to score music with LilyPond. There is no way for the documentation to make up for the user's lack of knowledge about the structure of music. Actually, in some ways there is -- the music glossary. And those links are at the top of every section in the Learning manual! I think you're right here. Nitpick: Shouldn't there be a see also: key signature in the music glossary 1.7 - accidental? Cheers, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme function for ossia
Jonathan Wilkes wrote Monday, August 24, 2009 6:34 PM Another thing I noticed is that \type, \alias, \remove, and \name are not in Appendix F of the NR. Index entries added in git. They'll appear in the Notation Reference in the next release. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme function for ossia
Hi Mats,
No! \alias does something completely different than you seem to
beleive.
Just to complete this (dangling) thread, and make sure *I* know what
it does... =)
\context
{
\name BAR
\alias FOO
...
}
informs lilypond that the newly-defined context called BAR should
accept any commands (\override, etc.) that are accepted by the
previously-defined context named FOO. However, none of the
\accepts, \removes, \overrides, \sets, etc. from the definition of
FOO are carried over automatically.
Correct?
Thanks,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Rhythm
Hi there, I cannot figure out how to encode a 16th note rhythm. When counting by mouth I would say: 1and 2and 3and 4and when all notes are taking part. In lilypond I would write: g16 g g g g16 g g g g16 g g g g16 g g g. But how do I: 1ad 2ad 3ad 4ad? Please notice I leave out the n. Thanks, Christian ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rhythm
On Tue, Aug 25, 2009 at 8:27 PM, Christian Henningchhenn...@gmail.com wrote: Hi there, I cannot figure out how to encode a 16th note rhythm. When counting by mouth I would say: 1and 2and 3and 4and when all notes are taking part. In lilypond I would write: g16 g g g g16 g g g g16 g g g g16 g g g. But how do I: 1ad 2ad 3ad 4ad? Please notice I leave out the n. Thanks, Christian Do you mean g16 g8 g16, repeated four times? Or maybe g16 g r g to get a rest instead of an eight note. You may find this helpful, if you haven't seen it already: http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/Simple-notation#Simple-notation Good luck, Andrew ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rhythm
On Aug 25, 2009, at 9:27 PM, Christian Henning wrote: Hi there, I cannot figure out how to encode a 16th note rhythm. When counting by mouth I would say: 1and 2and 3and 4and when all notes are taking part. In lilypond I would write: g16 g g g g16 g g g g16 g g g g16 g g g. But how do I: 1ad 2ad 3ad 4ad? Please notice I leave out the n. It's not clear what you are asking. 16th notes would just be 16th notes and your code would produce 16 16th notes correctly (you'd only need a g16 once at the beginning, although I think it is more sensible for every note to have the duration specified, so I would write 16 g16 notes. I don't understand what you are trying to accomplish with 1ad 2ad 3ad 4ad with or without the n in and. Especially since 1 and 2 and 3 and 4 and would usually suggest 8th notes rather than 16th notes. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
