Lilypond-2.4.6 for Slackware 10.1
Hello, Precompiled package of Lilypond-2.4.6 for Slackware 10.1 is available at www.linuxpackages.net. Ananda Murthy R S ___ 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: Creating Titles in Docs
Thanks for the bug report, the typo has been corrected.
Rob Vlasaty wrote:
In the Creating Titles section of the documents it says:
\paper {
bookTitleMarkup = \markup {
\fill-line @{
\fromproperty #'header:title
\fromproperty #'header:composer
@}
}
}
When I copied and pasted this to my file, lilypond stopped at the "@", saying expected
"{". After I removed the @'s it worked ok using 2.5.31 on Windows. Should the @'s be
removed from the documentation?
I'm only learning about markups and scheme functions, and it's pretty slow
going. I've programmed in C++, Fortran, and even assembly languages, but I
find this really tough. I guess that's because there seem to be a lot of
key-words, and I don't know where most of them come from.
For markup, you can find a complete list of functions in Section
"8.1.7 Overview of text markup commands". For Scheme, you would need
some documentation of the basic language (I survive quite well with the
standard document found at
http://www.schemers.org/Documents/Standards/R5RS/ but I knew other LISP
dialects before). Then, you can read in Chapter "11 Interfaces for
programmers" of the LilyPond manual for the LilyPond specifics and
finally browse your way Lilypond Documentation -> Program Reference
-> Scheme functions to get a complete(?) list of additional Scheme
functions available in LilyPond. You should also search the mailing
list archives for emails from Nicolas Sceaux, who has done lots of the
Scheme interface hacking and has provided several useful examples.
/Mats
Rob
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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: piano right hand with chorded eigths beneath a half
> Daniel Johnson wrote:
>
>>r4 c4 ~ << c2 \\ {r8 8 r8 8} >>
>>
>>
>>
> hmm. On second thought, the tie between the C's probably won't work
> here. << \\ >> by default generates new voices, and you can't do
> cross-voice ties. BUT, you can specify voice-names. So the following
> would (theoretically) work:
>
> \context Voice = rightHand r4 c4 ~ << \context Voice = rightHand c2 \\
> {r8 8 r8 8} >>
>
Easier would be to add silent notes:
r4 << {c4 ~ c2} \\ {s4 r8 r } >>
(beware, I haven't tested it ;)
Kristof
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: piano right hand with chorded eigths beneath a half
An alternative, which might be at least as easy to use is to
skip the \\ feature and manually specify where you want an
additional voice and where you want stems up or down.
Such an example is provided in Section "6.6.2 Explicitly instantiating
voices" in the manual for version 2.5.xx.
/Mats
Daniel Johnson wrote:
Daniel Johnson wrote:
r4 c4 ~ << c2 \\ {r8 8 r8 8} >>
hmm. On second thought, the tie between the C's probably won't work
here. << \\ >> by default generates new voices, and you can't do
cross-voice ties. BUT, you can specify voice-names. So the following
would (theoretically) work:
\context Voice = rightHand r4 c4 ~ << \context Voice = rightHand c2 \\
{r8 8 r8 8} >>
<< \\ >> generates a \context Voice = "1" and \context Voice = "2" by
default. But if you specify one of the voices to be the same as the
voice *outside* the double-angle-brackets, then you can perform the tie,
since both tied notes are in the same voice.
Make sense?
--Daniel
P.S. This same trick is useful in vocal scores, when you are binding
lyrics to a voice. Since by default << \\ >> generates new voices, your
lyrics will not bind to the notes inside the double-angle-brackets. But
if you specify one of the voices inside the << \\ >> to be the same as
the voice outside it, the lyrics flow just fine. Here's an example:
text = \lyricmode { La Ti Do }
\score {
<<
\context Staff = sopStaff {
\context Voice = sopVoice {
a2 << \context Voice = sopVoice b2 \\ {g4( f)} >> | 1
}
}
\context Lyrics = sopLyrics \lyricsto sopVoice \text
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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
4 line stave
Dear LilyPonders, I have been looking for music typesetting software that I can use for plainsong using square notes and a four line stave, with the plainsong modal key signatures. I don't suppose LilyPond can do this now, but are there any plans for developing it - it would look lovely!! Thanks, Mark Brown ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 4 line stave
You mean something like the example called ligature-vaticana.ly found at http://lilypond.org/doc/v2.4/input/test/out-www/collated-files.html ? /Mats Mark Brown wrote: Dear LilyPonders, I have been looking for music typesetting software that I can use for plainsong using square notes and a four line stave, with the plainsong modal key signatures. I don't suppose LilyPond can do this now, but are there any plans for developing it - it would look lovely!! Thanks, Mark Brown ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology 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: Extending beamed stems
Your suggested solution seems to be the way to do it. I tried it quickly, but
the NoteColumn #'force-hshift didn't do anything. Now, that may be because I am
not using the 2.5 yet and i didn't start looking in the manual for a way to
achieve this in 2.4. I will upgrade and try again and in any event, you have
pointed me in the right direction, and I am sure i will be able to find out. I
am still curious to find out why the Voice.Beam #'X-extent and Voice.Beam
#'extra-offset doesn't have any effect. This was what I tried at first. Anybody
knows why me and Daniel are unsuccessful in getting the desired effect?
Daniel Johnson <[EMAIL PROTECTED]> wrote:
> Hmm. This is a real puzzler, because even though the Beam object
> implements the grob-interface, only certain grob properties have any
> effect. Specifically, I tried the following on a small test file and
> they did nothing:
>
> \once \override Voice.Beam #'X-extent = #'(0 . 15)
> \once \override Voice.Beam #'extra-X-extent = #'(0 . 15)
>
> Oddly enough, the following DID have an effect:
> \once \override Voice.Beam #'extra-offset = #'(0 . 15)
> but of course I can't really imagine any use for this.
>
> Here's an idea:
>
> 1. Just beam from the first three notes over to the high G-flat.
> 2. On the D in the left hand, do a \once \override Voice.Stem
> #'flag-style = #'no-flag, and do a \stemUp.
> 3. On the D in the left hand, do a \once \override NoteColumn
> #'force-hshift = #-1. Adjust this value until the stem is aligned
> perfectly with the stem of the note in the right hand.
> 4. On the D in the left hand, do a \once \override Voice.Stem #'length =
> #12 or however long it needs to be to meet up with the beam.
>
> I did my research out of the 2.5 manual, so your mileage may vary; but I
> don't think there's anything especially late-breaking about any of the
> features I used above. The noteheads of the eighth-notes in the left &
> right hands won't be horizontally aligned, but their stems will meet the
> beam in the same place. Is that acceptable?
>
> --Daniel
>
> Henrik Frisk wrote:
>
> >I'm running lilypond 2.4.5 (fink installation) on OSX 10.3.9. Attached to
> >this mail is an example. Although this bar works OK the way it is, I would
> >have liked to beam it 1/4+1/8 rather than 1/8+1/8+1/8. Either by connecting
> >the lower beam of the first 1/8 note group to the stem of the second eighth
> >note (from a notation point of view this would be unorthodox since one of
> >the note heads would end up on the wrong side of the stem). The other way
> >would be to have the beam go below all notes on beat one and two (counting
> >eihgth notes).
> >
> >Here's the code for the bar:
> >
> > \time 3/8
> > ges'''16~[ \revert Beam #'positions ges64 \change Staff=lower f,32. ]
> > \change Staff=upper \stemExtend \noFlag ges'8-> \noBeam
> > \acciaccatura { g32^\pedalc } \change Staff = lower b,,,32 [ \change Staff
> > = upper f''~ f16~ ] |
> >
> >And here are the \noFlag and \stemExtend:
> >
> >noFlag = \once \override Stem #'flag-style = #'no-flag
> >stemExtend = \once \override Stem #'length = #32
> >
> >...and attached is an image.
> >
> >This is the first piece I do in LilyPond, so I'm not very experienced yet.
> >Tahnks for any help.
> >
> >/henrik
> >
> >
> >
> >
> >
> >
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extending beamed stems
Watch out when upgrading from 2.4 to 2.5 if you use lots of TeX markup (and it looks like you might, to achieve your /pedalc markup). Since 2.5 does not use TeX as a backend by default, you'll have to recode this stuff using standard markup. Version 2.5 writes PostScript directly without processing as TeX first. --Daniel Henrik Frisk wrote: >Your suggested solution seems to be the way to do it. I tried it quickly, but >the NoteColumn #'force-hshift didn't do anything. Now, that may be because I >am not using the 2.5 yet and i didn't start looking in the manual for a way to >achieve this in 2.4. I will upgrade and try again and in any event, you have >pointed me in the right direction, and I am sure i will be able to find out. I >am still curious to find out why the Voice.Beam #'X-extent and Voice.Beam >#'extra-offset doesn't have any effect. This was what I tried at first. >Anybody knows why me and Daniel are unsuccessful in getting the desired effect? > >Daniel Johnson <[EMAIL PROTECTED]> wrote: > > > >>Hmm. This is a real puzzler, because even though the Beam object >>implements the grob-interface, only certain grob properties have any >>effect. Specifically, I tried the following on a small test file and >>they did nothing: >> >>\once \override Voice.Beam #'X-extent = #'(0 . 15) >>\once \override Voice.Beam #'extra-X-extent = #'(0 . 15) >> >>Oddly enough, the following DID have an effect: >>\once \override Voice.Beam #'extra-offset = #'(0 . 15) >>but of course I can't really imagine any use for this. >> >>Here's an idea: >> >>1. Just beam from the first three notes over to the high G-flat. >>2. On the D in the left hand, do a \once \override Voice.Stem >>#'flag-style = #'no-flag, and do a \stemUp. >>3. On the D in the left hand, do a \once \override NoteColumn >>#'force-hshift = #-1. Adjust this value until the stem is aligned >>perfectly with the stem of the note in the right hand. >>4. On the D in the left hand, do a \once \override Voice.Stem #'length = >>#12 or however long it needs to be to meet up with the beam. >> >>I did my research out of the 2.5 manual, so your mileage may vary; but I >>don't think there's anything especially late-breaking about any of the >>features I used above. The noteheads of the eighth-notes in the left & >>right hands won't be horizontally aligned, but their stems will meet the >>beam in the same place. Is that acceptable? >> >>--Daniel >> >>Henrik Frisk wrote: >> >> >> ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lettres accentuées
Bonjour, Je cherche à utiliser des lettres accentuées dans de toutes petites partitions. Je n'ai pas trouvé, sans doute parce que j'ai mal cherché, la solution. Quelqu'un peut-il m'aider ? J'utilise la version 2.5.11 et je crois avoir compris les petits exemples du tutoriel : http://www.lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond/Single-staff.html#Single-staff Merci Jacques ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lettres accentuées
[j-f.stephant] > Je cherche à utiliser des lettres accentuées dans de toutes petites > partitions. Je n'ai pas trouvé, sans doute parce que j'ai mal > cherché, la solution. Quelqu'un peut-il m'aider ? J'utilise la > version 2.5.11 [...] C'est assez bizarre. Tout a toujours fonctionné directement pour moi, sans aucun problème, mais dans la mesure où j'utilise le code ISO-8859-1 (Latin-1) dans mes sources Lilypond (je n'ai pas essayé UTF-8, ni ISO-8859-15, quoique j'imagine que ce dernier devrait probablement fonctionner facilement). Je n'utilise pas une version aussi récente que 2.5.11, toutefois! :-) -- François Pinard http://pinard.progiciels-bpi.ca ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Title of a multi-movement piece of several ly files
Hello,
I created a Palestrina Mass score, each movement (Kyrie, Gloria, Credo,
Sanctus, Benedictus, Agnus I, Agnus II) in an independent file, and I
tried to create a file (missa.ly) to contain them all, using \include
"kyrie.ly" \include "gloria.ly" etc.
The header of missa.ly is:
\header {
title = "Missa Sine nomine"
composer = "Palestrina"
tagline = ""
}
whereas the headers of the individual files are
\header
{
piece="Kyrie"
composer=""
tagline= ""
}
I copied this from a file my brother did with Lilypond 1.6.5, and it
worked there.
I'm using 2.5.31 on Linux, and this does not work, I do not get title,
nor composer, and I get for each movement the piece title of "Agnus Dei
II", i.e. the piece information of the very last file.
How can this be done? I did not find information about this in the
manual, either.
Imruska
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lettres accentuées
"j-f.stephant" <[EMAIL PROTECTED]> writes: > Bonjour, > > Je cherche à utiliser des lettres accentuées dans de toutes petites > partitions. > > Je n'ai pas trouvé, sans doute parce que j'ai mal cherché, la solution. > > Quelqu'un peut-il m'aider ? > > J'utilise la version 2.5.11 et je crois avoir compris les petits > exemples du tutoriel : > http://www.lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond/Single-staff.html#Single-staff Pourriez-vous donner un petit exemple de ce que vous avez essaye, et qui ne fonctionne pas ? et avec quel systeme d'exploitation. A noter qu'il existe des versions plus recentes de LilyPond, il pourrait etre interessant d'essayer avec une 2.5.3X. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lettres accentuées
François Pinard wrote: [j-f.stephant] Je cherche à utiliser des lettres accentuées dans de toutes petites partitions. Je n'ai pas trouvé, sans doute parce que j'ai mal cherché, la solution. Quelqu'un peut-il m'aider ? J'utilise la version 2.5.11 [...] C'est assez bizarre. Tout a toujours fonctionné directement pour moi, sans aucun problème, mais dans la mesure où j'utilise le code ISO-8859-1 (Latin-1) dans mes sources Lilypond (je n'ai pas essayé UTF-8, ni ISO-8859-15, quoique j'imagine que ce dernier devrait probablement fonctionner facilement). Je n'utilise pas une version aussi récente que 2.5.11, toutefois! :-) Si tu utilises UTF-8, je crois que lilypond produira il texte exactement comme il apparais dans il fichier ".ly". Une explication en anglais: http://lists.gnu.org/archive/html/lilypond-user/2005-06/msg00367.html. Je suis désolé, mon francais est mal. J'ai etudié seulement 2 mois. Bonne chance! Kris Shaffer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
