Mark Stephen Mrotek wrote > Gentlemen, > > If each pitch name is enclosed in < >, the octaves are formed. > > Mark > > -----Original Message----- > From: lilypond-user-bounces+carsonmark=
> ca.rr.com@ > [mailto:lilypond-user-bounces+carsonmark= > ca.rr.com@ > ] On Behalf Of > Daniel Rosen > Sent: Sunday, January 05, 2014 8:52 AM > To: Pierre Perol-Schneider > Cc: > lilypond-user@ > Subject: RE: Automatic octaves > >> From: Pierre Perol-Schneider [mailto: > pierre.schneider.paris@ > ] >> Sent: Sunday, January 05, 2014 5:42 AM >> To: Daniel Rosen >> Cc: > lilypond-user@ >> Subject: Re: Automatic octaves >> >> A standart update works fine. >> Here you go : > > Pierre, > > This doesn't change anything for me. Is there something I need to change > on > my end? > > I actually should have been more precise before when I described the > output > I was getting from the original snippet: it works on the final chord in > the > example, but that's all. The same thing happens with your version. > > DR > _______________________________________________ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user I wrote an alternative approach to automatic octaves a little while ago. Maybe it's useful to you: http://pastebin.com/u9dbkENA It uses capital notenames to add octaves. For example c4 D e F is the same as c4 <d d'> e <f f'> If you don't use the default pitch-language you have to modify the code to suit your needs. It's not extensively tested nor is it tested with 2.18 but I guess it should work. Regards, Tao -- View this message in context: http://lilypond.1069038.n5.nabble.com/Re-Automatic-octaves-tp157172p157195.html Sent from the User mailing list archive at Nabble.com. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user