This seems to fix it: ... Arb w60m [-6 g83 zg- a8+ za- ] b4+ zb- e4s ze- / b84e a8 g4 g4e // d2+ zd- c4+ zc- /
But of course if I ever change the code in this area, then this would probably give a different result. I haven't done lots of checking, but I believe it's been the case since day 1 that beam positions are only based on main notes, and ignore chord notes. That would lead to lots of backward incompatibilities if I did change the code. --Don > -----Original Message----- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner....@tug.org] On Behalf Of Dirk Laurie > Sent: Tuesday, April 09, 2019 9:56 AM > To: Werner Icking Music Archive <tex-music@tug.org> > Subject: [Tex-music] PMX stem length error on beamed octave chords > > I can't believe I am the first person to report this. Yet the output for PMX > 2.73 > and PMX 2.82 looks the same. The non-beamed octave chords are perfect, > the beamed ones have their stem length wrong and therefore the beam > position too. > > I need this for something I am typesetting right now. i don't need a fix, a > workaround will do. > > ~~~~ > 2 -1 2 3 4 3 4 0.00000 -2 1 1 20 0 > > 60 > ./ > Tc > PMX 2.73 > Tt > Beam Error > Arb w60m > g83 zg- a8+ za- b4+ zb- e4s ze- / > b84e a8 g4 g4e // > d2+ zd- c4+ zc- / > ~~~~ > > The attached .pmx file contains the same PMX code. > > -- Dirk ------------------------------- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to https://tug.org/mailman/listinfo/tex-music
