lilypond-user
[Top][All Lists]
Advanced

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

Re: short Musikmesse minutes


From: Urs Liska
Subject: Re: short Musikmesse minutes
Date: Thu, 20 Mar 2014 11:30:47 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

Am 20.03.2014 10:25, schrieb David Kastrup:
Francois Planiol <address@hidden> writes:

Lily is free and that is a biiiig problem, for salesmen.

Remember the incandescent lamp? It was not expensive enough and
forcedly replaced by a dangerous CFL with a higher margin for
everybody except the end-customer. So forget it, when it is free. Just
even worse for commerce. (sure there is not some trust-negociations
between engraving programs companies and music publishing job?)

Free is not a problem but it also is not much of a selling point for
in-house software as pretty much all acquisition costs are dwarfed by
running expenses, particularly personnel.  How expensive is personnel
that can be trained to work with LilyPond, and how fast are they going
to crank out stuff?  And most importantly: when there are problems, is
there a reliable place you can throw money at to make them go away?

I think the concept of versioned collaboration offers an interesting path here: Start out with a project commissioned to LilyPond experts. The lectors will learn very fast how to apply fixes to the musical text. And they (and the existing engravers) can immediately get experiences on real-life projects. That doesn't replace some fundamental training, but is definitely more attractive than telling them to start their learning curve from { a b c }.

...



I think that LilyPond's main strength is transformative use: different
page formats, different media, different transpositions, individual
variations.

Yes, and I have/had the impression that it _is_ possible now to promote this feature. Of course I don't expect the final outcome to match my current enthusiasm, but I'll surely keep you informed about my progress.

Urs



reply via email to

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