Traditionally, vocal parts have autoBeaming only inside melismata. So it would be brilliant if we had an algorithm to do this automatically and not have to add manual beams so often.
I’d suggest to make this a third option for the autoBeaming context property: #t, #f and 'melisma.
I think this request is confused about LilyPond's default semantics. If you want "traditional" vocal beaming, you turn off autoBeaming and then use [ and ] for indicating melismata.
There is no sensible manner in which beams can indicate melismata while melismata indicate beams. So I'm voting to close this as Invalid.
Correct me if I’m mistaken (and pardon my ignorance of the actual internals of this), but I can’t see the flaw.
Manual beams, i.e. BeamEvents indicate melismata. The Auto_beam_engraver however creates beams in a way that doesn’t interfere with melismata, so if he would listen (after a
\set autoBeaming = #'melisma) to any events starting or ending a melisma, he could start or stop autoBeaming at these moments.Even if a manual beam, as starting a melisma, would cause the Auto_beam_engraver to resume work: would that be a problem? If a manual beam is present, autoBeaming doesn’t interfere.
I am getting your point now: you are referring to short melismata which are actually subsumed under one beam in entirety. For these, my request is obviously pointless. No, I was thinking about longer melismata, like in virtuoso baroque music, where it’s quite tedious to specify all the beams occurring in the meantime:
That could well be left to autoBeaming.
Last edit: Simon Albrecht 2015-10-27