Luc You can get round this particular problem by making the alto beam transparent by inserting the following override immediately before the note that starts the beam:
\once \override Beam #'transparent = ##t However, all this is really cludgy, needing manual tweaking for every occurrence, and there are likely to be other problems later. It might be easier to write the two parts together, using chords where only one voice is needed and introducing the second voice only when it is needed, like this: \context Staff = "upper" << \clef treble \context Voice = "upper" \relative g' { \key c \major <g e>8 <f c> <e c>4 <e c>2 | << { f4 d d2 } \\ { b8( c) d( c) b2 } >> | } >> although this doesn't meet your objective of keeping the parts distinct. Trevor > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:lilypond-user-bounces+t.daniels=treda.co.u > [EMAIL PROTECTED] Behalf Of > Luc Saffre > Sent: 27 December 2007 18:59 > To: lilypond-user@gnu.org > Subject: Re: alto stems up, tenor stems down > > > On 27.12.2007 20:26, Trevor Daniels wrote: > > There is no 'proper' way of doing this, unfortunately. > > The recent discussion on \partcombine which you can > > see in the archives points out the problems with this. > > Of course, you can always simply insert \stemUp and > > \stemDown commands in the alto line. These will give > > the appearance you want, but will generate lots of > > 'clashing note column' error messages. > > Thanks for your answer, Trevor. I just tried with > \stemUp and > \stemDown commands, and this indeed works for the > example I gave. > But the trick fails if there are 1/8 notes. I > join a slightly modified > example which shows the problem (the first line > is using \stemUp in the > alto voice and doesn't look well, the second line > looks well but uses my > cheating trick). > > I'll now try to understand the partcombine > discussion (I am a beginner, > you know) > > Luc > _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user