Set up a lilydrum file in the same way as there is a bagpipe.ly. Main focus is on pipeband (snare) drumming. https://deboone.nl/lilydrum
Go to file
ET de Boone 4ddf2e4bec Added License 2016-11-24 15:39:31 +01:00
lilydrum Various updates 2016-11-23 03:24:56 +01:00
.gitignore Decided to put all the music files in a separate git 2015-12-18 13:03:14 +01:00
LICENSE.md Added License 2016-11-24 15:39:31 +01:00
README.md put todo into README.md 2016-10-26 10:30:55 +02:00
cheatsheet.ly Various updates 2016-11-23 03:24:56 +01:00
lilydrum.ly Various updates 2016-11-23 03:24:56 +01:00
makedrum Can ignore lilydrum and -pipe files by setting --drumfile '' 2016-10-27 15:07:45 +02:00

README.md

pipeband-drumming

First trial with github, purpose is to set up a lilypond file in the same way as there is a bagpipe.ly (see github.com/svenax/bagpipemusic). Main focus is on pipeband snare drumming.

Somehow, the drums part in lilypond does not cover a notation with only right left. That is right is above the line and left is below it. In the same manner as the bagpipe.ly file, flams and drags are defined as a shortcut.

There has been a lilypond include file earlier made by Simon Froger (which includes all of the above). So first version is a shameless copy. This is meant to extend or translate some parts.

The original file can still be found at http://lsr.di.unimi.it/LSR/Snippet?id=970

As the repo has been torn apart to separate these files from an actual music repo, you can find most of my music on github, there's even a 'master repo' which should set up most of the environment needed to compile this music (also pulling in svenax's bagpipemusic).

##TODO

  • See if aliases work foo = { \bar }

  • show 8th and 16th beats in autobeaming, currently only 8ths: d32 g] d[ g d32 g] d[ g

  • Macro for tutti's (unisons)

    • on just one note
    • with open ending
  • Macro for "Part $m of $n"

  • If 8/16/32/..th notes come before a flam, they have a flag instead of a beam (fixable by explicit beaming, but rather have a good autobeaming)

  • A tuplet beginning with a flam has a strange tuplet beam (slanted) (fixable by putting the flam outside of the tuplet .. However the flam function doesnt work that way (yet))

  • It's customary to have 4 bars per line for portrait and 8 for landscape... (most of the time this can be accomplished by \break-ing every 8 measures and having enough notes in)

  • SIDE sticking rimshot default + cross

  • FLOURISHING short long note above-note ups \up arrow-up ( I don't like the arrow I scripted ) scoop \scoop arrow-right-(diag-up then diag-down) [propably start on beginning of note and filter out the last one] further EUSPBA symbols