[Lilypond-auto] Issue 4098 in lilypond: Create a Syllable_translator

[lilypond]

Status: Accepted
Owner: address@hidden
Labels: Type-Enhancement

New issue 4098 by address@hidden: Create a Syllable_translator
https://code.google.com/p/lilypond/issues/detail?id=4098

This translator will listen for note events, beam events, tie events, slur  
events, check out the various melisma* context variables and will create  
synthetic "syllable" events.  While it would seem nice to provide spanners  
(namely with spanner-direction START and STOP) for flexibility, stuff like  
dangling ties and tieWaitForNote make it unclear whether one can hope to do  
that reliably, to a degree where a syllable-stop event can only occur too  
late in situations where we warn about unfinished ties etc anyway.

Everything having to do with lyric synchronization will listen exclusively  
to syllable events.  Listening to NoteColumn grobs etc might still be  
desirable for graphic alignment purposes, but the respective engravers  
should be robust about not getting to see any.

This will make it possible to reliably synchronize lyrics to whole Staff  
environments (as issue 4097 implements but without being able to offer  
coherent melisma processing, something which would fall out painlessly as a  
side effect of having a Syllable_translator) processing a Lyric syllable  
whenever one of the contained voices starts a syllable.  It will also make  
all syllabic synchronization work identically across \layout, \midi, and  
whatever may be there to come.

It will greatly simplify the jiggery-pokery currently involved with the  
NullVoice context (causing the current impasse for issue 4093), even though  
NullVoice itself will lose much of its appeal with a reliably working  
version of issue 4097.

--
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