[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Do we really offer the future?
From: |
Kieren MacMillan |
Subject: |
Re: Do we really offer the future? |
Date: |
Mon, 20 Apr 2015 12:24:26 -0400 |
Hi Urs,
> this seems a good idea, but not for my original question.
Fair point.
> If you could find the time to put together a list of arguments (or maybe a
> nice blog post) why a *composer* should use LilyPond this would also be very
> helpful.
I would *love* to do that — a blog post sounds like the best approach (for
maximum visibility/distribution). I might even “simulcast” it on my own
website! Once I get my current scores out the door, I’ll move this up on the
priority list.
> For this kind of people it seems most important to get their music into the
> score as quickly and easily as possible. I'm thinking of composers who *do*
> need performance material but who do not necessarily need publication
> quality, just the one necessary for people to play from the material.
That’s a huge audience, of course. That being said, I will always whip out my
trump card: at 7:30PM on the opening night of “Robin Hood”, I ran into the
theatre office, pointed their browser at lilybin.com, and cranked out an
engraved piccolo part for the Overture which the player sight-read at 8PM. That
was pretty "quick and easy”, all things considered. ;)
> Sounds reasonable.
> I think I've identified (or was told) the following use cases:
> - producing scores "for the day" - editions without specialized demands and
> not necessarily intended for extra-long maintainment.
> - producing scores on short notice, e.g. performance material when the
> composer delivers too late
> - process existing material (either from the archives or from heterogenous
> contributors' systems)
> - scholarly editions and edition series with a long-term horizon.
I think, as (if?) this discussion moves forward, it will be critical to lay out
the use cases — a Venn diagram might actually be a useful tool here! — and see
which are viable targets for attack.
Best,
Kieren.
________________________________
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: address@hidden