Re: K460 does not compile under 2.6.0
On Saturday 09 July 2005 21.48, Sebastiano Vigna wrote:
> I don't want to seem iterative, but my source for K460
> (http://vigna.dsi.unimi.it/music/K460.ly) does not compile still with
> 2.6.0. Problems start with the appoggiatura at measure 28.
>
> I would like just to know if the answer is "won't fix", as I will try to
> fiddle with the source to see whether I can work around it. If anybody
> can suggest a workaround, I'd be immensely grateful.
I just realised - you can write your own repeat unfold! I'm no Scheme expert,
but I managed to write this quick hack:
unfold = #(def-music-function (parser location number music) (number?
ly:music?)
(letrec ((ccp (lambda (n)
(if (= 0 n) '() (cons music (ccp (- n 1)
)
)
(make-music 'SequentialMusic
'elements (ccp number)
)
)
)
{ \unfold #7 {\grace b8 c4 d e f } }
It's not exactly the same as \repeat unfold, and it might not be enough for
you (it doesn't work well together with \relative).
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypond and stability [Was: K460 does not compile under 2.6.0]
On Sun, 2005-07-10 at 20:07 +0200, Erik Sandberg wrote: > realised - you can write your own repeat unfold! I'm no Scheme expert, > but I managed to write this quick hack: Scheme hacks are not portable across versions, and certainly not fixed by convert-ly (I just removed a snippet from LSR because of that). In my view Lilypond is to music as TeX is to text (this might be a narrow view, of course). One of the basic issues that Knuth wanted to solve with TeX was to have a stable system that would compile forever his books exactly in the same way. Everybody knows that a Word document has a lifespan of a few years, after which the input filter start to get crazy and the document is gone (you have still the text, but the rest has just a pale resemblance with the original). But I can still compile my undergrad TeX notes without problems, getting the same output. Now, music has an even larger lifespan--technical books are often replaced by newer books, but music is never replaced. The problem I see with regressions is that people with a large body of Lilypond music will grow more and more scared of recompiling with new versions. I mean--what can you do? Check measure by measure that hundreds of pages of music are still getting out right? That your carefully chosen page/line breaks are still reasonable? Of course, it's a tradeoff--if you want to make the layout algorithms better, you change the output. And clearly Lilypond is constantly improving, which is a Good Thing(TM). I wonder, however, why several scores on mutopia that were compiled on Lilypond 1.x are not recompiled with newer versions. They could clearly get better, so my guess is that the author is scared of losing control of what will happen. -- Ciao, seba ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Stems up and down
Problems with J.S.Bach and polyphony
Have one voice, but played as 2 voices
I need the stems up for the "upper voice" and down for the "lower
voice", as in 2 voices but in one voice
;-)
\time 3/4
cis16 a,16_"forte" a'16 a,16 gis'16 a,16 a'16 a,16 b'16 a,16 gis'16
a,16 %63
Something like:
\time 3/4
cis16\stemUp a,16_"forte"\stemDown a'16\stemUp a,16\stemDown
gis'16\stemUp a,16\stemDown ...
<< { \stemUp ... } // { \stemDown ... } >> I try this but,
it s not correct because there is only one voice.
How to do it?
Thanks, sorry, sorry for my bad english
Georges
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stems up and down
On 11-Jul-05, at 4:34 AM, Georges Roux wrote:
<< { \stemUp ... } // { \stemDown ... } >> I try this but, it s not
correct because there is only one voice.
How to do it?
Use \\ instead of // .
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stems up and down
Graham Percival a écrit :
>
> On 11-Jul-05, at 4:34 AM, Georges Roux wrote:
>
>> << { \stemUp ... } // { \stemDown ... } >> I try this but, it s not
>> correct because there is only one voice.
>>
>> How to do it?
>
>
> Use \\ instead of // .
>
> - Graham
>
sorry but << { \stemUp ... } \\ { \stemDown ... } >> isn't good because
it's not 2 voices but one voice
Georges
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Argument transfer?
"Fairchild" <[EMAIL PROTECTED]> writes:
> 3) I don't understand some elements, and hope for enlightenment about:
>a) def-music-function (location MagArg) (number?)
This is the way to define new LilyPond "keywords", eg functions
manipulating their argument in order to build some music expression
programatically. See the LilyPond manual,
http://lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond/Extending-music-syntax.html
http://lilypond.org/doc/v2.6/Documentation/user/out-www/lilypond/Extending-music-syntax.html
>b) #(use-modules (ice-9 optargs))
this asks to load a module, which makes it possible to define functions
with variable number of arguments, keyword arguments, etc. Note that in
the example that you show, it is not necesarry. Just change 'define*' by
'define'. See the guile manual, chapter on modules:
http://www.gnu.org/software/guile/docs/guile-ref/Using-Guile-Modules.html
>c) #(define* (AltOn MagArg)
This should be define, not define*.
define* is for defining function with more complex arguments,
eg. keyword, rest or optional arguments. See the guile manual:
http://www.gnu.org/software/guile/docs/guile-ref/define--Reference.html
>d) (ly:export #{ . . . #}
See the LilyPond-internal manual:
http://lilypond.org/doc/v2.6/Documentation/user/out-www/lilypond-internals/Scheme-functions.html
> %%%
>
> \version "2.4.6"
> AltOn = #( def-music-function
> (location MagArg) (number?) #{
> #( define Mag $MagArg )
> #( define SizeIE (*(/ 6.0 (log 2.0)) (log Mag)))
> #( define Size (inexact->exact SizeIE ))
> \override Stem #'length = #(* 7.0 Mag)
> \override NoteHead #'font-size = #Size #})
> AltOff = {
> \revert Stem #'length
> \revert NoteHead #'font-size }
> { c' \AltOn #0.5 c' c' \AltOff c' }
>
> %%%
>
> \version "2.4.6"
> #(use-modules (ice-9 optargs))
> #(define* (AltOn MagArg) (ly:export #{
> #( define Mag $MagArg )
> #( define SizeIE (*(/ 6.0 (log 2.0)) (log Mag)))
> #( define Size (inexact->exact SizeIE ))
> \override Stem #'length = #(* 7.0 Mag)
> \override NoteHead #'font-size = #Size #}))
> #(define* (AltOff) (ly:export #{
> \revert Stem #'length
> \revert NoteHead #'font-size #}))
> { c' #(AltOn 0.65) c' c' #(AltOff) c' }
>
> %%%
The first of your two solutions is the more LilyPond-idiomatic. However,
the style is not very clean, here is how it could be rephrased:
\version "2.4.6"
AltOn = #(def-music-function (location mag) (number?)
#{ \override Stem #'length = #$(* 7.0 mag)
\override NoteHead #'font-size =
#$(inexact->exact (* (/ 6.0 (log 2.0)) (log mag))) #})
AltOff = {
\revert Stem #'length
\revert NoteHead #'font-size
}
{ c' \AltOn #0.5 c' c' \AltOff c' }
Or, with LilyPond 2.6 (note the extra 'parser' argument):
\version "2.6.0"
AltOn = #(def-music-function (parser location mag) (number?)
#{ \override Stem #'length = #$(* 7.0 mag)
\override NoteHead #'font-size =
#$(inexact->exact (* (/ 6.0 (log 2.0)) (log mag))) #})
AltOff = {
\revert Stem #'length
\revert NoteHead #'font-size
}
{ c' \AltOn #0.5 c' c' \AltOff c' }
However, I would rather write like this:
\version "2.6.0"
withAlt = #(def-music-function (parser location mag music) (number?
ly:music?)
#{ \override Stem #'length = #$(* 7.0 mag)
\override NoteHead #'font-size =
#$(inexact->exact (* (/ 6.0 (log 2.0)) (log mag)))
$music
\revert Stem #'length
\revert NoteHead #'font-size #})
{ c' \withAlt #0.5 { c' c' } c' }
For LilyPond 2.4.6, remove the 'parser' argument after def-music-function.
nicolas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cygwin install of 2.6?
I installed 2.6.0 for Cygwin on my Windows XP this morning. Lilypond says that it can not find my files when I try to run it. I also tried running my files through Lilypond-book and got the following errors: File "/usr/bin/lilypond-book", line 1616, in ? main () File "/usr/bin/lilypond-book", line 1582, in main chunks = do_file (file) File "/usr/bin/lilypond-book", line 1448, in do_file set_default_options (source) File "/usr/bin/lilypond-book", line 660, in set_default_options textwidth = get_latex_textwidth (source) File "/usr/bin/lilypond-book", line 1280, in get_latex_textwidth tempfile.tempdir = '' NameError: global name 'tempfile' is not defined Rob -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
multiline footer in Postscript backend
Hi, I'm working on a Mutopia score. I'm having trouble creating a multiline footer with the Postscript backend. Any suggestions on how to accomplish that in the most elegant way? Mark -- Mark Van den Borre Noormannenstraat 113 3000 Leuven, België +32 486 961726 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: force accidentals
Nicoas, Mehmet meant to say "Can the function be modified to not put an accidental or natural on notes repeated in the same measure." Put it another way and the question is: "Can we make the accidental engraver treat the natural exactly the way it treats the sharp and flat?" In Atonal music, there is not key signature. Normally, if there are not accidentals in the key signature, that means the key is either C Major or a minor. So how do we indicate on paper that there is no key signature? Simple. Put the natural on the same footing as the sharp and flat, treat each note as if it has an equal chance of being a natural, sharp, or flat. Accidentals are only normally put on a note the first time they occur in a measure, so we want the natural to be treated that way too. Instead of putting an accidental on every note, we want notes repeated in the same measure to be absent an accidental. Somewhere in the function forceAlterations you might have the line: (eqv? (ly:music-property m 'measureLength) 0) checking to see whether the present note is the first occurance of that note (within the same octave, as Mehmet stated) since the measure began. Doing it that way would be cumbersome and might make the function more complicated than it would have to be, but I am indicating what the function should do to engrave Atonal music properly. Shoenberg did note approve to the term 'Atonal'. However, this is how his music was originally published in the Universal Edition engravings. The proper term is 'Music without a Key Signature', but that is not as catchy as 'Atonal'. So how would you enforce the idea that the music has no key signature when absence of accidentals in the key signature indicates C major? The answer is treating the natural the same as the other two accidentals. This could be written into the accidental engraver as a standard style: #(set-accidental-style 'atonal) Stephen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cygwin install of 2.6?
Rob Vlasaty wrote: I installed 2.6.0 for Cygwin on my Windows XP this morning. Lilypond says that it can not find my files when I try to run it. I also tried running my files through Lilypond-book and got the following errors: File "/usr/bin/lilypond-book", line 1616, in ? main () File "/usr/bin/lilypond-book", line 1582, in main chunks = do_file (file) File "/usr/bin/lilypond-book", line 1448, in do_file set_default_options (source) File "/usr/bin/lilypond-book", line 660, in set_default_options textwidth = get_latex_textwidth (source) File "/usr/bin/lilypond-book", line 1280, in get_latex_textwidth tempfile.tempdir = '' NameError: global name 'tempfile' is not defined I just hit that one. It is known. That same python bug is also in the Linux version. It may be fixed in 2.6.1 and/or 2.7.0 Paul Scott ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Cygwin install of 2.6?
Specifying the whole path solved this problem: $ lilypond -V /cygdrive/z/temp/2.6/test/test.ly GNU LilyPond 2.6.0 But then 'PFAPFAemmentaler-26.pfa.pfa' is not found (the file 'PFAemmentaler-26.pfa' exists)??? Georg error: can't find file: `/usr/share/lilypond/2.6.0/fonts/type1//PFAPFAemmentaler -26.pfa.pfa' (load path: `/usr/share/lilypond/2.6.0/fonts/cff/:/usr/share/lilypo nd/2.6.0/fonts/svg/:/usr/share/lilypond/2.6.0/fonts/cff/:/usr/share/lilypond /2.6 .0/fonts/type1/:/usr/share/lilypond/2.6.0/fonts/otf/:/usr/share/lilypond/2.6 .0/s cm:/usr/share/lilypond/2.6.0/ps:/usr/share/lilypond/2.6.0/ly::/cygdrive/z/te mp/2 .5/test') -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Vlasaty Sent: Monday, July 11, 2005 4:20 PM To: lilypond-user@gnu.org Subject: Re: Cygwin install of 2.6? I installed 2.6.0 for Cygwin on my Windows XP this morning. Lilypond says that it can not find my files when I try to run it. I also tried running my files through Lilypond-book and got the following errors: File "/usr/bin/lilypond-book", line 1616, in ? main () File "/usr/bin/lilypond-book", line 1582, in main chunks = do_file (file) File "/usr/bin/lilypond-book", line 1448, in do_file set_default_options (source) File "/usr/bin/lilypond-book", line 660, in set_default_options textwidth = get_latex_textwidth (source) File "/usr/bin/lilypond-book", line 1280, in get_latex_textwidth tempfile.tempdir = '' NameError: global name 'tempfile' is not defined Rob -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ___ 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: Lilypond and stability
Sebastiano Vigna <[EMAIL PROTECTED]> writes:
> On Sun, 2005-07-10 at 20:07 +0200, Erik Sandberg wrote:
>> realised - you can write your own repeat unfold! I'm no Scheme expert,
>> but I managed to write this quick hack:
>
> Scheme hacks are not portable across versions, and certainly not fixed
> by convert-ly (I just removed a snippet from LSR because of that).
You're taking that the wrong way.
I think defining custom functions precisely helps maintaining large
scores. Let me tell you about a personal example. In a very large score,
I wanted tempo markings (Allegro...) to be written like this:
\mark \markup { "" \translate #(cons -3 2) "Allegro" }
What I did was to define a custom function, \tempoMark, invoked like
this: \tempoMark #"Allegro"
But some day, \markup { "" \translate ... } stopped working as before,
and had to be changed to: \markup { " " \translate ... } (note the space
between the double quotes.) This was simply done by just changing the
custom function definition, not the 148 places were \tempoMark was used.
nicolas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cygwin install of 2.6?
Rob Vlasaty wrote: I installed 2.6.0 for Cygwin on my Windows XP this morning. Lilypond says that it can not find my files when I try to run it. My other response did not address your first question. Others will probably pick this up faster and better since I have not run Lily under cygwin but how are you invoking lilyPond? Paul ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: force accidentals
"Stephen" <[EMAIL PROTECTED]> writes:
> Nicoas,
>
> Mehmet meant to say "Can the function be modified to not put an
> accidental or natural on notes repeated in the same measure."
>
> Put it another way and the question is: "Can we make the accidental
> engraver treat the natural exactly the way it treats the sharp and
> flat?"
>
> In Atonal music, there is not key signature. Normally, if there are
> not accidentals in the key signature, that means the key is either C
> Major or a minor. So how do we indicate on paper that there is no key
> signature? Simple. Put the natural on the same footing as the sharp
> and flat, treat each note as if it has an equal chance of being a
> natural, sharp, or flat.
>
> Accidentals are only normally put on a note the first time they occur
> in a measure, so we want the natural to be treated that way
> too. Instead of putting an accidental on every note, we want notes
> repeated in the same measure to be absent an accidental.
Here is *very* dirty trick, which produces lots of warnings, but the
output seems to be OK. The good way would be to pay Han-Wen to implement
that feature.
\version "2.7.0"
atonicKey =
#(def-music-function (parser location) ()
#{ #(ly:export (make-music 'EventChord
'origin $location
'elements (list (make-music 'KeyChangeEvent
'tonic (ly:make-pitch -1 4 0)
'pitch-alist '((4 . 5)
(5 . 5)
(6 . 5)
(0 . 5)
(1 . 5)
(2 . 5)
(3 . 5))
\set Score . extraNatural = ##f #})
\layout { raggedright = ##t }
{
\atonicKey
c'8 c' c'' c'' d' d' d'' d''
cis'8 cis' cis'' cis'' des' des' des'' des''
c'8 c' c'' c'' d' d' d'' d''
cis'8 cis' cis'' cis'' des' des' des'' des''
}
nicolas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
problems with (new) lilypond-book
After installing 2.6.0 with "lilypond-2.6.0.x86.package" (Thank you so much for this nice installation script!) on Debian System (the previous version version 2.4 worked fine) I have a problem with lilypond-book. I get this message: # lilypond-book -o out test.tex lilypond-book-bin-2.6.0 (GNU LilyPond) 2.6.0 test.tex lesen... Traceback (most recent call last): File "/usr/bin/lilypond-book-bin-2.6.0", line 1616, in ? main () File "/usr/bin/lilypond-book-bin-2.6.0", line 1582, in main chunks = do_file (file) File "/usr/bin/lilypond-book-bin-2.6.0", line 1448, in do_file set_default_options (source) File "/usr/bin/lilypond-book-bin-2.6.0", line 660, in set_default_options textwidth = get_latex_textwidth (source) File "/usr/bin/lilypond-book-bin-2.6.0", line 1280, in get_latex_textwidth tempfile.tempdir = '' NameError: global name 'tempfile' is not defined # Please help! Wolfgang -- Wolfgang Mechsner Goebenstr. 3 49076 Osnabrück Tel. 0541-2052090 Mobil 0179-9096684 [EMAIL PROTECTED] www.wolfgang-mechsner.de ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problems with (new) lilypond-book
Wolfgang Mechsner wrote: After installing 2.6.0 with "lilypond-2.6.0.x86.package" (Thank you so much for this nice installation script!) on Debian System (the previous version version 2.4 worked fine) I have a problem with lilypond-book. I get this message: # lilypond-book -o out test.tex lilypond-book-bin-2.6.0 (GNU LilyPond) 2.6.0 test.tex lesen... Traceback (most recent call last): File "/usr/bin/lilypond-book-bin-2.6.0", line 1616, in ? main () File "/usr/bin/lilypond-book-bin-2.6.0", line 1582, in main chunks = do_file (file) File "/usr/bin/lilypond-book-bin-2.6.0", line 1448, in do_file set_default_options (source) File "/usr/bin/lilypond-book-bin-2.6.0", line 660, in set_default_options textwidth = get_latex_textwidth (source) File "/usr/bin/lilypond-book-bin-2.6.0", line 1280, in get_latex_textwidth tempfile.tempdir = '' NameError: global name 'tempfile' is not defined # A known python bug just reported several times. It might be fixed in 2.6.1 and/or 2.7.0. How can I get 2.6.1 for x86? Paul Scott ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problems with (new) lilypond-book
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a known bug that is fixed in the CVS; the Python script which is lilypond-book is missing "import tempfile" near the beginning. If you are feeling courageous :) you can make the change yourself; just add the line import tempfile at the end of the first group of import statements, after "import string". Be sure to make a backup copy of lilypond-book before editing. - -- Nicholas Haggin A.M.D.G. Find my public keys at my website: http://nhaggin.freeshell.org/ -BEGIN PGP SIGNATURE- iD8DBQFC0uTgYbuXiaDnyW4RAsGWAKCO/YLXW3e2MLH1vU97bl8NPhOBggCfSXXb 9jjhMNkR7zMVlVcQTxtqR1Q= =mOkF -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problems with (new) lilypond-book
Nicholas Haggin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a known bug that is fixed in the CVS; the Python script which is lilypond-book is missing "import tempfile" near the beginning. If you are feeling courageous :) you can make the change yourself; just add the line import tempfile at the end of the first group of import statements, after "import string". Be sure to make a backup copy of lilypond-book before editing. Thanks. That was easy enough. Now a minor problem: [EMAIL PROTECTED]:~/music/stfrancis$ lilypond-book-2.6.0 --output=out --psfonts oilbook.tex lilypond-book-bin-2.6.0 (GNU LilyPond) 2.6.0 Reading oilbook.tex... Dissecting... Writing snippets... Processing... (snip) Compiling oilbook.tex... Writing `oilbook.tex'... Writing fonts to oilbook.psfonts... DVIPS usage: dvips -h out/oilbook.psfonts out/oilbook.dvi Paul ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cygwin install of 2.6?
Paul, you asked how I was invoking lilypond. In the Cygwin window, I navigate to the folder where my files are stored then I type in: lilypond test.ly Doing this always worked fine in version 2.4, but 2.6 can't find the file. Using Georg's method of typing in the whole path found the file. In my case it was: lilypond /home/Rob/2.6.0/test.ly but I also got the error about 'PFAPFAemmentaler-26.pfa.pfa' is not found. Rob -- ___Sign-up for Ads Free at Mail.com http://www.mail.com/?sr=signup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Jean-marc LEGRAND/CRS/FR/RM/Corp est absent(e).
Je serai absent(e) du 30/06/2005 au 24/07/2005. Je répondrai à votre message dès mon retour. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stems up and down
On 11-Jul-05, at 5:26 AM, Georges Roux wrote:
Graham Percival a écrit :
Use \\ instead of // .
sorry but << { \stemUp ... } \\ { \stemDown ... } >> isn't good because
it's not 2 voices but one voice
You are mistaken. Please read the manual section on Polyphony.
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond-book problem remains in 2.6.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The output issues I posted about earlier (to lilypond-user only) remain under 2.6.1, although the other bugs I ran into are now fixed. http://nhaggin.freeshell.org/lilybook-trouble/ Again, note the vertical placement of staves in hymnal.pdf. - -- Nicholas Haggin A.M.D.G. Find my public keys at my website: http://nhaggin.freeshell.org/ -BEGIN PGP SIGNATURE- iD8DBQFC0vs4YbuXiaDnyW4RAmciAJ9+9MtNDwap1AsDlQ6jE08WZeWVXgCfWRIW +fqc2dlVUPuGzQVht0d7SEQ= =Nlyn -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Figured Bass Improvements Potential Sponsorship of Improving this Feature.
Dear All, Currently I am thinking about sponsoring the improvement of the figured bass system within LilyPond. The Main features that I am proposing are: 1: The alignment of the figures are calcuated from the top of the figured group and spaced appropriately from the bottom of the note they appear under. i.e. the figures will be placed dynamically from the bass note rather than the current method of aligning along a baseline based on the number of figures. Also the same facility to place the figures above the continuo part and again dynamically spaced from the note to avoid collisions. 2: The introduction of spanner lines. These are used mainly in french baroque music as well as some sacred music scores. They indicate the prolongation of a figure or group of figures. e.g 6 -- 4 -- 2 --- or 6 4 - 2 indicating the entire group to be prolonged. or 6 --- 5 --3 2 - indicating that the 6th and 2nd stay the same but the 5th moved to a 3rd. 3. Lastly that the figures are centred on the number with modifying accidentals placed on either side. Also accidentals by themselves can be used eg. # 5 indicating a sharpened 3rd. If anyone else has ideas or wishes to contribute to the funding of this feature please contact me at [EMAIL PROTECTED]. Regards, Trent Johnston ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lyric placement
I'm just starting to play with lp by working on a hymn. The format is upper
and lower piano staves with the verses in the middle. I was using chords for
the upper and lower until I came to a place where I had two 8th notes in the
soprano over a 1/4 in the alto. I don't know if it's the best way, but I
found a way to do it. The problem is that I can't get a lyric to print under
those notes. Any suggestions would be appreciated.
Arthur
\version "2.6.0"
upper = \relative c' {
\clef treble
\key bes \major
\time 4/4
4 2 |
44. 8 2
4 2
4 << { c'8 bes } \\ { g4 } >> 4 f2
44. 8 2
44. 8 2
}
lower = \relative c {
\clef bass
\key bes \major
\time 4/4
4 2
44. 8 2
4 2
4 2
}
text = \lyricmode {
Can a lit -- tle child like me
Thank the Fa -- ther fit -- ting -- ly?
Yes, O yes! be good and true,
Pa -- tient, kind in _ all you do;
Love the Lord, and do your part;
Learn to say with all your heart,
}
\score {
\context GrandStaff <<
\context Staff = upper {
\context Voice = singer \upper }
\lyricsto "singer" \new Lyrics \text
\context Staff = lower <<
\clef bass
\lower
>>
>>
\layout {
\context { \GrandStaff \accepts "Lyrics" }
\context { \Lyrics \consists "Bar_engraver" }
}
\midi { \tempo 4=60 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
