This is great. I complain about a few problems and within a
few hours, most of them are already solved.
Thanks Jan and Han-Wen!
> > I'm typesetting a score of an unknown orchestral ouverture by
> > Gade, and I have to send a nice readable copy to the
> > conductor in a couple of weeks. Before that, I'd very
> > much appreciate if we could solve the following problems
> > in Lilypond.
>
> Goodbye hacking-without-fixing-any-bugs dreams.
I know, I have a few things to cleanup myself as well.
> > - (Annoying but not a bug:) Slurs that are broken at line
> > breaks often extend too far into the margin, both to the
> > left and to the right. How do you adjust it?
>
> Do you have an example? I made a fix in pl21, and although
> slur placement is still not perfect, its a lot better than
> before, see input/test/broken.ly.
I haven't tried this in pl21 because of the previously mentioned bug.
If it isn't solved, I'll come back with an example.
> > Another problem that is hard to solve quickly is that the
> > score takes 2 1/2 hour to process at the moment. 250 bars of
>
> Ouch.
> Did you try setting gourlay_maxmeasures to a reasonable minimum?
>
> \paper {
> gourlay_maxmeasures = 4.;
> ..
>
> > 16 voices on 14 staff lines. I should probably invest some more
> > memory on my PC. The process uses about 60MB and I only have
> > 32 MB physical memory available.
>
> hmm, i'm very sorry to say that lily really likes to have >=50Mb
> for these kinds of things...
>
> did you strip the lilypond binary (and kill X etc?).
I'll try all these good ideas and see what difference it makes.
> > Hopefully, I can make the score publicly available when it's
> > finished.
>
> I'd very much like to see such a big piece of real music. Why
> do you say 'Hopefully'?
I'll check with the library first that they don't have any complains
about copyright issues. Otherwise it's no problem.
/Mats
