New manual chapter: Putting it all together
I'm proposing that we add a chapter (to become the new chapter 4) which
demonstrates practical examples of lilypond. For example,
\header{
title = \markup \center-align < "Title first line" "Title second
line, longer" >
subsubtitle = #(string-append "subsubtitle LilyPond version "
(lilypond-version))
composer = \markup \center-align < "composer" \small "(1847-1973)" >
}
All this information is present in the manual somewhere, but beginners
may
have difficulty putting it together. This kind of doc has been
requested
numerous times, and most people who start to write their own lilypond
tutorial want to do this kind of thing. The idea is to have three or
four
complicated but short examples (maybe 20 lines each), with wordy
explanations for each line. Basically, it's an Advanced Tutorial.
Any objections?
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem running lilypond on FC3
Han-Wen Nienhuys wrote: Op di, 26-04-2005 te 09:29 -0400, schreef Stan Mulder: Peter Leschev wrote: Hi, I'm trying to get lilypond 2.5.21 running on FC3. Installed the latest ghostscript, lilypond & lilypond-doc. Running lilypong gives me a seg fault. here's the output of lilypond -V: ./lilypond -V GNU LilyPond 2.5.21 LILYPOND_DATADIR="/usr/share/lilypond/2.5.21" LOCALEDIR="/usr/share/locale" Effective prefix: "/usr/share/lilypond/2.5.21" Segmentation fault Any ideas? I get segmentation faults on 2.5.19 and higher. 2.5.18 works. can you intsall the lilypond-debuginfo RPM (from the same directory of lilypond.org) for the version you're running, and run the same in GDB? gdb /usr/bin/lilypond run -V backtrace and mail me what the backtrace says? thanks, Before I forget, using the rpm upgrade command (rpm -Uvh lilypond...) didn't upgrade lilypond. Instead it installed as a second copy. So I had to remove both copies and install the latest one again. [stan~]$ lilypond GNU LilyPond 2.5.21 Segmentation fault [stan~]$ gdb /usr/bin/lilypond GNU gdb Red Hat Linux (6.1post-1.20040607.43rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run -V Starting program: /usr/bin/lilypond -V [Thread debugging using libthread_db enabled] [New Thread -1208071456 (LWP 6201)] GNU LilyPond 2.5.21 LILYPOND_DATADIR="/usr/share/lilypond/2.5.21" LOCALEDIR="/usr/share/locale" Effective prefix: "/usr/share/lilypond/2.5.21" Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208071456 (LWP 6201)] 0x00afa21e in scm_mark_subr_table () from /usr/lib/libguile.so.12 (gdb) backtrace #0 0x00afa21e in scm_mark_subr_table () from /usr/lib/libguile.so.12 #1 0x00ad6245 in scm_igc () from /usr/lib/libguile.so.12 #2 0x00ad6363 in scm_igc () from /usr/lib/libguile.so.12 #3 0x00ad6428 in scm_must_realloc () from /usr/lib/libguile.so.12 #4 0x00af9fe6 in scm_c_make_subr () from /usr/lib/libguile.so.12 #5 0x00ae06c3 in scm_init_goops () from /usr/lib/libguile.so.12 #6 0x082180ff in Tuplet_bracket_print_init_functions () at tuplet-bracket.cc:96 #7 0x0814b1a3 in ly_init_ly_module () at array.hh:152 #8 0x00ad3688 in scm_c_with_fluids () from /usr/lib/libguile.so.12 #9 0x00ad377d in scm_c_with_fluid () from /usr/lib/libguile.so.12 #10 0x00ae9018 in scm_c_call_with_current_module () from /usr/lib/libguile.so.12 #11 0x00ae9162 in scm_c_define_module () from /usr/lib/libguile.so.12 #12 0x081495cb in ly_c_init_guile () at lily-guile.cc:214 #13 0x08164349 in main_with_guile () at main.cc:383 #14 0x00ae40d3 in scm_boot_guile () from /usr/lib/libguile.so.12 #15 0x08166bd3 in main (argc=2, argv=0xb944) at main.cc:554 (gdb) ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: mensural notation
Hi, Pal!
On Wed, 20 Apr 2005, Pal Benko wrote:
Hi all,
attached is a patch with changed mensural noteheads.
...
fet_beginchar("Mensural open head","s0mensural")
- draw_diamond_head (staff_space#, 0.15, 0.30, 30, true);
+% draw_diamond_head (1.8 staff_space#, 0.15, 0.40, 30, true);
+ draw_neomensural_open_head (staff_space#, 1.8 staff_space#);
fet_endchar;
fet_beginchar("Mensural open head","s1mensural")
- draw_diamond_head (staff_space#, 0.15, 0.30, 30, true);
+% draw_diamond_head (1.8 staff_space#, 0.15, 0.40, 30, true);
+ draw_neomensural_open_head (staff_space#, 1.8 staff_space#);
fet_endchar;
fet_beginchar("Mensural black head","s2mensural")
- draw_diamond_head (staff_space#, 0.15, 0.30, 30, false);
+% draw_diamond_head (1.8 staff_space#, 0.15, 0.40, 30, false);
+ draw_neomensural_black_head (staff_space#, 1.8 staff_space#);
fet_endchar;
What I do not understand, if you want neo-mensural noteheads, why not just
doing "\override Voice.NoteHead #'style = #'neomensural"?
Some problems:
1. MensuralStaff sort of ceased to work for me - or, rather,
I was using it inaccurately. Roughly I wrote
\score {
\context MensuralStaff {
% notes here
}
}
But since last week this doesn't work.
Ok, I will look into this.
2. I'd like to make punctus divisionis work as a new bar symbol,
\bar ".". But for correct positioning I need in
Bar_line::compound_barline the previous and the next note - how
can I get them (if I can at all)?
Maybe in the bar engraver, you can do something similar to what the
ligature engraver does: listening for note heads (but not eating it up
as the ligature engraver does), remembering the pitch of the last seen
one, and when a bar is created, putting the pitch as a grob value into the
bar grob, and doing similar for the pending next note's pitch. You
probably should discuss this with Han-Wen or Jan.
3. I hacked Mensural_ligature a bit so that now I don't have
those spurious warnings for flexa shapes and I have horizontal
positioning of dots all right.
Great to hear!
I want to have correct vertical
positions; in Mensural_ligature I can calculate the correct
position, but I don't know how to propagate this information
(and in fact I don't really know where to propagate it, but I
guess it's Dot_column or Dot_column_engraver).
See Han-Wen's reply.
Greetings,
JÃrgen
thanks,
Pal
Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a
FreeStarttol.
Probald ki most! http://www.freestart.hu
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: mensural notation: patch, question, plan
Hi, Benko!
I have finally (sorry for the extremely long delay!) applied your patch,
slightly modified, for using a constant thickness of horizontal lines in
flexa shapes (rather than using the thickness property). I still feel
somewhat uncomfortable with this solution, as the property thickness now
applies to the vertical lines only, while the horizontal lines are of
hard-wired constant thickness. Though, I realize that there are
notational examples where you want to have different thicknesses.
Greetings,
Juergen
On Sun, 27 Feb 2005, Pal Benko wrote:
2005-02-27 Pal Benko <[EMAIL PROTECTED]>
* lily/mensural-ligature.cc (brew_flexa):
make flexa parts of ligatures look more similar to square parts
* lily/include/mensural-ligature.hh: explanatory comments
Hi Jürgen (and all),
I've played a bit with flexa shape within a ligature;
this is in the attached patch.
I began experimenting with punctus divisionis as a new type of barline.
My first try was introducing one new type ("."),
but then I couldn't position it.
Is there a way of accessing the previous note in the barline code?
Then I'd know where to move the dot.
The second try was introducing a default case:
the glyph string is interpreted as a number,
and the dot is moved accordingly.
I have two problems with this:
I couldn't hack default-break-barline in output-lib.scm
(I know almost nothing of Lisp and nothing else about scheme),
so I get a warning for all puncti divisionis,
and I have a big space between the previous note and the dot.
Can I control that space somehow?
I reviewed the facsimiles I have, and found that
- a punctus divisionis can be at the end of a line
(and then the next line begins as if nothing happened),
so it can really be implemented as a new type of barline;
- augmenting dots within ligatures are generally placed after the note,
except first notes of flexae, which have it above.
I'll try to sort out this issue next.
Thanks,
Pál
Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a
FreeStarttol.
Probald ki most! http://www.freestart.hu
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ./ChangeLog Documentation/user/instrum...
Sorry, should now be more clearly separated: 2005-04-28 Pal Benko <[EMAIL PROTECTED]> * lily/mensural-ligature.cc (brew_flexa): apply thickness property only on vertical lines of flexa shape, and use a constant thickness value for horizontal lines (patch slightly modified by JÃrgen Reuter) * lily/include/mensural-ligature.hh: make 2 comments clearer 2005-04-28 JÃrgen Reuter <[EMAIL PROTECTED]> * lily/vaticana-ligature-engraver.cc (need_extra_space): renamed to need_extra_horizontal_space; bugfix: use class scope to avoid global namespace pollution * Documentation/user/instrument-notation.itely (ligatures): added comment on possible future syntax change and how to work around * lily/vaticana-ligature-engraver.cc, mf/parmesan-heads.mf (epiphonus, cephalicus): fine-tune shape of plica head for narrow intervals (fixes agnus dei example) * Documentation/user/instrument-notation.itely (white mensural ligatures): selected a more illustrative example Greetings, JÃrgen On Thu, 28 Apr 2005, Han-Wen Nienhuys wrote: Op wo, 27-04-2005 te 19:45 -0400, schreef JÃrgen Reuter: CVSROOT:/cvsroot/lilypond Module name:lilypond Branch: Changes by: Jrgen Reuter <[EMAIL PROTECTED]> 05/04/27 23:45:43 Modified files: . : ChangeLog Documentation/user: instrument-notation.itely lily : mensural-ligature.cc vaticana-ligature-engraver.cc lily/include : mensural-ligature.hh mf : parmesan-heads.mf Log message: * lily/vaticana-ligature-engraver.cc (need_extra_space): renamed to need_extra_horizontal_space; bugfix: use class scope to avoid global namespace pollution * Documentation/user/instrument-notation.itely (ligatures): added comment on possible future syntax change and how to work around * lily/vaticana-ligature-engraver.cc, mf/parmesan-heads.mf (epiphonus, cephalicus): fine-tune shape of plica head for narrow intervals (fixes agnus dei example) * lily/include/mensural-ligature.hh: make comments clearer * lily/mensural-ligature.cc: line thickness of flexa shape (originally by Pal Benko; slightly modified) * Documentation/user/instrument-notation.itely (white mensural ligatures): selected a more illustrative example Am I correct that this is actually Pal Benko's patch? If yes, can you clearly mark that as such in the ChangeLog? We want to be able to track backwards the copyright status of each file. thanks, ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem running lilypond on FC3
Op di, 26-04-2005 te 09:29 -0400, schreef Stan Mulder: > Peter Leschev wrote: > > > Hi, > > > > I'm trying to get lilypond 2.5.21 running on FC3. > > Installed the latest ghostscript, lilypond & lilypond-doc. > > > > Running lilypong gives me a seg fault. > > > > here's the output of lilypond -V: > > > > ./lilypond -V > > GNU LilyPond 2.5.21 > > > > LILYPOND_DATADIR="/usr/share/lilypond/2.5.21" > > LOCALEDIR="/usr/share/locale" > > > > Effective prefix: "/usr/share/lilypond/2.5.21" > > Segmentation fault > > > > > > Any ideas? > > I get segmentation faults on 2.5.19 and higher. 2.5.18 works. > can you intsall the lilypond-debuginfo RPM (from the same directory of lilypond.org) for the version you're running, and run the same in GDB? gdb /usr/bin/lilypond run -V backtrace and mail me what the backtrace says? thanks, -- Han-Wen Nienhuys - [EMAIL PROTECTED] LilyPond Software Design - http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ./ChangeLog Documentation/user/instrum...
Op wo, 27-04-2005 te 19:45 -0400, schreef JÃrgen Reuter: > CVSROOT: /cvsroot/lilypond > Module name: lilypond > Branch: > Changes by: Jrgen Reuter <[EMAIL PROTECTED]>05/04/27 23:45:43 > > Modified files: > . : ChangeLog > Documentation/user: instrument-notation.itely > lily : mensural-ligature.cc >vaticana-ligature-engraver.cc > lily/include : mensural-ligature.hh > mf : parmesan-heads.mf > > Log message: > * lily/vaticana-ligature-engraver.cc (need_extra_space): renamed > to need_extra_horizontal_space; bugfix: use class scope to avoid > global namespace pollution > > * Documentation/user/instrument-notation.itely (ligatures): added > comment on possible future syntax change and how to work around > > * lily/vaticana-ligature-engraver.cc, mf/parmesan-heads.mf > (epiphonus, cephalicus): fine-tune shape of plica head for narrow > intervals (fixes agnus dei example) > > * lily/include/mensural-ligature.hh: make comments clearer > > * lily/mensural-ligature.cc: line thickness of flexa shape > (originally by Pal Benko; slightly modified) > > * Documentation/user/instrument-notation.itely (white mensural > ligatures): selected a more illustrative example Am I correct that this is actually Pal Benko's patch? If yes, can you clearly mark that as such in the ChangeLog? We want to be able to track backwards the copyright status of each file. thanks, -- Han-Wen Nienhuys - [EMAIL PROTECTED] LilyPond Software Design - http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
