Re: Example massacre
On 2-Dec-04, at 10:40 AM, Mats Bengtsson wrote: I mentioned one in my original email. I haven't investigated deeply, but spent a few minutes to find missing example files that are linked from within the manual, and came up with the following list: I must admit that I haven't been checking the "see also" to links. In the future I'll check to make sure they work and still make sense. In input/test/: chords-without-melody.ly As Han said, it's actually included in the text now. Link removed. lyric-hyphen-retain.ly I've included it in the manual, although commented out -- I can't test it right now, and that's one change that I should test before committing in un-ignored form. lyrics-melisma-faster.ly lyrics-melisma-variants.ly I can't find these examples in 2.2, 2.0, or 1.6; links removed. page-breaks.ly Nothing interesting in that example; I have no idea why it was included in the first place. to-xml.ly Fixed directory to point to no-notation. unfold-all-repeats.ly That's a nice example, re-added to input/test/ Han: I might move it into the manual when I revamp the "changing defaults" section, but right now the manual page that talks mentions this example is long enough already. In input/regression/: volta-chord-names.ly Not necessary; covered by volta-multi-staff.ly Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: percussion notation issues
I don't know anything about percussion notation, but this might be of interest to lilypond-devel as well. - Graham On 22-Dec-04, at 6:50 AM, Bruce McIntyre wrote: Hello all. I've just finished reading through Norman Weinberg's _Guide to Standardized Drumset Notation_ published by the Percussive Arts Society (1998). I've put up a synopsis of some of the more important points at http://home.iprimus.com.au/brucemcintyre/percussion-notation.png Note the numbers on the toms. If you need to describe music for 3 toms, use toms 1, 2 and 3. If you want 6 toms use toms 1, 2, 3, 4, 5 and 6. The pitch of each tom is governed by its height as in normal music--tom 9 is higher than tom 1; tom 10 lower. The notation conventions recommended by Mr Weinberg have been adopted by Modern Drummer Magazine, the various PAS publications as well as publishers such as audiograffiti (http://www.audiograffiti.com.au/doc/audiograffitidrumnotation.pdf) berklee and others. Lilypond's drum notation is missing a few features to implement this scheme: 1. Rimshot notation (where a \ overlays the notehead) 2. Crosstick notation (circle surrounding notehead). 3. The "ghost" note, where the notehead is in parentheses. This can be implemented by molecule call backs, but looks kludgy at the moment. 4. Lilypond's naming conventions don't support enough instruments: 10 toms are needed (I personally don't own that many!) 2 hihats 2 rides 3 crashes 5. Some symbol shapes are wrong: The triangle should be equalateral with the base parallel with the staff lines. Here noteheads-d1do and noteheads-d2do would suffice. The symbol for a minim or semibreve cymbal should not be an open 'x' but an open diamond, somewhat like that used for harmonics. 6. Lilypond lacks the mallet symbols as well as the bell/edge center/edge symbols. Personally I find Norman's Bell and Edge symbols ugly. The latter especially is frustrating as it projects out to the right of the note colum. Rod Morgenstein in his _Drum Set Warm-Ups_ follows this scheme, but uses cross with circle surrounding for a cymbal bell indication. Often drummers will alternate between ride cymbal bell and normal strokes every other quaver or semiquaver. Morgenstien's scheme is much less cluttered-looking than Weinberg's when this is notated. I hope this email provides some ideas for future improvements to our beloved Lilypond. Cheers, Bruce. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
LilyPond MediaWiki extension, v2
Hi, I hereby announce the 2nd version of my LilyPond extension, which has these new features (but still using LilyPond's safe mode): If run with ..., all pages are displayed (as PNGs), not only one note line. Also, if your code requests a midi file, by clicking on one of the PNGs you can download that. If you want midi output for a fragment, just use instead of . You can find this extension at: http://lily4jedit.sf.net/mediawiki-LilyPond-extension-v2.tar.gz Ciao, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Triplets at the other direction
On 18-Dec-04, at 8:22 AM, Mats Bengtsson wrote:
Joshua Koo wrote:
Hi,
When I have triplet, the 3 is in the same direction of the stems (eg.
3 is at the bottom if stem are down) . However I like it at the side
of the note head, which means the opposite direction the stem are
facing. (eg. I would like the 3 to be above the notes when stems are
down).
If I were to use the \tupletUp or \tupletDown then I would have to
specify every triplets I have. Is there a \trupletOpposite? Or maybe
there's ae property to be set to negative?
As far as I know, this is not supported for the moment, but it might
be a nice feature to
have an additional possible value for the direction property of any
object, which means
do the opposite of the default value (the latter part of the answer is
intended for the
developers).
Interesting idea. Couldn't this be done with repeats, tupletUp/Down,
and
part combining?
I'm not certain of the syntax, but something like this?
opposites= {
\repeat unfold 8 { \tupletUp s4 \tupletDown s4}
}
music = {
blah blah
}
\score{
<< \opposites \music >>
}
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
