Hugh Myers wrote:
I think I was keeping track of individual bars that way (with braces
that is)--- you are right, newline would work just as well and few
characters='s less clutter.
Well, bar checks would even work better, since they are actually checked
by LilyPond, thus the name... :-)
Use "
Here is the template I'm working with. The notes are nonsense, but the
problems are the ones I've run into and have had to solve...
\version "2.13.7"
upper = {
c4 d e f \startTextSpan % polyphonic
\repeat volta 2 {
g4 a b c % monophonic, see below
}
\alternative {
{ b4 \stopTextS
I think I was keeping track of individual bars that way (with braces
that is)--- you are right, newline would work just as well and few
characters='s less clutter. Regards \stop etc. I got it to work more
or less as you say. It is on another machine, I'll show you the
template in the next email.
-
> Since I normally program in lisp, I don't have any problems with
> nested delimiters. Are you suggesting that excess (at least to your
> eyes) braces are the problem or are you suggesting that the \stop is
> at the wrong level?
I was wondering why you add braces here: { a,8 [e'] g, [e'] f, [e']
Since I normally program in lisp, I don't have any problems with
nested delimiters. Are you suggesting that excess (at least to your
eyes) braces are the problem or are you suggesting that the \stop is
at the wrong level?
--hsm
2009/11/25 Frédéric Bron :
>> It would also help if the suggested cha
> It would also help if the suggested change worked. In stead I still get:
Maybe it is because you use curly braces { } everywhere. Try to put
the \stop... inside the { } block and not outside. But why using so
many braces?
Frédéric
___
lilypond-user m
It would also help if the suggested change worked. In stead I still get:
C:\Users\hsmyers\Desktop\Lily Projects>lilypond.exe malaguena.ly
GNU LilyPond 2.13.7
Processing `malaguena.ly'
Parsing...
malaguena.ly:56:1: error: syntax error, unexpected EVENT_IDENTIFIER
\stopTextSpan
malaguena.ly:89:0:
Since the piece in question, Malaguena, already has mixed monophony
and polyphony, as well as tablature, adding voices to it doesn't seem
like a very good idea. Yes, I'm aware that <<,\\ >> is shorthand for
voicing, but since it is shorthand, the visual complexity of the score
is kept to a readable
Le Wed, 25 Nov 2009 16:39:08 -0700,
Hugh Myers a écrit :
> So where do I place it? Bearing in mind that note-wise, both the start
> and stop are correctly placed?
\stopTextSpan is unexpected because \startTextSpan is in another Voice !
There was a warning in the [old] doc about this :
(implicit
This:
firstPolyRepeat = {
<< { r4 \startTextSpan \times 2/3 {gis'8 b e } e,4 \times 2/3 {gis8
b e} e,2 } \\ {e,2.~e} >>
}
secondMono = {
{ e'8 [e'] gis, [e'] b [e] }
{ e,8 [e'] gis, [e'] b [e] }
{ a,8 [e'] c [e] b [e] }
{ a,8 [e'] g, [e'] f, [e'] }
}
thirdMono = {
{ e,8 [e'] gis, [e']
10 matches
Mail list logo
