I tested them on 10.6.5 and they seem to work (no test with real input, just
checking that the libraries load at program start doesn't fail). If there's a
possibility to get binaries linked in a way that they don't get broken at a
change of the OS version I'd be interested to know how that works
after having reinstalled fink and gcc45 (which needs a download of the java
package from developers.apple.com because Apple has broken some dependencies in
the packages and gcc45 contains par default also java) gfortran is accessible
and compiles pmx2521.f out of the box, barsant.pmx is translat
hi everybody
to find out what could be Philipp's problem (and to get PMX back to life after
a system upgrade from Mac OS X 10.5 to 10.6) I tried to install the intel386
version for MacOS provided on the WIMA page ... and failed
1st attempt, run the binary pmxab: the compiled pmxab relies on a d
Hi Philipp
I can't test your code right now because I just have updated my Mac OS to 10.6
which broke all the programs still compiled for PPC. However, the line end
thing (line end character in Mac != DOS != UN*X) you can test easily with a
tool like zip/unzip:
> zip temp.zip test.pmx
> unzip
> It would be very regrettable if the many hours and great deal of knowledge
> that have been put in these programs would be lost because it is locked up in
> a programming language that nobody knows any more.
>
> With a port to Lua (or Perl, Python, Ruby), I see as the main advantages from
> t
Thanks Dirk to draw our attention to this new development. Such a major
change--and it would be a major change--would perhaps also give opportunity to
think about how to overcome some limitations to MusixTeX and friends which are
due to its design. Quite some inline TeX coding could probably mov
16GB of disk space is not a great deal for a decent server; I fear
that 10 TB/Day (with a peak of 103 TB in a single day!) is the real
problem.
Indeed, 16GB disk space is no big deal, setting up a mirroring system
could spread the load, though that asks for quite some work, knocking
at a
> The results that I have, now, are quite weird, because:
> 1. the creation of a TeX file from MTX of from PMX work pretty fine
> 2. the final TeX file is compiled without any error
> 3. the final aspect of the compiled TeX file is quite bad, and shows
> all the notes moved on the left side of the
I had the same problem and found this the most practicable solution:
generate the PMX code, translate it to TeX and then move the text into
the LaTeX source. You have to add some \input commands in the header
of the LaTeX document and then the exact formatting can be done there.
I also use this
Hi Don
I don't know if the error message caused by the code snippet below
points to a real bug: the code has been generated by mtx with meter set
to 4/4/4/4. However, do to a superlfuent 16th in the bar before (not
contained in the snippet) mtx inserted a m1/16/0/0. And this runs into
the err
In this case M-Tx expects 4 lines of music instead of two and
aputomagically puts two empty bars for the absent lines. The only
solution I can imagine is to manually delete those lines of rests
before to process the files with pmx.
for the time being you may fill the needless staves with invis
When a person familiar with Word, Powerpoint, or Finale, or other
WYSIthingy stuff sees me making corrections in a MusiXTeX file after
he pointed out errors in my score, his face becomes green :-)
Has anybody a similar experience? I doubt things would be different
with PMX.
The point should
In my humble opinion, the whole sentence is obsolete. Can anyone tell
me
why it is untouchable?
What's about replacing/completing it by an advice to use the
preprocessors and presenting the manual more as a sort of technical
reference to the musixTeX internals, being only one (of course very
This problem should be solved with MusiXTeX 113. Which version do you
use?
ups, still version 112, thanks for the hint
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
one: Voices B; Clefs F;
Style: one
Meter: m4/4/0/6
Sharps: 2
Size: 16
%%\input exampledef
%% B Ab w155m
r4 d83 a d f1.d a+ a- a- b c | d f a d- c e a e b d g b- a c f a- |
g12 b e g f a d f- g b d g- a8 a- |
Bernhard Lang | Physical Chemistry Department,
Sciences
e code it complaines about. Shouldn't that def
be added to musixtex.tex?
regards
Bernhard
Bernhard Lang | Physical Chemistry Department,
Sciences II
21, Avenue du Denantou | University of Geneva; 30, Quai Ernest Ansermet
CH-1006 Lausanne, Suisse| CH
e code it complaines about. Shouldn't that def
be added to musixtex.tex?
regards
Bernhard
Bernhard Lang | Physical Chemistry Department,
Sciences II
21, Avenue du Denantou | University of Geneva; 30, Quai Ernest Ansermet
CH-1006 Lausanne, Suisse| CH
Thanks Andre and Don, merci Jean-Pierre for your suggestions.
\zcharnote g{\musixchar71} (between \notes and \en)
(but you must care about the spacing yourself)
that's the reason why I asked the question :-). The empty clefs are a
clever solution. Concernig the size of the symbols and conce
Hi all
I've got two questions concerning clefs and keys:
Is it possible to force a clef symbol being printed (with all automatic
spacing) whithout the key
is being changed? (\changecontext does not put a clef symbol when the
\setclef is called with the actual clef as parameter).
When setting
I seems that G77 is so well optimized that it closes the output file
*before* it writes the last lines into it. The faster the computer, the
more likely the error.
The workaround I found was to open files like this:
open (unit=9, file='jollyfile.txt', status='unknown')
close (unit=9,
The interesting thing is that if I launch that binary on barsant.pmx
with end-of-lines converted to mac format (Ctr-R) then I get the
reported error message. But if I replace with a unix end-of-line
format (Ctr-N) file then pmxab completes successfully with a MusiXTeX
processable file barsant.t
I have downloaded and installed the MAC OSX version of PMX 2.510. To
test the installation I ran PMX on barsant.pmx. This produced the
files barsant.pml and pmxaerr.dat (which contains only the single
integer 0) but no barsant.tex. I also get the error message
Starting first PMX pass
fmt: read
Note where the pause sign and the "|" have gone!
Is it offending to make a macro with already a \def in its definition?
No, but the "|" is the problem. This character seems to be declared as
active (TeX's catcodes) inbetween \notes...\en. Replace the "|" by a
\nextstaff and you'll get what yo
2. TeX and the X pronounced as the Greek chi is absolutely NOT like
"Bach" or "Loch"! There are two very different versions of "ch", the
Bach and Loch version being more deep throat and ugly, and the chi and
TeX version being softer and higher, it is somewhat a relative to
"f".
Where do y
mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
Bernhard Lang | Physical Chemistry Departement,
Sciences II
21, Avenue du Denantou | University of Geneva; 30, Quai Ernest Ansermet
CH-1006 Lausanne, Suisse
If you are typesetting guitar-music with two voices you often need
in the lower voice a half note and the upper voice has for example
a figure consisting of eighth notes. The first note of both voices
have the same pitch. Usually the half note has a stem down and an
upper stem is integrated in t
At the other side is a lawyer question. I think I can write for myself
as
much I like. But am I allowed to publish this work (pdf)? I don't plan
to
sell it. But would it legal to sell the pdf or printed paper?
Details will depend on the country you're living in, where IMA is
hosted (Danmark)
nor any command which controls page numbering--unless Don used
some fancy tricks I missed when quickly scanning through the file.
Well I'm not sure I'd glorify it as "fancy", but there is a macro
\toppageno
defined in pmx.tex, which PMX uses for inserting page numbers and
optional
text into a
Did you already consider to use PMX/Mtx? It makes typesetting music
_much_ easier, especially adding lyrics.
On Nov 29, 2005, at 4:08 PM, Bob Tennent wrote:
I've just added lyrics to a piece for the first time using what was
apparently available, according to the musixtex documentation. It was
How to prevent page numbers to appear in the score? The command
/nopagenumbers doesn't work at all.
I've tried to switch off the numbers and remove pageno from theese
definitions (I've put them to the score of course). Without success.
From what you're telling us I'm pretty sure that you've put
On Aug 15, 2005, at 2:32 PM, Trent J wrote:
Hello all,
Is there a way for setting barlines for instrumental groups in either
pmx or mtx?
i.e. continous barlines for upper strings violins I & II, Viola. Then
a separate barline for voice then continuo.
Is there a way to do this.. all that
I'm confused. The code
e2 za zb Gm02Afs4 g
does not work for me in PMX. More precisely, PMX finishes, but
produces bad
TeX. The PMX code does appear to obey the syntax rules OK, asking for 2
graces with multiplicity 0, not 1 (eight note graces) as Bernard
stated).
I've checked the FORTRAN, a
The code dealing with 'G' is ancient, and probably can't cope with all
the extensions to the PMX syntax that have happened since it was
written.
M-Tx needs to know the number of grace notes, so it counts them by the
primitive expedient (adequate at that time) of expecting the first
character
af
hi all
the following code snippet
e2 za zb Gm02Afs4 g
works well with PMX (a chord with two following up 8th grace notes) but
MTX refuses issuing
Bar end occurs in mid-note: ERROR
Obviously, the last letter 'g' is considered as a normal note, which of
course isn't. Is there a way to bypass
On Jul 27, 2005, at 6:22 AM, Veronica Brandt wrote:
Remember a while ago some people were worried about spam so they made
a page with the email addresses in an image file:
http://www.icking-music-archive.org/email-addresses.html
I've had a few (maybe three) requests for certain often obscure p
One question to this hint: must I always set three voices (I mean in
every
bar) even though if I somtimes only have two voices, or only one voice?
When using only two voices, pmx keeps track of changing number of
voices in the same stave (for obvious reasons you may change number of
voices on
==
1 1 4 4 4 4 0 0 1 2 20 0
t
.\
c44 D"Less dangerous" b a g | \zqu u\ c b a g /
c44 D"Safe" b a g | \zqu{16}\ c b a g /
==
does the job
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-ar
dotted half note at pitch g in the tenor octave.
For details of the syntax you should refer to musixdoc.dvi
Other variants of inline TeX start with either two or three consecutive
backslashes. This controls where PMX inserts the chunk into its own TeX
output.
hop
requested URL was not found on this server. If you entered the URL
manually please check your spelling and try again.
If you think this is a server error, please contact the webmaster
Error 404
icking-music-archive.org
Fri 13 May 2005 05:27:23 PM CEST
Apache/2.0.40 (Red Hat Linux)
Bernhard Lang
the composer will do
the job. Just that you have to add some keywords like "free", "sheet
music", "edition" etc to avoid lots of CD advertisings (most of them
even out of sold)
regards
Bernhard Lang | Physical Chemistry
Departement,
So my question in now: is it really only possible to set two voices? If
not, how can I set three and more voices?
Very recently, someone asked the same question and you'll find the
thread in the mailinglist's archive. I remember also a very clever
solution by superposing two staves with zero vert
your 20 pt File is O.K. I suppose you have simly forgotten to
delete the .mx2-File before compiling the changed source. Delete
the .mx2-file and run pmx-tex-musixflx-tex. Then You'll get, what you
want.
Gerd
I can simlpy describe, what I've done:
First for the file with 10pt:
1) pmxab file.pmx
2)
hi all
I've got two questions to the MusixTeXperts: a) the sequence
\setclef10\changeclefs
produces output only when the clef before is different from 0. Is there
a possiblility to force the output even when the clef happens not to
change at that place?
b) the sequence
\generalsignature{-1}\setc
cript stumbles across the kpathsea library. It cannot
find/use it although it must be there and working since TeX works. How
is this on your machine? Do you use dvipng, or is there an alternative?
dvipng seems not to be supproted by the fink collection.
best regards
Bernhard
Bernhard
f the same piece are incorporated in one souce (by
using the CASE statement). When changing clefs or staves, the octave
has often to be readjusted according to the clef. With the possibility
of giving absolute octaves when prefered (as in PMX) this problem would
not occur.
best regards
Bernard
Ber
On Mar 18, 2005, at 1:20 PM, Dirk Laurie wrote:
I suggest the following patch to lyrics.c (I don't know how that reads
in the pascal version)
546c546
< sprintf(l, "\\mtxAssignLyrics%s%s", instr, atag);
---
sprintf(l, "\\mtxAssignLyrics{%s}%s", instr, atag);
Or even better,
spri
urces, p2c.h is needed and some modifications to the makefile have
to be done (having some c-files as sources in the c-only version and as
targets in the pas->p2c->c version induces a conflict).
As p2c is under GNU copyleft, couldn't that file be included in the
mtxC dis
I can reproduce the error similarily on a Redhat Fedora Core 2 pc when
processing the sample source with pmxab 2.501..
Furthermore, on the Fedora pc a pmx 2.506 binary compiled with g77
fails with a segmentation fault if there are trailing newline
characters in the pmx source. If I remove the n
kind of things without having seen the
score. Thus, in an edition, I would make an annotation but put these
notes all as f-sharps.
- two possible typos
bar 5, third note in tenor: c sharp?
bar 13, last note in the bass: a?
a happy new year
Bernhard
Bernhard Lang | Physical
I'm surprised no one has mentioned numbering at a regular frequency
rather than at the start of each system. Doesn't anyone want that
option? I suppose I could browse thru the archive to see what folks
have done.
But in musixtex it is implemented freqbarno or something like this, no?
Therefore
What's about defining something like
\def\writebarno{\ifnum\barno>1\formatbarno{\the\barno}\barnoadd\fi}
\def\formatbarno#1{\lrlap{\tenrm\it#1}} % (to stay with Hermann's
example)
in pmx.tex? Redefining of the output is then much easier, any fancy
formatting would be possible this way.
Other pr
On Nov 17, 2004, at 5:03 PM, Christof Biebricher wrote:
On Wed, 17 Nov 2004, Jean-Pierre Coulon wrote:
I agree that it is a nuisance to find our open source scores thus
made
subject to bargaining. However, what can we do about it? I'm unsure
whether http://www.pianofiles.com/ breaks any 'laws' at
On Oct 18, 2004, at 8:04 PM, Dirk Laurie wrote:
Surely there must be a compiler option for Turbo Pascal source
compatibility.
There are --borland-pascal and --delphi which have the same effect on
the mtx sources, making string size warnings disappearing, but
"notes.pas:159: error: `name' is a ke
eX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
Bernhard Lang | Physical Chemistry Departement, Sciences II
21, Avenue du Denantou | University of Geneva; 30, Quai Ernest Ansermet
CH-1006 Lausanne, Suisse| C
]
[mailto:[EMAIL PROTECTED] Behalf Of
Bernhard
Lang
Sent: Monday, October 18, 2004 3:52 AM
To: Typesetting music with TeX
Subject: Re: [TeX-music] MtX compilation problem (linux)
But p2c is obsolescent. It has survived
despite being unmaintained for eleven years because there was no
decent
alternative
But p2c is obsolescent. It has survived
despite being unmaintained for eleven years because there was no decent
alternative. Now there is one. It is only a question of time, see
http://www.freepascal.org/fpcmac.html
before fpc runs on a Mac, and then the last remaining reason for
providing C
On Oct 17, 2004, at 9:20 PM, Guido Milanese wrote:
after a computer crash I am reinstalling all my musitex system. All
right with
musixtex and pmx. A problem now with mtx. I try to compile following
the
instructions on the README under section 5 (Compiling with a C
compiler on a
GNU system). I a
On Oct 7, 2004, at 2:54 PM, Mag. Mario Aschauer wrote:
I have been trying to use music symbols such as notes and rests in
texts
written in LaTex using MusixTex. While I do get nice results for
complete
scores I can't manage to put in, say a half-note or a short rhythmic
sequence in a regular sent
On Oct 5, 2004, at 2:21 AM, Simon Dreher wrote:
how can I code a breve note with m-tx / pmx?
using length '9'. This should work "out of the box" and all your
questions should be answered by this.
regards
Bernhard
Bernhard Lang | Physical C
On Oct 5, 2004, at 2:21 AM, Simon Dreher wrote:
Why the fermata at the last full bar rest is shifted to the right and
not centered in the middle of the bar? How can I get it centered as on
notes?
The full bar rests seem to be a little bit more to the right, too; you
can see it much better if you
Dear All
In a larger LaTeX document I've included a lot of several lines long
music examples typeset by MTX/PMX. I want to have the music centered,
but including the PMX output into a center environment flushes to the
left anyway (why?). Only including all music in \mbox-es or \parbox-es
yields
You are getting exactly what you ask. Maybe not what you think you
ask.
|| is not a bar line, it is a visual separator. It can appear in the
middle
of a bar, and the way you have coded this excerpt, in the middle of
the bar
is just where it appears every time.
What you want is probably
Met
hi Dirk
when MTXing the following code
---snip---
oneline: Voices B; Clefs F;
Style: oneline
Meter: m8/2/0/0
d0 c || f d c9 || a0+ d- c9 || e0 d c9 || a0 d c9 ||
---snap---
additional bar lines are inserted in the middle of all bars except in
the first. This not a severe problem as starting with m
Can anyone help me install musixtex on a Mac with Oztex? I have
followed the advice of Eric Petersen from this list (14 November 2001)
yet when I try to compile any musixtex examples I just get voluminous
complaints from Oztex usually regarding runaway arguments.
Did you put the musixtex files s
the idea is to have a key signature and then to group
the notes of a melody, but this notes have accidents
and some are natural.
Could you provide a more concrete example of what you want to get and
your code which gives the problem?
regards
Bernhard
__
On Mar 20, 2004, at 10:42 AM, Guido Milanese wrote:
Dear Experts,
while compiling a tex file of a vocal score obtained from mtx | pmx
(both do not complain) I receive this error message:
*
MusiXMore ADditional instruments T.99 <24
On Mar 3, 2004, at 10:20 AM, Cornelius C. Noack wrote:
On Wed, 3 Mar 2004, Andre Van Ryckeghem wrote:
How can i put a '"' in a D-command, ie: D"R\"uckpos."
Thanks
Andre
Olivier's method is a bit difficult (or at least lengthy)
to use for non TeXperts. Perhaps someone can come u
I'm trying to set up a local MusixTeX installation in my home
directory at
my university. I use the TEXINPUTS and MFINPUTS environment variables,
and
kpathsea can find the musixtex macro and font files.
In any case, $TEXINPUTS tells tex, directly to scan the directories for
the files it is searc
Dear Irwin
Thanks for that hint about note edit.
There exists an e-mail list for MusicXML developers:
http://www.recordare.com/lists/index.html
I already subscribed there and posted more or less the same question.
The answer was a clear no.
Grüße
Bernhard
___
hi all
Triggered by a recent thread on this list I looked into musicXML as
defined on http://www.musicxml.org/ and found it worth to give it a
try. Hopefully in not too far future I'll come out with an experimental
version of pmx2xml / mtx2xml (opposite direction is much more work to
implement
LaTeX is taking exactly \textwidth times \textheight as body of the
page. Anything else, like \headheight, \headsep, \footskip, is stuff
around which may shift the body of the page, but it won't affect its
size. In TeX, to my knowledge, the job is done by \hsize and \vsize
which give
the dimens
On Jan 15, 2004, at 2:08 AM, Don Simons wrote:
The argument of the command will be the
name of the file including any necessary path information
What do you think about a second environment variable PMXINPUTS which
points to a common location where include files are to be found (like
TEXINPUTS f
Hi Don
I just compiled your example using the gnu fortran compiler g77 (you
should have mentioned that lines have to be indented) under Mac OS X
and it works. But, as someone pointed out already on the list this
morning, you have to set your environment as
export PMXMODDIR=...
or
PMXMODDIR=.
I've seen the line end problem also (PPC-Linux). If I remember well, the
last line wasn't seen if it ended without line feed, but I'm not sure.
Adding such a LF or CR (don't ask me which one) reduced the error to a
warning and I didn't care anymore. But I would also say there's something
in the PMX
> 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 dimensions in the source code and recompile it himself.
I did this onc
On Fri, 5 Dec 2003, Christof Biebricher wrote:
> Old music scores where each voice has its own stave should contain
> neither slurs nor ties. There are unnecessary. Slurs originated in
> string music where the notation really made sense. It later was
> introduced to other instrumental music as `im
On Fri, 5 Dec 2003, Christof Biebricher wrote:
> Both solutions leave out the possibility of using phrasing slurs in
> vocal music, but it is rarely used and in my opinion contradictory,
> because phrasing should be dictated by the text. Legato is -- and
> should be -- indicated in vocal music exp
On Mon, 1 Dec 2003, Roland Stigge wrote:
> It's possible to call fromdos from your build scripts, Makefile, etc.
Yes, but that means not only that you have to tell your Makefile rules how
to read things coming from another system but also you have to tell it how
to make formats for other systems
On Mon, 1 Dec 2003, Roland Stigge wrote:
> On Mon, 2003-12-01 at 11:34, Bernhard Lang wrote:
> > The only clean solution: write your own input routine which is capable of
> > handling the different line end codings.
>
> Feel free to use already existing tools like d
On Mon, 1 Dec 2003, Dirk Laurie wrote:
> Don Simons skryf:
> >
> > It was the d*#@ line-ending characters! Why doesn't everyone just use
> > Windows? :-)
> >
> One might also ask the question: why can't all compilers produce code
> that will accept any of CR, LF, CR+LF or LF+CR as end-of-line?
Th
On Wed, 5 Nov 2003, Maurizio Codogno wrote:
> ps: please remember the new address for the list,
> [EMAIL PROTECTED] !
It should be [EMAIL PROTECTED] no?
^
regards
Bernhard
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-musi
81 matches
Mail list logo
