>> Van Ryckeghem Andre wrote:
>> 
>> Who is willing to help me?

and Christian Mondrup wrote

>The problem is a conflict of beam-ID's in the generated MusiXTeX code.
>Hence the problem can be solved by forcing a change of beam ID. One way
>to do that is to split the beaming groups among separate voices. 
>...
>Another might be to give the pmx typesetters access to beam ID's
>analogously to the slur/tie ID's - Don ?

and a third would be to fix the bug that's causing this in the first place.
I had broken this feature when I did that major overhaul of the horizontal
spacing (2.1?).  Some of my own old sources didn't even work right.  So I
worked on it over the weekend and I think I have the beam numbering
straightened out.  However, as it now stands the up-downness of beam
termination is not always right, leading to a horizontal gap or overlap. But
this can be changed by the user assigning an up-downness to the last segment
of the staff-jumping beam.  I'm considering two possible levels of
automation here, one an option to simply *flip* the up-downness from
whatever PMX does (fairly easy to program but still requires user
intervention); the other to detect the height of the beam termination
relative to the notehead and set the up-downness accordingly (no user
intervention, but very tricky to program).

Stay tuned.

--Don Simons

Reply via email to