On Sun, Feb 15, 2015 at 02:58:11AM -0700, bensonby wrote: > I have the same problem too. As a quick solution, I split the note > into two with a tie, one for sustainOff and one for sustainOn. > > If there are no "real" solutions, I guess someone may write a function > to automatically achieve this, say, \sustainOffOn [...]
Hmm, that's not a bad idea. What if the function that breaks a note into two tied parts, like you said, also manipulates the grobs so that it still renders as if it's the original note? Not sure if this is actually achievable, but it *seems* that it should be possible with a sufficiently clever Scheme function... (I'm currently cutting my teeth on using Scheme in lilypond.) Having a function that automatically does this is essential for me, since I use this a LOT in my piece, and it would be far too tedious to manually split every note where the problem occurs. Or I could try to locate the source of the problem in the lilypond code and fix it there... I'm not sure which one would require more effort, though, since I first have to understand enough of the code to figure out where it might have gone wrong. :-P T -- If blunt statements had a point, they wouldn't be blunt... _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
