Holly Briscoe earthlink.net> writes:
> \new Lyrics = "sopranoWords" { s1 } % this line puts the "thee" [...]
> \new Staff = women <<
> \new Voice = "women" { << \womenMusic >> }
> >>
> \new Lyrics = "women" { s1 }
> \new Lyrics = "altoWords
Quoting Mike Amundsen <[EMAIL PROTECTED]>:
While creating identifiers for fret diagrams I found the identifiers
can be alpha only. I've searched the archives to see if there was a
discussion that described the reasons for that constraint. I'd guess
it's for reasons of simplicity and/or something
Quoting Paul Bakker <[EMAIL PROTECTED]>:
Thanks for Lilypond.
Is it possible to have two notes that have different note values
occupying the same position in one stave?
Of course:
\version "2.8.0"
\score{
\new Staff \relative c' { << c1 \\ {c2 b} >> }
}
See "Basic Polyphony" for more inform
[EMAIL PROTECTED] wrote:
The example in the manual wouldn't work at first - Lilypond just died quietly
with no error messages at all. Changing #(def-music-function to
#(define-music-function
sorted it though. Is this a typo? I was puzzled before about the difference
between the two.
That's ol
I achieve this by creating 2 parts, so that the transposed chords appear
below the original ones. I've seen this format used in a number of
published song books. You can create the "Capo 3", or similar text using
the \set instrument command. This puts "Capo 3" to the far left of the
first system, a
[I'm not sure how to reply in the thread, since there's no "reply link" in the
thread itself--at least the way I'm looking at it, which is simply by using
Mozilla Firefox and the page's web address. So this continuation of the thread
may not be attached properly--my apologies. I couldn't find a
Mats Bengtsson schreef:
OnionRingOfDoom wrote:
Ok, thanks for the quick help there! Someone should fix the doc so
that it's
a little easier to find that info though...
Please see
http://lilypond.org/web/devel/participating/documentation-adding
That doesn't apply here, though, as it's in
Holly Briscoe wrote:
> [I'm not sure how to reply in the thread, since there's no "reply link" in
> the thread itself--at least the way I'm looking at it, which is simply by
> using Mozilla Firefox and the page's web address. So this continuation of the
> thread may not be attached properly--my
