I've just uploaded this to WIMA. The only difference from
the earlier version is that instead of adding a call and
reset of \atnextbar to \changeclefs, this is done in a new
command \Changeclefs. This would be used to ensure centering
of material within the region that excludes the new clefs.
Bob
>|my pmxab.exe is an old one (from pmx2704).
That will generate the 3-argument call of \mbrest.
>|When i use pmxab.exe from pmx271 then i got a fortran
>|error: libgcc_s_dw2-1.dll is missing, program cannot
>|start. I downloaded pmx271 from the link in the latest
>|email.
Perhaps you have a
The '\def\atnextbar{\znotes\mbrest3{11}0\en}%' is generated by pmx
The only difference i see is that i use windows 10. And my pmxab.exe is an
old one (from pmx2704). When i use pmxab.exe from pmx271 then i got a
fortran error: libgcc_s_dw2-1.dll is missing, program cannot start. I
downloaded p
Not until I get a new scanner, I'm afraid -- my old one chose today to
give up the ghost!
Will the attached PDF do? It was compiled from the musixtex source I
posted earlier and shows the single-bar coda placed beneath
the last (partial) line, but the word "FINE" is in the correct place
and I w
That is definitely a symptom of the TeX file calling \mbrest with 3
arguments rather than 1. I do not get the error when I run Andre's PMX code
with
executable PMX, Version 2.71 , 26 Dec 15,
MusiXTeX(c) 1.21 <2015-12-27>, and pmx.tex file
PMX, a Preprocessor for MusiXTeX, Version 2.71b <26 Dec 15>
Bob Tennent wrote:
>|Andre:
>|
>|You should be getting
>|
>|\def\atnextbar{\znotes\mbrest3\en}%
Check which pmxab you're using.
The sample from André's log file reports the PMX version:
(C:\Users\Andre\AppData\Roaming\musixtexmf\tex\generic\musixtex\pmx.tex
PMX, a Preprocessor for
Raphaela,
my idea would be to write the notes first with noteedit, export the result to musixtex and go there further. I enclose the musixtex- source (Latex, not TeX!) and the resulting pdf.
Regards
Christof
Gesendet: Samstag, 02. Januar 2016 um 16:25 Uhr
Von: Raphaela
An: tex-music@
>|Andre:
>|
>|You should be getting
>|
>|\def\atnextbar{\znotes\mbrest3\en}%
Check which pmxab you're using.
Bob T.
---
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
>|With the latest musixtex and pmx , i got a '110' in bar 2, probably coming
>|from the tex output line:
>|
>|\def\atnextbar{\znotes\mbrest3{11}0\en}%
>|
>|Am i overlooking something?
Andre:
You should be getting
\def\atnextbar{\znotes\mbrest3\en}%
--- Packages actually used accordin
On Sat, 2 Jan 2016, Raphaela wrote:
Could some kind person please help me with a layout issue? I'm
typesetting a guitar piece which has a one-bar coda, and what I would
like to do is something along the lines of the (highly schematic)
example layout in the attached file -- except that the final
Dear all,
With the latest musixtex and pmx , i got a '110' in bar 2, probably coming
from the tex output line:
\def\atnextbar{\znotes\mbrest3{11}0\en}%
Am i overlooking something?
Thanks for helping,
Andre
This lines are from the log:
(C:\Users\Andre\AppData\Roaming\MiKTeX\2.9\tex\generic\
Hello all,
Could some kind person please help me with a layout issue? I'm
typesetting a guitar piece which has a one-bar coda, and what I would
like to do is something along the lines of the (highly schematic)
example layout in the attached file -- except that the final bar
should be placed alongs
12 matches
Mail list logo