OK, I finally figured out that Andre's latest use of "hidden features" includes creating a forced beam in one staff with a single note in it, with an extended top or bottom so that the stem stretches upward or downward. I never realized that a beam with only one note would have no crossbar. But for single notes I don't see why the note in the other staff needs to be in a forced, single-note, xtuplet, joined beam. My testing suggests that
a13 r1 r4d / [-10 b14 ] r1 r4d / works just as well as Andre's [ a13x1n ]j r1 r4d / [-10 b14 ] r1 r4d / I do plan to extend the "S" option to allow stem lengthening. I've looked in the code and it seems it'll be fairly easy. Once that's done, we'll have easy PMX ways to form unbeamed chords across staves, using Andre's forced beam trick for flagged notes, and "S" (or "L" with positive argument?) for unflagged ones. I need to spend some more time studying the options for beamed chords across staves. By the way, in my experimenting, I ran into some problems that I think were caused either by Andre's use of letters for pitches in inline TeX, or by not setting the octave for the first note in a block. Since PMX never parses inline TeX, letters can confuse which octave it's in. I never use letters for pitches in inline TeX. And for safety, I always use an octave option on the first note in a block. --Don From: TeX-Music [mailto:[email protected]] On Behalf Of Andre Van Ryckeghem Sent: Friday, February 05, 2016 9:29 PM To: Werner Icking Music Archive <[email protected]> Subject: Re: [Tex-music] NEw pmx- VErsion Ok, the "\chorsi{^OM}" is a little bit far fetched (it is going back to the previous note and using musixtex notations) I added another bar without in line code, but again using hidden features in Don's beautiful pmx. By the way, it is a pity one cannot use ie. 'b4S-9' in pmx. Andre ================== 2 1 4 4 4 4 0 4 1 2 20 0 bt ./ w150m \\def\chorsi#1{\prevstaff\zq{#1}\nextstaff}\ <file:///\\def\chorsi%231%7b\prevstaff\zq%7b%231%7d\nextstaff%7d\> %\\def\chorsii#1#2{\prevstaff\zq{#1}\zq{#2}\nextstaff}\ % with beams, all in pmx b42 ze- e2 zb+ b4 ze- // [l+24+1 g8 g zc b b ]j [l+24+1 g8 ]j rb [j b ]j [j b ]j / [j c8 rb e e ] [j c8 ]j [j c zg ]j [j e+ ]j [jl e zc ] // g05 / % %Normal chords b4 zf+ X2 Gxe+s f2 zb- f4 zb- // rbp / \chorsi{^OM}\ d8 zf \chorsi{PM}\ d4 zf \chorsi{PM}\ d4 zf \chorsi{PM}\ d4 zf \chorsi{PM}\ d8 zf / % % \sk's needed if rests at start of bar m2424 r8 rb4 r8 / r8+0 \prevstaff\sk\zq{^N}\nextstaff\sk\ f \prevstaff\sk\sk\zq{N}\nextstaff\sk\sk\ fs r+0 // r8b+0 b zds b zdsi rb+0 / % other method [ a83x1n ]j [+20m1 b8 ] a4 / [-10 b8 ] [ a8x1n ]j \stemlength{12}\ b4 / [ a1x1n ]j [+20m1 b ] r4d / [-10 b1 ] [ ax1n ]j r4d / ================== From: Dieter Sent: Friday, February 5, 2016 2:22 PM To: [email protected] <mailto:[email protected]> Subject: Re: [Tex-music] NEw pmx- VErsion Hi Andre, I am most impressed what you can do already with the "[j... ]j" statement. However the meaning of "\chorsi{^OM}" is not obvious for me. I wonder whether I will understand enough, in order to make use of these techniques for my MusicXML-->PMX translator. Thanks and regards, Dieter
------------------------------- [email protected] mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
