Hi Erik,
On Tue, Oct 14, 2014 at 1:28 PM, erik flister
wrote:
> thanks a lot david, i learned a lot from studying this!
>
>
Glad to hear it!
> looks like there would be two options to get lilypond to report pitch info:
>
> \void \displayLilyMusic % types absolute pitches to console
> \in
thanks a lot david, i learned a lot from studying this!
looks like there would be two options to get lilypond to report pitch info:
\void \displayLilyMusic % types absolute pitches to console
\include "event-listener.ly" % writes file w/midi numbers
but your example inspired me to figure
ng-pitches#relative-octave-entry),
but i don't want to reimplement relative octave detection (not because
it's hard, but i in principle don't want to duplicate logic).
i would think automatic fingering annotation would be a desirable
feature in lilypond itself -- per
On Sun, Oct 12, 2014 at 9:34 AM, David Nalesnik
wrote:
>
>
> It is possible to create markups in the score through a Scheme engraver.
> The one I've attached looks for a NoteHead that has had its
> 'display-property property set to #t.
>
>
I mean 'display-fingering...
_
octave detection (not because
> it's hard, but i in principle don't want to duplicate logic).
>
> i would think automatic fingering annotation would be a desirable
> feature in lilypond itself -- perhaps a markup flag where i request
> the standard fingering for the note
i want to support relative octave entry
(http://lilypond.org/doc/v2.18/Documentation/notation/writing-pitches#relative-octave-entry),
but i don't want to reimplement relative octave detection (not because
it's hard, but i in principle don't want to duplicate logic).
i would
