Don is reading:-) While certainly musically reasonable, the example does violate the limitation stated in the PMX manual: "Hairpins must be contained completely within the same input block." I have confirmed that if the input lines are simply rearranged so they're all in one input block, everything goes through fine.
I'll look into the source and see if there's a reasonable way to lift the restriction. If I decide to throw in the towel on that, I'll at least see if I can generate a more illuminating error message. --Don >-----Original Message----- >From: [email protected] [mailto:[email protected]] On Behalf Of >Dirk Laurie >Sent: Tuesday, November 08, 2011 8:49 AM >To: Werner Icking Music Archive >Subject: Re: [Tex-music] Crescendo and Dsecrescendo in polyphonic music and mtx > >2011/11/8 Sebastian Canagaratna <[email protected]>: >> I discovered the removing the bar lines in the uptext restores the sign. >> I was under the impression that bar lines could be there if there were >> fillers for the notes (the tilde sign). >A bar line in uptext means "skip the rest of this bar". If the bar is already >filled by >spacers, the bar line applies to the next bar. >Uptext lines tend to be nearly empty and bar lines are used to get quickly to >where >the action is. I.e. >U: | | | mp >It's different on music lines where bar lines are just cosmetic, since the >notes and rests >must all be there anyway, > >> Is there any way of giving these signs in the music line and passing it to >> pmx. >Certainly. D> after the note where the decresc starts, another D> after the >one where >it stops. Since D means nothing to M-Tx, it is simply passed to PMX. > >Having said that (I hope you reading this, Don), I can't get your example to >work this >way. PMX complains in the case of the attached >file: > Started one kind of hairpin while other is on > >This may be a very ancient bug, since I find this in the M-Tx manual: > > Put < or > where the sign starts, and <. or >. where it ends. This feature > gives > unpredictable results when you try to use it in more than one voice at the > same > time. > >At the time I was satisfied that the uptext method (which generates different >TeX) >works even though counting elemskips is tricky, and did not try to isolate the >reason >why the inline method does not. > >Dirk ------------------------------- [email protected] mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
