Shift rests
% Isn't a pitched rest supposed to shift to the right or - vice versa - a
chord relative to the rest?
\version 2.11.37
\paper { ragged-right =##t }
{ d' g' }
\\
{ \override NoteColumn #'force-hshift = #2. b \rest }
{ \override NoteColumn #'force-hshift = #2. d' g' }
\\
{ r }
--
Gruss
Luc
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Halving the duration of every note
...is it also possible to achieve this without changing the appearance? Means: printing notes that have a different duration than they look like (something that \times does, just without brackets and numbers). thanks! stefan Kieren MacMillan wrote: Hi Alasdair: This means halving the duration of every note in the original. Is there an easy way to do this? http://lsr.dsi.unimi.it/LSR/Search?q=looksFaster Best wishes, Kieren. ___ 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
xandros
Dear Lilypond-users, I wanted to install Lilypond on Xandros, but without success. Does anyone know how to do this? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
2008/1/6, Graham Percival [EMAIL PROTECTED]: help ur program is broken. where are teh buttons 2 click on ahahahaha :) (irrepressible hysterical laugh) Still, if I might add a comment here, the quality we need the most is *not* a high LilyPond skill-level, but simply patience, enthusiasm, and preferably a taste for pedagogy. (Yes, Graham is kind of an exception :) One year ago, I was a *complete* newbie. I just wanted to give a hand. I proposed a few sponsoring offers that were all ignored, and at some point I realized this was not about money but about resources, man-hours. I realized the most useful and needed improvements were often very basic and immediate: -translating some documentation into my own language, -asking (and then answering) questions on the mailing list, -adding a few snippets to the LSR or reporting incorrect snippets, -reporting some bugs I came to find, -etc. During all this time, I never realized I was actually learning how to use LilyPond. And yet, it is the *best* way to progressively know what you're talking about. There are still many topics I absolutely don't know about. Everybody laughs at Graham everytime he says he doesn't know how to to do some simple tasks with LilyPond (e.g. adding lyrics), but I now realize that he is indeed a total ignoramus like myself :) This is what you are (unless you wrote the program yourself), this is what I am: just another absolutely unexperienced guy, who just happens to love LilyPond scores and have some time to spend on it. We will all happily welcome you, no matter your age, your (bad) English, your (absence of) former experience or your (lack of) skills. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rests in Percussion Notation
Hi,
Reilly-3 wrote:
Can I manipulate whole and half measures rests in various 1-line staves?
Half rest should be below line
Whole rests should rest on line not levitate above line
I'm now writing a small score, which contains percussion (cymbals) and I was
searching for RhythmicStaff stuff and I found this message.
I don't know much about percussion notation but the half / whole rest
position you presented somehow made me curious. Should they really be
written the other way round as in normal 5 line notation? Any reason why?
Well, I'm happy even with the current style except for the floating whole
rest (multimeasure rest, R1). I've lowered it by #-0.02 and now the ledger
line coincides with the main line. The stubby line is showing through the
line, though. :-( I also tried to replace R1 with s1*1/2 r1*1/2 but they
did not always match with R1s on other staves.
Is there a way to change the R1 glyph from rests.0o to e.g. rests.0 for
that staff?
Is this a bug?
-Risto
%% Start %%
\version 2.11.34
\score{
\new RhythmicStaff
{
r4 r8 c' r2
r1
R1
\override MultiMeasureRest #'staff-position = #-0.02
R1
}
\layout
{
\context {
\RhythmicStaff
\consists Clef_engraver
clefGlyph = #clefs.percussion
clefPosition = #0
\override TimeSignature #'style = #'numbered
}
}
}
%%% END %%%
--
View this message in context:
http://www.nabble.com/Rests-in-Percussion-Notation-tp14539033p14647733.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Halving the duration of every note
You can use \times and suppress the tuplet number with \override TupletNumber #'transparent = ##t or your can change the duration of a note by appending a number or fraction: eg a4*2/3 but both will affect the barring. See section 1.2.1 in the R11 documentation for details. Trevor D -Original Message- From: [EMAIL PROTECTED] [mailto:lilypond-user-bounces+t.daniels=treda.co.u [EMAIL PROTECTED] Behalf Of Stefan Slapeta Sent: 06 January 2008 10:52 To: Kieren MacMillan; lilypond-user@gnu.org Subject: Re: Halving the duration of every note ...is it also possible to achieve this without changing the appearance? Means: printing notes that have a different duration than they look like (something that \times does, just without brackets and numbers). thanks! stefan Kieren MacMillan wrote: Hi Alasdair: This means halving the duration of every note in the original. Is there an easy way to do this? http://lsr.dsi.unimi.it/LSR/Search?q=looksFaster Best wishes, Kieren. ___ 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 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Halving the duration of every note
how about \compressMusic (see Polymetric Notation in the manual)? ole Am 06.01.2008 um 13:27 schrieb Trevor Daniels: You can use \times and suppress the tuplet number with \override TupletNumber #'transparent = ##t or your can change the duration of a note by appending a number or fraction: eg a4*2/3 but both will affect the barring. See section 1.2.1 in the R11 documentation for details. Trevor D -Original Message- From: [EMAIL PROTECTED] [mailto:lilypond-user-bounces+t.daniels=treda.co.u [EMAIL PROTECTED] Behalf Of Stefan Slapeta Sent: 06 January 2008 10:52 To: Kieren MacMillan; lilypond-user@gnu.org Subject: Re: Halving the duration of every note ...is it also possible to achieve this without changing the appearance? Means: printing notes that have a different duration than they look like (something that \times does, just without brackets and numbers). thanks! stefan Kieren MacMillan wrote: Hi Alasdair: This means halving the duration of every note in the original. Is there an easy way to do this? http://lsr.dsi.unimi.it/LSR/Search?q=looksFaster Best wishes, Kieren. ___ 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 ___ 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: Filling the page
Wilbert,
On Jan 6, 2008, at 1:47 AM, Wilbert Berendsen wrote:
Try:
\paper {
ragged-last-bottom = ##f
}
Uitstekend! Dank u.
Jeremiah
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rests in Percussion Notation
Hi again, Risto Vääräniemi wrote: Is there a way to change the R1 glyph from rests.0o to e.g. rests.0 for that staff? I got the R1 rests to hang below the line by setting \override RhythmicStaff.MultiMeasureRest #'extra-offset = #'(0.0 . -1.0) Not so elegant solution, though. -Risto -- View this message in context: http://www.nabble.com/Rests-in-Percussion-Notation-tp14539033p14648714.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Leaving: I can't help
2008/1/6, Eyolf Østrem [EMAIL PROTECTED]: Ehem... unless with currently you mean at this very moment, we do have one, although too pressed for time at this very moment (lasting until the middle of the month) to be as active as desirable. But *zero*? No. (S! You're ruining Graham's rhetorical effect!) :-) Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: xandros
2008/1/6, Stefan Thomas [EMAIL PROTECTED]: Dear Lilypond-users, I wanted to install Lilypond on Xandros, but without success. Does anyone know how to do this? AFAIK it should work like on any other linux distribution: -download the linux-x86 installer on http://lilypond.org/web/install/ -open a terminal -(as root user), cd to the download directory (e.g. your Desktop) and -type sh lilypond-2.*-x86.sh and press Enter Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rests in Percussion Notation
2008/1/6, Risto Vääräniemi [EMAIL PROTECTED]: Is there a way to change the R1 glyph from rests.0o to e.g. rests.0 for that staff? Why don't you try: \override MultiMeasureRest #'stencil = #ly:text-interface::print \override MultiMeasureRest #'text = \markup \musicglyph #rests.0 Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
Graham and fellow Lilyponders: I have been following the discussion of Graham's planned departure from the Lilypond team and other recent discussions on the extent to document code in style sheets and tweaks. I began using Lilypond in the summer of 2007, after rejecting demo versions of the major commercial notation software. It has been a rocky transition from pencil and paper to digital notation. The output from version 2.11.35 is quite good and much better than 2.10. I would like to contribute back to the Lilypond community which has been very helpful to me, but, unfortunately, I cannot *commit* at this time. This doesn't mean I cannot help, just that I cannot commit. (The truth is, my life is in shambles financially speaking --- no different than many other musicians?) No offense to everyone who has worked on the documentation for Lilypond, but the documentation is the weakest component of the package. The index often lacks entries for my questions. The entries more often than not, do not address my problems. The coded examples are often too clever and don't illuminate my ignorance. Obviously everyone wants to make the documentation equal to the programming. That is why the GDP is underway. Suggestion: Collect a team of Lilypond MUSIC Consultants. This could be the general lilypond-user group or a subset. Volunteer members would agree to answer questions. The GDP team should *not* spend time researching answers to musical or notational questions IF they can find a local Lilypond user who knows the answer. For instance, take the questions below: On Jan 6, 2008, at 2:58 AM, Graham Percival [EMAIL PROTECTED] wrote: Concrete example? Well, there's falls and doits in Expressive marks. I have no clue what these are. Something for jazz singers? Saxophonists? Maybe they're used in Baroque notation? Or a special mark for accordion players? Is the current doc section acceptable? I have no clue. Judging from the picture and the input, \bendAfter does *something*. But I don't know what it's doing, nor what else the doc should say here. Maybe people who use \bendAfter would also want a link to the ancient notation articulations? Or the vocal aligning syllabels ? I have no clue. For example, f somebody writing the GDP had a question about falls or doits, he (Graham in this case) could simply post to the Lilypond Consultant list, What is a fall? What is a doit? And, a user responds: A fall is a downward glissando while decrescendoing from an initial pitch to an indeterminate pitch below. There are long falls (gliss down an octave) or short falls (gliss down a fourth). I primarily see them in jazz notation. A doit is an upward glissando of about a fifth from an initial pitch. The notes fade as the pitch rises. Falls and doits can be played (or faked) on most instruments not just saxophones. I've never seen a fall or doit notated in baroque notation (baroque notation is pretty lean). In a few months, if GDP is still progressing, we'll be tackling NR 2 specific notation. These problems will be even worse then. I honestly think that I've /never/ seen any classical guitar sheet music. How am I supposed to supervise work on this section? I can check submissions for accordance to the doc policy, but I certainly can't judge the *contents* of those docs. Now what about the poor GDP helper who gets assigned work on Guitar music? I don't think that any of the current helpers play guitar, so they'll have the same problems that I face. (nothing personal against guitars... I know virtually nothing about everything else in NR 2, including vocal music) Many of the volunteers begin their emails saying I know almost nothing about music notation, but I'm willing to help if you think I can without embarassing myself. I am completely baffled about all these volunteers -- I mean, I'm incredibly happy about them, but baffled nevertheless. Why do so many people want to help after reading nothing more than the lilypond tutorial? And conversely, why is it that nobody who actually *is* familiar with music notation and lilypond volunteers? Responding to Graham's public expression of ignorance, I will share my own: I am completely baffled by Lilypond code at least half the time. I don't understand Scheme. I don't get make-event. I don't understand when I code \once \override Score . RehearsalMark #'self-alignment-X = #-1 which should left justify the RehearsalMark to the time signature (I am leaving out other code here), the rehearsal mark is *not* left aligned. I finally shifted the rehearsal mark 7 spaces leftward until is was properly aligned. What I do know is various musical instruments, musical styles, and musical notation: piano pipe organ classical guitar saxophone clarinet viola accordion recorder trombone tuba voice familiar with Renaissance, Baroque, Classical, Early Romantic, Jazz (all styles), 20th century, and contemporary
Debugger; draft mode
I am ignorant of what is possible or available in Lilypond. I am currently running 2.11.36 on a Mac PPC running OS 10.3.9. I write my code either directly into a Lilypond file or into TextEdit and then cut and paste. (1) I am working on a symphony (22 staves) which takes more than 20 minutes to compile and the time increases rapidly as I add more music to the score. I have developed a work around for proofing my input: I compile individual parts which take about 15 seconds. This is okay for checking note entry. But I also need to check part alignment vertically. Gosh, it is easy to get a measure off, especially when I rewrite an early section of the music. Would it be possible to add a \draft mode to Lilypond which would ignore markups, text, dynamics, and formatting and just do the music (4 bars to a line or something), so I can do a quick read-through of the score? (Yes, I do know that Lilypond offers a feature to process only the most recent music --- this does not help me). (2) I use TeXShop for my LaTeX. A superb program with an excellent debugger. When I process a LaTeX file, if the compiler encounters an error, it stops and offers me an option via a click button to go to error. Usually the error precedes this location, but it does give me a start in debugging. I do not find the Lilypond compiler window helpful --- in fact, I usually find it very confusing because the error messages are murshky-murshky to me. One misplace } can lead to 39 SCM error files messages. Perhaps, the limitation is in me? Obliged, Jeremiah ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Changing vertical extent on-the-fly?
Hi all,
I recently asked a similar question on the list, now noticing again that
I'd like to have this feature.
A minimal example:
\version 2.11.37
\score {
\relative c' {
\new Staff { c4 d e f | f e d c \break |
\override Staff.VerticalAxisGroup #'minimum-Y-extent = #'(-8 . 4) %
does not work
c d e f | f e d c | }
\new Staff { f4 e d c | c d e f | f e d c | c d e f | }
}
}
Is it possible to change minimum-Y-extent for a Staff on-the-fly like in
the example?
Maybe something with NonMusicalPaperColumn could do the job the same
way, but I don't really know how to figure this out at this time.
Thanks for all advice,
Michael
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Debugger; draft mode
2008/1/6, Reilly [EMAIL PROTECTED]: I am ignorant of what is possible or available in Lilypond. (1) I am working on a symphony (22 staves) which takes more than 20 minutes to compile and the time increases rapidly as I add more music to the score. I have developed a work around for proofing my input: I compile individual parts which take about 15 seconds. This is okay for checking note entry. But I also need to check part alignment vertically. Gosh, it is easy to get a measure off, especially when I rewrite an early section of the music. Would it be possible to add a \draft mode to Lilypond which would ignore markups, text, dynamics, and formatting and just do the music (4 bars to a line or something), so I can do a quick read-through of the score? (Yes, I do know that Lilypond offers a feature to process only the most recent music --- this does not help me). This is great to see your mail: as it happens, we were just talking with Rune the other day about some possibility to implement such a feature. It definitely would be a HUGE improvement in LilyPond, and since I'm writing a 300 pages opera, I know what you're talking about :) This answer is unfortunately: no at this time. It might be technically possible but it would require several developers to work full-time on it. We could start a fundraising but I'm afraid we would never have enough money to actually pay coders so that they could make a living out of it; only organizations sponsored by companies can achieve such things (e.g. the Mozilla or the Wikimedia Foundation). So, the only way to hope that such a thing will happen someday is a very long shot: -spread LilyPond everywhere you can, -use it, -use LilyPond scores, -talk about it, -make other people use it, -make other people love it, -and possibly in the end some official structures will be interested in spending some money in it. For example, LilyPond is starting to be used in music-education in some European countries; if it became official, maybe some local governments would contribute to its development. Another idea from Rune: maybe in the end some music publishing companies will understand they'd better use LilyPond instead of paying proprietary licenses, hundreds of copyists, and however still printing miserable scores ;) (2) I use TeXShop for my LaTeX. A superb program with an excellent debugger. When I process a LaTeX file, if the compiler encounters an error, it stops and offers me an option via a click button to go to error. Usually the error precedes this location, but it does give me a start in debugging. I do not find the Lilypond compiler window helpful --- in fact, I usually find it very confusing because the error messages are murshky-murshky to me. One misplace } can lead to 39 SCM error files messages. Perhaps, the limitation is in me? Actually, I find that the error messages provided by LilyPond are quite useful. The program indicates the line where something's wrong, and it's generally easy to find it yourself. Otherwise, i don't remember if you're planning to upgrade to Tiger or Leopard someday (better wait for a few months before installing Leopard though), but as soon as you'll have a 1.5 Java version, you'll be able to install and use the great jEdit text editor, alongside with its special plugin called LilyPondTool: http://lilypondtool.organum.hu/87.0.html One of it's most useful features is that it detects syntax errors as you're typing, and underlines them in red, so that you can correct mistakes without even having to compile your score! It works under Windows, Linux, and Mac 10.4 (yes, my girlfriend has 10.3.9 too, and I know how frustrating these compatibility issues are). Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Halving the duration of every note
Hi all, how about \compressMusic (see Polymetric Notation in the manual)? That's definitely my preferred method. Best, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
On 06.01.2008 (09:51), Reilly wrote:
No offense to everyone who has worked on the documentation for Lilypond, but
the documentation is the weakest component of the package. The index often
lacks entries for my questions. The entries more often than not, do not
address my problems. The coded examples are often too clever and don't
illuminate my ignorance. Obviously everyone wants to make the documentation
equal to the programming. That is why the GDP is underway.
Hopefully, the GDP will be able to remedy some of this. As one of the
rewriters of the Notation Reference (in fact the *only*, AKA Mr Zero), I
can subscribe to some of the criticism. I don't know about the index -- I
hardly ever use it, perhaps for the reasons you mention -- but as for the
examples, it has been my guiding principle that if I don't understand an
example, down to the details of why does this setting do that, why does it
have to follow this syntax?, it needs to be rewritten. I've tested all the
examples I've been through so far according to that principle.
To some extent, this runs counter to another documentation principle which
I've reluctantly, very reluctantly come to accept, if not endorse: since
all the music examples are updated automatically with convert-ly if syntax
changes etc. are introduced in Lilypond, the explaining text should not be
too directly tied to the examples, since it will then require quite a lot
of extra effort to go over all the text that is NOT automatically updated,
and this is a constant risk of error. I don't like it, but I see the
rationale.
Suggestion:
Collect a team of Lilypond MUSIC Consultants. This could be the general
lilypond-user group or a subset. Volunteer members would agree to answer
questions. The GDP team should *not* spend time researching answers to
musical or notational questions IF they can find a local Lilypond user who
knows the answer. For instance, take the questions below:
Re. your
What is a fall?
What is a doit?
example, the problem is not so much knowing what it means -- that can be
looked up quite easily -- but to know (a) what kind of variations does a
user expect? does size matter? angle? are different symbols or styles in
use, and are they informative variations, etc.; (b) figure out how to
effect all these variations through Lilypond code; (c) choose how much of
this is really needed in the docs, and how much of it can be written
meaningfully without violating the don't comment the examples directly
principle.
Your suggestion of a group of music consultants is fine, and I intend to
try to distribute some responsibility along similar lines when we come to
the Specialist notation chapters (so that Graham would not have to write
the guitar section), but I fear that such a group would tend to become too
loose (volunteers come and go), and it would probably be too much of a
hit-and-miss thing -- can I expect to have a sax player in the group when I
write about doits? Maybe, maybe not. It is probably more practical if
people write in with concrete suggestions if something is missing, wrong,
or unclear in their particular field of expertise.
A general *alert* to the GDP team: music notation is NOT standardized.
We know that...
I am conflicted in
regard to notation. I want to keep the flexibility of Lilypond to tweak the
output to my needs. Yet, I want to introduce some consistency in output to
improve the quality of printed music for all the composers who don't want to
tweak their output. I think minimally this would require a number of style
sheet packages (like LaTeX packages) which (a) address all the issues
appropriate for the intended output (e.g. contemporary conducting score
style sheet; contemporary study score style sheet; contemporary condensed
score style sheet); and (b) at the same time, make the issues user
tweakable.
Yes, and as Graham pointed out in another thread, this is perfectly doable
-- it just takes someone to do it. I'd love to be able to write
\rehearsalmarks{alphabetic} or \setlenght{betweensystemspace}{2em} if
someone writes a package that includes it.
Eyolf
--
`...we might as well start with where your hand is now.'
Arthur said, `So which way do I go?'
`Down,' said Fenchurch, `on this occasion.'
He moved his hand.
`Down,' she said, `is in fact the other way.'
`Oh yes.'
- Arthur trying to discover which part of Fenchurch is wrong.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
2008/1/6, Eyolf Østrem [EMAIL PROTECTED]:
Hopefully, the GDP will be able to remedy some of this. As one of the
rewriters of the Notation Reference (in fact the *only*, AKA Mr Zero), I
can subscribe to some of the criticism. I don't know about the index -- I
hardly ever use it, perhaps for the reasons you mention
Jeremiah,a question comes suddenly to my mind: do you ever use the
LilyPond Snippet Repository?
(It's OK if you don't, it would just mean that it's not visible enough)
http://lsr.dsi.unimi.it
The LSR makes looking for tips extremely easy (Plus, we have a tagging
system that is gonna be accessible Real Soon Now, so things will be
made even easier).
Plus, it includes the whole LilyPond Documentation as well, and
searching for keywords is definitely much easier with this tool than
with the very limited index -- AFAIK only Graham has ever used it ;)
http://lsr.dsi.unimi.it/LSR/Manual
I'd love to be able to write
\rehearsalmarks{alphabetic} or \setlenght{betweensystemspace}{2em} if
someone writes a package that includes it.
What, you mean something like:
http://lsr.dsi.unimi.it/LSR/Item?id=368
:-)
Cheers,
Valentin
(PS. It's just a first try, which is why I haven't advertised it yet;
the whole code is commented out, as it is written for 2.11 and the LSR
is temporarily running 2.10)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Leaving: I can't help
Hi Graham, Okay, the guilt and peer pressure has finally overwhelmed my better judgement! ;-) If I had an advanced lilypond user offer to help, I wouldn't ask them to work on the texinfo files directly (unless they particularly wanted to). I just want somebody who can review the material in detail, answer questions from other helpers, etc. Maybe create a few small lilypond examples to replace (or add to) existing examples. I'm in. Send me (or point me to), one at a time, the section(s) you want me to review/rewrite. I'll do what I can, and when I'm done a section, point me to the next. Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
On 06.01.2008 (17:15), Valentin Villenave wrote:
2008/1/6, Eyolf Østrem [EMAIL PROTECTED]:
I'd love to be able to write
\rehearsalmarks{alphabetic} or \setlenght{betweensystemspace}{2em} if
someone writes a package that includes it.
What, you mean something like:
http://lsr.dsi.unimi.it/LSR/Item?id=368
Something like it, yes. Great to see the example. But I also had something
more general in mind: a set of macros to avoid any direct fiddling with
scheme altogether, sth. like LaTeX in relation to plain TeX. I really,
really hate things like Staff.VerticalAxisGroup #'minimum-Y-extent = #'(-8
. 4), and it shouldn't be necessary to write something like that for
something as common as adjusting the vertical spacing. OK, if you want to
slant your stems by 5 degrees, then it would be nice to have the option,
but all the \once \override and #'(stencil bla bla) stuff should be made
much easier.
If someone cares to do it, that is...
eyolf
--
Besides, REAL computers have a rename() system call.:-)
-- Larry Wall in [EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
cross staff beaming
I looked at the lsr for cross staff beaming and it doesn't look like what I'm after. Piano staff and a run of notes from gis through middle c to e changing staff at e below middle c but slanted not flat beams and I don't want to change the distance between the staves so reading the code from the LSR is confusing. What's necessary and what can I leave out? or is this not the way to do it? Yours- Jay Jay Hamilton www.soundand.com 206-328-7694 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
Greetings all:
On Jan 6, 2008, at 11:15 AM, Valentin Villenave wrote:
Hopefully, the GDP will be able to remedy some of this. As one of the
rewriters of the Notation Reference (in fact the *only*, AKA Mr
Zero), I
can subscribe to some of the criticism. I don't know about the index
-- I
hardly ever use it, perhaps for the reasons you mention
Everything about version 2.11 is much improved, including the rewriting
of the Notation Reference.
Jeremiah,a question comes suddenly to my mind: do you ever use the
LilyPond Snippet Repository?
(It's OK if you don't, it would just mean that it's not visible enough)
Yes, I do use the LSR. I also have found several private Lilypond
code libraries where users have been thoughtful enough to catalog their
solutions. I used Lilypond six months before posting my question to the
user's group because I feel it is my responsibility to make every
effort to use the published resources and not ask questions with
*obvious* answers. Now, I usually work several hours on a problem
before I post a question and at least half the time I find the solution
on my own. I enjoy the work and the effort makes me a better user. The
other half of the time, I do get stumped.
http://lsr.dsi.unimi.it
The LSR makes looking for tips extremely easy (Plus, we have a tagging
system that is gonna be accessible Real Soon Now, so things will be
made even easier).
Plus, it includes the whole LilyPond Documentation as well, and
searching for keywords is definitely much easier with this tool than
with the very limited index -- AFAIK only Graham has ever used it ;)
http://lsr.dsi.unimi.it/LSR/Manual
I respectfully suggest that usefulness of the LSR and the documentation
is impaired by the snippets themselves and not the search capabilities.
I don't have time to dig out an example now, but basically, I seach, I
find, and the snippet (or doc ref) does not answer my problem.
I'd love to be able to write
\rehearsalmarks{alphabetic} or \setlenght{betweensystemspace}{2em} if
someone writes a package that includes it.
What, you mean something like:
http://lsr.dsi.unimi.it/LSR/Item?id=368
cheerios,
Jeremiah
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
On 06.01.2008 (14:21), Reilly wrote: Eyolf, On Jan 6, 2008, at 12:00 PM, [EMAIL PROTECTED] wrote: Perhaps I misunderstand the purpose of Graham's example question. It's easy: the purpose of ALL of Graham's examples is that THIS TAKES RESOURCES and no matter how good the idea is, someone has to do it. :) It's annoying as hell, but he's right... In re your clarification re falls and doits above (a), yes, lots of variations, sometimes the length of the gliss indicates length of fall or doit. The fall/doit symbol is something like a musical font. I personally would not tweak this feature much, unless I hated the preset symbol. Thanks I think we disagree slightly on how my proposal would work (or, perhaps, how people behave). If I have to notate a classical guitar passage and I consult the Lilypond documentation and I find it inadequate, it is expecting a lot of my --- aka, the casual music engraver --- to rewrite the documentation and send it to somebody. (I don't even know to whom I would send it.) On the other hand, if I am a subscriber to a Lilypond Resource List and a specific question comes along to which I know the answer, I think I would be inclined to answer it. I do agree that from the documentation team's point of view it is more practical for volunteers to commit to rewrite sections of the manual. I was thinking more along the lines of: person A writes a lot of guitar scores, over the years (or months) he has aquired a good understanding of how the guitar-specific features of LP work, and he has also assembled a number of tweaks. He would be in a better position to rewrite those sections or come up with good/annoying questions than person B, who only writes polyrhytmic stuff for gamelan gongs. I was unclear about the somebody part. This list is a good candidate (although things tend to disappear in the bulk of messages here unless one has a good email client and working habits; I try to flag important messages, but I know I miss things); the docs meister is another -- once there is one again. ps: How would an English speaker pronounce your name? Eye-olph with the stress on the first syllable. Should be easy, but I have friends who still call me Eee-loph, even after almost a decade... Eyolf -- The Principal of Greenbow County Central Schools: Your momma sure does care 'bout your schoolin' son ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating a book of music
Le 4 janv. 08 à 00:15, Reinhold Kainhofer a écrit : Are you thinking about turning your framework into a general lilypond-for-books package (with some documentation on how to use ;-) ) so that we ordinary lilypond users can also benefit from it? A book titling stylesheet has been published on LSR: http://lsr.dsi.unimi.it/LSR/Item?id=368 It requires a 2.11.something LilyPond version. nicolas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Leaving: I can't help
On Sun, 6 Jan 2008 15:19:13 +0100 Valentin Villenave [EMAIL PROTECTED] wrote: 2008/1/6, Eyolf __strem [EMAIL PROTECTED]: Ehem... unless with currently you mean at this very moment, we do have one, although too pressed for time at this very moment (lasting until the middle of the month) to be as active as desirable. But *zero*? No. (S! You're ruining Graham's rhetorical effect!) Exactly. :) It's been about a month since an update from you. I know your book is due at the end of Jan, and this of course takes priority. I'm not complaining about you. However, this is still a problem for me. I have formatters working on sections which have never been touched by a rewriter. My intent was to have this work like a production line in a factory: 1) Rewriters fix the content (such as lilypond examples, adding rough text, etc). 2) Formatters polish the presentation of the content (fix the English writing, fix indentation in lilypond examples, add links, etc) 3) advertise section of the docs on -user, get comments about what work still needs to be done. Go back to step 1 and repeat until we have no more commments. If step 1 isn't being done, it's a problem. Besides, did you _really_ want to be the only person working on the content? It would be much, much better if we had a couple of different people working on this, so you could all check each other's work. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating a book of music
Le 6 janv. 08 à 21:56, Graham Percival a écrit : On Sun, 6 Jan 2008 21:50:38 +0100 Nicolas Sceaux [EMAIL PROTECTED] wrote: Le 4 janv. 08 __ 00:15, Reinhold Kainhofer a __crit : Are you thinking about turning your framework into a general lilypond-for-books package (with some documentation on how to use ;-) ) so that we ordinary lilypond users can also benefit from it? A book titling stylesheet has been published on LSR: http://lsr.dsi.unimi.it/LSR/Item?id=368 It requires a 2.11.something LilyPond version. This could be a problem; LSR is currently on 2.10.12. If you have any difficulty publishing it on LSR, you could try sending it ot Valentin privately; he can add it to LSR once it's been upgraded. Actually, that's what I've done: Valentin added it to LSR. nicolas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Leaving: I can't help
On 06.01.2008 (12:52), Graham Percival wrote: It's been about a month since an update from you. Ten days, to be exact :) Besides, did you _really_ want to be the only person working on the content? Of course not! I just reacted to the zero part. eyolf -- Who dat who say who dat when I say who dat? -- Hattie McDaniel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Leaving: I can't help
On Sun, 6 Jan 2008 22:08:26 +0100 Eyolf __strem [EMAIL PROTECTED] wrote: On 06.01.2008 (12:52), Graham Percival wrote: It's been about a month since an update from you. Ten days, to be exact :) ... since an updated .itely file since you? (to be honest, I was guessing. As soon as I've committed a patch / merged a file, I forget all about it) Besides, did you _really_ want to be the only person working on the content? Of course not! I just reacted to the zero part. Again, rhetoric. Hey, it finally guilt-tripped Kieren into offering to help. Don't argue with results. :) Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Instrumental Group Names in Score
Hi Kieren,
On Jan 3, 2008, at 12:39 PM, Kieren MacMillan wrote:
I have easily spent 10 times the amount of time studying Lilypond
and understand only 1/10th of what I can do in LaTeX.
This may be because LaTeX includes *significantly* more (and more
complex) macros which sit on top of (Plain) TeX -- i.e., you don't
have to hand-code as much in LaTeX as you do in Lilypond.
I *understand* LaTeX; I am *baffled* by Lilypond.
Yes, but you're comparing apples to oranges in a way...
You should compare a Lilypond file to a (Plain) TeX file where you
need to define your own stylesheet -- I think you'd find that Lilypond
compares (more) favourably there.
Thank you for this comparison. Yes! I want the LaTeX equivalent in
Lilypond. LaTeX stills permits a great deal of tweaking within a
structure.
This is not to say that Lilypond shouldn't be easier (the way LaTeX is
*MUCH* easier than Plain TeX).
I'm just pointing out that LaTeX is much more mature that way.
I imagine you might be in the same situation if you needed to edit a
real (low-level) TeX stylesheet file, e.g.
\def\plaincases#1{\left\{\,\vcenter{\normalbaselines
\mathsurround=0pt\relax
\ialign{$##\hfil$\quad##\hfil\crcr#1\crcr}}\right.}
\def\plainmatrix#1{\null\,\vcenter{\normalbaselines\mathsurround=0pt\re
lax
\ialign{\hfil$##$\hfil\quad\hfil$##$\hfil\crcr
\mathstrut\crcr\noalign{\kern-\baselineskip}
#1\crcr\mathstrut\crcr\noalign{\kern-\baselineskip}}}\,}
\def\pplainmatrix#1{\left(\plainmatrix{#1}\right)}
\let\plainpmatrix\pplainmatrix
The benefit of LaTeX, coupled with whatever documentclass and packages
you use, is that you don't NEED to access the code at that level.
Lilypond just doesn't have those abstracted stylesheets.
Yikes! This is exactly what I spend time doing in Lilypond which I want
to reduce. And, I am very glad that I don't have to resort to this
level of coding in LaTeX.
Today I found an example of Lilypond coding which illustrates my
bafflement in Lilypond which goes beyond the TeX/LaTeX comparison.
I wanted to fill-out a two page orchestral part and Lilypond insisted
on filling only 1.7 pages leaving several inches blank on page 2. (You
may have already reviewed my comments in another thread.) I treated my
problem as a vertical spacing problem. Consulting the Lilypond manual
I was directed to section 5.5.1
(http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Vertical-
spacing-inside-a-system#Vertical-spacing-inside-a-system) which
suggested code like \override VerticalAlignment #'max-stretch =
#ly:align-interface::calc-max-stretch inside a Score context. Nothing I
tried solved my problem. After posting to the user's group, I got
several replies along the line of
ragged-last-bottom = ##f
raggedbottom = ##f
raggedbottomlast = ##f
Here's where I get baffled. (A priori) I don't know that these settings
exist and when I search on vertical spacing (within a system) in the
documentation, I am not directed to these settings. I certainly do
understand why these settings are relevant and why setting the desired
value solves my problem. It is just not easy to find the appropriate
settings in the documentation. This kind of problem is very typical for
me. (Perhaps it is the way I think?)
Cheerios,
Jeremiah
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
On Sun, 6 Jan 2008 17:15:34 +0100 Valentin Villenave [EMAIL PROTECTED] wrote: Plus, it includes the whole LilyPond Documentation as well, and searching for keywords is definitely much easier with this tool than with the very limited index -- AFAIK only Graham has ever used it ;) No bloody way. I always look in the table of contents. Of course, I already have a pretty good idea of where everything is. And also, since I never use lilypond myself, I don't really look up anything in the docs these days. I think Mats uses the index occasionally. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
On Sun, 6 Jan 2008 09:51:13 -0500 Reilly [EMAIL PROTECTED] wrote: package. The index often lacks entries for my questions. This is, fortunately, the easiest thing to fix. In the docs, index entries are made in the relevant section. So for example, in the Ambitus section, we might have something like @cindex ambitus @cindex Showing the range of pitches Adding more entries is extremely easy, *if* we have specific suggestions. I'm willing to bet that I can add a new entry within 30 seconds of getting an email. ;) Want to play? Here's the rules: - send me an email with index in the subject. - the format is like this: SECTION TITLE INDEX TEXT 1 INDEX TEXT 2 ... for example: - Easy notation note heads Showing note names Printing note names Beginners, showing note names Instrument transpositions transposing moving music up or down printing music in different keys these index entries are getting silly but they illustrate the point --- You can add as many entries as you like for each section. The section names (ie the first piece of text in each paragraph) must be written correctly (copy and paste from the docs), because I'll be searching for that piece of text. As an experiment, please take 10 minutes (right now? :) to add some index terms. I suspect that this is an easy task that you could do whenever you have a few spare minutes. The entries more often than not, do not address my problems. The coded examples are often too clever and don't illuminate my ignorance. Obviously everyone wants to make the documentation equal to the programming. That is why the GDP is underway. This is a much harder problem to address. For now, please read NR 1.1 Pitches and see if there's any entries that don't address the issues. Collect a team of Lilypond MUSIC Consultants. This could be the general lilypond-user group or a subset. Volunteer members would agree to answer questions. The GDP team should *not* spend time researching answers to musical or notational questions IF they can find a local Lilypond user who knows the answer. For instance, take the questions below: We tried that a bit last Oct / Nov. There were very few responses. However, I've started a list of GDP Consultants; hopefully if people specifically put their name on this list, they'll look for GDP: blah blah emails and respond more. (I've already added your name) Responding to Graham's public expression of ignorance, I will share my own: I am completely baffled by Lilypond code at least half the time. I don't understand Scheme. I don't get make-event. I don't That kind of tweaking is much more advanced than the current problem -- I still need people who understand the basic lilypond stuff. That said, please consider the checking the LM job. You'll learn a lot more about lilypond (including such tweaks), and we need people to check it. Make sure you read the GDP version, *not* the 2.11 version. A general *alert* to the GDP team: music notation is NOT standardized. We are quite aware of this -- and in any case, this is a general lilypond issues, not a documentation issue. Fortunately, lilypnod is extremely flexible and can deal with these situations. Again, I recommend checking out the new LM, specifically LM 4 Tweaks. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volunteering with LilyPond
On Sun, 6 Jan 2008 14:21:15 -0500 Reilly [EMAIL PROTECTED] wrote: Eyolf, On Jan 6, 2008, at 12:00 PM, [EMAIL PROTECTED] wrote: example, the problem is not so much knowing what it means -- that can be looked up quite easily It *can be*. But *I'm* not going to bother. Why should I? I don't know the instrument, I don't care about the instrument; if the users of that instrument can't be bothered to help, then I won't be bothered to write docs for them. A very real example of this: vocal music. Yes, most users of lilypond are vocal people. But I'm not. So I've never edited the Vocal music section -- despite the fact that it's the most-read section. How do we do divisi lyrics? How do we align syllabels to notes? I don't have a clue, and I don't care to have a clue. (at this point, nobody can seriously accuse me of being lazy or unhelpful, so I have no trouble being completely blunt about this) - but to know (a) what kind of variations does a user expect? does size matter? angle? are different symbols or styles in use, and are they informative variations, etc.; (b) figure out how to effect all these variations through Lilypond code; (c) choose how much of this is really needed in the docs, and how much of it can be written meaningfully without violating the don't comment the examples directly principle. These are also important... Perhaps I misunderstand the purpose of Graham's example question. The quality and useful of answers would depend on asking the RIGHT questions. ... but Reilly understood exactly my point. Here's an example -- the *only* example :) -- where I play the part of the helpful user. We'll pretend that Trevor Daniels (vocal guy) is editing the Orchestral string section. Trevor: What's this artificial harmonics garbage? Aren't all harmonics naturally occuring? Graham: It means you put two fingers on the string; the lower note is notated with a normal notehead, and the upper one is a harmonic. Trevor: cool. Like this? a cis\harmonic4 ? Graham: oops, sorry. No; it needs to be a fourth or a fifth. Like this a d\harmoinc2 bes ees\harmonic2 | a e\harmoinc2 bes fes\harmonic2 | Trevor: thanks, docs updated. (ideally I would have included the lilypond exapmle in my first reply, instead of waiting for another question from Trevor) If I didn't reply, Trevor *could* have found the answer. Maybe 15 minutes googling for the definition of artificial strings, maybe 10 minutes of figuring it out in lilypond... but as somebody who _knows_ orchestral strings, it only takes me 60 seconds to bash out a quick example. That saves Trevor almost half an hour of stumbling around in the dark -- all the while thinking this is stupid, a string player should be doing this stuff. Oh, and I could also point out Stravinksi's customary print the actual sounding pitch in a small black notehead above the two existing noteheads trick. Again, that's something that's trivial for a string player, but not at all obvious to a vocalist. In my experience, it is almost always more informative to ask someone who is an expert of sorts in the area I am confused. Exactly. I think we disagree slightly on how my proposal would work (or, perhaps, how people behave). If I have to notate a classical guitar passage and I consult the Lilypond documentation and I find it inadequate, it is expecting a lot of my --- aka, the casual music engraver --- to rewrite the documentation and send it to somebody. (I don't even know to whom I would send it.) After a bit of searching, you'd find http://lilypond.org/web/devel/participating/documentation-adding which directs you to either me or the -devel list. But yes, it *is* asking a lot. That's why we're doing GDP: a limited-time push to seek out anybody who could contribute (or simply be consulted), so that we can ask questions in advance. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating a book of music
On Sunday 06 January 2008, Nicolas Sceaux wrote: Le 6 janv. 08 à 21:56, Graham Percival a écrit : On Sun, 6 Jan 2008 21:50:38 +0100 Nicolas Sceaux [EMAIL PROTECTED] wrote: Le 4 janv. 08 __ 00:15, Reinhold Kainhofer a __crit : Are you thinking about turning your framework into a general lilypond-for-books package (with some documentation on how to use ;-) ) so that we ordinary lilypond users can also benefit from it? A book titling stylesheet has been published on LSR: http://lsr.dsi.unimi.it/LSR/Item?id=368 It requires a 2.11.something LilyPond version. This could be a problem; LSR is currently on 2.10.12. If you have any difficulty publishing it on LSR, you could try sending it ot Valentin privately; he can add it to LSR once it's been upgraded. Actually, that's what I've done: Valentin added it to LSR. nicolas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user I am pretty new to Lilypond and wanted to experiment with this sample, but no success. The stylesheet also has a lot of strange characters. I think they are not correctly stored in the document: * %%;; an accented character is seen as two characters by guile #(let ((lower-case-accented-string éèêëáà âäÃìîïóòà ´Ã¶ÃºÃ¹Ã»Ã¼Ã§Åæ) (upper-case-accented-string ÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃà ÅÃ)) My Lilypond version is 2.11.31 -- Thomas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating a book of music
2008/1/7, Thomas Spuhler [EMAIL PROTECTED]:
I am pretty new to Lilypond and wanted to experiment with this sample, but no
success.
Hi Thomas,
here's a small how-to:
-Download the file I'm sending with this mail
(It's just the LSR file, you could have copy/pasted it as well)
-Create a new file, in the same folder, and name it whateveryouwant.ly
-In this new file, paste the following code (taken from the LSR):
\version 2.11.36
\header {
title = The Title
composer = The Composer
poet = The Lyricist
date = 1740-1742
arrangement = ...
copyright = Copyright line
}
\paper {
%% Translate the TOC title
tocTitle = TABLE OF CONTENTS
}
\include book-titling.ily %% change this line accordingly to your filename.
\bookTitle Title for header
%% set to #f to turn off piece numbering
\useRehearsalNumbers ##t
%% Table of contents
\pageBreak
\markuplines \table-of-contents
%% 1st Chapter
\chapter Act I
\section Scene 1
\titledPiece \markup Overtura
\repeat unfold 12 { c'4 d' e' f' \break }
\section Scene 2
\piece \markup { Choir: \italic { bla bla bla } }
\repeat unfold 12 { g'4 f' e' d' \break }
\chapter Act II
\section Scene 1
\titledPiece \markup Overtura
{ c'4 d' e' f' g'1 }
-save this new file.
-compile it with LilyPond
-open the result with a PDF reader.
-now you can start changing the text elements, adding you own music,
staves etc (at the places where Nicolas has put some dummy \repeat
unfold notes.
The style sheet also has a lot of strange characters. I think they are not
correctly stored in the document:
Yes, they are :) It's an advanced susbstitution function, that detects
accented characters and makes sure that LilyPond will handle them
correctly (the code has been written to work even with foreign
languages).
Regards,
Valentin
book-titling.ily
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Polyphonic problem...
Ok, I tried with the 2.10 version (the only other lilypond version I have) and it works fine, maybe it's close to the 540 issue... Regards -- View this message in context: http://www.nabble.com/Polyphonic-problem...-tp14615208p14616301.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Orchestral score
I am stumped. I have a score with 22 staves, one system to a page. I want Lilypond to layout the score so that the the score fills the page. It would be very nice if the first staff and last staff on each page lined up when laid side by side. In other words, I want Lilypond to stretch the interstaff spacing appropriately for each page. I have searched the manual and the LSR without success. I've tried setting VerticalAlighment #'max-stretch = #ly:align-interface::calc-max-stretch without any change. In particular, the first page is the worst. Lilypond is pushing the staves way down (actually off) the page and leaving a large gap at the top between the title and the first staff. I am running 2.11.36. Much obliged, Jeremiah ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Volunteering with LilyPond 2nd posting
The previous discussion got a bit off-topic, so to make this easier to see I'm posting it again. I've updated the list of open jobs and posted it online: http://web.uvic.ca/~gperciva/lilyjobs.html Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
