On 9/7/11 9:24 AM, "Reinhold Kainhofer" <reinh...@kainhofer.com> wrote:
> > Please let me know what you think about it, before I'll announce it on -user. > For example, if you feel that some score type is missing, it's really easy to > add more than the currently available. Way cool! This is marvelous. I think it's an absolutely brilliant app, with very nice execution. I think there should be a 2-staff choir with piano reduction type. I think "Quartet" is misspelled as "Quartett" in string and piano. > > I'd also like to see how well it scales to more than one user. Lilypond takes > a bit to create the score (and also the preview), so if you have any idea how > to speed up lilypond, I'd like to hear it, too. LilyPond takes a while, but it's indicated in the preview, so I think it's OK. Cached scores are instantaneous. > > Currently, I'm caching all already created scores and previews, so lilypond is > only run once for each size / sysstem count / type / etc. combination. > > I did not enable manual input of title/subtitle/composer/etc. on purpose, > because that will increase the server load dramatically, because caching is no > longer possible then (each different title requires a separate lilypond run). > If you really need to create your custom title on an empty score page, mail me > privately and I can tell you how to enable those controls. But I won't make it > available to the general public. If you could put a null markup placeholder in the generated .ly, then anybody who needed it could handle it by themselves, as long as they had LilyPond. > > PS: With the landscape paper formats you can see an example of bug 1819 > (http://code.google.com/p/lilypond/issues/detail?id=1819 ) Yes, it's definitely there. Thanks, Carl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
