RE: divisi parts and another general question

[Kieren MacMillan]

David,

> That makes me doubt your memory.

That is your prerogative. For my part, I just double-checked your function against the one in my backups — they are identical, excepting whitespace.

Feel free to ponder how changes in the Lilypond code since v2.9 (which was the time of that backup) may have affected the non-functioning of that code. Or spend your time more wisely, e.g., working on improving the current codebase.

Kieren.

>
> > I have far too much work composing and engraving right now (~18 months
> > of classical and music theatre commissions) to spend time testing your
> > function.
>
> That is no problem as long as you don't promote rather opaque code to
> others without good reason.
>
> > However, if you'd like to exhaustively test the two versions with
> > multiple \transpose and \relative commands, etc., and get back to me
> > with a whitepaper on the results, I would be happy to look it over.
>
> There is little point for me to test identical music expressions for
> identical results. I have to admit _one_ difference: I've drawn
> \oneVoice into a more logical place. You can move it back to the end of
> the function if you want to but I don't see that making a difference in
> the typeset results.
>
> Other than that, the function will produce exactly the same music
> _expression_ after this change, just written in a different manner.
>
> --
> David Kastrup