Updates:
Summary: fast lilypond processing via localhost network server
Comment #7 on issue 1199 by percival.music.ca: fast lilypond processing via
localhost network server
http://code.google.com/p/lilypond/issues/detail?id=1199
... ok, I've changed the title.
The speed of processing can make a huge difference. When generating 5000
files which normally take 0.75 seconds each, saving 0.5 seconds on each
file will make the entire job take 20 minutes instead of 62 minutes. And
yes, I've generated that many files as part of my Masters thesis on
computer-generated sight-reading exercises.
In some situations, it's even more important. Back in 2006, I was doing
interactive sheet music -- I generated a short .ly file in concert,
displayed one line of music to the performers, then generated a second line
of music in response to my real-time actions while the performers played
the first line. The latency between me finishing "acting" a line of music
and displaying it for the performers could make a huge difference in how
difficult this sight-reading was -- good musicians do not read a score
linearly; their eyes flick back and forth constantly. Being able to see
the general shape of music to come 8 beats in advance, instead of 2 beats
in advance, makes the "live sight reading" much more palatable.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
