Re: Automatic ottava handling

[Gilberto Agostinho]

Hi David,


David Nalesnik-2 wrote
> Actually, no, it averages the ledger lines of the chord members.  If the
> average is above the threshold, we get an ottava.  I'm welcome to better
> algorithms!  (It would be easy enough to implement what you describe.)

I believe that considering the lowest note of a chord for ottava and the
highest note for ottava bassa would be better. This way you'd get more
consistent results (think of some extreme cases like with a xylophone), but
this is obviously up to you. The way it is now also works fine during most
of the cases, but it may come across lacking consistency for someone viewing
the score.


David Nalesnik-2 wrote
> I don't see the problem you've describe.  The attached shows the snippet
> without and with \ottavate, with short names for clarity.

Me neither! I believe I miscounted the ledger lines, or I used your default
settings #'(4 . 7) #'(-3 . -6) instead of #'(4 . 7) #'(-4 . -7) and got
confused. I spent way too much time with LilyPond and Pure Data today, so
forgive my lack of sense sometimes.


David Nalesnik-2 wrote
> I should say my "goal" was that automatic ottavas would be a simple,
> uncomplicated thing to achieve.  And of course wishing makes it so.
> The alist idea seems like a great alternative to a long list of arguments
> you have to look up every time you use the command.

This alist idea seems very interesting indeed. I am really looking forward
to v3.0 of your function!

Thanks once again for your effort, and take care,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Automatic-ottava-handling-tp167190p167775.html
Sent from the User mailing list archive at Nabble.com.