[Top][All Lists]

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

Re: Introducing OrchestralLily: A package to easily create complex orche

From: Reinhold Kainhofer
Subject: Re: Introducing OrchestralLily: A package to easily create complex orchestral scores in lilypond
Date: Mon, 3 Mar 2008 13:08:22 +0100
User-agent: KMail/1.9.7

Am Montag, 3. März 2008 schrieben Sie:
> this is quite impressive. I wish such a tool already existed when I
> started writing my opera :)
> May I suggest to add parts of it to the LSR, as "stylesheets" like Nicolas'
> one?

Well, I don't like the idea of keeping whole packages in LSR, which is 
particularly meant for "Snippets". LSR is simply not suited as a package 
repository, where you need to keep track of versions, updates, good 
documentation, FAQ's, installation instructions, etc.

Furthermore, I'm releasing the parts that I wrote under the GPL (mainly 
because I don't want to give up all rights (yet?)), so putting everything 
into the LSR is also not possible due to licensing issues.

About putting parts into the LSR: The first 350 lines are the code for 
score/staff/group generation, so they really belong together and are the core 
of the package. They also require some score-settings (e.g. to display staff 
group brackets also for a single staff  -- which is is already in LSR

I've already submitted the cue note functions to the LSR:

Similarly with the "sempre pp/ff" dynamic alignment:

Filtering articulations from Voice II:

Rest combination:

> I'm looking forward to have more snippets like this one (even if, like
> in this very case, we have to keep the code commented out until the
> LSR is upgraded). This way perhaps it's more visible, more useful --
> and quite an excellent demonstration of LilyPond potential power :)

Again, I don't think the LSR should be a package repository (in particular, I 
don't think that Nicolas' package should be there, either). For the (still 
very small number of) packages it would be better to have a separate section 
on the homepage, which proper documentation. 
In particular, the LSR does allow for exactly one source file and one output 
file, so a demonstration of features or a tutorial ar not possible. Look at 
Nicolas' style sheet. I think it's really a shame that no example of the 
fantastic output is given, but instead only some lilypond code, which gives 
only an impression what you have to write, but not what the output will be 
(title page, toc, header style, etc). 


Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden,
 * Financial and Actuarial Mathematics, TU Wien,
 * K Desktop Environment,, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien",

reply via email to

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