On Sun, Feb 15, 2015 at 9:58 AM, 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.
>
Does that not add an extra note column (affecting layout)?
___
lily
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
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
--
View this message in context:
http://lil
On Mon, Feb 02, 2015 at 09:27:44PM -0800, H. S. Teoh wrote:
[...]
> So, I decided to try the latest git version of lilypond (2.19.16) to
> see if this glitch still exists, and I'm happy to report that it's now
> fixed!!
[...]
Oops, I spoke too soon. :-( The glitch still exists, just in a
differen
On Mon, Feb 02, 2015 at 05:34:56PM -0800, H. S. Teoh wrote:
> Hi All,
>
> I'm having some trouble with the MIDI output from lilypond for a new
> piano composition. I have a lot of \sustainOff\sustainOn sequences in
> the music, and while they show up fine on the score, the MIDI file
> appears to s
