Ralph Palmer wrote
> I'm a former fiddler/violinist who has graduated to viola. I've been
> trying
> to learn fiddle tunes on the viola, and I've been using Lilypond to
> transpose tunes into alto clef. I transcribe the tunes in treble clef
> first
> so I can proofread them. I use a slightly different setup than you use or
> than seems to have been suggested. I'm attaching some files as a minimal
> (three pages) example.
Hello Ralph,
Thanks for your message and for sharing your files and approach to this. It
would be great to see a copy of your tune list, and I'd be happy to give you
a pointer to this collection when the update is finished. There will be an
alto clef version! Although, there may be a lot of overlap since you have
500 tunes. This collection has a little over 200 I think.
Your message got me focused on making it easy to transpose the whole
collection and/or change clefs. I think I will follow your lead and have
files for each tune with just the music and chords in variables, and a score
block that is commented out. It can be temporarily un-commented to edit,
proofread, or just render a single tune.
Then I have my main collection file where I \include each of the tune files
(at top level). This collection file has a \paper and \layout block and
then a series of \bookpart blocks like Federico suggested. Each \bookpart
is a single page and contains 1-3 \score blocks, one for each tune. The
clef for each tune will be set in this score block just before the melody
variable (and not inside the melody variable). That will make it easy to
find/replace within this one main file to change the clef for every tune,
and/or to enter a \transpose command before each of the melody and chord
variables -- to create different PDF versions like an alto clef version for
viola, or a version for Bb clarinet.
(Hmmm... it would probably be better to use variables and/or script these
things instead of using find/replace... )
Using \bookpart will let me have a custom header for each \bookpart (page)
that contains a custom header field called "manual-page-number." It will be
used in the global \paper block to print a page number at the bottom of the
page. (There are different sections, some that have page numbers like "J1"
or "R1" hence the need for manually setting this.)
Another option is printing a separate PDF for each page. I can do this with
a find/replace and make each \bookpart into a \book (each \book produces a
separate PDF). Then using \bookOutputName in each \book (normally commented
out when they are \bookparts) will let me assign each of those single-page
PDFs its own name. (The files are currently a collection of one-page PDFs,
so this is a way to recreate that without having to have separate .ly files
for each page.)
Ok I think that covers it. Maybe some of this will be helpful for anyone
else doing this kind of collection?
One thing I noticed looking at your main Tunebook.ly file... it looks like
you have the same \layout block in each \score block:
\layout {
indent = #0
\context {
%prevent tunes from printing on two pages
\override NonMusicalPaperColumn.page-break-permission = ##f
}
}
so I think you could just have one top-level \layout block for the file with
these settings, and just not have one in each \score ?
Thanks again and all the best,
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Using-only-manual-page-breaks-in-a-large-file-with-many-short-scores-tp159781p159818.html
Sent from the User mailing list archive at Nabble.com.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
