scheme music function going backwards in time (or better mp dolce)
Four years ago, it was impossible to write a music function that
affected the music event it was attached to. (if I understand
this post correctly):
http://lists.gnu.org/archive/html/lilypond-devel/2004-08/msg00019.html
Is this possible now? I'm running into this problem.
I have a scheme function for nicely-spaced dynamic+text marks (ie
mp dolce), but it adds the dynamic to the note *after* it appears
in the score -- to add f legato to the E, I need to write
c \flegato e d c
instead of
c e\flegato d c
Can anybody see a nice solution to this? Omiting the initial
(make-music 'SequentialMusic) puts the dynamic on the right note,
but the OverrideProperty stops working. Writing the dynamic in
front of the note produces good output, but it breaks the lilypond
postfix-ish notation.
Cheers,
- Graham
#(define (make-dynamic-extra dynamic string)
(make-music
'SequentialMusic
'elements
(list
(make-music
'OverrideProperty
'pop-first #t
'grob-property-path (list (quote X-offset))
'once #t
'grob-value -1
'symbol 'DynamicText)
(make-dynamic-script (markup
#:box #:line(
dynamic
#:text string)))
)))
flegato = #(make-dynamic-extra f legato)
\relative c' {
% adds dynamic to the D -- wrong
c e\flegato d c
% adds dynamic to the E -- good output, but code looks bad
c \flegato e d c
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: scheme music function going backwards in time (or better mp dolce)
2008/10/1 Graham Percival [EMAIL PROTECTED]: Is this possible now? I'm running into this problem. Yes, me too. But since I use music functions everywhere, I'm getting used to typing commands before the affected music. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On Tue, Sep 30, 2008 at 3:07 PM, Neil Puttock [EMAIL PROTECTED] wrote: I don't know whether it's something that's broken at my end (I've been getting some weird docs breakages recently), but I've just compiled following your latest changes and the navigation's disappeared. Strange... The new docs on lilypond.org have no navigation bars either. But everything is fine on my computer with a clean compile. The texi2html cvs revision I have is from Sept. 25. -Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
could you point me to doc about first time bar, second time bar, dal capo etc?
Hi, Within the notation manual, could you please give me the link to pages discussing about commands for first time bar, second time bar, da capo and da signo a fine? THanks! Daryna ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On 2008/09/30 3:45 PM, Reinhold Kainhofer [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 1. Oktober 2008 schrieb John Mandereau:
On 2008/09/30 14:04 -0700, Patrick Horgan wrote:
Well done:) I still prefer Patrick's style and wish it were the
default.
+1
Okay, it seems we are the majority ;-) I've now switched the two style sheets,
so that Patrick's style is now the default and Andrew's style is the
alternative css.
I've not changed their filenames, so before the release we should probably
straighten this out and move the default style to lilypond.css
-1, but I've got mad enough skillz to make a user style sheet. That way, I
can make it look however I please.
I have attached my current user style sheet, to be applied in lieu of
Patrick's styles (in case anyone's interested).
Kurtis
whose mantra is I am *not* a representative user
/**/
/* PAGE-WIDE SETTINGS*/
/**/
html {
height: 100%;
}
body {
background-color: white;
color: black;
font-size: 80%;
height: 100%;
line-height: 1.25em;
margin: 0 auto;
padding: 0;
}
/***/
/* HEADERS*/
/***/
.chapter, .section, .subsection,
.appendix, .appendixsec, .appendixsubsec,
.unnumberedsubsubsec, .subsubheading,
.unnumbered, .subheading {
border-bottom: 1px dashed black;
color: #204a87;
padding-bottom: 0.4em;
margin-bottom: 1em;
margin-top: 1em;
}
.settitle {
background-color: #eef;
border-bottom: 1px solid #3465A4;
font-size: 2em;
margin: 0.25em 0 0 0;
padding: 0.75em;
text-align: center;
}
.chapter {
font-size: 1.8em;
}
.section {
font-size: 1.6em;
}
.subsection {
font-size: 1.4em;
}
.unnumberedsubsubsec {
font-size: 1.25em;
}
.subsubheading {
font-size: 1em;
font-weight: bold;
}
/***/
/* LINKS */
/***/
a:link {
/* color: #4169e1; */
/* color: #3555b6; */
color: #3465a4;
}
a:visited {
color: #8f5902;
}
a:hover {
color: #ce5c00;
}
a:active {
color: #73d216;
}
/***/
/* BLOCK FORMATTING */
/***/
blockquote {
border: thin solid #3465a4;
border-width: 0 0 0 2px;
margin: 1em 0 1em 3em;
padding: 0;
}
blockquote p {
margin: 0;
padding: 1em;
}
blockquote blockquote {
border: thick red dashed;
}
.verbatim, .example .example, .lisp {
font-size: 1em;
margin: 0;
padding: 1em;
}
.example {
padding: 0;
margin: 0;
}
hr {
height: 0;
padding: 0;
border: 0;
margin: 0;
text-indent: -999em;
}
table.cartouche {
background: #eee;
border: 1px solid #3465a4;
border-width: 1px 0;
width: 85%;
padding: 0 0.5em;
margin: 0 auto;
}
table.cartouche p {
padding: 1em;
margin: 0;
}
table.cartouche td {
border: none;
}
/***/
/*MAIN CONTENT */
/***/
div#main {
position: absolute;
top: 0;
right: 0;
bottom: 0;
left: 27%;
padding: 0;
margin: 0;
overflow: auto;
}
div#main li {
padding: 0 1em 0.5em 0;
}
div#main ul {
margin: 0;
}
h1, h2, h3, h4, p, table, address, dt {
padding-left: 1em;
padding-right: 1em;
}
p {
margin: 1em 0;
}
#languages {
margin: 0;
padding: 1em;
}
pre.menu-comment {
font-size: 1em;
padding-top: 1em;
padding-bottom: 0;
margin: 0;
}
/***/
/*TOC SIDEBAR */
/***/
div#tocframe {
position: absolute;
top: 0;
right: 73%;
bottom: 0;
left: 0;
padding: 0;
margin: 0;
overflow: auto;
background-color: #f9f9ff;
z-index: 100;
list-style-type: none;
font-size: 0.83em;
line-height: 1.4em;
}
/* position: fixed for savvy browsers */
@media screen {
body div#tocframe {
position: fixed
}
}
/*
#tocframe a:link, #tocframe a:visited {
text-decoration: none;
}
#tocframe a:hover {
text-decoration: underline;
}
*/
div#tocframe h4 {
font-size: 1.2em;
font-weight: normal;
color: #344;
background-color: #eef;
padding: 2px 0 1px 1em;
border-bottom: 1px solid #3465A4;
margin: 0;
}
#tocframe .contents {
background-color: transparent;
list-style-type: none;
padding: 0;
border: 0;
margin: 0;
}
#tocframe ul.toc {
padding: 1em 0.5em;
list-style-type: none;
margin: 0;
}
#tocframe ul.toc
Re: could you point me to doc about first time bar, second time bar, dal capo etc?
Hy Daryna, Within the notation manual, could you please give me the link to pages discussing about commands for first time bar, second time bar http://lilypond.org/doc/v2.11/Documentation/user/lilypond/ Repeats#Repeats da capo and da signo a fine? http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Text- marks#Text-marks HTH! Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: scheme music function going backwards in time (or better mp dolce)
Hi Graham, I have a scheme function for nicely-spaced dynamic+text marks (ie mp dolce), but it adds the dynamic to the note *after* it appears in the score -- to add f legato to the E, I need to write c \flegato e d c instead of c e\flegato d c Can anybody see a nice solution to this? Omiting the initial (make-music 'SequentialMusic) puts the dynamic on the right note, but the OverrideProperty stops working. Writing the dynamic in front of the note produces good output, but it breaks the lilypond postfix-ish notation. I use flegato = #(make-dynamic-script (markup #:hspace 0 #:raise -1 #:line(#:dynamic f #:hspace -0.3 #:normal-text #:italic legato ))) and tweak the spacing — it ain't a nice solution, but it works. Hopefully, one of the responses to your post will *really* fix the problem! Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: todays git segfaults [backtrace]
I ran your file with the same results (built Lilypond yesterday from git source). I'm on Ubuntu Linux 8.04 if that makes a difference. Jon Wilbert Berendsen wrote: Hi, I updated my LilyPond today, it built fine but it segfaults on some file (while working perfect on others). I attach the file and here is the backtrace. The crash is in the instrument name code. When I comment line 189 in the ly file, to remove the instrument name engraver from the choirstaff, LilyPond does not segfault. -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: todays git segfaults [backtrace]
I ran the same file on two other machines, and it failed the same way with 2.11.59 but ran successfully on 2.11.57. Jon Wilbert Berendsen wrote: Hi, I updated my LilyPond today, it built fine but it segfaults on some file (while working perfect on others). I attach the file and here is the backtrace. The crash is in the instrument name code. When I comment line 189 in the ly file, to remove the instrument name engraver from the choirstaff, LilyPond does not segfault. 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
Re: todays git segfaults [backtrace]
Op woensdag 1 oktober 2008, schreef Jonathan Kulp: I ran the same file on two other machines, and it failed the same way with 2.11.59 but ran successfully on 2.11.57. I upgraded from 2.11.58, so the regression might be somewhere in 2.11.59. best regards, Wilbert Berendsen -- LilyKDE, LilyPond for KDE: http://lilykde.googlecode.com/ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: todays git segfaults [backtrace]
Op woensdag 1 oktober 2008, schreef Wilbert Berendsen:
I upgraded from 2.11.58, so the regression might be somewhere in 2.11.59.
I investigated somewhat further: The crash in today's git occurs when I use
(as in the file I sent):
\score {
\new ChoirStaff \with {
\consists Instrument_name_engraver
} ...
but not when I add the Instrument_name_engraver in the layout section, like:
\layout {
\context {
\ChoirStaff
\consists Instrument_name_engraver
}
}
best regards,
Wilbert Berendsen
--
LilyKDE, LilyPond for KDE: http://lilykde.googlecode.com/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Lyric tie glyph not found (directory separator problem?)
Hi, Something strange just happened. I tried to use the lyric tie (~) in one song and LP complained that it couldn't find the glyph. These kind on messages usually appeared when the file wasn't saved as UTF but this time the same file works on my work computer (don't tell my boss). The directory separators seem to be / instead of \. That could be the reason why LP / Pango / whatever cannot find the file. If that's the next question is why have the separators changed in the first place. I'm using XP Pro SP3 on a MacBook. Does anyone else run LP on Boot Camped Mac? Any problems? -Risto GNU LilyPond 2.11.61 Processing `lyric_tilde.ly' Parsing... Interpreting music... Preprocessing graphical objects... programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000203F, file C:/Program Files/LilyPond_2.11.61/usr/share/ lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000203F, file C:/Program Files/LilyPond_2.11.61/usr/share/ lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000203F, file C:/Program Files/LilyPond_2.11.61/usr/share/ lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `lyric_tilde.ps'... Converting to `./lyric_tilde.pdf'... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: todays git segfaults [backtrace]
2008/10/1 Jonathan Kulp [EMAIL PROTECTED]: I ran your file with the same results (built Lilypond yesterday from git source). I'm on Ubuntu Linux 8.04 if that makes a difference. This file compiles successfully on Linux64 with a 5-days-old git. I removed the rest-merging function, by the way. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On Tue, Sep 30, 2008 at 11:53 PM, Kurt Kroon [EMAIL PROTECTED] wrote: -1, but I've got mad enough skillz to make a user style sheet. That way, I can make it look however I please. I have attached my current user style sheet, to be applied in lieu of Patrick's styles (in case anyone's interested). Kurtis whose mantra is I am *not* a representative user Hi Kurt, Thanks for responding. I wish you would have contributed earlier. ;-) I like your stylesheet, in general. But I think some of the font sizes you are using will render parts of the documentation illegible on certain platforms (such as in the TOC). I like your choice of color especially. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: todays git segfaults [backtrace]
On Wed, Oct 1, 2008 at 8:20 AM, Valentin Villenave [EMAIL PROTECTED] wrote: This file compiles successfully on Linux64 with a 5-days-old git. I removed the rest-merging function, by the way. Same here, with the latest git. I removed the function you mentioned and the included file, and it compiled fine for me. -Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Patrick, if you add a line-height: 1.125em; to the .settitle section it fixes the strange overlap on small windows. The one it inherits from the body section uses a different em, and although you specify it in ems, it's inherited in pixels. Or in CSS speak, you don't inherit the specified value, but the computed value. (See the CSS2 spec section 6.1.1 below. Or, you could just take it out of the body section, but definitely it looks better with it. Here's part of the CSS2 spec that explains it and more (trying to whet your interest so that you'll go to w3c and get your own copy of the spec;) 6.1.1 Specified values User agents must first assign a specified value to each property based on the following mechanisms (in order of precedence): 1. If the cascade [p. 94] results in a value, use it. 2. Otherwise, if the property is inherited [p. 92] and the element is not the root of the document tree, use the computed value of the parent element. 3. Otherwise use the property’s initial value. The initial value of each property is indicated in the property’s definition. 6.1.2 Computed values Specified values are resolved to computed values during the cascade; for example URIs are made absolute and ’em’ and ’ex’ units are computed to pixel or absolute lengths. Computing a value never requires the user agent to render the document. The computed value of URIs that the UA cannot resolve to absolute URIs is the specified value. When the specified value is not ’inherit’, the computed value of a property is determined as specified by the Computed Value line in the definition of the property. See the section on inheritance [p. 92] for the definition of computed values when the specified value is ’inherit’. The computed value exists even when the property doesn’t apply, as defined by the ’Applies To’ [p. 25] line. However, some properties may define the computed value of a property for an element to depend on whether the property applies to that element. 6.1.3 Used values Computed values are processed as far as possible without formatting the document. Some values, however, can only be determined when the document is being laid out. For example, if the width of an element is set to be a certain percentage of its containing block, the width cannot be determined until the width of the containing block has been determined. The used value is the result of taking the computed value and resolving any remaining dependencies into an absolute value. 6.1.4 Actual values A used value is in principle the value used for rendering, but a user agent may not be able to make use of the value in a given environment. For example, a user agent may only be able to render borders with integer pixel widths and may therefore have to approximate the computed width, or the user agent may be forced to use only black and white shades instead of full colour. The actual value is the used value after any approximations have been applied. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Patrick McCarty wrote: I like your stylesheet, in general. But I think some of the font sizes you are using will render parts of the documentation illegible on certain platforms (such as in the TOC). I like your choice of color especially. I know that most of this is personal, but I looked at it and still prefer the choice of color in Patrick's except I'd still like more contrast in the sidebar. It's amazing how nice the different left margin in the blockquote section looks. I wouldn't have thought of that. (But of course I will now, in CSS gratitude is shown by appropriation! ;) Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
2008/9/30 Reinhold Kainhofer [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Mittwoch, 1. Oktober 2008 schrieb Neil Puttock: I don't know whether it's something that's broken at my end (I've been getting some weird docs breakages recently), but I've just compiled following your latest changes and the navigation's disappeared. Update texi2html to the latest CVS version. Patrice changed the API of some functions... Cheers, that's fixed it. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Am Mittwoch, 1. Oktober 2008 schrieb Kurt Kroon: I have attached my current user style sheet, to be applied in lieu of Patrick's styles (in case anyone's interested). I've now added your CSS as another alternative style sheet so that everyone can have a look at it and judge the different styles. Cheers, Reinhold -- -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung Jung-Wien, http://www.jung-wien.at/ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: todays git segfaults [backtrace]
Op woensdag 1 oktober 2008, schreef Patrick McCarty:
Same here, with the latest git. I removed the function you mentioned
and the included file, and it compiled fine for me.
Now I removed the merge-rests function and include, but even then LilyPond
(git as of today) segfaults (signal 11, with the same backtrace).
Attachting the .ly file again just to be sure...
best regards,
Wilbert Berendsen
--
LilyKDE, LilyPond for KDE: http://lilykde.googlecode.com/
\version 2.11.61
#(set-global-staff-size 18)
\header {
title = 3. Die Könige
subtitle = from “Weihnachtslieder” op. 8
composer = Peter Cornelius (1824-1874)
poet = \markup \column {
\line { Peter Cornelius (1824-1874) }
\line { Text and melody “Wie schön leuchtet der Morgenstern” (1599) }
\line { by Philipp Nicolai (1556-1608) }
}
copyright = \markup {
\center-column {
\line {
Arranged and engraved by
\with-url #http://www.wilbertberendsen.nl/; {
Wilbert Berendsen (http://www.wilbertberendsen.nl/)
}
}
\line {
Copyright © 2008
\with-url #http://www.cpdl.org/; {
The Choral Public Domain Library (http://www.cpdl.org/)
}
}
\line {This edition may be freely distributed, edited, performed or recorded.}
\null
}
}
}
global = {
\key g \major
\time 3/4
\partial 4.
#(set-accidental-style 'modern)
}
\paper {
ragged-last-bottom = ##f
between-system-padding = #0
}
soloVoice = \relative c' {
\global
\dynamicUp
% Muziek volgt hier.
d8\p b' fis |
a(g) b, c e8. d16 |
\time 4/4
d4 r8 d g a b a16 g |
g8 c g4 r8 g b c |
d b16 a g8 fis16 g e8 b'4 a8 |
g a b ais16 b d8 cis16(b) a4 |
r8 a gis a c a b a16 g |
c8 g b a16(g) e8(fis) g d |
\time 2/4
e8 fis16(e) d4
\time 3/4
r4 r8
d8 b' fis |
a(g) b, c e8. d16 |
\time 4/4
d4 r8 d g a b a16 g |
g8 c g4 r8 g b c |
d b16 a g8 fis16(g) e8 b' b a8 |
g(a) b ais16(b) d8 cis16(b) a4 |
r8 a gis a c a b a16 g |
c8 g b a16(g) e8(fis g) d |
e8 fis16(e) d4~d8 r8 r4 |
r4 r8 d b'8. c16 b4 |
g8 fis e g fis2 |
r8 d c'8. a16 e'8(d) b(g) |
r8 g g e b'2 |
r8^\markup\italicun poco piú mosso c b g e fis16 e dis8 e |
fis c' b a16 g e8 fis16 e dis8 e fis fis c' b a g16(e)
d8^\markup\italicrit. d'16 c |
b4^\markup\italica tempo b8 a16 g d'8(b) g(fis) |
e fis16(g) d4 r2
e4\p d8. d16 b'2\fermata
\bar|.
}
verseSoloVoice = \lyricmode {
% Liedtekst volgt hier.
Drei Kön’ -- ge wan -- dern aus Mor -- gen -- land;
ein Stern -- lein führt sie zum Jor -- dan -- strand.
In Ju -- da fra -- gen und for -- schen die drei, wo der
neu -- ge -- bo -- re -- ne Kö -- nig_ sei?
Sie wol -- len Weih -- rauch, Myr -- rhen und Gold
dem Kin -- de __ spen -- den zum Op -- fer -- sold.
Und hell er -- glän -- zet des Ster -- nes Schein,
zum Stal -- le ge -- hen die Kön’ -- ge ein;
das Knäb -- lein schau -- en sie won -- nig -- lich,
an -- be -- tend nei -- gen die __ Kön’ -- ge __ sich;
sie brin -- gen Weih -- rauch, Myr -- rhen und Gold
zum Op -- fer __ dar __ dem Knäb -- lein hold. __
O Men -- schen -- kind! hal -- te treu -- lich Schritt!
Die Kön’ -- ge wan -- dern, o wand -- re mit!
Der Stern der Lie -- be, der Gna -- de Stern,
er -- hel -- le dein Ziel, so du suchst den Herrn,
und feh -- len Weih -- rauch, Myr -- rhen und Gold,
schen -- ke dein Herz __ dem __ Knäb -- lein hold!
schenk ihm dein Herz!
}
soprano = \relative c'' {
\global
\dynamicUp
% Muziek volgt hier.
r8 r4 r r
g\p d' b g d' e e d2 r4 d e fis g fis e e d2 r4 b e d c b a2 g
r4 r r
g d' b g d' e e d2 r4 d e fis g fis e e d2 r4 b e d c b a2 g
d' b R1 d2 b R1 c4 b a b c b a b c c8(b) a2 g\
g8\f(g'4) fis8~fis e4 d\ c b8 a2\p g\fermata
}
alto = \relative c' {
\global
% Muziek volgt hier.
r8 r4 r r
e g fis e g g g g2 r4 g g b b b b a8(g) fis2 r4 g g g g8(fis) g4 g(fis) d2
r4 r r
e g fis e g g g g2 r4 g g b b b b a8(g) fis2 r4 g g g g8(fis) g4 g(fis) d2
fis g R1 fis2 g R1 dis4 e e fis8(e) dis4 e e fis8(e) dis4 e e(d) d(g)
g g g g fis g g(fis) d2
}
tenor = \relative c' {
\global
% Muziek volgt hier.
r8 r4 r r
c b d b g8( d') c4 c b2 r4 d b dis e b d cis d2 r4 d c b a8(d) d4 e(d8 c) b2
r4 r r
c b d b g8( d') c4 c b2 r4 d b dis e b d cis d2 r4 d c b a8(d) d4 e(d8 c) b2
a4(d) d2 b4(cis) d2 c4( a8 d) d2 b4(cis) dis2
fis,4 g e a8(g) fis4 g e a8(g) fis4 g g4.(fis8) g(b cis4)
d d c b d d e(d8 c) b2
}
bass = \relative c' {
\global
\dynamicDown
% Muziek volgt hier.
r8 r4 r r
g\p g, d' e b c c g'2 r4 b g fis e d g a d,2 r4 g c, g' a8(d,)g(b,) c4(d) g2
r4 r r
g g, d' e b c c g'2 r4 b g fis e d g a d,2 r4 g c, g' a8(d,)g(b,) c4(d) g2
d g g4(\e)\ b2\! a4(d) g2 g4(\e)\ b2\!
a4 g c b a g c b a g c(d) g(\e)
b\f b' c g\ a b c8(\p c, d4) g g,2
}
verseChoir = \lyricmode {
% Liedtekst volgt hier.
Wie schön leuch -- tet der Mor -- gen -- stern
voll Gnad und Wahr -- heit von dem Herrn,
die
Re: WANTED: Design for documentation (Photoshop power users!)
But what about the pdf version? I suggest to ignore it for the time being. It hurts myself, but there are so many things necessary to fix so that it becomes a well looking document. I guess, sine it's so much raw tex, changing it may be more troublesome (at least the attempts I made failed), but it would really be good, either just to spice up the layout a little (better distinction between levels of headlines, e.g.), or even better: to bring it in better accordance with the html/css version, such as using colors, borders, etc. It's a texinfo document, and it thus has the limitations of this format. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Take a look at texinfo's texi2pdf. That's how we build it; the program converts texinfo to tex (or maybe latex; I can't remember), and from that to pdf. No, the document gets directly processed by tex. If the built-in customization doesn't do what you want, then your only option is to hack texi2pdf directly. That involves C programming, Not at all. texi2pdf is a simple wrapper for the texi2dvi shell script. The only possibility to customize the look of the PDF is to modify texinfo.tex. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
[solved] Re: todays git segfaults [backtrace]
Op woensdag 1 oktober 2008, schreef Wilbert Berendsen: Now I removed the merge-rests function and include, but even then LilyPond (git as of today) segfaults (signal 11, with the same backtrace). Now I rebuilt LilyPond with --disable-optimising and it does not segfault anymore. I remember having had other issues with the default optimisation on my GCC 4.1.2 (from Gentoo), that cause strange formatting problems. best regards, Wilbert Berendsen -- LilyKDE, LilyPond for KDE: http://lilykde.googlecode.com/ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [solved] Re: todays git segfaults [backtrace]
On Wed, Oct 1, 2008 at 11:07 AM, Wilbert Berendsen [EMAIL PROTECTED] wrote: Op woensdag 1 oktober 2008, schreef Wilbert Berendsen: Now I removed the merge-rests function and include, but even then LilyPond (git as of today) segfaults (signal 11, with the same backtrace). Now I rebuilt LilyPond with --disable-optimising and it does not segfault anymore. I remember having had other issues with the default optimisation on my GCC 4.1.2 (from Gentoo), that cause strange formatting problems. Have you tried GCC 4.3.x without disabling optimization? (I assume this is somewhat straightforward with Gentoo) Regards, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
horizontal spacing questions
Hi.
Given these three bars:
{c c c c | c c c c | c c c c}
with the following output:
o o o o | o o o o | o o o o
--measureLength---
1) I would like to change the notes' spacing inside the second bar in this
way:
o o o o | o o o o | o o o o
--pad-- --pad--
--measureLength---
where pad = measureLength/3 and measureLength remains the same.
2) I would like to change the notes' spacing inside the second bar in this
other way:
o o o o | o o o o | o o o o
A B C D
--measureLength---
where A and D (=notes) have their normal position, while B C form a group with
A which is proportionally compressed with a given scale factor. And measure
length remains the same.
Which is the easiest solution for both problems?
Thanks,
Luca
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [solved] Re: todays git segfaults [backtrace]
2008/10/1 Wilbert Berendsen [EMAIL PROTECTED]: Now I rebuilt LilyPond with --disable-optimising and it does not segfault anymore. I remember having had other issues with the default optimisation on my GCC 4.1.2 (from Gentoo), that cause strange formatting problems. I've just recompiled from today's git (without any particular option), and experience no segfault (it's a 64bits system). Indeed, you might want to update your GCC... Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
questions about horizontal spacing (correct msg)
Hi .
(I'm sorry if I send again this message but some errors occurred while sending
the previous one)
Given these three bars:
{c c c c | c c c c | c c c c}
with the following output:
o o o o | o o o o | o o o o
--measureLength---
1) I would like to change the notes' spacing inside the second bar in this
way:
o o o o | o o o o |
o o o o
--pad-- --pad--
--measureLength---
where pad = measureLength/3 and measureLength remains the same.
2) I would like to change the notes' spacing inside the second bar in this
other way:
o o o o | o o o o | o o o
o
A B C D
--measureLength---
where
A and D (=notes) have their normal position, while B C form a group
with A which is proportionally compressed with a given scale factor.
And measure length remains the same.
Which is the easiest solution for both problems?
Thanks,
Luca
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On Wed, 01 Oct 2008 20:06:14 +0200 (CEST) Werner LEMBERG [EMAIL PROTECTED] wrote: If the built-in customization doesn't do what you want, then your only option is to hack texi2pdf directly. That involves C programming, Not at all. texi2pdf is a simple wrapper for the texi2dvi shell script. Sorry. I've never used dvi for anything other than as an intermediate stage on the way to pdf, so I wrapped the two up together in my mind. The only possibility to customize the look of the PDF is to modify texinfo.tex. Ah, I see. Well, there *is* good news for Eyolf: any modifications he makes can be added to the official docs instantly. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
The only possibility to customize the look of the PDF is to modify texinfo.tex. Ah, I see. Well, there *is* good news for Eyolf: any modifications he makes can be added to the official docs instantly. Mhmm. texinfo.tex is quite complex. Nothing for the fainthearted. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: questions about horizontal spacing (correct msg)
A good starting point is to read about scaling durations
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Scaling-durations#Scaling-durations
in the manual. For the first request, you could then use something along
the lines of
{c c c c |
s4. c4*1/4 c c c s4. |
c c c c |}
which spaces the notes in the second measure as if they were 16th notes.
This will not result in exactly the mathematical spacing you describe,
but may be close enough. If you really want such exact
spacing, you also have to combine this technique with the support for
proportional note spacing.
/Mats
Luca Rossi wrote:
Hi .
(I'm sorry if I send again this message but some errors occurred while
sending the previous one)
Given these three bars:
{c c c c | c c c c | c c c c}
with the following output:
oooo| oooo|oooo
--measureLength---
1) I would like to change the notes' spacing inside the second bar in
this way:
oooo| o o o o |oooo
--pad-- --pad--
--measureLength---
where pad = measureLength/3 and measureLength remains the same.
2) I would like to change the notes' spacing inside the second bar in
this other way:
oooo|o o oo|oooo
A B C D
--measureLength---
where A and D (=notes) have their normal position, while B C form a
group with A which is proportionally compressed with a given scale
factor. And measure length remains the same.
Which is the easiest solution for both problems?
Thanks,
Luca
___
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: Lyric tie glyph not found (directory separator problem?)
Have you read the warning about the font you need, in http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Entering-lyrics#Entering-lyrics /Mats Risto Vääräniemi wrote: Hi, Something strange just happened. I tried to use the lyric tie (~) in one song and LP complained that it couldn't find the glyph. These kind on messages usually appeared when the file wasn't saved as UTF but this time the same file works on my work computer (don't tell my boss). The directory separators seem to be / instead of \. That could be the reason why LP / Pango / whatever cannot find the file. If that's the next question is why have the separators changed in the first place. I'm using XP Pro SP3 on a MacBook. Does anyone else run LP on Boot Camped Mac? Any problems? -Risto GNU LilyPond 2.11.61 Processing `lyric_tilde.ly' Parsing... Interpreting music... Preprocessing graphical objects... programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000203F, file C:/Program Files/LilyPond_2.11.61/usr/share/ lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000203F, file C:/Program Files/LilyPond_2.11.61/usr/share/ lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000203F, file C:/Program Files/LilyPond_2.11.61/usr/share/ lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `lyric_tilde.ps'... Converting to `./lyric_tilde.pdf'... ___ 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: WANTED: Design for documentation (Photoshop power users!)
On 01.10.2008 (21:24), Werner LEMBERG wrote: The only possibility to customize the look of the PDF is to modify texinfo.tex. Ah, I see. Well, there *is* good news for Eyolf: any modifications he makes can be added to the official docs instantly. Mhmm. texinfo.tex is quite complex. Nothing for the fainthearted. I have noticed. Not only is texinfo the worst beast I've ever worked with, it's badly documented too, at least once one moves past the basics -- ironic, for a documentation format... And that texinfo.tex file... phew... I haven't given up yet, but... eyolf -- Marriage is the sole cause of divorce. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On Wed, Oct 1, 2008 at 8:53 AM, Patrick Horgan [EMAIL PROTECTED] wrote: Patrick, if you add a line-height: 1.125em; to the .settitle section it fixes the strange overlap on small windows. The one it inherits from the body section uses a different em, and although you specify it in ems, it's inherited in pixels. Or in CSS speak, you don't inherit the specified value, but the computed value. (See the CSS2 spec section 6.1.1 below. Or, you could just take it out of the body section, but definitely it looks better with it. Here's part of the CSS2 spec that explains it and more (trying to whet your interest so that you'll go to w3c and get your own copy of the spec;) [snip] Hi Patrick, Thanks for the suggestion. This will be implemented in my forthcoming patch. I also changed the background color of #tocframe to `beige', as a compromise between the grey (#eee) and pure white (#fff). Regards, Patrick McCarty ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
On 2008/10/01 8:30 AM, Patrick McCarty [EMAIL PROTECTED] wrote: On Tue, Sep 30, 2008 at 11:53 PM, Kurt Kroon [EMAIL PROTECTED] wrote: -1, but I've got mad enough skillz to make a user style sheet. That way, I can make it look however I please. I have attached my current user style sheet, to be applied in lieu of Patrick's styles (in case anyone's interested). Kurtis whose mantra is I am *not* a representative user Hi Kurt, Thanks for responding. I wish you would have contributed earlier. ;-) I like your stylesheet, in general. But I think some of the font sizes you are using will render parts of the documentation illegible on certain platforms (such as in the TOC). I like your choice of color especially. Thanks, Patrick Easy fix: in the body selector, change the font-size to 100%. And while I'm thinking about it, you could deal with the line-height issue by setting it to 1.125, without any units. ( See Eric Meyer's excellent article about this issue: http://meyerweb.com/eric/thoughts/2006/02/08/unitless-line-heights/ -- in particular, the part where he strongly recommends unitless numbers when you set it on items with descendants.) ) Best Kurtis ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation (Photoshop power users!)
Kurt Kroon wrote: And while I'm thinking about it, you could deal with the line-height issue by setting it to 1.125, without any units. Thanks! I'd read the section on this in the spec, (and just re-read it), and it doesn't point out how much better it is for inheritance, and I didn't get it. I will from now on! Thanks a lot! Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: png cropping
After much revision, addition, and general fussing about with it, I'm
happy to post the official version of what we're calling lily2image, a
script for converting lilypond source files to cropped image files in
many different formats suitable for insertion into documents (theses,
research papers, etc) or web pages. This works equally on Mac and
Linux, but not on Windows. Dependency: netpbm (available in Linux repos
and MacPorts)
Many, many thanks to Patrick Horgan for all of his work on this. He
added tons of code and gave me excellent guidance as I was learning how
to script. This was a great learning experience.
Thanks also to Josh Parmenter, who jumped in somewhere along the way and
made very helpful suggestions, and also tested every revision I sent
him. Thanks for a fun project, guys! I hope others in the Lilypond
community will find it a useful tool.
Jon
p.s. I've also attached my manpage for the script: lily2image.1. Just
put it somewhere in your manpath and make sure it has read permissions
for all users. I put it here on Linux:
/usr/share/man/man1/lily2image.1
It was slightly different on Mac but now I can't remember. If someone
needs help I'll check on it.
--
Jonathan Kulp
http://www.jonathankulp.com
#!/bin/bash
#**#
# Script for making image files from lilypond source suitable for use as #
# musical examples to insert in a document or web page.#
# Creator - Jonathan Kulp#
# Scripting Guru- Patrick Horgan #
#**#
# Change log
#
# 1.2 Added loop to image conversion to accommodate lilypond files that
# have more than one page. It loops until it has converted each of
the
# png files output by Lilypond.
# 1.1.1.12 Added final exit 0 status at end of file; updated manpage
# 1.1.1.11 Added jpg=jpeg, tif=tiff when values set at command line; added
# echoes of netpbm activity and echoes at end of process.
# 1.1.1.10 -V implies -p ph
# 1.1.1.9 Added range check to getnumval ph
# 1.1.1.8 -p flag is now necessary for preview--image is not opened in
# viewer by default. jk
# Quiet mode is really quiet as long as sufficient parameters are
# set at command line for process to succeed. jk
# 1.1.1.7 Added -p flag: allows forced preview even in quiet mode. jk
# Made quiet mode more quiet. jk
# 1.1.1.6 Changed the call to Lilypond on OSX by defining $PATH
# early in the script. Changed Patrick's Johnny Come Lately to
# Major Contributor :) and added a few echoes when formats,
# resolutions, and so forth are set. We could remove these if you
# they're too much. jk
# 1.1.1.5 Added -w option to specify white background and avoid prompt for
# transparency jk
# 1.1.1.4 Added lines to clean up png file if desired format is not png. jk
# 1.1.1.3 Changed list of Darwin viewers--Darwin doesn't have eog and evince
# Added quiet mode -q (I think it works!) jk
# 1.1.1.2 Fixed handling of dirs and files with spaces ph
# 1.1.1.1 Added search for default list of viewers ph
# 1.1.1 Added -a, -V and much comments changed default viewer to xdg-open ph
# 1.1 Added checking of return codes so we could
# abort if something failed. ph
# 1.0 Initial beta release jk
#~~~
# in quiet mode exits with various return codes from
# failures
# 40 - transparency not set and no default
# 41 - format not set and no default
# 42 - resolution not set and no default
# 43 - netpbm utilities not installed
# 44 - unable to find conversion program for desired output
# 45 - resolution from command line not positive numeric
# 46 - format from command line invalid
# various - if any of the programs we call fail, we
# exit with whatever error code they returned
#~~~
# setformatlist - gets the list of all the things that # you can convert to
#~~~
setformatlist()
{
currentdir=`pwd`# Remember our current directory
examp=`which ppmtojpeg` # find out where the progs are
returnstatus=$?
if [ $returnstatus -eq 0 ] ; then
# We found it! Use it as model to find the rest.
OUTDIR=`dirname $examp` #grab the directory
cd $OUTDIR # change to it so we can
# find all the programs starting with ppmto
# and remove the initial part so that we can
# figure out what ppms can be converted to
ppmtos=`ls ppmto* | sed -n s/ppmto//p`
# same for pnmto
Re: WANTED: Design for documentation (Photoshop power users!)
Mhmm. texinfo.tex is quite complex. Nothing for the fainthearted. Not only is texinfo the worst beast I've ever worked with, You are exaggerating. The LaTeX kernel stuff is worse IMHO. it's badly documented too, at least once one moves past the basics It's getting better. Until recently, only Karl has worked on texinfo.tex; now there are more contributors, and they add comments here and there. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
