[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LilyPond processing mode

From: Graham Percival
Subject: Re: LilyPond processing mode
Date: Sat, 5 Nov 2005 17:50:16 -0800

On 5-Nov-05, at 5:11 PM, Han-Wen Nienhuys wrote:

Graham Percivalwrote:
Seriously?!  Please please please!

see attached; the file will listne on port 2904 for a quoted string, and process that as .ly; of course, this is one of many options.


I think I can avoid the latency issues by creating the music one system in advance... but still, saving 1 second for each run would be great! Especially if I wanted to try having one computer displaying parts for two (or even four) people.

Cool project; I suspect it will be a lot of work to glue together all the parts.

Yes and no -- it depends on how nice I want it to act. How much time I spend on the infrastructure vs. the musicality and algorithms is something we'll be determining later.

I already have it working (on a single computer) in chuck and pd. In both languages, I simply write lilypond code into a text file, call lilypond on that file, then call "open foo.pdf" (which in osx opens it up in Preview, of course).

My first example was called "sadism" -- it began by giving the cellist random notes from a D major traid, and listened to the intonation. The worse the intonation was, the harder the notes got (ie more distance between notes, notes outside of the scale, etc). It was surprisingly easy to make... but of course, that was just a simple example, for a single musician, on a single platform.

I could easily extend that to a quartet -- have one laptop for each member of the quartet, with a directory of a fifth laptop remotely mounted. Whenever a new .ly file appears in there, the quartet member laptops copy it to themselves, run lilypond, etc. Of course, this is quite inefficient; I'll definitely do something better than this. But how much better is still an open question. :)

- Graham

reply via email to

[Prev in Thread] Current Thread [Next in Thread]