Message: 3
Date: Tue, 29 Oct 2019 14:21:48 -0400
From: "Christopher R. Maden" <address@hidden>
To: address@hidden
Subject: Re: Doing A Fiddle Tunebook in Lilypond
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8; format=flowed
On 10/29/19 1:14 PM, Solomon Foster wrote:
> I've been using Lilypond to render fiddle tunes for nearly a decade
> now, and I'm looking at taking the next step -- namely making a
> proper, large scale tunebook with it. While the book I'm working on
> right now has hundreds of tunes, it's not mine to redistribute, so
> I've put together a quick PDF with some of my own tunes so you can
> get the idea what sort of music I'm talking about:
> http://www.harmonyware.com/tunes/chunes.pdf
Pretty sure I’ve answered this question on this list before...
For each individual tune, I have one file (tunename_tune.ly) which only
defines variables, and a wrapper (tunename.ly) which makes a PDF and a
MIDI using those variables. Then I have a big wrapper (tunebook.ly)
which includes all the tunename_tune.ly files and makes a book out of them.
The important part is to have files for each tune that define all the
info but which don’t actually *do* anything. That gives you the
flexibility to do different things with that info in different contexts.
Is there a technical reason to do this, or is it purely for your organizing? I ask because I'm autogenerating my Lilypond from ABC anyway, so my typical approach would be to do different contexts by tweaking the ABC -> Lilypond translator.
I have a helper file called tunes.ly which handles layout and making a
MIDI of a dozen instruments playing in unison.
That would be very interesting to see, I think?
Thanks,
Sol