RE: Expecting '='
Duh. Thanks, Mats.
Ralph
-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2008 8:01 AM
To: Palmer, Ralph
Cc: lilypond-user@gnu.org
Subject: Re: Expecting '='
The first error message tells you that the \Score is wrong and as you
certainly know, the
capitalization matters in LilyPond. Just replace \Score with \score and
things should work
better.
/Mats
Palmer, Ralph wrote:
> Greetings -
>
> I'm missing something, but I don't know what. I'm running LP 2.11.27
> under Windows XP SP 2. I use a short "Section Test" file to check
> problems or to see if something works. When I run the following, it
> produces the PDF I expect, but the log file sees a problem. I can't
see
> what's wrong. Can anyone help me out?
>
> Ralph
>
> +
> Ralph Palmer, CEM
> Energy/Administrative Coordinator
> Keene State College
> Keene, NH 03435-2502
> Phone: 603-358-2230
> Cell: 603-209-2903
> Fax: 603-358-2456
> [EMAIL PROTECTED]
>
>
> +++ .ly file
>
> %Section Test
>
> \version "2.11.27"
> \include "english.ly"
> \paper {
> ragged-right = ##t
> }
>
> SectionTest = {
> \key c \major
> \clef treble
> \time 4/4
> \relative c'' {
> c4 d e f
> f4 e d c
> }
>
> }
>
> \Score {
> \SectionTest
> }
>
> +++ log
>
> # -*-compilation-*-
> Changing working directory to: `C:/Documents and Settings/rpalmer/My
> Documents/Ralph/Sheet Music/LilyPond/Test'
> Processing `C:/Documents and Settings/rpalmer/My Documents/Ralph/Sheet
> Music/LilyPond/Test/SectionTest.ly'
> Parsing...
> C:/Documents and Settings/rpalmer/My Documents/Ralph/Sheet
> Music/LilyPond/Test/SectionTest.ly:21:0: error: unknown escaped
string:
> `\Score'
>
> \Score {
>
> C:/Documents and Settings/rpalmer/My Documents/Ralph/Sheet
> Music/LilyPond/Test/SectionTest.ly:21:7: error: syntax error,
unexpected
> '{', expecting '='
> \Score
>{
>
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `SectionTest.ps'...
> Converting to `SectionTest.pdf'...
> error: failed files: "C:\\Documents and Settings\\rpalmer\\My
> Documents\\Ralph\\Sheet Music\\LilyPond\\Test\\SectionTest.ly"
>
>
> ___
> 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: [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: GDP, NR, 1.2.6.1: Grace note snippet
GDP has not touched that section yet, but thanks for the warning. I'm sure that when we get there, we'll fix it. Cheers, - Graham On Tue, 27 May 2008 18:10:06 +0300 "Risto Vr__niemi" <[EMAIL PROTECTED]> wrote: > Hi, > > Just in case someone is interested... I browsed the NR in GDP and one > snippet in grace note section caught my eye. > > http://kainhofer.com/~lilypond/Documentation/user/lilypond-big-page.html#Grace-notes > (Selected snippets) > > I guess either there shouldn't be a \relative statement or then the > most of the single quotes should be removed. > > > -Risto > > > ___ > 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: hairpin across line breaks is placed too high on the second line
On Mon, May 26, 2008 at 10:20 AM, Neil Puttock wrote: > > A rather inelegant workaround would be to use a callback with > 'extra-offset (ugh), like the one detailed in 7.7.2 Difficult tweaks: > > #(define (my-callback grob) > (let* ( > ; have we been split? > (orig (ly:grob-original grob)) > > ; if yes, get the split pieces (our siblings) > (siblings (if (ly:grob? orig) > (ly:spanner-broken-into orig) '() ))) > > (if (and (>= (length siblings) 2) > (eq? (car (last-pair siblings)) grob)) > (ly:grob-set-property! grob 'extra-offset '(0 . -1.8))) > ly:hairpin::after-line-breaking)) > > \once \override Hairpin #'after-line-breaking = #my-callback Hi Neil, Do you know if this is the only way the 'after-line-breaking property can be manually tweaked? There is some text in NR 1.3.1.2 (Dynamics): Crescendi and decrescendi that cross a line break will be continued on the second line. If they end on the first note of a new line, nothing will be printed on that line. To change this behavior, use \override Score.Hairpin #'after-line-breaking = ##t Is this tweak no longer valid? I wanted to see if anyone can enlighten me about this, so I can decide whether to remove (or keep) this information in NR 1.3.1.2. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book and the path
Dear Michael, thanks, it works now! 2008/5/27 Michael Käppler <[EMAIL PROTECTED]>: > Hi Stefan, > >> Dear lilypond-users, >> I made a strange experience. >> If I process the following quoted file with lilypond-book in the path " >> ~/partituren " everything is fine! >> But if I do the same in " ~/partituren/schüler/humboldt" it doesn't work! >> What could be the reason? >> > I'm able to reproduce it here - seems that lilypond-book (more exactly > lilylib.ly) doesn't process the umlaut correctly. > Ugly workaround: rename the folder to schueler instead of schüler. > > Michael > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Instruments with Diatonic Fretting
I am notating for instruments that are not chromatically fretted. Consider the modern mountain dulcimer. One possibility is three strings with frets placed to produce the following steps: Whole, Whole, Half, Whole, Whole, Half, Half, Half. This produces a major scale with the addition of a flat seven. Older dulcimers and most European ancestors are fretted W, W, H, W, W, H, W, W. Newer dulcimers are fretted W, H, H, H, W, W, H, H, H. I have been using Tabledit but would MUCH RATHER use Lilypond. Considering the instruments I'm arranging for, will Lilypond make my job easier and/or more fruitful? THANK YOU, Stephen Seifert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: hairpin across line breaks is placed too high on the second line
Hi Patrick, 2008/5/27 Patrick McCarty <[EMAIL PROTECTED]>: > On Mon, May 26, 2008 at 10:20 AM, Neil Puttock wrote: >> >> A rather inelegant workaround would be to use a callback with >> 'extra-offset (ugh), like the one detailed in 7.7.2 Difficult tweaks: >> >> #(define (my-callback grob) >> (let* ( >> ; have we been split? >> (orig (ly:grob-original grob)) >> >> ; if yes, get the split pieces (our siblings) >> (siblings (if (ly:grob? orig) >> (ly:spanner-broken-into orig) '() ))) >> >> (if (and (>= (length siblings) 2) >> (eq? (car (last-pair siblings)) grob)) >> (ly:grob-set-property! grob 'extra-offset '(0 . -1.8))) >> ly:hairpin::after-line-breaking)) >> >> \once \override Hairpin #'after-line-breaking = #my-callback > > Hi Neil, > > Do you know if this is the only way the 'after-line-breaking property > can be manually tweaked? I think so. It's documented as being a dummy property; I can't say I've seen it used in any other way. > There is some text in NR 1.3.1.2 (Dynamics): > > > > Crescendi and decrescendi that cross a line break will be continued on > the second line. If they end on the first note of a new line, nothing > will be printed on that line. To change this behavior, use > > \override Score.Hairpin #'after-line-breaking = ##t > > > > Is this tweak no longer valid? I wanted to see if anyone can > enlighten me about this, so I can decide whether to remove (or keep) > this information in NR 1.3.1.2. I'd guess that's a legacy item; it's strange that the context is specified as Score, since Hairpins work at the Voice context. I've done a bit of investigating in the source, and I can't see any way of forcing a broken hairpin for the first note of a new line - when hairpins are printed, the function consider_suicide () is called, which decides whether a Hairpin should be printed. It checks for the special case above, and kills the hairpin, so there's no way of overriding this behaviour. As a test, I've commented out the code which performs the "broken-hairpin-on-first-note-new-line" test and attached the output below; as you can see, it results in a small hairpin after the break, which I'd imagine would be the desired effect of the tweak, were it to work. So, unless I'm mistaken, I'd say the tweak isn't valid; it certainly has no effect, even when 'hairpin-to-barline = ##f. Regards, Neil test.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Fingering between notehead and beam?
Hi lilyponders,
When note stems are up and beamed, fingerings (when up) will go above
the stem and beam. How can I place them just above the note head
but left of the stem and below the beam?
I have found in the reference an "add-stem-support" property, but I
found it is used for e.g. StringNumber to avoid stems by going above
them (which is not done by default). For Fingering it does not seem to
work (they avoid stems by default, and setting add-stem-support to ##f
does not change that).
What I would like is not disable collision checks, but ensure the
fingering goes above the head, left of the stem, and below the beam,
for example for:
{ c'16-1 d'-2 e'-3 f'-4 }
I have found nothing else that seems to be related to stem/beam placement.
Thanks for any help!
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fingering between notehead and beam?
I'm not sure if this will get precisely what you want, but it should get
you on the right track:
http://kainhofer.com/~lilypond/Documentation/user/lilypond-learning/Within_002dstaff-objects.html#Within_002dstaff-objects
It has to do with placement of objects, including fingerings. I tried
all of these while proofreading for the GDP and was able to make them
work as shown in the examples, but haven't tried any finer placement.
If you come up with tweaks that get exactly the placement you want,
please share with the list. I'd like to know how to do this, too.
Jon
Papa Eric wrote:
Hi lilyponders,
When note stems are up and beamed, fingerings (when up) will go above
the stem and beam. How can I place them just above the note head
but left of the stem and below the beam?
I have found in the reference an "add-stem-support" property, but I
found it is used for e.g. StringNumber to avoid stems by going above
them (which is not done by default). For Fingering it does not seem to
work (they avoid stems by default, and setting add-stem-support to ##f
does not change that).
What I would like is not disable collision checks, but ensure the
fingering goes above the head, left of the stem, and below the beam,
for example for:
{ c'16-1 d'-2 e'-3 f'-4 }
I have found nothing else that seems to be related to stem/beam placement.
Thanks for any help!
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
