File: README

package info (click to toggle)
lilypond 2.2.6-3
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 11,260 kB
  • ctags: 7,622
  • sloc: cpp: 47,787; lisp: 11,217; python: 11,203; sh: 3,290; yacc: 2,011; lex: 831; perl: 373; ansic: 309; makefile: 132; csh: 8
file content (51 lines) | stat: -rw-r--r-- 1,451 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

* Naming conventions for voices/staves
  (think: \autochange, \partcombine)?

* Add (commented-out) stuff like \time 3/4
  \property Staff.TimeSignature \set #'style = #xxx?

* Handy emacs shortcuts to (these) templates?

* Mutopia headers?

* Another approach would be to not include any music in the templates,
  and standardise the naming of the music, so that you'd do:

    title = 'Piano piece'
    upper = \notes { ... }
    lower = \notes { ... }

    \include "template/piano.ly"

  In this case, we'd also need one simple music example file per
  template.  This approach can be even easier to use, but is not very
  flexible, it only works for simple and uniform pieces.

* Possibly some of you already have created something like this?  I was
  thinking of having templates for:

  single melody  = melody.ly
  melody with lyrics = melody-lyrics.ly 
  melody with lyrics and chords = melody-lyrics-chords.ly
  piano = piano.ly
  piano with several voices = piano-4-voices.ly
  piano with lyrics (between staves) = piano-lyrics.ly
  piano with melody and lyrics = piano-melody-lyrics.ly

TODO (Choral templates, anyone?)
  piano with lyrics and chords
  (string) duet 
  (string) duet parts
  string quartet
  string quintet parts
  orchestral score
  orchestral parts
  choral score with piano reduction (i.e., the piano staves have the
          same notes as the choral parts)
  choral score with piano accompaniment
  choral parts