Fugue! That comes from being shortsighted and not checking names twice. I apologize!
As I see it putting something like this into the official release would be a bit problematic, as the whole thing is might cause very weird behaviour. There are probably cleaner ways to achieve this result. Cheers, Valentin 22.01.2022 19:27:12 Kenneth Wolcott <kennethwolc...@gmail.com>: > Hi Valentin; > > I feel too honored to be mistaken for Kieren :-) > > Thank you so much for the "Jump" code; it is very interesting. > > The details are ***WAY*** beyond my understanding, but it looks very > useful and usable. > > I will experiment with it. > > Is there a possibility that the next release of Lilypond would have > such functionality built-in? > > Thanks, > Ken > > On Sat, Jan 22, 2022 at 5:27 AM Valentin Petzel <valen...@petzel.at> wrote: >> >> Hello Kieren, that seems to be correct. >> >> One could also try something like this. >> >> Cheers, >> Valentin >> >> Am Samstag, 22. Jänner 2022, 03:22:42 CET schrieb Kenneth Wolcott: >>> Hi; >>> >>> I have a piece of music from which I am engraving that confuses me. >>> >>> At bar #13 there is the Segno sign. >>> >>> At the end of bar #20 there is a "Fine". >>> >>> At the end of the piece (bar #37) there is a "D.S. al Fine". >>> >>> I'd like to have Lilypond generate midi output that would match this >>> intent. >>> >>> Does this mean: >>> Play all the way through; then start at the Segno and continue until the >>> Fine? >>> >>> I think that's what it means. >>> >>> So I need to have bar #1 to bar #12 in one macro; >>> bar #13 through bar #20 in a second macro; >>> and the third macro would contain bars 21-33. >>> >>> Then I need "M_one", "M_two", "M_three", followed by "M_two" to >>> implement this in the midi score section. >>> >>> Is that correct? >>> >>> Thanks, >>> Ken Wolcott
