Hi Don,

thanks again for your rapid help. I am happy that I am able to solve the problem within PMX. In particular with respect to automatizing the conversion from MusicXML to PMX.
Yes, I am still working on this!

Happy New Year to you, as well.

Dieter
Am 01.01.2016 um 17:40 schrieb Don Simons:
2016-01-01 12:27 GMT+02:00 Dieter <[email protected]>:
a04  D<   D< | /
   a04  D> | /
...
Is this the recommended modeling or are there alternatives?
Look at the TeX file generated by PMX. You will see

\hpstrt10\hpcend100

Experiment with the parameters. When you get the result right, use inline
TeX instead of D< D<.
It turns out there's no need to go outside of PMX. Unfortunately on p.13
pmx270.pdf is at best ambiguous when it says "There can only be one of the
letter-groups on each note, but there may also be D< and/or D> on the same
note." I'll fix that in the new release of PMX 2.71, but in the meantime,
the following two options will work.

I'll also mention that you didn't use Ap (Type K postscript slurs) and you
should. Hairpins are different (with Ap, they don't have to be horizontal,
and the width can be fine-tuned more precisely). I checked that the example
works fine with Ap.

Finally, Happy New Year!

--Don Simons

  =============================
% nstaves ninstr mtrnuml mtrdenl mtrnump mtrdenp
     1    1    4    4    4    4
% npickup nkeys
  0    0
% npages nsystems musicsize fracindent
     01    2   20 0.05

t
.\
w150pt
Tt
Test crescendo
a04  D< D<+0+3 | a04 D> D>+0+3 | r4 r2d /
a04  D< | a04 D<+0-2 D> | r4 D>+0-2 r2d /
==============================

-------------------------------
[email protected] mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music



-------------------------------
[email protected] mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

Reply via email to