Re: GDP: welcome, helpers!
Quoting Trevor Bača [EMAIL PROTECTED]: One concern: is Ravel mutopia-worthy? How long has he been dead? I hate to ask, but... :( Ravel died in 1937 but the Sonatine was finished earlier, in 1905 (http://en.wikipedia.org/wiki/Sonatine_%28Ravel%29). Isn't copyright something like 75 years max? If so the Sonatine should be public by now, though it's possible that any of his various publishers along the way may have taken out renewals or something. Please read the information at Mutopia, that was referred in an earlier email, before spreading rumors like this. The 75 years are after the death of the composer (or arranger or whoever holds the copyright). Please somebody correct me, but my understanding of fair use is that a snippet of absolutely anything, regardless of medium -- score, soundfile, text, film, whatever -- is perfectly acceptable to use, so long as you're not trying to make any money with it (which we're in the bizarrely unique position of). So I would assume that a snippet of any score -- even a bit of Grisey published only a couple of years back -- should be completely acceptable; I seem to remember the upward limit being something like no more than 10% of a work quoted, even if in separate fragments. I'm certainly not a lawyer, but I've learned that you should be extremely careful with copyrighted material and would therefore recommend to replace the snippet with something were we are certain about the copyright status (which really is a pity, since it's a nice example). 2. Is there a way to set slur attachment points to *end-of-stem* rather than notehead? The two-note chordal slurs would look better that way. If it's intensely manual I don't wanna mess with it; but if there's a smart way to make that specification, then cool. IIRC this feature was removed in 1.6 or so (because it wasn't a smart way :) and was never re-implemented (in a smart way). Hm, I thought I remembered as much, but couldn't be sure. OK, it's not a requirement. What *is* a requirement is getting rid of that hideous line-breaking with the slurs at the beginning of line two. Perhaps someone else on the list can help clean up the example and answer some of my earlier questions about the Ravel fragment ... or perhaps not since my posts to both user and devel were rejected do violating our 64k message size limit ... which still, years on, makes absolutely no sense to me. Have you tried using phrasing slurs instead of ordinary slurs? I seem to recall that they sometimes behave differently at line breaks. /Mats ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: welcome, helpers!
On 9/25/07, Mats Bengtsson [EMAIL PROTECTED] wrote: Quoting Trevor Bača [EMAIL PROTECTED]: One concern: is Ravel mutopia-worthy? How long has he been dead? I hate to ask, but... :( Ravel died in 1937 but the Sonatine was finished earlier, in 1905 (http://en.wikipedia.org/wiki/Sonatine_%28Ravel%29). Isn't copyright something like 75 years max? If so the Sonatine should be public by now, though it's possible that any of his various publishers along the way may have taken out renewals or something. Please read the information at Mutopia, that was referred in an earlier email, before spreading rumors like this. The 75 years are after the death of the composer (or arranger or whoever holds the copyright). Mats (and Graham), Please understand that there is a difference between piracy and citation. No one is proposing the addition of a playable or readable copy of anything to Mutopia or any other resource. Turns out ... http://en.wikipedia.org/wiki/Fair_use ... that fair use is American law. Perhaps that explains the confusion on the list. Trevor. -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: welcome, helpers!
Trevor Bača wrote: Please understand that there is a difference between piracy and citation. No one is proposing the addition of a playable or readable copy of anything to Mutopia or any other resource. Turns out ... http://en.wikipedia.org/wiki/Fair_use ... that fair use is American law. Perhaps that explains the confusion on the list. Trevor, Unfortunately you are incorrect. Instead of pointing to wikipedia, at the very least I would recommend reading http://www.templetons.com/brad//copymyths.html This page is not authoritative by any means, but it is much more trustworthy than wikipedia. Fair use is an American construct, but countries in the British Commonwealth have Fair dealing. Similar legislation exists for non-commonwealth countries, although I wouldn't presume to be able to spell whatever the Dutch or Finnish law is. Fair use is not a blanket allowance for copying small sections of a copywritten work. In my non-expert, no-legal-training opinion, it is designed for copying a small portion for the purpose of reviewing the work, such as a scholarly article or newspaper review. Unfortunately, the lilypond manual is not such a document. I would also like to reinforce my distinction between morality and legality. I have infringed on copyrights -- I have photocopied an entire cello concerto from a friend so that I could see her fingerings and bowings. I owned my own copy of the concerto, but I wanted to see her personal annotations. This was illegal -- I should have copied her markings by hand, or borrowed her music for a few weeks. But I was certain that my action was morally justified (I owned an identical copy of the music, and I only wanted to see her annotations so I could combine them with my own, I wasn't seeking or offering financial compensation, etc), so I infringed the copyright without any guilt. However, my personal beliefs about the morality of copyright should not influence whether we include material in the lilypond manual. Do I think that there are any _moral_ problems with including that short fragment of Ravel? No, not at all. The notion that this might be ethically wrong is laughable. Am I certain that there are no _legal_ problems? Unfortunately, no. With the deepest of regret, I have removed this example until 1 January 1, 2008. At least this date is not too far away; the example will certainly be in the 2.14 release. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: welcome, helpers!
On 9/21/07, Graham Percival [EMAIL PROTECTED] wrote: I've posted initial instructions for GDP helpers here: http://opihi.cs.uvic.ca/~gperciva/helper.txt If somebody could send those to the list (as a reply to this), that would make it easier for other people to read. ASIDE: I wouldn't believe this if I didn't see it for myself, but attempting to send that email to the list causes the switch in my parent's house to stop working. My brother theorizes that the power output of my ethernet interface is too high, and thus it disrupts the router when I attempt to send large packets. We tried repeated experiments, and this is 100% repeatable -- when I attempt to send that message, via SMPT (to gmail), HTTP (via gmail webmail), or even scp (to the current host), our switch stopped working. I had to bzip that text file in order to scp it. (!) We're not idiots or unfamiliar with computers -- I'm doing a Masters in the subject, and my brother has a Ph.D in computer science. This is totally amazing. Hi Graham, Trevor, IIRC you didn't officially sign up as a helper, but you're in charge of the Inspirational Headwords. If you could come up with something for Pitches and Rhythms soon, that would be awesome. Remember that these don't need to be existing, famous pieces of music; a portion of your own compositions would be great for Rhythms. Also remember that we can always update stuff later. Let's get something to slap in there to demonstrate the concept. :) Will do. Also, your power shenanigans are bizarre ... ;-) -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: welcome, helpers!
Trevor Bača wrote:
Something like this? These are the closing measures of the first
movement of the Ravel sonatine.
Other than the things you mentioned, looks great. See it in action here:
http://opihi.cs.uvic.ca/~gperciva/lilypond/Documentation/index.html
One note: click on the image, and see the source. All the headwords
will have the same \paper{} section; you simply create great stuff in
the ly snippet section. This way you should be able to see exactly
what the doc output will look like.
If you'd rather have the headwords with slightly different
specifications (larger font, slightly changed line-widths), that's
possible... but I'd like every headword to have the same specs.
Don't miss the #(set-global-staff-size) -- that should be placed inside
the cut--paste section. I'll file a bug report about that.
One concern: is Ravel mutopia-worthy? How long has he been dead? I
hate to ask, but... :(
2. Is there a way to set slur attachment points to *end-of-stem*
rather than notehead? The two-note chordal slurs would look better
that way. If it's intensely manual I don't wanna mess with it; but if
there's a smart way to make that specification, then cool.
IIRC this feature was removed in 1.6 or so (because it wasn't a smart
way :) and was never re-implemented (in a smart way).
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: welcome, helpers!
Graham Percival wrote: One concern: is Ravel mutopia-worthy? How long has he been dead? I hate to ask, but... :( Wikipedia lists his date of death as 28 Dec 1937, so his music will go out of copyright in most of the world on 1 January 2008. To be extra safe, you should stick to music first published before 1923 to ensure that it is out of copyright in the USA. See the Wikipedia Public Domain page for more info: http://en.wikipedia.org/wiki/Public_Domain Regards, Chris -- Chris Sawer - [EMAIL PROTECTED] - Mutopia team leader Free sheet music for all at: http://www.MutopiaProject.org/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: welcome, helpers!
On 9/24/07, Graham Percival [EMAIL PROTECTED] wrote:
Trevor Bača wrote:
Something like this? These are the closing measures of the first
movement of the Ravel sonatine.
Other than the things you mentioned, looks great. See it in action here:
http://opihi.cs.uvic.ca/~gperciva/lilypond/Documentation/index.html
Oh wow. The exact image is at ...
http://opihi.cs.uvic.ca/~gperciva/lilypond/Documentation/user/lilypond/Pitches.html#Pitches
... and looks great to my eyes (minus the slur gripes I mentioned in
the previous mail).
Question: is the amount of the Ravel example what you're looking for?
I think you had said 8 staves total (either 8 *1 or else 4 * 2 or else
2 * 4 or else 1 * 8)? This is only half that amount, but looks right
to my eyes. What do you think?
One note: click on the image, and see the source. All the headwords
will have the same \paper{} section; you simply create great stuff in
the ly snippet section. This way you should be able to see exactly
what the doc output will look like.
Perfect. This is exactly what I was looking for.
If you'd rather have the headwords with slightly different
specifications (larger font, slightly changed line-widths), that's
possible... but I'd like every headword to have the same specs.
Yes, agreed.
Don't miss the #(set-global-staff-size) -- that should be placed inside
the cut--paste section. I'll file a bug report about that.
OK.
Question: should the global-staff-size be the same for all headwords?
I'm leaning towards yes ... I'll see if I can make it happen.
One concern: is Ravel mutopia-worthy? How long has he been dead? I
hate to ask, but... :(
Ravel died in 1937 but the Sonatine was finished earlier, in 1905
(http://en.wikipedia.org/wiki/Sonatine_%28Ravel%29). Isn't copyright
something like 75 years max? If so the Sonatine should be public by
now, though it's possible that any of his various publishers along the
way may have taken out renewals or something.
Please somebody correct me, but my understanding of fair use is that a
snippet of absolutely anything, regardless of medium -- score,
soundfile, text, film, whatever -- is perfectly acceptable to use, so
long as you're not trying to make any money with it (which we're in
the bizarrely unique position of). So I would assume that a snippet
of any score -- even a bit of Grisey published only a couple of years
back -- should be completely acceptable; I seem to remember the upward
limit being something like no more than 10% of a work quoted, even if
in separate fragments.
At any rate, there are three separate copyright strategies (at least)
that we can take with the headwords:
1. Use only stuff that we're absolutely certain is public domain,
which in our case means tonal stuff from the common practice;
2. Use whatever we want, so long as we're respect fair use guidelines
in a professional way;
3. Write our own examples.
Copyright strategy #1 is certainly the safest and there is without
doubt an abundance of beautiful material in scores of the common
practice. But many of the most beautiful scoring achievements of all
live in later centuries.
Copyright strategy #2 should be fine. This is the point of fair use, after all.
Copyright strategy #3 is actually a possibility for our team -- we
have a community of composers available (and I'm not just guessing
here -- I've traded score with many new friends on the list, and I've
been quite astounded in some cases). So this might ultimately be the
most interesting strategy of all -- commission each chapter's headword
from a different composer on the list. I'll get the ball rolling by
hacking up an original headword for 1.2 Rhythms, just as you had
suggested. If the example works (beautiful and characteristic of Lily,
both interesting and inviting) then maybe we can ask some of the other
composers on the list to contribute, too, or extend an open
invitation; I'd be happy to help guide the process and make
selections.
2. Is there a way to set slur attachment points to *end-of-stem*
rather than notehead? The two-note chordal slurs would look better
that way. If it's intensely manual I don't wanna mess with it; but if
there's a smart way to make that specification, then cool.
IIRC this feature was removed in 1.6 or so (because it wasn't a smart
way :) and was never re-implemented (in a smart way).
Hm, I thought I remembered as much, but couldn't be sure. OK, it's not
a requirement.
What *is* a requirement is getting rid of that hideous line-breaking
with the slurs at the beginning of line two.
Perhaps someone else on the list can help clean up the example and
answer some of my earlier questions about the Ravel fragment ... or
perhaps not since my posts to both user and devel were rejected do
violating our 64k message size limit ... which still, years on, makes
absolutely no sense to me.
If anyone else is following this thread and wants to look at the
proposed snippet for 1.1 Pitches, please click
Re: GDP: welcome, helpers!
Trevor Bača wrote: ... and looks great to my eyes (minus the slur gripes I mentioned in the previous mail). Well, the slur across the key signature looks _awful_... but maybe that'll encourage new developers to tackle more bugs. :) Question: is the amount of the Ravel example what you're looking for? I think you had said 8 staves total (either 8 *1 or else 4 * 2 or else 2 * 4 or else 1 * 8)? This is only half that amount, but looks right to my eyes. What do you think? IIRC I said 4 staves, so this is perfect. :) (I'm pretty certain that I _did_ say up to 4 single-staff lines; I'm not just making this up) Question: should the global-staff-size be the same for all headwords? I'm leaning towards yes ... I'll see if I can make it happen. Yes, but that's part of the file that's auto-generated. (not part of your ly snippet area) Please somebody correct me, but my understanding of fair use is that a snippet of absolutely anything, regardless of medium -- score, soundfile, text, film, whatever -- is perfectly acceptable to use, so long as you're not trying to make any money with it (which we're in the bizarrely unique position of). Err... no, that is totally incorrect. Movie piracy (on the internet, not in physical form) is almost entirely not trying to make money with it, but is forbidden by law in most countries. (let's not get sidetracked by a discussion about morality; I'm only addressing the legal status of fair use or fair dealing, as I understand them with my non-expert knowledge, in Western countries) So I would assume that a snippet of any score -- even a bit of Grisey published only a couple of years back -- should be completely acceptable; I seem to remember the upward limit being something like no more than 10% of a work quoted, even if in separate fragments. Again, no. Many university post a no more than 10% of the work rule in various places, but that's already using their special educational exceptions. 2. Use whatever we want, so long as we're respect fair use guidelines in a professional way; I'm not positive that fair use applies in this case. If we were evaluating the musical worth of Ravel -- particularly if we were comparing it to something else -- then quoting six bars is totally fine. But we're not reviewing his work; we're using his music as an example of our typesetting quality. 3. Write our own examples. This is my preferred option. That's why I started composing, after all. So this might ultimately be the most interesting strategy of all -- commission each chapter's headword from a different composer on the list. I'll get the ball rolling by hacking up an original headword for 1.2 Rhythms, just as you had suggested. If the example works (beautiful and characteristic of Lily, both interesting and inviting) then maybe we can ask some of the other composers on the list to contribute, too, or extend an open invitation; I'd be happy to help guide the process and make selections. I would rather not go this route. I'm all for composers contributing their own work, but not in any kind of competitive manner. I could easily see this getting out of hand. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
GDP: welcome, helpers!
I've posted initial instructions for GDP helpers here: http://opihi.cs.uvic.ca/~gperciva/helper.txt If somebody could send those to the list (as a reply to this), that would make it easier for other people to read. ASIDE: I wouldn't believe this if I didn't see it for myself, but attempting to send that email to the list causes the switch in my parent's house to stop working. My brother theorizes that the power output of my ethernet interface is too high, and thus it disrupts the router when I attempt to send large packets. We tried repeated experiments, and this is 100% repeatable -- when I attempt to send that message, via SMPT (to gmail), HTTP (via gmail webmail), or even scp (to the current host), our switch stopped working. I had to bzip that text file in order to scp it. (!) We're not idiots or unfamiliar with computers -- I'm doing a Masters in the subject, and my brother has a Ph.D in computer science. This is totally amazing. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: welcome, helpers!
Graham Percival wrote:
I've posted initial instructions for GDP helpers here:
http://opihi.cs.uvic.ca/~gperciva/helper.txt
If somebody could send those to the list (as a reply to this), that
would make it easier for other people to read.
The instructions:
Sorry again for the delay in getting this part organized. We still have
some technical problems, but resolving those will probably take at least
a month. I've identified some things that we can work on, which won't
depend on whether or not the technical stuff is fixed.
TRIVIAL/EASY HELPERS
We're going to work on these sections at first:
Tutorial
Pitches
Rhythms
Expressive marks
Simultaneous notes
Staff notation
Educational use
I'm still finalizing your exact instructions (see the email GDP:
documentation guidelines), but it will probably take a week to get into
our workflow.
The plan is this: you all sign up for one section (first-come,
first-choose; send emails to both me and the list, so you can see what
other people have chosen). Then you work on that section for one week.
At the end of that week, you send me whatever you've done, and I'll
put it back together. Then you all pick another section, and do similar
work on that.
I hope to have each section examined at least three times. It's not
that I don't trust you, it's that... well, ok, I don't trust you. :)
But in this context, I don't even trust myself: I always thought that I
was careful to write the docs correctly, but I've found many many
mistakes in my previous work.
Another reason why we will rotate the sections like this is to reduce
stress. When you go through the docs, fix what you can, but if
something is too confusing, you can leave it for the next person. For
example, if you don't feel confident about fixing English grammar, you
could leave a comment that a rewrite was necessary, and simply continue
fixing the formatting issues. Alternatively, if you are confident about
grammar but not LilyPond input, feel free to concentrate on the grammar
and ignore lilypond stuff.
WORKING
If you're comfortable with git (or svn/cvs) or diff, let me know. I'm
assuming that you're not familiar with those programs, so don't worry if
you've never heard of them before.
Take a look at the files here:
http://opihi.cs.uvic.ca/~gperciva/gdp/
These are the source files of the documentation. Pick one -- say,
tutorial.itely -- and compare that text file with the pdf or html docs.
You should be able to pick out a few major things:
@node Foo
@subsection Foo
is a standard portion of the documentation.
@lilypond[blah,blah,blah]
...
@end lilypond
produces a lilypond example.
@ref{other_section_name} produces a link to that section.
The language is called texinfo; you can see its manual here:
http://www.gnu.org/software/texinfo/manual/texinfo/
but you don't _need_ to read those docs. The most important thing to
notice is that text is text. If you see a mistake in the text, you can
fix it. If you want to change the order of something, you can
cut-and-paste that stuff into a new location.
Try downloading one of the files (ideally the one that you're planning
on picking -- for example, if you want to work on Rhythms, download
rhythms.itely) and make a few small changes with a text editor, then
send it back to me.
I should repeat: make a FEW, SMALL changes. It will probably take a few
tries until we're comfortable working on the .itely files, so I might
need to say sorry, that didn't work. Please download the file again,
make those changes (in a slightly different way), then send me the new
file.
MEDIUM HELPERS
You should probably follow the same steps as the trivial/easy people (in
regards to downloading a file and sending me an updated file), just for
practice. The following items have priority:
- tutorial 2.4 Songs. This is the weakest part of the tutorial; does
anybody want to rewrite or add more material here?
- polyphony: we need to move some (or all) of the explanations into the
Learning Manual (particularly Fundamental concepts). Volunteers?
- take a careful look at Pitches and Rhythms; find broken examples, make
a list of new things we should cover, start planning a rewrite of any
sections which are too complicated.
If you're interested in the third point, just make notes by yourself for
now. I'll post a more in-depth examination of those two sections in a
few days, and the discussion can progress from there.
Trevor, IIRC you didn't officially sign up as a helper, but you're in
charge of the Inspirational Headwords. If you could come up with
something for Pitches and Rhythms soon, that would be awesome. Remember
that these don't need to be existing, famous pieces of music; a portion
of your own compositions would be great for Rhythms. Also remember that
we can always update stuff later. Let's get something to slap in there
to demonstrate the concept. :)
Cheers,
- Graham
--
Michael Rasmussen, Portland Oregon
Be
Re: GDP: welcome, helpers!
On 9/23/07, Trevor Bača [EMAIL PROTECTED] wrote:
On 9/23/07, Trevor Bača [EMAIL PROTECTED] wrote:
On 9/21/07, Graham Percival [EMAIL PROTECTED] wrote:
I've posted initial instructions for GDP helpers here:
http://opihi.cs.uvic.ca/~gperciva/helper.txt
If somebody could send those to the list (as a reply to this), that
would make it easier for other people to read.
ASIDE: I wouldn't believe this if I didn't see it for myself, but
attempting to send that email to the list causes the switch in my
parent's house to stop working. My brother theorizes that the power
output of my ethernet interface is too high, and thus it disrupts the
router when I attempt to send large packets.
We tried repeated experiments, and this is 100% repeatable -- when I
attempt to send that message, via SMPT (to gmail), HTTP (via gmail
webmail), or even scp (to the current host), our switch stopped working.
I had to bzip that text file in order to scp it. (!)
We're not idiots or unfamiliar with computers -- I'm doing a Masters in
the subject, and my brother has a Ph.D in computer science. This is
totally amazing.
Hi Graham,
Trevor, IIRC you didn't officially sign up as a helper, but you're in
charge of the Inspirational Headwords. If you could come up with
something for Pitches and Rhythms soon, that would be awesome. Remember
that these don't need to be existing, famous pieces of music; a portion
of your own compositions would be great for Rhythms. Also remember that
we can always update stuff later. Let's get something to slap in there
to demonstrate the concept. :)
Will do.
Hi Graham,
Something like this? These are the closing measures of the first
movement of the Ravel sonatine.
I whipped this up just now right after getting back from a jog. If
this is what we're looking for, then I have a couple of questions:
1. What on earth is going on with the slurs across the line break?
Good heavens. Anyone know a way to get rid fo the ugliness at the
beginning of the second line crossing through the key signature? (If
not, I'll remove breaking slurs entirely.)
2. Is there a way to set slur attachment points to *end-of-stem*
rather than notehead? The two-note chordal slurs would look better
that way. If it's intensely manual I don't wanna mess with it; but if
there's a smart way to make that specification, then cool.
3. Anyone know why the exta-offset on the final arpeggio seems to do
nothing? The arpeggio should nudge ever so slightly to the left to
avoid collision with the fermata.
4. If we do go with this snippet (for pitches, for example), I'd like
to tweak the line breaking and spacing on the actual doc site to make
sure the notation breathes enough; the rendering here is far too
crowded (but I don't know the line length details that we're going to
use on the doc site so I haven't bothered tweaking).
5. Can somebody with the score handy please proof? I whipped this up
pretty quickly and I'm sure there's something fun hiding in there
somewhere.
Oh, and here's the input:
%%% BEGIN RAVEL %%%
\version 2.11.33
\include english.ly
#(set-global-staff-size 20)
\layout { indent = #0 }
\new PianoStaff
\set PianoStaff.connectArpeggios = ##t
\new Staff {
\time 2/4
\key fs \major
\new Voice {
\voiceOne
fs''8 (
^ \markup \column {
\line \bold { Un peu retenu }
\line \italic { très expressif } }
es''16
cs''16
as'4 )
|
fs''8 (
es''16
cs''16
as'4 )
|
fs''8 (
es''16
cs''16
as'8
cs''8 )
|
}
\new Voice {
\voiceTwo
r8 \ppp
fs'4 (
es'8 )
|
r8
fs'4 (
es'8 )
|
r8
fs'4 (
es'8 )
|
}
\clef bass
ds b! es'4 (
^ \markup \bold { Rall. }
\once \override Script #'padding = #2
ds' as'8 ) \fermata
\noBeam
\clef treble
\slurUp
as fs'8 ( \pp
|
gs b cs'4. )
^ \markup \bold { a tempo }
\slurUp
as fs'8 (
|
gs b cs'4. )
\new Voice {
\voiceOne
as fs'8 (
^ \markup \bold { Rallentando }
|
cs'8
b16
cs'16
d'8
e'16
fs'16
|
as! cs' gs'4. )
s8
|
r8
cs'' as'' cs'''4 \arpeggio
e''16 (
^ \markup \bold { Lent }
fs''16
|
\stemDown
as'! cs'' gs''2 )
|
}
\new Voice {
\voiceTwo
Re: GDP: welcome, helpers!
Michael Rasmussen wrote: Graham Percival wrote: I've posted initial instructions for GDP helpers here: http://opihi.cs.uvic.ca/~gperciva/helper.txt I'll take pitches for $100, er first week. Graham, for the git-able among us what is the path to the git repository? (let's keep this on the mailist, in case I mis-typed somebody's email address... and in case this encourages more people to join. :) Great! We have our first claim; Michael Rasmussen is doing Pitches. We're using the lilypond/gdp branch. The lilypond repo is... actually, I don't know. See the Developing pages on the lilypond website; the address is there. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
