Currently, for instrumental music, I'm using a modified copy of the partcombine scm (attached) which skips solo/a2 analysis, keeps unisons and close notes pointing the right directions, and combines simultaneous rests properly. There are still shortcomings involving multi-measure rests. (Please don't ask for a proper patch, as I have no time.)
You'll also need something like this to combine voices with the different options:
voicecombine =#(define-music-function (parser location part1 part2) (ly:music? ly:music?)
(dfe-make-voice-combine-music parser (list part1 part2))) -- Dan
part-combiner.scm
Description: Binary data
On 2009-09-13, at 19:18 , Anthony W. Youngman wrote:
In message <blu0-smtp76a410ac3d24e8496e9aaa94...@phx.gbl>, Kieren MacMillan <kieren_macmil...@sympatico.ca> writesI'm game. My two problems are (1) finding time, and (2) I'll need a fair bit of hand-holding to start off with, I expect. I'm very much a procedurally trained programmer (C, Fortran, *decent* BASICs).Hi Reinhold, Wol, et al:I've been thinking about implementing something like that myself (basically controlling combined/split voices via context properties, overriding the badchoices the partcombiner makes).What say we make a serious effort at rewriting the partcombiner from the ground up? There are at least three of us who want and are willing to tackle the problem, learn/improve our Scheme as necessary, etc.I can't think of very many feature fixes that would have a bigger bang-for-the-buck.Cheers, Wol -- Anthony W. Youngman - anth...@thewolery.demon.co.uk _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel