Re: Issue 1632 in lilypond: beam staff change weird angular beam

[lilypond]

Comment #3 on issue 1632 by address@hidden: beam staff change weird  
angular beam
http://code.google.com/p/lilypond/issues/detail?id=1632

This was a problem earlier that is caused by the fact that, with automatic  
beams, the beams are considered to belong to the voice they finish in (not  
start in).  So, the beam's covered grob list is full of grobs that  
shouldn't be there.  Furthermore, the beam is part of covered grob lists  
that it should not be a part of.

This goes away if the beam is manual.  I sent out a patch earlier today  
(issue4432063) to address this.