Re: templates

[Mats Bengtsson]

Great that you want to contribute!

Some comments:

- Citing the introductory text of the LSR: "LSR is a place where people
  can contribute there creative ideas ...these ideas are represented by
  snippets of Lilypond sources—small examples, short and to the point,
  that show a particular feature or a hack."
  I have myself argued that LSR is also a place for "templates", i.e.
  examples of how to organize an .ly file.
  Before you submit your score, take a moment to consider what it really
  is you want to illustrate. The impression I got when looking at your
  example was that it illustrated a large number of different things.
  Maybe it's better to cut it down and separate out several snippets
  where each is more focused on some specific aspect?

- Add comments in the code to make it easier for others to follow
  what you are doing.

- See below for specific comments on the issues you brought up.

Peter Mogensen wrote:
> Peter Mogensen wrote:
>
> > Thanks... I was wondering. Since there's many ways to do things in
> > Lilypond, there's also many ways to do them wrong.
> > Are there some kind of review process when I add to the repository?
>
>
> Anyway... He're an example (I think there's no copyright problems with
> this one):
>
> http://bigendian.dk/lily/
>
> Please tell me if you think it's good enough to upload.
>
> As I said, it's not perfect. When I look at the source, I can think of
> the following problem/hacks:
>
> * Ties are not continued into second endings

The standard trick is to add a tie from an invisible note. You can
find several examples in the mailing list archives.

> * There's no support for flams, ruffs and rolls in Lilypond (slip=flam)
Here you can also find some examples of solutions in the mailing list
archives, using embedded postscript commands.

> * I had to make ghost gracenotes in the other instruments because of
>   flams in the snare voice
> * It's difficult to get rehearsalmarks to not collide with volta and
>   other text like "Fine" and metronome indications.

The standard solution is to move all rehearsal marks upwards by
increasing the padding property.

> * I was lucky with this piece that tremolo strokes were not needed on
>   any beamed notes (to simulate ruffs and rolls). Beames would have
>   caused them to align to the beam, producing wrong results.
> * When you create a \book, you can change the "piece" text for each
>   piece, but you can't change the "instrument". So I used "piece"

Read about printallheaders in "10.1.4 Page formatting" in the manual.

> * The final partial meassure has a "r4", which doesn't show. The reason
>   is that I had to use "R4" to get the staff hidden when empty. (look
>   the last measure of the drumStaff)
One possible workaround is to use the \tag feature described in
"8.2.8 Different editions from one source"

> * When using a one-line staff, rehearsalmarks think they can move closer
>   to the remaining line... and then they collide with the bars :(

Send an example to bug-lilypond.

> * Bar numbers collide with StaffGroup braces.

Well-known problem. Just increase the padding of the BarNumber
layout object.

> * I had to do a wierd hack to the last full measure of the snare and
>   explicitly write the beam. Else Lilypond would place to stroked 8ths
>   instead... Don't know why.
>
>
> ... oh.. .and don't mind the MIDI-info. It's probably broken.
>
> Peter


   /Mats