Thanks, Dirk. The problem that I was having with the inline method is the same one you got: started one kind of hairpin while the other is on. Thiis problem arises only in polyphonic music. I had already seen the warning about unpredictable results in the M-tx manual, but i thought it referred to using > and >. in the uptext line instead of e.g. >8.
The only possibility I could think of was to code the mtx without the crescendos and decrescendo, get the pmx file from the mtx file and introduce the crescendo and decrescendo signs directly in the pmx file. I will try it out and see whether it works. Sebastian. On Tue, Nov 8, 2011 at 11:48 AM, Dirk Laurie <dirk.lau...@gmail.com> wrote: > 2011/11/8 Sebastian Canagaratna <s-canagara...@onu.edu>: > > 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 > > ------------------------------- > TeX-music@tug.org mailing list > If you want to unsubscribe or look at the archives, go to > http://tug.org/mailman/listinfo/tex-music > >
------------------------------- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
