On Nov 20, 16:59, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>
> This release features support for repeats and sane tuplets.
>
> (Temporary) syntax for these :
>
> \times 2/3 { [c8 c8 c8] } % a triplet
I tried this and got
tt.ly:3:7: warning: No one to print a tuplet start bracket:
\times
2/3 { [c8 c8 c8] }
[1]
> \repeat 3 % repeat 3 times
> { { c1 c1} } % body to be repeated.
> \alternative {
> g1 % first ending
> a1
> b1 % third ending
> }
I really dislike the way that \relative doesn't penetrate into these
structures. I don't want to say \relative repeatedly for each
fragment. Why are the extra brackets required for the body of the
\repeat?
When I don't have lily.scm in the current directory, lilypond hangs
for ever. When I tried to install, only the binaries were installed.
I had to go into all the other directories and run 'make install'
myself.
When compiling, I got
make[1]: Entering directory `/home/team/adrian/src/lilypond-1.1.8/intl'
../stepmake/stepmake/c-targets.make:7: warning: overriding commands for target
`out/config.h'
../stepmake/stepmake/c-targets.make:4: warning: ignoring old commands for target
`out/config.h'
to install libintl type 'make lib; make install-lib'
true
make[1]: Leaving directory `/home/team/adrian/src/lilypond-1.1.8/intl'
make[1]: Entering directory `/home/team/adrian/src/lilypond-1.1.8/stepmake'
make[1]: *** No rule to make target `all'. Stop.
make[1]: Leaving directory `/home/team/adrian/src/lilypond-1.1.8/stepmake'
make: *** [all] Error 2
In addition to some funny looking output, I get mysterious messages like:
warning: can't open file: `8.afm'
warning: guessing dimensions for font style: `number-1'
warning: can't open file: `cmbx8.afm'
warning: guessing dimensions for font style: `bold'
from this:
\header{
bogus = nothing;
title = "Trip to Sofia";
composer = "David Bartley";
}
\score{
\notes \relative c'' { \key f; \time 4/4;
\repeat 2 { \relative c''{
[e8 d] | [cis a a e] [g a cis a] | [bes a g a] [bes d e f] |
[g a, f' a,] [e' a, cis a] | [bes d e d ] cis4-\prall [a8 d] |
[cis a a e] [g a cis a] | [bes a g a] [bes d e f] |
[g a, f' a,] [e' a, cis a] } }
\alternative{ \relative c''{[g f f g ] e4 } \relative c''{ [g'8 f f g ] e2 } }
\repeat 2 { \relative c''{
[bes8 a g a] [bes d e f] | [g a, f' a,] [e' a, cis a] |
[bes a g a] [bes g'] [ f d ] | [cis d e d ] cis4-\prall a |
[bes8 a g a] [bes d e f] }}
\alternative { \relative c'''{ [g a, f' a,] [e' a, cis a] |
[a' g g f] [f e e d] | [d cis d e ] cis4-\prall a }
\relative c''{
[a'8 g f a] [g f e g] | [f e d f] [e d cis a] |
[bes d f gis] a4 }}
}
\paper{}
\midi{\tempo 4 = 220;}
}
Here I tried to put in repeats using the new syntax. Weird stuff
happens. I think it may have to do with the fact that the repeats
fall in the middle of measures. But the output looks kind of strange
in various ways.
I couldn't figure out extenders. What do I do if I want to have the
lyric "foo____________________" where the long line extends over
several notes?
Here are updates to the reference manual. I think the accordion
symbols should be explained in the reference manual.
Only in lilypond-1.1.8/Documentation/man/out: dummy.dep
Only in lilypond-1.1.8/Documentation/ntweb: out
Only in lilypond-1.1.8/Documentation: out
Only in lilypond-1.1.8/Documentation/pictures: out
Only in lilypond-1.1.8/Documentation/tex: out
Only in lilypond-1.1.8/Documentation/tex: refman.old
diff -ur lilypond-1.1.8/Documentation/tex/refman.yo
lilypond-1.1.8.new/Documentation/tex/refman.yo
--- lilypond-1.1.8/Documentation/tex/refman.yo Wed Nov 25 15:12:01 1998
+++ lilypond-1.1.8.new/Documentation/tex/refman.yo Wed Nov 25 15:16:15 1998
@@ -15,6 +15,12 @@
the explanation of how lyrics mode parses words seems ridiculous.
Is there a simple way to explain this, or is the behavior
too complicated for a reasonable explanation?
+ \relative and \tranpose and \times make it necessary to specify
+ an explicit \type staff, or bizarre things happen.
+ catalan.ly
+ accordion symbols
+ extender* (see extender.ly)
+ \repeat & \alternative -> probably should have an example
)
@@ -40,7 +46,7 @@
whentexinfo(notableofcontents())
-article(Mudela 1.0.7 / LilyPond 1.0.15 Reference Manual)
+article(Mudela 1.0.7 / LilyPond 1.1.8 Reference Manual)
(Adrian Mariano, Han-Wen Nienhuys and Jan Nieuwenhuizen)
(nop()PIPETHROUGH(date "+%B %d, %Y")()()nop())
@@ -113,6 +119,11 @@
file(init.)var(ext) must contain the code(\maininput) keyword or LilyPond
will not read the user specified file.
+When LilyPond processes file(filename.ly) it will produce file(filename.tex) as
+output. If file(filename.ly) contains a second code(\paper) keyword, then
+LilyPond will produce file(filename-1.tex) as well. Subsequent code(\paper)
+keywords will produces sequentially numbered file names. Several files can be
+specified; they will each be processed independently.
sect(Syntax)
@@ -213,16 +224,16 @@
letter and are entirely alphanumeric. It is also impossible to refer
to an identifier whose name is the same as the name of a keyword. The
following words are keywords:
-verb(absdynamic header musicalpitch remove times
-accepts in name score translator
-bar include notenames script transpose
-cadenza key notes shape type
-clef keysignature paper skip version
-cm lyrics partial spandynamic
-consists maininput penalty symboltables
-duration mark property table
-font midi pt tempo
-grouping mm relative time)
+verb(absdynamic grouping mm relative symboltables
+accepts header musicalpitch remove table
+alternative in name repeat tempo
+bar include notenames scm time
+cadenza key notes scmfile times
+clef keysignature paper score translator
+cm lyrics partial script transpose
+consists maininput penalty shape type
+duration mark property skip version
+font midi pt spandynamic)
The right hand side of an identifier assignment is parsed completely
when the assignment is made. It therefore must have any context
@@ -332,6 +343,11 @@
_ _ _ _ % 4 words, each one a space
))
+It is possible to create words that break the rules by prefixing them with the
+dollar sign code($). Regardless of the context, a word beginning with code($)
+extends until the next white space character. Such words can contain numbers
+(even in Note mode), or other forbidden characters. The dollar sign can be
+used to create and access identifiers that could not otherwise be used.
COMMENT(
These modes are of a lexical nature. Normal and Note mode largely
@@ -454,6 +470,10 @@
mudela(fragment,verbatim,center)(
[a'8 a'] [a'16 a' a' a']
)
+If you want to put beams over chords, you will find that the obvious
+construction does not work. You must do the following:
+mudela(fragment,verbatim,center)(<[a'8 c''> b' <c'' e''> <a' c'']>)
+The bracket characters must appear immediately adjacent to a note.
In order to create triplets, you must use a length multiplier after
the brackets. An open bracket code([) followed by a fraction
@@ -529,13 +549,13 @@
c''-\open c''-\flageolet c''-\reverseturn
c''-\trill
c''-\prall c''-\mordent c''-\prallprall c''-\prallmordent
- c''-\upprall c''-\downprall }
+ c''-\upprall c''-\downprall c''-\thumb}
\type Lyrics \lyrics{
accent marcato staccatissimo fermata stopped
staccato tenuto upbow downbow lheel rheel ltoe rtoe turn
open flageolet reverseturn
trill prall
- mordent prallprall prallmordent uprall downprall }>
+ mordent prallprall prallmordent uprall downprall thumb}>
\paper{linewidth = 5.875\in;
indent = 0.0;
}
@@ -576,6 +596,13 @@
terminated with code(\rced). There are also shorthands for these
marks. A crescendo can be started with code(\<) and a decrescendo can
be started with code(\>). Either one can be terminated with code(\!).
+Note that code(\!) must go before the last note of the dynamic mark whereas
+code(\rc) and code(\rced) go after the last note. Because these marks are
+bound to notes, if you want to get several marks during one note, you must use
+spacer notes.
+mudela(fragment,verbatim,center)(
+c'' \< \! c'' d'' \decr e'' \rced
+< f''1 {s4 \< \! s4 \> \! s2 } >)
Tremolo marks can be printed by a note by adding code(:)[var(length)]
after the note. The length must be at least 8. A var(length) value
@@ -868,6 +895,9 @@
code(\translator) block. It specifies what contexts are allowed with the
context that is being defined. See Section ref(translators).
+dit(code(\alternative) code({) var(music1) var(music2) ... code(}))
+Specifies alternative endings. Must come after a code(\repeat) keyword.
+
dit(code(\bar) var(bartype)code(;)) Prints a special bar symbol, or at
measure boundaries, replaces the regular bar symbol with a special
symbol. The argument var(bartype) is a string which specifies the
@@ -906,6 +936,7 @@
mudela(center)(
\score{
\notes{\cadenza 1; \clef alto; c'4_"\kern -10mm alto"
+ \clef scarlatti; c'4_"\kern -4mm scarlatti"
\clef mezzosoprano; c'4^"\kern -10mm mezzosoprano"
\clef soprano; c'4_"\kern -10mm soprano"
\clef treble; c'4^"\kern -6mm treble"
@@ -943,8 +974,9 @@
top of the file describing the file's contents. If a file has
multiple code(\score) blocks, then a header should appear in
each score block describing its contents. Tools like code(ly2dvi) can
-use this information for generating titles. Some possible key values
-are: title, opus, description, composer, enteredby, and copyright.
+use this information for generating titles. Key values that are used
+by ly2dvi are: title, subtitle, composer, opus, poet, instrument,
+metre, arranger, and piece.
dit(code(\in)) Specify a dimension in inches.
@@ -1041,6 +1073,16 @@
code(\translator) block. Specifies that a performer or engraver named
var(string) should be removed. See Section ref(translators).
+dit(code(\repeat) var(count) code({) var(music) code(}))
+Repeats the specified
+music var(count) times. Alternative endings can be specified by adding a
+code(\alternative) keyword after the code(\repeat).
+
+dit(code(\scm) var(scheme)code(;)) Embeds specified Scheme code.
+
+dit(code(\scmfile) var(filename)code(;)) Reads Scheme code from the specified
+file.
+
dit(code(\score) var(statementlist)) Create a Score context. This
is the top level notation context.
COMMENT(this still needs work)
@@ -1256,6 +1298,10 @@
force slurs down. The shorthands code(\slurup), code(\slurdown), and
code(\slurboth) are available.
+dit(code(tieYDirection)) Set to code(\free) for free choice of tie
+direction, set to code(\up) to force ties up, set to code(\down) to
+force ties down.
+
dit(code(slurdash)) Set to 0 for normal slurs, 1 for dotted slurs, and
a larger value for dashed slurs. Identifiers code(\slurnormal) and
code(\slurdotted) are predefined to set the first two settings.
@@ -1786,9 +1832,6 @@
dit(code(Lyric_engraver)) Engraves lyrics. Normally in code(LyricVoice).
dit(code(Multi_measure_rest_engraver)) Engraves multi-measure rests that are
produced with code(R). Normally in code(Voice).
-dit(code(Note_heads_engraver)) Engraves note heads. Normally in code(Voice).
-Removing this gives a fatal error.
-COMMENT(Perhaps should be Note_head_engraver)
dit(code(Piano_bar_engraver))
dit(code(Pitch_squash_engraver)) Treat all pitches as middle C. Used in
code(RhythmicStaff). Note that the notes move, but the locations of
@@ -1799,6 +1842,8 @@
In code(LyricVoice).
COMMENT( Should this be named Plet_req_swallow_translator? )
dit(code(Priority_horizontal_align_engraver))
+dit(code(Repeat_engraver)) Handles repeats? In code(Staff) and
+ code(RhythmicStaff).
dit(code(Rest_collision_engraver)) Handles collisions of rests. In code(Staff).
dit(code(Rest_engraver)) Engraves rests. Normally in code(Voice).
dit(code(Rhythmic_column_engraver))
@@ -1824,6 +1869,7 @@
dit(code(Timing_engraver)) Responsible for synchronizing timing information
from staffs. Normally in code(Score). In order to create polyrhythmic music,
this engraver should be removed from code(Score) and placed in code(Staff).
+dit(code(Tuplet_engraver)) Engraves tuplet brackets? In code(Staff).
dit(code(Vertical_align_engraver))
)
Only in lilypond-1.1.8.new/Documentation/tex: refman.yo.orig
Only in lilypond-1.1.8.new/Documentation/tex: refman.yo~
Only in lilypond-1.1.8/Documentation/topdocs: out
Only in lilypond-1.1.8: GNUmakefile
Only in lilypond-1.1.8: aclocal.m4~
Only in lilypond-1.1.8/buildscripts: out
Only in lilypond-1.1.8: config.cache
Only in lilypond-1.1.8: config.h
Only in lilypond-1.1.8: config.log
Only in lilypond-1.1.8: config.make
Only in lilypond-1.1.8: config.status
Only in lilypond-1.1.8/debian/out: BLURB
Only in lilypond-1.1.8/debian/out: changelog
Only in lilypond-1.1.8/debian/out: copyright
Only in lilypond-1.1.8/debian/out: dummy.dep
Only in lilypond-1.1.8/debian/out: postinst
Only in lilypond-1.1.8/debian/out: postrm
Only in lilypond-1.1.8/debian/out: rules
Only in lilypond-1.1.8/debian/out: watch
Only in lilypond-1.1.8/flower/include: out
Only in lilypond-1.1.8/flower: out
Only in lilypond-1.1.8/init: out
Only in lilypond-1.1.8/input/bugs: out
Only in lilypond-1.1.8/input: out
Only in lilypond-1.1.8/input/test: out
Only in lilypond-1.1.8/intl: out
Only in lilypond-1.1.8/lib/include: out
Only in lilypond-1.1.8/lib: out
Only in lilypond-1.1.8/lily/include: out
Only in lilypond-1.1.8/lily: out
Only in lilypond-1.1.8/make/out: dummy.dep
Only in lilypond-1.1.8/mf: out
Only in lilypond-1.1.8/mi2mu/include: out
Only in lilypond-1.1.8/mi2mu: out
Only in lilypond-1.1.8/mutopia/Coriolan: out
Only in lilypond-1.1.8/mutopia/J.S.Bach/Cembalo-Partitas: out
Only in lilypond-1.1.8/mutopia/J.S.Bach/Petites-Preludes: out
Only in lilypond-1.1.8/mutopia/J.S.Bach/Solo-Cello-Suites: out
Only in lilypond-1.1.8/mutopia/J.S.Bach: out
Only in lilypond-1.1.8/mutopia/W.A.Mozart: out
Only in lilypond-1.1.8/mutopia: out
Only in lilypond-1.1.8: out
Only in lilypond-1.1.8/po: out
Only in lilypond-1.1.8/ps: out
Only in lilypond-1.1.8/scripts: out
Only in lilypond-1.1.8/stepmake/bin: flower.pyc
Only in lilypond-1.1.8/stepmake/bin: packagepython.pyc
Only in lilypond-1.1.8/test: out
Only in lilypond-1.1.8/tex: out
