Still no real answer, but it's not the \lower4\internote and it's not the
dot, it's the \hbox, which somehow isolates part of the beam from knowing
that there was a \noteskip inside. What's really weird is that the 16th note
comes in the right place. And you don't even need an \hbox, just surround
the spacing command with parentheses and you still get the error:
% Bar count 1
\pnotes{1.41}{\ds}\sk\sk\ccl{'G}\ibbl1E0\qb1F%
\tbbl1\qb1E&\qs\qs\qs\qs\qp\en%
\pnotes{2.00}\tbl1\qb1{'D}&\en%
--Don
>-----Original Message-----
>From: tex-music-boun...@tug.org [mailto:tex-music-boun...@tug.org] On
Behalf Of
>Don Simons
>Sent: Tuesday, July 12, 2011 8:18 PM
>To: 'Werner Icking Music Archive'
>Subject: Re: [Tex-music] A note with flags *and* beam
>
>This is a great puzzle, and I don't see the solution yet. Both the PMX code
AND THE
>TEX CODE look fine to me. I simplified it a bit further, to
>
>%=========================
>2 2 2 4 0 0 0 -3
>1 1 20 0
>Cello
>Violin
>bt
>./
>r8-4d g13 f e d8 /
>r1 r r r r4 /
>%=========================
>
>and the main part of the TeX is
>
>%=========================
>% Bar count 1
>\pnotes{1.41}\lower4\internote\hbox{\dsp}\sk\sk\ccl{'G}\ibbl1E0\qb1F%
>\tbbl1\qb1E&\qs\qs\qs\qs\qp\en%
>\pnotes{2.00}\tbl1\qb1{'D}&\en%
>%=========================
>
>pmx.tex defines \dsp as \def\dsp{\pt5\ds}. If you replace r8-4d by r8d it's
OK. Somehow
>putting \dsp inside the \hbox and lowering it causes the beam to start
early.
>
>C'mon, TeXperts!
>
>--Don Simons
>
>
>
>
>
>
>
>
>
>
>
>>-----Original Message-----
>>From: tex-music-boun...@tug.org [mailto:tex-music-boun...@tug.org] On
Behalf Of
>>Terrence Enger
>>Sent: Tuesday, July 12, 2011 2:00 PM
>>To: tex-music@tug.org
>>Subject: [Tex-music] A note with flags *and* beam
>>
>>Greetings,
>>
>>Can anybody tell me if I am doing something wrong here? The first note in
the cello
>part
>>has both flags and a beam.
>>
>>I shall append the source and attach the resulting .dvi file. I have
reduced the source
>to
>>the point where removing any of lots of things makes the problem of
flags+beam go
>>away. (The source made more sense before I started cutting it down.
Honest, it did.
>><grin /> In particular, the cello part has a second voice so that I can
insert dynamic
>>markings and words spaced out within one note.)
>>
>>I am using musixtex 1.14; and I get the same result from pmx Version
2.521, 16 May
>09
>>and pmx Version 2612 , 22 Jun 11.
>>
>>Thank you for your help.
>>Terry.
>>
>>========================== source
>>=====================================
>>% -------------------------------------------------
>>% Sixteenth G in cello part gets flags *and* beams %
--------------------------------------------
>--
>>---
>>%
>>% nstaves,noinst,mtrnuml,mtrdenl,mtrnump,mtrdenp,xmtrnum0,isig,
>> 3 3 4 4 0 0 0 -3
>>%
>>% npages,nsyst,musicsize,fracindent
>> 1 1 20 0.15
>>Piano
>>Cello
>>Violin
>>tbt
>>./
>>
>>% === m. 136
>>% % If I remove the clef change in the l.h., the problem in the
>>% % cello part disappears. If I move the clef change one sixteenth
>>% % later, again the problem disappears. Go figgur!
>> r2
>> r8d
>> Cb r1 r4 /
>> r4
>>% % FIXME: The sixteenth note G gets two flags *and* it is beamed.
>>% % What gives?
>> r8d g13 f e d8
>> r4
>>% % Without second voice, problem goes away.
>> //
>> rb0
>> /
>> rb4
>>% % Without notes here, problem goes away.
>> r1 e14 d1 e
>> rb2 /
>
>
>
>
>-------------------------------
>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
