Re: [Lilypond-auto] Issue 4093 in lilypond: put NullVoice in Staff by default

[lilypond]

Comment #6 on issue 4093 by address@hidden: put NullVoice in Staff by default
https://code.google.com/p/lilypond/issues/detail?id=4093

Ok, here is an excerpt from scm/define-context-properties.scm:

     (melismaBusyProperties ,list? "A list of properties (symbols) to
determine whether a melisma is playing.  Setting this property will
influence how lyrics are aligned to notes.  For example, if set to
@code{'(melismaBusy beamMelismaBusy)}, only manual melismata and
manual beams are considered.  Possible values include
@code{melismaBusy}, @code{slurMelismaBusy}, @code{tieMelismaBusy}, and
@code{beamMelismaBusy}.")

Now this just cries for a melismaBusyTranslator that listens to slur, tie  
(and note), and beam events and sets the respective busy flags.  Obviously,  
this translator can work perfectly fine in either Midi or Layout.  Equally  
obviously, it does not require _any_ grob to pass by in order to do its  
actions.

So with that translator, we can just remove all the grob-producing  
engravers and have things work fine in NullVoice.

Also we get the same melismata in Midi and Layout without effort.

That's so much less fickle than trying to produce grobs that can then be  
almost but not quite be ignored.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings