Re: extra note

2017-06-15 Thread Rafael González
Thank you guys, it worked! "Whenever anything goes wrong, just follow instructions" Rafael On Thu, Jun 15, 2017 at 5:12 AM, David Kastrup wrote: > Michael Gerdau writes: > > >> I am using \version "2.19.55" > >> > >> the following line, bar > >> > >> e,8 << b'' e >> << d a >> 16 b 8. g,

Re: extra note

2017-06-15 Thread David Kastrup
Michael Gerdau writes: >> I am using \version "2.19.55" >> >> the following line, bar >> >> e,8 << b'' e >> << d a >> 16 b 8. g,16 a b d d b e' e | >> >> the attachment shows that, after compilation, I get an extra a16 after >> the second double stop, why? > > I don't know what y

Re: extra note

2017-06-15 Thread Michael Gerdau
> I am using \version "2.19.55" > > the following line, bar > > e,8 << b'' e >> << d a >> 16 b 8. g,16 a b d d b e' e | > > the attachment shows that, after compilation, I get an extra a16 after > the second double stop, why? I don't know what you want to achieve - you don't provi

Re: extra note

2017-06-15 Thread David Kastrup
Rafael González writes: > I am using \version "2.19.55" > > the following line, bar > > e,8 << b'' e >> << d a >> 16 b 8. g,16 a b d d b e' e | > > the attachment shows that, after compilation, I get an extra a16 after the > second double stop, why? Because you write an extra 16 . It

Re: extra note

2017-06-15 Thread marc
Am 15.06.2017 1:45 nachm. schrieb Rafael González :I am using \version "2.19.55" the following line, bar   e,8 <<  b'' e >> <<  d a >> 16  b 8. g,16 a b d d b e' e       |the attachment shows that, after compilation, I get an extra a16 after the second double stop, why? Lilypond seems to interpret