Kieren MacMillan: > Absolutely. Again, most engravers I intersect with either donât > want to use Lilypond because âthereâs too much codingâ, or use > Lilypond and complain that âthereâs too much coding [to make a > simple score]â.
Yea, I can understand that, sometimes lilypond things seems to be black magic. > If I had the following two things, I could probably convert a > half-dozen of my colleagues (who already marvel at the output > I get) to using Lilypond for lead sheets: > > 1. a \makeLeadSheet function that Did The Right Thing⢠> (modulo 80/20 rule, of course!); and > 2. a stylesheet system that allowed me to [potentially] quickly > generate each colleague their own housestyle.ily stylesheet. ... Perhaps someone more fluent in lilypond-scheme than me could help out. There is a: https://gitweb.git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=ly/satb.ly;h=9255d50d6587edd68c3ee0dbbf334812998351a9;hb=HEAD that might be used a starting point. /// My first try gave me: tt.ly:72:1: error: music function cannot return ##<Score> But this works: makeMidi = #(define-music-function () () #{ \unfoldRepeats << \mstaffSup \mstaffCon \mstaffTen \mstaffBas >> #}) \score { \makeMidi \midi { } } Where tt.ly is a copy of [1] plus the wrapping of midi parts into a music-function. Regards, /Karl Hammar [1] https://aspodata.se/git/musik/Cl%c3%a9ment_Marot/ps36/ps36_01.ly
