Hey y'all,
I've got a long-term Lilypond-related project I'm interested in
working on, and I wanted to brainstorm a bit...
I'm planning to publish all my music using Lilypond... of course! ;-)
And for the most part, I will be personally making all the engraving
choices (ahead of time), generating the appropriate PDFs, and making
them available as "static documents" -- the standard publishing
workflow.
However, for my (Broadway-style) musicals, I'm hoping to allow the
"consumers" to make certain choices and have Lilypond "dynamically"
generate them the scores/parts/etc. Specifically, the customer should
be able to accomplish as many as possible/feasible of the following:
1. Specify transpositions (on a per-song or even per section
basis).
2. Make cuts (i.e., omit sections of the music).
3. Add/remove/modify repeats (e.g., "In Song #1, make mm. 22-24
a vamp").
4. Force page turns.
5. Choose cue setups (e.g., "Reed 4 music: Song #1 goes into the
synth part; Song #2 into the Reed 3 part; ...").
I'm sure there are other potential/desirable mods I'm not thinking of
right now, but that's a good place to start this thread...
What I'm looking for are some "best practices" for how this might be
set up -- first from a technological standpoint (e.g., how to
configure such a server), and second from a Lily-code standpoint
(e.g., how to write code that would allow "in-line" modifications of
the volta structures).
Like I said, this is a *long-term* thought, so there's no rush... but
if anyone has any bright ideas, I'd love to hear them! =)
Best wishes,
Kieren.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
