> Date: Mon, 3 Apr 2000 09:23:52 +0200 (MEST)
> From: Bernhard Lang <[EMAIL PROTECTED]>
> musixflxing some music I get the following on the screen
>
> <<< musixflex 0.83/T.63dt+jh.2 >>>
>
> ... decoding command line
> ... open <mv.mx1> for input
> ... testing versionnumber
> ... open <mv.mx2> for output
> ... reading
> ... compute
>
> Division by zero ! Ask a wizard !
>
> Does anyone out there feel to be wizard enough to help me? To my knowledge
> the music itself --- some pieces from Monteverdi's Selva Morale --- does
> not contain anything strange. This happened all of a sudden. Contents of
> mv.mx* are added below.
Thanks for adding the required data.
You could have tried "musixflx mv d" for debugging?
The above output shows, that the first section is being computed or
is finished already. The mx2-file shows at the end
> \lineset{ 18}{ 3}{ 5.32889pt}{ 7.10521pt}{ 0.00000pt}% 52 - 54
that bars 52-54 heve been processed already.
mx1 shows for the next bars:
> b 54
> * 1 0
> 54 1 0.0pt
> 54 1 0.0pt
> 54 0 4.90004pt
> b 55
> * 0 0
That seems to be the problem :-) There is something with no content.
Lines in .mx1 beginnig with "*" always denote a new section; the next
two numbers are \muloosenes and \linegoal.
Have a look what happens between bar 54 and 55. And then tell us,
what to avoid in the future.
It's not too hard to read .mx1 and .mx2. For .mx1 compare your
input against the contents of .mx1. For each bar the space requirement
is notated somehow.
.mx2 tells for each line of music it's number, the number of bars in it,
\elemskip, \afterruleskip, \beforruleskip and as comment the bar numbers.
Hope this hilft -- Werner
