I cannot reproduce the error. What version of PMX are you running? Is the error
from PMX or from MusiXTeX? What is the error message? It might help if you
provide a screen shot of the messages being generated.
--Don Simons
> -Original Message-
> From: TeX-Music [mailto:tex
can produce a MIDI file by itself, without
having installed TeX or MusiXTeX. But you would not be able to see the score,
so editing the MIDI file would be very difficult.
Good luck!
--Don Simons
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of
This seems to fix it:
...
Arb w60m
[-6 g83 zg- a8+ za- ] b4+ zb- e4s ze- /
b84e a8 g4 g4e //
d2+ zd- c4+ zc- /
But of course if I ever change the code in this area, then this would probably
give a different result.
I haven't done lots of checking, but I believe it's been the case since day 1
t
Dirk Laurie wrote
> Op Di. 9 Apr. 2019 om 20:00 het Don Simons < <mailto:dsim...@roadrunner.com>
> dsim...@roadrunner.com>
> geskryf:
> >
> > This seems to fix it:
> >
> > ...
> > Arb w60m
> > [-6 g83 zg- a8+ za- ] b4+ zb- e4s ze-
I finally figured out that you’re asking about cue notes. Short answer: it’s
not easy. You have to use inline TeX. There are some macros in pmx.tex that
simplify some things a little bit:
\def\smno#1{\off{.17\qn@width}\tinynotesize#1\normalnotesize\off{-.17\qn@width}}%
\def\pmno#1{\roffset{.
y\ f1 za ] r2db /
===
Am 10.04.2019 um 18:12 schrieb Don Simons:
I finally figured out that you’re asking about cue notes. Short answer: it’s
not easy. You have to use inline TeX. There are some macros in pmx.tex that
simplify some things a little bit:
\
I'm not familiar with \boxit or \circleit and I'm not sure what you mean by
"rehearsal marks". Maybe an example would help. But if they're text, you can
put them anywhere you want using the D"..." command with vertical and
horizontal shift options.
--Don
>Hi Don,
>it is amazing how easy it is
Excellent bug and bug report! I haven't solved it yet, but it goes away if you
only replace the last line of movement 3 with r0 | c04 /. So there's some very
subtle problem with the way PMX is handling centered whole-bar rests. More as
it develops.
--Don
> -Original Message-
> From: Te
ignment both horizontally and vertically in the final image, this would be
a PERFECT workaround.
--Don
> -Original Message-
> From: Dirk Baack [mailto:d...@baack-lamstedt.de]
> Sent: Friday, April 12, 2019 1:15 PM
> To: Don Simons
> Subject: Re: [Tex-mu
Finally an easy one. RTFM! (Section 2.3.9)
=
1 1 2 4 2 4 0 0
1 1 20 0
t
./
w2i
X1: c25x3 c c X: //
d25x3 d d /
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Dirk Baa
is, but if line
15 is replaced by line 16, it fails. The only thing that changes is the
argument of \centerbar within the \atnextbar command, from \liftpause0 to
\pause . I would very much appreciate having one of the TeXperts explain why
it works in one case but not the other
Bob Tennent wrote
...
> Instead of duplicating IMSLP, for no evident benefit, I suggest that
authors
> can send sources for M-Tx, PMX, autosp or MusiXTeX processing to me for
> inclusion in "contrib"
> sub-directories of subsequent CTAN releases of those packages. They will
> then be incorporated i
maurizio .mau. codogno wrote
>I agree that a section of sources would be very useful: as many have said,
> it is easier not to start from scratch if you want to edit a piece of sheet
> music.
>(I would even accept abc sources!) But I also >think that it would be better
>to
>have it as a side
I can't reproduce that error, and beyond that I'm very confused by it,
because it refers to line 25, which appears to properly list the two clefs.
It's doubly confusing because in the error message PMX should print out the
line up to the point of the error. When I run PMX 2.84, I do get another
seq
Can anyone come up with a cleaner way to shorten a single line…not necessarily
the last one on the page…in PMX (without trial and error)? If so I may
incorporate it into PMX.
--Don
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Thursday, April 25, 2019 10:03 PM
To: 'D
"Hello"+8-2 Rz /
> =
>
> You get the attached result.
>
> Regards
>
> --
> Danai
>
> On Sun, 28 Apr 2019 at 23:51, Don Simons
> wrote:
> >
> > Can anyone come up with a cleaner way to shorten a single line…not
>
at the
beginning (bar33).
Andre
From: Don Simons
Sent: Sunday, April 28, 2019 5:51 PM
To: 'Werner Icking Music Archive'
Subject: [Tex-music] Line-length challenge for the TeXperts
Can anyone come up with a cleaner way to shorten a single line…not necessarily
the last
Bob Tennent wrote
> Hi Don.
>
> Here's how to do this in musixtex, based on Olivier's coda.pmx. Notice
there
> are *three* groups of special commands, before and after the "short"
> system, and then after the 2nd short system (or text after the short
system).
With great thanks to Bob, And
r /
\\\def\alaligne{\
\\\endpiece\egroup\egroup\
\\\startpiece\addspace\afterruleskip\let\alaligne\oldalaligne}\
L5
c44 d e f g a b c /
c44 d e f g a b c /
===
Thanks,
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behal
RTFM. The first of the four numbers is the numerator of the true meter, and
it cannot be zero. You would have zero quarter notes per bar. And BTW the
3rd and 4th numbers being 0 and 4 means the printed meter would be a single
digit 4, which I don't think I've ever seen used.
--Don
> -Original
Well, I could have created a better error message :).
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Tuesday, May 07, 2019 1:09 AM
To: Werner Icking Music Archive
Subject: Re: [Tex-music] strange reaction of PMX 284
Sorry Don,
Dieter—
If you are referring to the black square after the “tr” in bar 15 of the second
example, the reason is related (in some mysterious way I can’t understand) to
the very short \noteskip caused by the 16th notes in the bass. For me, with the
default page width of 524 pt, the black square
Hi, Danai--
I'm really glad you mentioned the 3rd bar in your text, because when I compiled
your source after simply cutting and pasting it from the email without looking
at it in detail, it came out with just 2 bars that looked awful. I soon
realized that in the email process the first two "/r
For the last 3 weeks I've been struggling with revising PMX to insert blank
gaps either in the middle or at the end of a line. I do see ways to cover
most possible cases in MusiXTeX, but it's proving really tricky to build
them all into PMX. Different handling is needed for gaps in the middle or
en
For me, this file works OK:
===
\input musixtex
\hsize=524pt
\vsize740pt
\def\nbinstruments{1}
\setstaffs11
\setclef10
\generalmeter{\meterfrac{4}{4}}%
\nostartrule
\startmuflex
\parindent 253pt
\startpiece\addspace\afterruleskip%
\notes\wh c\en%
\Endpiece
Yep, tricky to figure out. But the good news is that if you don't do exactly
what they want, they will usually tell you what's "wrong".
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina
> Sent: Wednesday, May 15,
Bob Tennent wrote
...
>
> The error message says
>
> Don't stress \mulooseness too much !!!
>
> This shouldn't happen ! Too few bars or \mulooseness too large ?
>
> But there's no problem if you avoid musixflx.
>
> >|And is there any way to allow \parindent > 253pt?
>
> You'd have to loo
Bob Tennent wrote
>...
> The following works for me:
>
> =
>
> \input musixtex
> \hsize=524pt
> \vsize740pt
> \def\nbinstruments{1}
> \setstaffs11
> \setclef10
> \generalmeter{\meterfrac{4}{4}}%
> \nostartrule
> \startmuflex
> \parindent 256pt
> \startpiece\a
I wrote
>...
> This suggests that PMX could produce short, right-justified codas on lines
of
> their own, using "Mi", if for that line only PMX used \bar rather than
\xbar.
> But unfortunately, aside from allowing possible unintended line breaks in
the
> coda, that still wouldn't admit single-bar
> Rodolfo Medina writes:
>
> > "Don Simons" writes:
> >
> >> Yep, tricky to figure out. But the good news is that if you don't do
> >> exactly what they want, they will usually tell you what's "wrong".
> >
> > Don
Rodolfo Medina wrote
> "Don Simons" writes:
>
> >> Rodolfo Medina writes:
> >>
> >> > "Don Simons" writes:
> >> >
> >> >> Yep, tricky to figure out. But the good news is that if you don't
> >
then error_exit(2) end
>
> at line 923-925 in musixflx.lua (0.83.3.lua7).
>
> Note: I tested it with C version musixflx.c 0.83.2 (in T.115 zip archive)
line 720
> and line 790-793, because I'm not familiar with lua.
>
> Hiroaki
>
> - Original Message -
&g
Hi, Rodolfo--
Welcome to the club!
Your issue with the dot reveals two problems, one with the details in the
manual, and the other one a bug. In the instructions for moving dots, I
should have included a suggestion to put the dot last in the note command to
avoid any confusion. Your command was "
Rodolfo--
I think you've exposed a real bug. It seems that whole-bar rests in the
first bar are not centered as intended. I'll need to look into this some
more and report back later. I'm very surprised it hasn't come up before.
As for r0, RTFM. The manual's section on rests starts out "The comman
o.med...@gmail.com]
> Sent: Sunday, May 19, 2019 10:16 AM
> To: Don Simons
> Cc: 'Werner Icking Music Archive'
> Subject: Re: [Tex-music] PMX: full-bar rest not centered
>
> "Don Simons" writes:
>
> > Rodolfo--
> >
> > I think you'
There's no provision for ornaments on grace notes in PMX. You could put one
on the next note and move it as needed:
G1m1b1 d03s o>-18-2.4 za3 zc4 zb2 /
but this comes out in the main font. If you want one in a smaller font you
could get it with the D command, again assigning it to a main note and
Rodolfo Medina wrote
> Is it possible, in MusiXTeX code, to move a note's dot a little right,
left, up or
> down such as PMX does? In MusiXTeX manual, on p.26, I see \lpt and \lppt
> to lower the dot but nothing else.
Anything PMX can do must be able to be coded in MusiXTeX, because all PMX
does
Andre, this couldn't be more elegant! The inline TeX doesn't require any
dimensioning. If I ever finish my current PMX improvement project (blank
gaps) I may consider trying to build this method into PMX.
But I do wonder exactly what you mean when you say that a dummy page cannot
be used when maki
I'm getting close to releasing a version of PMX that enables arbitrary blank
gaps at the beginning or middle of any staff, relying on TeXniques designed
by Olivier Vogel and expanded by Bob Tennet. In modifying PMX it hasn't been
at all easy to account for all the possibilities involving movement b
eX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner....@tug.org] On Behalf Of Don Simons
> Sent: Friday, May 24, 2019 9:09 PM
> To: 'Werner Icking Music Archive'
> Subject: [Tex-music] TeXperts: Help!
>
> I'm getting close to releasing a version of PMX that enabl
ize=.70\hsize% \contpiece
>
> Andre
>
> -----Oorspronkelijk bericht-
> From: Don Simons
> Sent: Saturday, May 25, 2019 6:08 AM
> To: 'Werner Icking Music Archive'
> Subject: [Tex-music] TeXperts: Help!
>
> I'm getting close to releasing a version o
Bob Tennent wrote
> Sent: Friday, May 24, 2019 10:19 AM
> To: Dieter
> Cc: Werner Icking Music Archive
> Subject: Re: [Tex-music] Duration of multirests below the staff?
>
> >|How could I put the duration of a multirest below the staff?
>
> what are you using to generate the multirest? musixte
r after the gap with an "R"
command option on the last note in voice 1, but that command MUST be the
very last one before the group-ending "/".
Once again, please give it a workout and report any bugs or issues.
--Don Simons
---
TeX-music@tug.org ma
The package is available from WIMA at the following address:
http://icking-music-archive.org/software/pmx/pmx290.zip
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Don Simons
> Sent: Saturday, June 01,
That’s an RTFM, but in this case, it’s the MusiXTeX manual, and it wasn’t that
easy to find. You need to enter inline \stdstemfalse\ before the note where you
want it to ignore the standard rule for extending all stems to the middle staff
line.
--Don
From: TeX-Music [mailto:tex-music-bou
Thanks very much, Luigi. I'm not sure why I messed this up, but it's easy
to fix, and will be fixed in the next release.
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Luigi Cataldi
> Sent: Sunday, June 09, 2019 12:2
This is educational...over the years I've noticed some horizontal alignment
issues related to whole notes, but never realized there was a built in macro
to fix them. So naturally PMX doesn't make the whole note correction. I
suppose I could make PMX automatically use \wholeshift when appropriate. B
> -Original Message-
> From: Bob Tennent [mailto:rdtenn...@gmail.com]
> Sent: Sunday, June 30, 2019 4:40 AM
> To: Don Simons
> Cc: 'Werner Icking Music Archive'
> Subject: Re: Re: [Tex-music] alignment of \flageolett in \Largenotesize
>
> >|This
39 AM
> To: Werner Icking Music Archive
> Subject: [Tex-music] Varying number of instruments
>
> I stumbled across a problem, which was already treated by Dirk Baack and
> Don Simons, but the solution is unclear to me.
>
> I have a configuration with voice and piano. And I want some
Andre, thanks for discovering this bug.
I don't have a solution yet. This will be pretty difficult. The basic reason
is that for normal moved dots, I got them to move by redefining \C@Point ,
which musixtex includes in the dotted note macros \qup etc. But for 2-note
tremolos, I use a different me
om: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner....@tug.org] On Behalf Of Don Simons
> Sent: Tuesday, August 13, 2019 11:11 AM
> To: 'Werner Icking Music Archive'
> Subject: Re: [Tex-music] Trills in pmx
>
> Andre, thanks for discovering this bug.
>
>
> \def\hbp{\h@symbol\@qbp}
> \def\hbpp{\h@symbol\@qbpp}
> \makeatother
> ====
>
> I should say sorry if my guess is wrong.
>
> regards,
> Hiroaki
>
>
>
> - Original Message -
> > From: "Don Simons"
> > To: "'
Jean-Pierre--
I'm having a hard time understanding what you're saying and doing. But I'm
quite sure your MusiXTeX coding is inserting some "unrecorded" horizontal
space somewhere, because when I process it I get the dreaded "underfull box"
(see below), and that doesn't happen with Bob's solution,
One solution...the best in my book :) ... is simply to use PMX:
==
2 1 11 16 0 0 0 0
1 1 20 0
tt
.\
rb4 rb1 [j e14 ]j rb8 rbd8 /
[ f15 g- c g+ ] [-3 e ]j rb[ju a- b b+ a g ] /
==
(To be hone
Hi, Aki--
I'm afraid there no direct way to do this in PMX. There are two
work-arounds, illustrated in the code below. You could write a TeX macro to
slightly simplify the input for the \zcharnote approach.
--Don
% nv noinst mtrnuml mtrdenl mtrnump mtrdenp xmtrnu
As “huge” as it may be, you should attach the full PMX file or I probably won’t
be able to help.
--Don Simons
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Tuesday, January 07, 2020 4:11 AM
To: tex-music@tug.org
Subject: [Tex-music
Dieter--
I managed to narrow this down to the full bar rests right before the change
from 2 instruments to 1 . Then déjà vu did strike. I searched emails for
\atnextbar and found that you had uncovered exactly the same problem in July.
It was very tricky to nail down and there’s still no per
PMX can’t yet handle bar-crossing beams. Here’s a way you could get that with
inline TeX. I’ve used numerical values for the note levels to avoid any
possible later confusion about which octave later notes are in. And that’s the
same reason I put rests rather than notes in the original PMX, in p
working example. In
particular I do not understand, why you must use rests in order to print eighth
notes. I do not see, how I could extend this example to solve my real life
problem.
Have you been working on this problem?
--Dieter
Am 16.01.2020 um 18:14 schrieb Don Simons:
1 1 2 4 2 4
[l e15l e16l ] r1 r1 d15sl | /
===
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Thursday, January 16, 2020 2:45 PM
To: 'Werner Icking Music Archive'
Subject: RE: [Tex-music] bar crossing beam causes error message
\shlft8{\islurd0{'g}\grcu g\off{-\noteskip}}%
\ts0{'a}{-.6}\txtdyn{14}{-.5}{\medtype\it cho.}\ql a\en%
--Don Simons
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Akihiro
> Moriguchi
t; >
> > t
> >
> > .\
> >
> > w1i
> >
> > Gsxg5 a4 D"cho."+19 /
> >
> > =
> >
> > which produces
> >
> > The TeX input is
> >
> > \input pmx
> >
> >
Aki--
Congratulations on finding this guidance in CCN's expanded PMX manual.
However, I'd caution you (and others) that that manual has not been updated
in quite some time. So you should also keep handy the latest version of the
basic PMX manual, which I update with every official release. (And I'
n dotted 2-note tremolos. I'd
appreciate any feedback in case I've introduced any bugs. Bob Tennent will
soon be preparing it for submission to TeXLive to make it more easily
available to platforms other than Windows.
--Don Simons
---
TeX-music@tug
fully they're now fixed. If you downloaded the older one from yesterday,
to be safe please replace it with today's version.
Happy PMX'ing!
--Don Simons
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Monday, January 27, 2020 7:30 AM
To: 'Werner Icking Music A
x27;d very much
appreciate it if some more folks would download the zip, compile pmx294.for,
and report back on what system and compiler you used and whether the
resulting executable runs OK.
Thanks,
--Don Simons
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Tuesday, January 28,
It's frustrating not having any Linux version in which I can personally
investigate the problems people are reporting with compiling and running
PMX294. As far as I recall, we've never had problems like this before. So if
it's possible to make it run alongside or under my Windows 7 OS, I'm willing
Jean-Pierre wrote
>
> BTW does anybody know why are MusiXTeX and pmx files downloaded
> about 10 % as many times as the pdf? Who finds something useful in them?
>
How does one find out how many time a particular file on IMSLP has been
downloaded?
Rodolfo et al--
The purpose of those two commands is to adjust the vertical spacing between
systems on a page so that the distance between the bottom line of the last
staff in each system and the top line of the first staff in the next system
are all equal. \starteq must be entered somewhere in th
Rodolfo et al--
I sent this message 4 hours ago and it seems like it never got posted, so
I'm trying again.
The purpose of those two commands is to adjust the vertical spacing between
systems on a page so that the distance between the bottom line of the last
staff in each system and the top line
ic [mailto:tex-music-
> bounces+dsimons=roadrunner....@tug.org] On Behalf Of Don Simons
> Sent: Wednesday, July 01, 2020 1:06 PM
> To: 'Werner Icking Music Archive'
> Subject: Re: [Tex-music] PMX: \starteq and \endeq
>
> Rodolfo et al--
>
> I sent this message 4
copy the files into wherever
you keep .pfb's . You probably don't even need to update the filename
database.
--Don Simons
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
Francois--
On my Win98 system, I go to Start|Programs|MiKTeX|MiKTeX Options. After
clicking on (i.e., running) "MiKTeX Options", the very first screen
("General" tab) has a button labelled "Refresh Now".
--Don Simons
> -Original Message-
> From
There was some reason I included that restriction in the docs, but at the
moment I can't recall what it was. I just tried two simultaneous cross-block
postscript hairpins and they did work, even across a linebreak. I'll offer a
free copy of the upcoming PMX 2.5 to the first person who
X level solution. In other words I (probably) ask for
> a new PMX
> feature.
I downloaded ritornel4.mtx from the archive but I can't get it to compile. I
get the message
c:\my documents\pmx>prepmx ritornel4
==> This is M-Tx pre0.54c (Music from TeXt)
I wrote
> I downloaded ritornel4.mtx from the archive but I can't get it to
> compile. I
> get the message
>
> c:\my documents\pmx>prepmx ritornel4
> ==> This is M-Tx pre0.54c (Music from TeXt) <15 August 2003>
> Writing to ritornel4.pmx
> No music paragraphs!: ERROR on line 1
>
> Any idea what's
Olivier wrote
> Dear Christian,
>
> Would you like to get that?
>
> % 24-25
> m4400 b8 o> g c4 \MB{1.5}\ r4 r8 c |
> L: fri-ske Kys, Pe-
> m4400 (d bu4- Dmf-3+1 zg zd cu8+ )f-7 zg zc- [ g8++ o. e o. c o.
> a o. ] cu za ze o. |
> m4400 r4db [+2-2 g8 Df-2+1 o.-10 e o.-10 c o.-9 ]j r4b |
> m4400 r2b
ative
accidentals, "n" means "leave it right where it is according to the key
signature" and "s" means "raise it 1/2 step from where it would be according
to the key signature", etc.
--Don Simons
> -Original Message-
> From: [EMAIL PROTECTED
n find is 1.36 dated
4/98, and it allows slur ID numbers, so the "s&t only" days were before
that. The oldest M-Tx I find is 0.52 dated 10/98, but it may have started
earlier.
--Don Simons
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTE
Andre Van Ryckeghem wrote
> To Olivier : i did not test if the midi is not right, but i suppose, if
> using in line tex for the keychange, the midi will not see it.
I haven't looked at this yet. But maybe you could use midi-only accidentals
after the in-line TeX key change.
--Don
___
> Christian Mondrup wrote
> ...The ritornel 'Søde Narcisse' published today
> illustrates that, for example in bar 4 where I have vertically offset the
> RH staccato dots to positions above and below the beams. The PMX syntax
> allows fractionwise vertical offset, but typesetting result demonstrat
ended to be used, you don't have to enter anything twice:
% nv,noinst,mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig,
11 4 4 4 4 0 -1
% npages,nsyst,musicsize,fracindent
1 1 20 0
t
./
Ar
%1 K+1+1
d it. I suppose that's
because the most common reasons for shifting dots have to do with chords or
slur or tie ends, none of which applies to rests.
--Don Simons
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Hiroaki
> MORIMOTO
&
Olivier Vogel wrote
> The problem is due to PMX. If a whole note is shifted to the
> left, respectively to the right, PMX introduces the code
> \loff{\wh *}, respectively \roff{\wh *}.
>
> I consider that as a bug of PMX, because the width of whole notes
> equals 1.25 width of other notes (half, qu
n T.111, it lists the
horizontal shifts as all being about 6 pt. First, the shifts for whole notes
described in this section should be 25% larger than for non-whole notes, and
second, the absolute distance depends on musicsize; 6pt only applies to
non-whole notes at 20pt musicsize.
--Don Sim
#x27;t
> understand why [m2lj f1 ] doesn't work. Does it mean that the
> multiplicity can not be forced for staff-jumping beams?
I've looked at the issue of changing multiplicity of staff-jumping beams in
the past, and thrown up my hands i
I never considered the possibility that anyone would want to have a slash on
a single grace with 2 flags. You are probably the first person in history to
try this, so there is no "normal". Is this a notation you really want?
--Don Simons
> -Original Message-
> From:
t; And I
believe that's the truth.
If anyone would like to suggest a better way to state all this in the PMX
manual compared to what's there now, fire away.
BTW, as I just suggested, ANY user with access to a FORTRAN compiler is free
to fiddle with the
ices than it should, but if each voice within the last input block is
otherwise OK (meaning syntactically correct and containing the same number
of bars as all the others in that input block), then PMX will silently
ignore all of that input without any error messages.
--Don Simons
If you inse
. The view over the LA basin was jaw-dropping,
from the ocean to downtown to the mountains. We could see snow-covered peaks
over 100 miles away.
--Don Simons
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
d. Here's a program you could try with g77 to
test the concept:
character*80 pathq
call getenv('PMXMODDIR',pathq)
print*,'PMXMODDIR: ',pathq
end
Before running the test, you can set the environment variable by entering
PMXMODDIR=/whatever/whenever/
on the command line.
--
7;t want to create a default path to pmx.mod because (1) that would
only have required one positive action (creating pmx.mod) to initiate,
making it more likely that a user would lose track of things, and (2) that
would be difficult to make compatible across different OS's.
--Don Simons
___
The new beta version 2.146 at
http://icking-music-archive.org/software/pmx/pmx2416.zip
has a hack at enabling include files. Please do some testing of these
capabilities, including purposely introducing errors in syntax, file names,
or file locations. The length of the following description is a sm
7;t
surprise me at all if Olivier or Andre comes up with a more elegant solution
:-)
And I'm really looking forward to Lully!
--Don Simons
=
3 3 4 4 4 4 0 0
3 6 20 .1
Basso
Viola
Violin
bat
.\
%1S5P1
%3S5P1
%2S4P1
h
Movement I
c03 d e f g a b c
er someone
inadvertantly went up an octave when he meant to go down, nor questioning
where there is any organ in the world that has such high notes on its
keyboard. But evidently by bar 25 PMX got exhausted and gave up. I think we
should all give PMX a round of applause for
ot; in a
slur command will cause the slur to have the normal curvature (between "f"
and "h").
--Don Simons
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
Andre wrote
> I known
> that Don (always) is right ...
I appreciate the thought, but I disagree with it. But if I'm not always
right, maybe I'm wrong about this, and maybe therefore I really am always
right. And I know a barber who shaves everyone in town except himself.
Here's one argument why
> \readmod{..\..\vlzingt\vlzingtpmx\savobei}
>
> (! Too many }'s
> \.#1->{\accent 95 #1}
> .
>
> Is there a way out for this error (without putting all files in 1
> directory)?
>
Try using forward slashes in the path name. TeX may be confused by the
backslashes.
--Don
main reason I didn't bother to create an index.
(The other is just laziness).
--Don Simons
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
Robin--
Thanks for keeping your eyes open :-)
--Don Simons
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Robin
> Fairbairns
> Sent: Sunday, February 15, 2004 3:19 PM
> To: Typesetting music with TeX
> Subject: Re: [Tex-m
1 - 100 of 859 matches
Mail list logo
