[Tex-music] Font-based slurs in PMX
I have been using PMX for seven years, but confess to still basically being in the dark about the difference between font-based s and t slurs. So I did some systematic experiments. Here is everything the PMX Reference Manual has to say on the topic. With font-based slurs, t is equivalent to s but with several minor differences to be explained later. ... ID codes cannot be used with font-based t slurs. ... For font-based slurs, the unique aspect of t slurs is that if one starts or ends on the same note as an s slur, the former will be moved away from the notehead to avoid a collision. This only works if neither slur has an ID code. This feature is only retained for backward compatibility. ... To specify a font-based tie in PMX, use a slur command and include the option t in it, somewhere after the initial ( , ) , s or t. In practice, some not-so-minor differences are encountered. The first of these flatly contradicts the User's Manual. c44 d e f g a b g c2 tt c tt ERROR in line 17, bar 3 Cannot use t as an option on a tie c44 d e f g a b g c2 t-1 c t-1 ERROR in line 17, bar 3 +|- for slur height only allowed in s-slurs Thus, t is indeed a poor brother of s, its only virtue being that in one very special case its use saves one some manual adjustment. I suspect the original reason for the t slur was only because, before labelled slurs, one needed two different slur symbols in the slur-over-a-tie situation. Given that the use of labelled slurs now allows enormous flexibility, it seems that the t slur is retained in PMX for the sake of backward compatibility only. New scores need not use it at all. Am I wrong in saying this? Dirk ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [Tex-music] Right justifying
Staffan Lundberg skryf: I have a problem with right justifying of U: text The text Till~omkv\ade should be right justified, regardless of the actual system length. I have tested several variants, with more or less success. Does anybody have a solution which automatically does this justification so that I can skip this manual trial-and-error method? The line U: ~ ~ ~ ~ ~ ~ !bf Till~omkv\ade means: six notes with no uptext, set bf as the default uptext font, put 'Till~omkv\ade' above the seventh note, sticking out to the right of the note. The line U: \hfill !bf Till~omkv\ade means: on the first note put the uptext described by \hfill (since there are no actual letters, nothing happens), set bf as the default uptext font, put 'Till~omkv\ade' above the second note, sticking out to the right of the note. By trial-and-error you presumably mean that it is just lucky that the uptext happens to end exactly at the right of the system, since the amount of space defined by where the notes are is just right, whereas if you had more or fewer notes it would be wrong. Aligning things relative to the end of a system is an old problem and I do not know the answer. If anyone knows how to do these in MusiXTeX: (a) Right-justify D.C. al Fine with the end of the system (b) Put a fermata above the final double-bar please tell me too. BTW: I had some difficulty processing your sample. Next time: send the files as attachments so that they are easy to save and so that e-mail line breaks do not ruin them, and let the main version of the input be one that demonstrates the problem, not hidden in comments. The person who tries to reproduce the problem wants to save the file, run M-Tx and look at the output. If he has to edit the source first, he is going to ignore the query unless he happens (as I am today, so far) in a good mood. Dirk ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] M-Tx 0.55c
M-Tx 0.55c is now available. Follow the links on
http://icking-music-archive.org/software/
You will need one of the three program zip files, depending on your
system.
1. If you have the Free Pascal compiler, download the Pascal source
and compile it.
2. If you are using MS-Windows, download the Win32 binary.
3. If you have an ANSI C compiler, download the C source and compile
it.
You will also need the PDF file of the documentation. The zip file of the
documentation source is useful if you want to see how to integrate music
examples with LaTeX; the mtxlatex.sty file mentioned in the documentation
is in there.
BE SURE TO USE AN UNZIPPER THAT CONVERTS TEXT FILES TO YOUR SYSTEM'S FORMAT.
New users of M-Tx must read the first few sections of the manual first.
It is fast going if you already know PMX; if not, a careful reading
now will save you a lot of time later. Old users can just follow the
NEW 0.55 references in the index.
The README is mainly directed at people who wish to know how to compile
from source. It says nothing about how to use M-Tx. That is in Appendix
C of the documentation.
New features: include files, improved slur and tie handling, improved
implementation of the Space: command, human-friendly feature selection.
Include files
You can now say e.g.:
Include: part1.mtx
at any point of the score. The included file may itself include
other files.
Slur and tie handling
1. The meaning of {...} and (...) slurs, vague in previous releases,
is now fixed: (...) are ordinary slurs, {...} are ties. Because of
this feature, you will need a very recent PMX: 2.502 or later.
PMX 't' slurs are no longer used, except those that you code yourself.
Except in the case of continuation slurs )( and ties }{, PMX 's'
slurs are not used either.
2. You can have as many levels of nested slurs as you like, subject only
to the restriction of how many open slurs there may be. For example,
( c ( d ( e { f f } g ) a ) b )
is allowed. To turn this into legal PMX, labels are automatically
inserted, so that the above is equivalent to
(S c (Q d (O e {T f f }T g )O a )Q b )S
Note that the labels are chosen in a part of the alphabet which
(one hopes) few people have been using for their own labels.
Spacing between systems
A different method is now being used to implement the spacing between
systems. You will no longer need to make a vertical adjustment to the
lyrics on the bottom line when Space: has been changed. Unfortunately,
this is not backward compatible with old scores in which you needed to
do that -- you will probably need to take out all lyrics adjustments of
the bottom voice. This change is at the mtx.tex level only and if you do
not like it, you can just put back the mtx.tex file from an older version.
Features rather than options
The Options: directive with Unix-like letters for options is being
phased out, and has been supplanted by Enable: and Disable: directives
that have descriptive feature names. E.g. you can say
Enable: solfaNoteNames
rather than
Options: f
Enjoy!
Dirk Laurie
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] bug in mtx?
Bernhard Lang skryf: 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. 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 Meter: 0/2 Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] bug in mtx?
Bernhard Lang skryf: a) MTX does not see a pickup in my example since '||' is not recognised as bar line (am I right?) Indeed. You could code d0 c | || f d c9 which will recognize the pickup but print a double bar line. b) that bars of length brevis should be noted 0/2 and not 8/2. Not quite. 8/2 is fully legal. 0/2 is the M-Tx abbreviation for treat the whole input line as one big bar, but check that it contains an integer number of half-notes. In the manual it is (somewhat misleadingly) called barless music. Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] MtX compilation problem (linux)
maurizio codogno skryf: Probably we need just some header file - Í'll investigate. However, as of now, mtxC055c is useless :-) Until about 0.50, my development environment was Borland Pascal, either running on a DOS machine or under xdos. Then it was p2c. When Christian told me that Free Pascal can compile M-Tx, I switched my development environment to Free Pascal. The first version of 0.55 indeed did not compile under p2c, but Christian found that a few small changes fixed the problem. 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 source will disappear. Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Clef change
Christof Biebricher skryf: It is common practice to prescribe the usual clefs, for piano treble clef for the right hand and bass clef for the left hand. If a deviation is intended, say for the left hand treble clef, one rather prescribes a clef change before the first note to emphasize the change than starting right away with the intended, but unexpected clef. Common practice, you say? In my copy of Volume One of Schubert's songs, Der Tod und das Mädchen starts with both hands in the bass. No G-then-F clef. Maybe accompanists have anyway to be more alert than soloists ;-) Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Bug in T112/musixtex.tex (was: Strange things)
Trent J skryf:
! Undefined control sequence.
l.39 \pnotes{1.73}\qb1{'C}\cclp
{'e}\en%
?
! Undefined control sequence.
l.42 \pnotes{1.73}\tbu1\qb1{'C}\cclp
{'e}\en%
This is an omission in musixtex.tex, version T112. Insert the line
[EMAIL PROTECTED]@cclp}
just after line 3229.
Dirk
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Up-front meter change not allowed in PMX?
I'm writing a piece in 4/4, so complicated that I asked for my first M-Tx PMX tex compile before completing the first bar. PMX complained. Reason: if the last bar of a piece is incomplete, M-Tx issues a blind meter change to make it look complete. But now the last bar is also the first bar. Boiling down the problem to a near-minimal input file, I came up with the following PMX input file: === % === --- --- 1 -1 1 4 4 0 6 0.0 0 1 1 20 0 0 ./ m3/8/0/0 da84d da1- da8 / === % === which produces === % === This is PMX, Version 2.504, 02 Nov 04 Opening bug.pmx Starting first PMX pass ERROR in line 8, bar 2 Pickup bar length disagrees with mtrnum0 v da84d da1- da8 / ^ === % === I make the deduction that a meter change at the start of the first bar is not allowed. It has been noted before on this list that a clef change at the start of the first bar is ignored. Both of these represent undocumented behaviour. A logical argument can be made out that a meter change at this point is preposterous, but there are situations in which a clef change is logical. As the author of a brief PMX tutorial, soon to be revised, I am in a quandary whether to document this behaviour. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] PMX default duration
The PMX manual states: Duration is never inherited and must be set at the start of each input block. A little experimentation with omitting to set duration reveals: 1. At the start of the piece, duration is 0 (i.e. whole notes). 2. Duration is inherited from the preceding voice. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Small error on PMX reference card
On the PMX 2.50 reference card, the syntax for accidentals in a note is given as [f,s,n] Accidental. Repeat for double. [+,- i +,- x] Vertical shift, \internotes; horiz. shift, notehead widths. [, x] Horiz. shift, notehead widths. [i] MIDI-only accidental. [c] Cautionary accidental. This means that any of the four items may follow the main accidental letter, in any sequence. However, experiment reveals that there must not be anything between the accidental letter and the adjustments, and that it is not important whether [c] comes before or after. Thus, the present (entirely logical) behaviour of pmxab corresponds more closely to the syntax: [c] Treat accidental, if any, as cautionary. [f,s,n] Accidental. Repeat for double. [+,- i +,- x] Vertical shift, \internotes; horiz. shift, notehead widths. [, x] Horiz. shift, notehead widths. [i] MIDI-only accidental. [i] is incompatible with [c] and the shift options, but IMHO that goes without saying: anyone coding 'dcni' will be unable to explain whether a cautionary MIDI-only accidental is printed or not. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Vertical space between systems
The story starts with my old bugbear: the PMX benign bug which distributes
free vertical space everywhere. In particular, it spreads the staves within
a system further apart rather than doing what I would prefer: put all free
vertical space between systems. Of course, it is not really a PMX bug: it
is standard TeX behaviour when you get to the end of a page.
I now have a solution, so obvious that it must have appeared on this list
before, and I apologise in advance to whoever has already pointed it out.
(BTW: searching the list archives is a tough job. You either have to know
in which month a contribution appeared or download the full list archive.)
The definition of \alaligne in musixtex.tex reads:
\def\alaligne{\stoppiece\contpiece}
Change this to
\def\alaligne{\stoppiece\vfill\contpiece}
and the free vertical space goes between the staves.
Dirk
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] PMX feature request: left-shifted arpeggios
MusiXTeX has a macro \larpeggio which gives a left-shifted arpeggio, to be used when some notes in a chord contain accidentals. PMX 2.50x does not support it: the ? ... ? construction generates either \arpeggio or \raisearp, a refinement which sets the arpeggio symbol half a notehead higher. It is easy to define \lraisearp by changing \arpeggio to \raisearp in the MusiXTeX definition of \larpeggio. My current workaround is: \let\carpeggio\arpeggio\let\craisearp\raisearp and then type 3 inline TeX when needed \\\let\arpeggio\larpeggio\let\raisearp\lraisearp\ reset by the corresponding code with \carpeggio etc. It will work until a score comes along with both arpeggio types in a single block. My request: PMX should support the insertion of \larpeggio and \lraisearp in the place of \arpeggio and \raisearp by one of the following mechanisms: (a) Extension of the syntax of '?', e.g. '?l' instead of the closing '?'. (b) (Preferable) By the time pmxab gets to processing the second '?', it is already known whether the notes in between contain accidentals, and the insertion of 'l' between '\' and the macro name could be made by pmxab itself. (c) (Ideal) (b) is the default behaviour, but (a) can be used to override it. I had a stab at implementing (b) last night, but forgive me Don, this time I could not successfully reverse-engineer the program logic. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] mtx patch suggestion
Bernhard Lang skryf:
when mtx-ing with more than 9 vocal voices, mtx produces under certain
circumstances faulty pmx/tex code like
\mtxAssignLyrics10{...} which should be \mtxAssignLyrics{10}{...}
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,
sprintf(l, \\mtxAssignLyrics{%s}{%s}, instr, atag);
In lyrics.pas, look for
l := '\mtxAssignLyrics' + instr + atag;
and change it to
l := '\mtxAssignLyrics{' + instr + '}{' + atag + '}';
This is a genuine oversight. While scanning lyrics.pas for more
of these, I found also:
songraise:='\mtx'+s+'LyricsAdjust'+toString(PMXinstr(voiceStave(voice)))
+'{'+toString(lyr_adjust)+'}';
which should be changed to
songraise:='\mtx'+s+'LyricsAdjust{'+toString(PMXinstr(voiceStave(voice)))
+'}{'+toString(lyr_adjust)+'}';
Dirk
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] M-Tx 0.60
M-Tx 0.60 is available on the Software page of the Icking Music Archive http://icking-music-archive.org/software/indexmt6.html 1. Documentation There is ready-made documentation on the site. If you have never used M-Tx, download only the documentation and read it. After installing the software, it is a good test of your installation to rebuild the documentation. 2. The preprocessor. 2.1 Windows and Mac users can download binaries. Thanks for Christian Mondrup for preparing these. 2.2 Linux users should make sure they have Free Pascal (if not, follow the link on the software page). Download the two zipfiles (mtxP060.zip has free Pascal sources and mtxD060.zip has sources to build the documentation). Then: (a) Unzip each zipfile into its own empty directory (I'll call them code and doc respectively). (b) Inside the code directory, type make. After a few seconds, there should be an executable called prepmx. (c) Move prepmx to a directory in you path, e.g. /usr/local/bin or $HOME/bin. Make sure by typing which prepmx that the new version is the one that the system sees. 3. TeX installation Copy the files mtx.tex (from mtxP060.zip) and mtxlatex.sty (from mtxD060.zip) to a place where TeX will find them. 4. Rebuilding the documentation. These instructions are for Linux. (a) Inside the doc directory, type make pdftarget. (If you must absolutely insist on still using DVI files, type make dvitarget instead.) Then type make config. Check that everything looked for was found. Then type make. (b) After screens and screens full of messages that scroll past your eyes, there should be a file mtx.pdf (or mtx.dvi) that you can read at your leisure. 5. Obsolescence warning The things said in the README about Borland Pascal and conversion to C using p2c are probably no longer true. They have not been deleted because some intrepid soul might try them and with some ingenuity might even get them working. BUT: they will not appear in the next README, since M-Tx is now developed using Free Pascal and no attempt will be made to retain compatibility with other ways of compiling the Pascal code. 6. What's new? 6.1 Chord ties (page 13) 6.2 Macros (page 17) Enjoy! Dirk Laurie ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] (Off-topic) Noteedit 2.8.0 Beta 1 released
Reinhard skryf: Noteedit 2.8.0 Beta 1 has been released. This is the first beta in the release cycle of the coming 2.8.0 release of NoteEdit. Test it hard and report any bugs to the developer mailing list or in the Bug tracker of the noteedit berlios developer page (preferred). I don't know how to do that. I tried building 2.8.0 and got to the point where it said: The important program kconfig_compiler was not found! Please check whether you installed KDE correctly. I checked Google for this, and found that kconfig_compiler is part of KDE 3.2. I have KDE 3.1. Upgrading all of KDE is not an option on my system, so I'll stick with noteedit 2.5.0. I guess the easiest wat to 'fix' this bug is to say in INSTALL that noteedit 2.8.0 requires KDE 3.2. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Bar problems with PMX
Cornelius C. Noack skryf:
(b) the answer to your problem is nevertheless simple:
musixTeX, and thus also PMX uses its own fonts for the
creation of musical scores, and therefore you can use only
the 2 (musical) font sizes that are presently available,
which are called 16 and 20 -- basta! (the exact answer is
a little more complicated: if you look at the font names
loaded into you TeX installation by musixTeX, you will see
some more fonts. But consider that you also need fonts for
grace notes etc, so just be content with the above).
Perhaps some day one of our musixTeX specialists will come
up with a more flexible size handling system; but I doubt
it: it would be a sizable programming project, and I haven't
heard anyone complain loudly about this lack of
flexibility.
In M-Tx (and therefore a fortiori in PMX) one can get 13pt, 16pt,
20pt, 24pt or 29pt notes. Easily. True, there are a few MusiXTeX
instructions you need to give if you also want the annotations etc
to look right.
If that is not good enough the answer is also simple. Suppose you
want 32pt. Scale the page layout parameters (height, width, margins ...
down by a factor 29/32. Then let a later program do the work.
The attached example was made by
$ prepmx bigger; pmxab bigger
$ tex bigger; musixflx bigger; tex bigger
$ dvips -x1200 bigger -o bigger.ps; ps2pdf bigger.ps
Dirk
Title: Bigger, biggger
Size: 29
PMX: w150m
c d e f g a b g c0
---
\def\mtxversion{0.70b}
\def\mtxdate{5 May 2005}
\input mtx
\mtxTitleLine{Bigger, biggger}
---
1 -1 1 4 4 0 6 0.0 0 1 1 20 0
0
./
\\mtxSetSize{1}{\mtxHugeSize}\
Tt
\mtxTitle
w150m
% Paragraph 2 line 0 bar 1
c44 d4 e4 f4 /
%Bar 2
g4 a4 b4 g4 /
%Bar 3
c0 /
% Coded by M-Tx
bigger.pdf
Description: Adobe PDF document
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music]
Jean-Pierre Coulon skryf: On Wed, 11 May 2005, Roge Sánchez wrote: Como podría conseguir la partitura de Susana un día de Orlando di Lasso?. Gracias http://www.cpdl.org/modules.php (type 'lasso' and 'jour' in their Score Search) En hoppant que ça helpe, Ek lees nou die dag dat Sint Frans Borgia in sy jong dae 'n komponis was, en dat Lassus sy werk aangeprys het. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music]
Bernhard Lang skryf: Como podría conseguir la partitura de Susana un día de Orlando di Lasso?. Gracias http://www.cpdl.org/modules.php (type 'lasso' and 'jour' in their Score Search) En hoppant que ça helpe, Ek lees nou die dag dat Sint Frans Borgia in sy jong dae 'n komponis was, en dat Lassus sy werk aangeprys het. Interessant - jeg har søgt på Google efter oplysninger om Francesco Borgia som komponist. Men resultatet var desværre magert:-( Francesco Borgia era troppo impegnato a fare il superiore dei Gesuiti per mettersi anche a comporre... ma è vero che a quel tempo si era più eclettici di oggi. ciao, .mau. Ist Francesco einer der Borgias, die besser mit Gift als mit Noten umgehen konnten? Den norske katolske kirkes website skriver om Frans Borgia (http://www.katolsk.no/biografi/frborgia.htm): Siden pave Alexander VI har navnet Borgia naturligvis hatt en dårlig klang, men Frans var blant dem som brakte det i ære. Auso, ich häb dänchkt, dös siggi ä Mäilinglischte, wo mr numme änglisch schwötzt. Abr s'isch offebar nit aso. I think we have proved that those who understand the universal language, music, can communicate even when they have no other language in common. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Hanging slur
Neil Killeen skryf: On compiling this source (MTx 0.53F, PMX 2.4) I get a warning about a hanging slur. It's to do with the tie across the second and third bars in the upper voice. Despite this, the notes seem to typeset ok. However, the lyric gets confused. There should be one 'Ah' per slur (bar). But instead the second 'Ah' goes on forever... In the meantime M-Tx 0.60 has appeared. I'm happy to report that there is no warning, and there does start another slur in bar 4. Not in bar 3, though, and I respectfully submit that M-Tx does the logical thing here: there is a tie still going on. Maybe you want the previous slur to end after the tie. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] MTx V0.60 in C
Neil Killeen skryf: Christian On Mon, 30 May 2005, Christian Mondrup wrote: Neil Killeen wrote: Hi I'd like to install the new MTx v0.60. However I can't find the C-sources, mtxC060.zip, in the software archive. I can only find the Pascal, mtxP060.zip (which I can't do anything with) You can by downloading and installing the FreePascal compiler from http://www.freepascal.org/. The M-Tx pascal source files are specifically written for that compiler available for quite a few operating systems. -- yes i am aware of that possibility but was hoping to avoid it ! The README for MTx refers to the possibility of building MTx from C-sources (see below) which presumably someone (Dirk?) creates from the Pascal source via p2c or the like. Some time ago I wanted to retire as maintainer of M-Tx. I was persuaded to carry on, but on the condition that I supply only Free Pascal source -- other people build binaries for Windows, Mac etc. My main reason for so doing is that p2c is no longer maintained, but Free Pascal is. It is a major effort to keep M-Tx source compatible with the quirks (read: bugs) of fpc and it requires someone who wants C source more fervently than I do. If you are putting up your hand to do this and keep doing it, I will advise, but IMHO you would be flogging a dead horse. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] grace notes in mtx
Don Simons skryf: I'm confused. The code e2 za zb Gm02Afs4 g does not work for me in PMX. I don't understand how you guys could have gotten this to work. I didn't - it failed at the TeX level exactly as you described - but I thought it's because my PMX and MusixTeX are not up-to-the-minute. So I took out the 'm0'. Before Dirk does any new coding, let's figure out what's going on here. Then let's decide if anyone is ever really going to want multiple graces with no flags. It may not be too difficult to implement but I'm not going to do it if no one wants it, and I can't recall this ever coming up before. Well, the sad fact is that M-Tx can't cope with grace notes after the main note. It classifies PMX features as coming before or coming after the main note, and 'G' is one of those that come before. This is in a very old and deeply-buried part of the code, and I won't be able to do anything about it soon. In the meantime, the best kludge I can come up with is this (to be followed by 'm2400' in the next bar): Meter: m5824 PMX: w60m e2 za zb G2fs4 g r8b The space occupied by the blind rest is ugly, but at least the grace notes are there. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] more space at each system
Jean-Pierre Coulon skryf:
I am trying to add some space at the beginning of each system after the
general signature and before the first note (I don't want to change
\afterruleskip at other bars).
I have tried saying \def\everystaff{\addspace{5\afterruleskip}} before
\starpiece, but this results in adding space between the clef and the key
signature, besides adding some space at the place I want at some random
lines.
See line 35 of the attached file.
Using \hardspace instead of \afterruleskip is still worse.
Is another trick possible?
The ideal solution to this sort of thing would be to have a
\newlength\aftersignature in MusiXTeX itself, which the user could
override. I know that Daniel was very cautious about such things
because one easily gets 'TeX capacity exceeded'. However, nowadays
all it takes to increase TeX capacity is to edit texmf.cnf, so maybe
we no longer need to be so careful.
Dirk
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Zigzag lyrics (Was: anyone knows this a-capella march?
Bodo Meissner skryf:
Does anyone know this march?
No, but the comments at the bottom caught my eye:
% Note:
%
% I changed the definition of \setlyrstrut in my copy of musixlyr.tex
% (version MusiXLYRics 2.1c June 10, 2003)
%
% \def\setlyrstrut{% set up strut according to currently active font
% \setbox0=\hbox{(\Ag)}%
% \setbox\lyrstrutbox=\hbox{\vrule height 1.1\ht0 depth 1.1\dp0
[EMAIL PROTECTED]
%
% The original had \hbox{()} which does not work for pncr font.
%
% Without this change in musixlyr.tex you may get zigzag lyrics lines.
% The following TeX command in a line before \setlyrstrut will help.
%
%
%%\def\setlyrstrut{\setbox0=\hbox{(\Ag)}\setbox\lyrstrutbox=\hbox{\vrule
height 1.1\ht0 depth 1.1\dp0 width 0pt}}
%
This is a useful tip. I have also experienced problems with zigzag
lyrics in non-Knuthian fonts.
Dirk
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] PMX compilation for Linux
Luigi Cataldi skryf: I've just turn my back on Windows for Linux and I'm in trouble with my best preferred software: PMX of course. G77 compiler isn't present in my Fedora core 4 distribution and I wasn't able install it (a problem with the gcc compiler version that I can't solve). So I used gfortran compiler that comes with fedora distribution. You are not the first person in the world who has had this problem. Rather than trying to bully Don into making the code Fortran 95 compatible (the attempt will not work), use the solution provided by the Fedora designers and install the package compat-gcc-32-g77 that is part of the Fedora core 4 distribution. I saw this tip on https://www.redhat.com/archives/fedora-list/2005-June/msg03414.html after Googling for 'g77 Fedora core 4'. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Pronunciation of MusiXTeX
Mark J. Reed skryf: The question is: should the first X in MusiXTeX be pronounced the same way as the last X (however you pronounce it!)? Or otherwise? Surely there must be someone who heard Daniel Taupin say it? And that pronunciation should be definitive. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Test, ignore
___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Gregorian chant and musixlyr
Rainer Dunker skryf: I'd be interested in enhancing musixlyr so that it could typeset Gregorian chant lyrics properly. What additional features would be needed for this? I can see these topics: ... Have I forgotten anything? Automatic selection of some appropriate pre-Gutenberg font :-) Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Index added to musixdoc
Don Simons skryf:
This might be a good time to mention something about indices that I've often
thought about. If you are viewing a document electronically rather than in
hard copy, there's hardly any use for an index. Just text search for the
entry you want. And if it's a tex document, then whether or not every
occurrance gets into the index depends on the vigilance of the editor. A
text search will not skip over any occurrances, and could very well be more
accurate.
A well-made index is a great help, even for electronic viewing. By well-made
I mean that it incorporates expertise on where to find the nitty-gritty.
Say I want to know something about \zqu.
A text search gives me a dozen hits. Daniel's index gives me one: the
one I need.
And if you \usepackage{hyperref}, then you can just click the page
number in the index when viewing the PDF file and that puts you straight
on that page.
A poorly-made index is no use at all, I agree.
Dirk
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Index added to musixdoc
Don Simons skryf:
Then perhaps either Dirk or Olivier would like to volunteer to edit the
index for the upcoming (but not necessarily soon), completely revised
version of musixdoc.
It is precisely because I do NOT have the intimate acquaintance
with the contents of musixdoc required for that task, that I have
the warmest appreciation for what Daniel Taupin produced, and tried
imitating his index (to the extent of borrowing his macros) in mtxdoc.
One does not edit a TeX index. The author of the document inserts a
command in the text wherever a word to be indexed appears. Then
makeindex takes care of producing the index.
E.g. PMX was written by \ixem{Don Simons} will print PMX was written
by Don Simons and produce an index entry for Don Simons, whereas
PMX was written by Don Simons \index{Simons!Don} will produce one for
Don as a subentry under Simons.
I dare not volunteer to add index macros to all of the new documentation.
But I do volunteer to give technical advice on Daniel's indexing macros
(including how to modify them for use with hyperref.sty) to whoever needs
it.
Dirk
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Musixtex package
Christof Biebricher skryf: More of a problem are the executables. I suggest that one offers binaries for windows and linux-i*86; for all other systems one has to add the program sources for compiling, if possible, as C programs. After we agree about the new package, it would be possible to replace the complicated and then obsolete installation instructions and clean up the now rather complex software catalogue. I recently switched to Ubuntu Linux, a Debian variant. MusiXteX, musixlyr, PMX and M-Tx are available packages and to install them was simple. If you say aptitude -r install m-tx, everything is installed in one go. If you have only one functional finger, you can even do it by selectng menu items from a GUI. Other Linux distributions offer similar features of installing recommended packages, although as far as I know, Debian is the only one that has our packages as part of the official release. What is my point? Basically, that any user sophisticated enough to get useful results from a generic linux-i*86 would not need the combined package, and that easy solutions for some distros are already available. Megalithic packages offering everything are a bit out of fashion in the Linux world. Maybe it makes sense in the Windows world - I would not know. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Kuykens's warning, history of MusiXTeX
Don Simons skryf: I agree that disk space is no longer an issue, and that the tone of the Kuyken remark is too negative, However, it is still true, at least for the tetex distribution, that MusiXTeX sails dangerously close to TeX capacity exceeded. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] MusixTeX is great. What to choose next?
Bernhard Lang skryf: If you have many few bars long music lines to embed TeX capacity exceeded can become an issue On any TeX system that has a texmf.cnf file this is no problem. You simply edit that file to increase TeX capacity. Multiply stack sizes by 10 --- your modern computer has a lot of RAM and the original TeX sizes date back to the days of 8-bit machines. Dirk ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-Music] [BUG FIX] Re: 13pt size with m-tx
Dirk Laurie skryf:
Simon Dreher skryf:
I just tried to typeset a piece in a small font size (13pt) with m-tx.
The style is SATB, so I have 2 staves.
According to the m-tx manual, Size: 13 in the mtx-preamble should be
OK. But unfortunately, running pmx on the generated pmx file, I get an
error message Musicsize must be 16, 20, 24, or 29.
The correct behaviour I can get with Size: 13 13. Did I misunderstand
the Size command, or is this a bug? Shouldn't this line accept a single
size which is used for all staves?
It is a bug.
If you are in a position to compile the Pascal code, find line 300:
if word='' then exit;
in preamble.pas and replace 'exit' by 'break'.
This is alpha code -- I am not at this moment in a position to test
the patch myself -- but it should fix the problem.
Unfortunately the fix is more complicated. I append the complete
preamble.pas required to fix it.
Dirk
unit preamble;
{$X+}
{ Interpret preamble paragraph, compose PMX preamble }
interface uses globals;
function thisCase: boolean;
procedure preambleDefaults;
procedure interpretCommands;
procedure doPreamble;
procedure doPMXpreamble;
procedure respace;
procedure restyle;
function startString(voice: voice_index0): string;
procedure augmentPreamble(control_para: boolean);
function omitLine(line: paragraph_index): boolean;
procedure nonMusic;
procedure setOnly(line: string);
function isCommand(command: string): boolean;
const known = true;
implementation uses control, mtxline, strings, files, status, utility;
{ fpc mistakenly thinks CONTROL is not used }
{EMBED
#include cfuncs.h
}
const blank = ' ';
colon = ':';
semicolon = ';';
comma = ',';
known_styles: integer = 12;
max_styles = 24;
warn_redefine: boolean = false;
type command_type =
( none, title, composer, pmx, options, msize, bars, shortnote,
style, sharps, flats, meter, space, pages, systems,
enable, disable, name, indent,
poet, part, only, octave, start );
line_type = ( unknown, colon_line, command_line, comment_line,
plain_line );
style_index = 1..max_styles;
style_index0 = 0..max_styles;
const c1 = title; cn = start;
commands: array[command_type] of string[16] =
( 'NONE', 'TITLE', 'COMPOSER', 'PMX', 'OPTIONS',
'SIZE', 'BARS/LINE', 'SHORT',
'STYLE', 'SHARPS', 'FLATS', 'METER', 'SPACE', 'PAGES', 'SYSTEMS',
'ENABLE', 'DISABLE',
'NAME', 'INDENT', 'POET', 'PART', 'ONLY', 'OCTAVE', 'START');
cline: array[command_type] of string =
( '', '', '', '', '', '', '', '1/4',
'', '0', '', 'C', '', '1', '1', '', '', '', '', '', '', '', '', '' );
redefined: array[command_type] of boolean =
( false, false, false, false, false, false, false, false, false,
false, false, false, false, false, false, false, false, false,
false, false, false, false, false, false );
(** Known styles *)
known_style: array[style_index] of string = (
'SATB:Voices S,A T,B; Choral; Clefs G F',
'SATB4: Voices S A T B; Choral; Clefs G G G8 F',
'SINGER: Voices Voice; Vocal; Clefs G',
'PIANO: Voices RH LH; Continuo; Clefs G F',
'ORGAN: Voices RH LH Ped; Continuo; Clefs G F F',
'SOLO:Voices V; Clefs G',
'DUET:Voices V1 Vc; Clefs G F',
'TRIO:Voices V1 Va Vc; Clefs G C F',
'QUARTET: Voices V1 V2 Va Vc; Clefs G G C F',
'QUINTET: Voices V1 V2 Va Vc1 Vc2; Clefs G G C F F',
'SEXTET: Voices V1 V2 Va1 Va2 Vc1 Vc2; Clefs G G C C F F',
'SEPTET: Voices V1 V2 Va1 Va2 Vc1 Vc2 Cb; Clefs G G C C F F F',
'', '', '', '', '', '', '', '', '', '', '', '');
var old_known_styles: style_index;
style_used: array[style_index] of boolean;
omit_line: array[paragraph_index] of boolean;
orig_style_line: array[style_index] of style_index0;
var nclefs, n_pages, n_systems, n_sharps, ngroups: integer;
part_line, title_line, composer_line, pmx_line, options_line,
start_line, voices, clefs: string;
group_start, group_stop: array[1..maxgroups] of integer;
instr_name: array[stave_index] of string[40];
style_supplied: boolean;
{ -- Styles -- }
function voiceCount(s: string): voice_index0;
var i, l: integer;
begin l:=length(s); for i:=1 to l do if s[i]=comma then s[i]:=blank;
voiceCount:=wordCount(s);
end;
function findStyle(s: string): style_index0;
var i: style_index0;
begin
i:=0; s:=s+colon; findStyle:=0;
while iknown_styles do
begin inc(i);
if startsWithIgnoreCase(known_style[i],s) then
begin findStyle:=i; exit; end;
end;
end;
procedure addStyle (S: string);
var sn: style_index0;
begin
sn:=findStyle(NextWord(S,colon,dummy));
if sn0 then known_style[sn] := S
else if known_styles max_styles then
begin inc(known_styles);
known_style[known_styles] := S;
end
else error('Can''t add another style - table full',print);
end;
procedure readStyles;
var eofstyle: boolean;
S: string;
l: style_index0;
begin
Re: [TeX-Music] [BUG FIX] Re: 13pt size with m-tx
Christian Mondrup skryf:
My attempt to compile the updated pascal code (fedora core 5, fpc 2.0.4)
fails, see the attached output from 'make'.
Apologies! I inadvertently used a version of preamble.pas from
my development tree, which relies on several changes in the other
units as well.
I hope the attached file is better.
Dirk
unit preamble;
{$X+}
{ Interpret preamble paragraph, compose PMX preamble }
interface uses globals;
function thisCase: boolean;
procedure preambleDefaults;
procedure interpretCommands;
procedure doPreamble;
procedure doPMXpreamble;
procedure respace;
procedure restyle;
function startString(voice: voice_index0): string;
procedure augmentPreamble(control_para: boolean);
function omitLine(line: paragraph_index): boolean;
procedure nonMusic;
procedure setOnly(line: string);
function isCommand(command: string): boolean;
const known = true;
implementation uses control, mtxline, strings, files, status, utility;
{ fpc mistakenly thinks CONTROL is not used }
const blank = ' ';
colon = ':';
semicolon = ';';
comma = ',';
known_styles: integer = 12;
max_styles = 24;
warn_redefine: boolean = false;
type command_type =
( none, title, composer, pmx, options, msize, bars, shortnote,
style, sharps, flats, meter, space, pages, systems,
enable, disable, name, indent,
poet, part, only, octave, start );
line_type = ( unknown, colon_line, command_line, comment_line,
plain_line );
style_index = 1..max_styles;
style_index0 = 0..max_styles;
const c1 = title; cn = start;
commands: array[command_type] of string[16] =
( 'NONE', 'TITLE', 'COMPOSER', 'PMX', 'OPTIONS',
'SIZE', 'BARS/LINE', 'SHORT',
'STYLE', 'SHARPS', 'FLATS', 'METER', 'SPACE', 'PAGES', 'SYSTEMS',
'ENABLE', 'DISABLE',
'NAME', 'INDENT', 'POET', 'PART', 'ONLY', 'OCTAVE', 'START');
cline: array[command_type] of string =
( '', '', '', '', '', '', '', '1/4',
'', '0', '', 'C', '', '1', '1', '', '', '', '', '', '', '', '', '' );
redefined: array[command_type] of boolean =
( false, false, false, false, false, false, false, false, false,
false, false, false, false, false, false, false, false, false,
false, false, false, false, false, false );
(** Known styles *)
known_style: array[style_index] of string = (
'SATB:Voices S,A T,B; Choral; Clefs G F',
'SATB4: Voices S A T B; Choral; Clefs G G G8 F',
'SINGER: Voices Voice; Vocal; Clefs G',
'PIANO: Voices RH LH; Continuo; Clefs G F',
'ORGAN: Voices RH LH Ped; Continuo; Clefs G F F',
'SOLO:Voices V; Clefs G',
'DUET:Voices V1 Vc; Clefs G F',
'TRIO:Voices V1 Va Vc; Clefs G C F',
'QUARTET: Voices V1 V2 Va Vc; Clefs G G C F',
'QUINTET: Voices V1 V2 Va Vc1 Vc2; Clefs G G C F F',
'SEXTET: Voices V1 V2 Va1 Va2 Vc1 Vc2; Clefs G G C C F F',
'SEPTET: Voices V1 V2 Va1 Va2 Vc1 Vc2 Cb; Clefs G G C C F F F',
'', '', '', '', '', '', '', '', '', '', '', '');
var old_known_styles: style_index;
style_used: array[style_index] of boolean;
omit_line: array[paragraph_index] of boolean;
orig_style_line: array[style_index] of style_index0;
var nclefs, n_pages, n_systems, n_sharps, ngroups: integer;
part_line, title_line, composer_line, pmx_line, options_line,
start_line, voices, clefs: string;
group_start, group_stop: array[1..maxgroups] of integer;
instr_name: array[stave_index] of string[40];
style_supplied: boolean;
{ -- Styles -- }
function voiceCount(s: string): voice_index0;
var i, l: integer;
begin l:=length(s); for i:=1 to l do if s[i]=comma then s[i]:=blank;
voiceCount:=wordCount(s);
end;
function findStyle(s: string): style_index0;
var i: style_index0;
begin
i:=0; s:=s+colon; findStyle:=0;
while iknown_styles do
begin inc(i);
if startsWithIgnoreCase(known_style[i],s) then
begin findStyle:=i; exit; end;
end;
end;
procedure addStyle (S: string);
var sn: style_index0;
begin
sn:=findStyle(NextWord(S,colon,dummy));
if sn0 then known_style[sn] := S
else if known_styles max_styles then
begin inc(known_styles);
known_style[known_styles] := S;
end
else error('Can''t add another style - table full',print);
end;
procedure readStyles;
var eofstyle: boolean;
S: string;
l: style_index0;
begin if styleFileFound then eofstyle:=true else eofstyle := eof(stylefile);
l:=0;
while not eofstyle do
begin readln(stylefile,S); if S'' then
begin addStyle(S); inc(l); orig_style_line[known_styles]:=l; end;
eofstyle := eof(stylefile);
end;
end;
procedure applyStyle(s, stylename: string;
first_inst, first_stave: stave_index);
var clef, subline, subcommand: string;
i, last_inst, last_stave: stave_index0;
continuo, toosoon, vocal: boolean;
begin last_inst:=first_inst-1;
toosoon := false; continuo:=false; vocal := false;
subline:=GetNextWord(s,blank,colon);
while
Re: [TeX-Music] changes in number of voices
Christof Biebricher skryf: This works. I have no idea what in mtx.tex interferes with scor2prt. The reason is that I have never needed scor2prt and therefore did not know enough about it to include it in the design. The 'Only' feature is a not very well conceived alternative. The undesired appearance of incompatibilities is a major problem with all pieces of software that give extra flexiblity to the user by 'passing through' untranslated code to the next stage. Basically this practice provides undocumented features, and we all know what that is a euphemism for. So: M-Tx allowing raw PMX PMX allowing raw TeX The TeX command \special are recipes for disaster, but treated by our little community as challenges to its ingenuity. Caveat! Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] Ubuntu, TeTeX, TeXlive
Robin Fairbairns skryf: i know that. i'm a bit surprised it's still distributing tetex -- i had thought most distributions were doing texlive now. (after all, even redhat now distributes texlive, and they distributed tetex 2 for ages after tetex 3 came out...) There is no TeX in the default Ubuntu: you have to install it yourself once your machine is up. It's your choice which TeX to install, tetex or texlive. Both are available on the repository. They are mutually exclusive, though: installing one will cause the other to be removed. But tell me: why should I switch to texlive if I have been using tetex for ten years? Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] Ubuntu, TeTeX, TeXlive
Simon Dreher skryf:
[...]
But tell me: why should I switch to texlive if I have been using tetex
for ten years?
Because Thomas Esser (the former tetex maintainer) stopped his support
in favour of texlive?
Because tetex is frozen at the status of some years ago and no new
packages, bugfixes, features etc. are supported?
Those are powerful reasons. I have just replaced my tetex by texlive.
I notice no change in behaviour. In particular, when building mtxdoc.pdf,
it still builds, but still gives about 4 lines of error messages:
Embedded font uses undefined procedure RD
Embedded font uses undefined procedure ND
followed by
This file had errors that were repaired or ignored.
The file was produced by:
pdfeTeX-1.30.5
Please notify the author of the software that produced this
file that it does not conform to Adobe's published PDF
specification.
Dirk
___
TeX-music mailing list
[EMAIL PROTECTED]
http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] M-TX 0.60c compile problem
Christian Mondrup skryf: I compiled prepmx with p2c+gcc. This is probably the cause of your error. You _must_ compile prepmx with fpc (Free Pascal), see http://www.freepascal.org/. There is a Debian installation package available. In fact, errors like this one were the reason why I abandoned p2c. They are caused by bugs in p2c and the only two ways round them is to tweak the C code (that way lies madness) or try equivalent Pascal code that follows a different path in p2c. Look, p2c was great at its time, but the developer always meant it only as a way to get a basis to start from when porting applications from Pascal to C. The fact that there was no other Linux compiler available tempted people like me to use it for code maintained in Pascal. When I started work on M-Tx in the mid-1990's, p2c was already no longer being maintained: the last official release of p2c was in 1991, with an alpha release in 1993. Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] Help! (MTX and MusixTex)
Carlo Centemeri skryf: I am in big troubles with a MTX file which has given me tons of problems. In the position of some octave shifts it kept on saying me pitch too high (and I was inside the lines of the voice), so I said I'll keep it one octave lower and I will correct it later in PMX. But now also the tex compiling gives me a lot of problems (in other measures) and I really don't know how to manage it. I also do that. It is a bad habit, but so is drinking too much coffee. The following hint may help you to minimize the negative effects of this bad habit. In the M-Tx source, use e.g. c= every so often to make sure you are in the desired octave relative to the default octave. Then the wrong octaves do not get a chance to run wild. If you only use + and -, it is very easy to lose track of where you are, particularly if you build chords with z instead of C:. Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] M-Tx-PMX-Problem
Christian Mondrup skryf: Don Simons wrote: The length of that variable is limited to 65536 characters by my compiler. Without any fortran knowledge nor programming experience I'm surprised with the 64K size limit of _string_ variables (or does fortran really have a _character_ datatype having size expandable up til 64K?). Without any knowledge of Don's compiler, it is my guess that the restriction is not in Fortran, it's in the compiler. Many things in PMX (and M-Tx before I dropped Borland Pascal and p2c from the supported platforms, and even MusiXTeX itself for that matter) are restricted by the desire to retain compatibility with (by modern standards) rather primitive computers and software --- some of which have a 64K restriction on any one addressable structure, caused by the design of the ancient 8086 chip. Personally, if someone came to me today with the source language of PMX and M-Tx specified and asked me to write a system from scratch for compiling it to MusiXTeX, I would use Python for both. Everything in one program - no user-specified intermediate calls to tex, musixflx etc. Extremely convenient character string handling. Dirk ___ TeX-music mailing list [EMAIL PROTECTED] http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] PMX problems
Bob Tennent skryf: I've been trying to use pmxab to obtain tex files from the four pmx files in fairy_queen.zip in http://icking-music-archive.org/scores/purcell_h/fairy_queen/ on Linux systems. Two of the files (p_bc, p_va) work fine. The other two produce, depending on which version of PMX and which Fortran compiler I used to compile pmxab.for (f77, f95), either error messages WARNING: Last non-blank character is , not /,% ASCII code: 0 at the end of the first pass, or At line 15468 of file pmxab.for Fortran runtime error: End of file An all-purpose fix for end-of-line problems is: unzip -a fairy_queen.zip The -a converts the files to local text format. I have not recently checked whether this fix also copes with a Ctrl-Z end-of-file terminator. Dirk ___ tex-mu...@icking-music-archive.org mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] [Poll] IDE for PMX
On Mon, Aug 03, 2009 at 04:54:20PM +0200, Jill-Jênn VIE wrote: Don't you think it would be interesting to have an IDE for PMX? I'm interested in programming it :D There is already noteedit, a GUI that exports inter alia to PMX. But maybe you mean a sort of intelligent editor that checks PMX syntax, runs pmxab, comes back into the PMX code to some error not found by the syntax checker, or runs tex-musixflex-tex if pmxab is clean. An ideal application for Python-Qt. For such an application, as for M-Tx, one problem is to have a clean way of coping with the evolution of PMX syntax. I tried several years ago to design a BNF-like way to specify that, resembling the PMX quick reference card, but failed. Without such a description, adding awareness of new PMX features can be a painful process. Dirk ___ tex-mu...@icking-music-archive.org mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
[TeX-Music] A new application for PMX
The system administrator at Stellenbosch University has enforced new rules for passwords: 1. It must contain a member from at least three of the classes (a) upper and (b) lower case letters, (c) special characters, (d) digits. 2. It may contain spaces. 3. It must be between 8 and 32 symbols long. 4. You may not re-use your last ten passwords. 5. You must change it at most every 90 days. How on earth will I remember such a string of nonsense passwords? Well, a tune in PMX/M-Tx notation looks a lot like that! So a sequence of easy-to-remember passwords might be: Meter: 3/4 g4 d.g fs8.g a4d g8 fs8.g a d e f g4 d2 g4 d.g gs8.a b4d Of course, this sequence is unfinished. Dirk ___ tex-mu...@icking-music-archive.org mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] Searchability of pdf's
On Tue, Mar 09, 2010 at 06:41:17AM +0200, Don Simons wrote: I've noticed a strange feature of the version of musixdoc.pdf in the archive at http://www.icking-music-archive.org/software/indexmt6.html/musixtex/musixtex .pdf . When I open it with Adobe Acrobat 8 Standard under Windows XT I cannot successfully do any word searches. I'm pretty sure I made the PDF using gsview32. When I remade it locally the same way, the problem went away and I could do word searches. 1. Does anyone else see the same feature? 2. Does anyone have any idea what's going on and how to prevent it? I can't find it at that address on the new server, but following the links, it is at http://www.icking-music-archive.org/software/musixtex/musixdoc.pdf Using Acrobat 9 under Ubuntu Intrepid, I can't find volta anywhere. The same happens using xpdf. However, pdftotext converts to text successfully, and when I open it with evince (which is the standard PDF viewer for the Gnome desktop) word searches work successfully. Inside Acrobat, if you click File-Properties, you find that the file was made on 18/10/2009 at 16:57:37 by LaTeX with hyperref package, followed by dvips+AFPL Ghostscript 8.53, to the 1.2 PDF standard, readable by Acrobat 3.x. Dirk ___ tex-mu...@icking-music-archive.org mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] M-Tx, number of staves
On Fri, Jun 04, 2010 at 11:56:24AM +0200, Jean-Pierre Coulon wrote: would it be possible to change in a score the number of staves within a system? I had this problem a few years ago and solved this problem by using an individual mtx-file for each group of systems with the same number of staves, making eps-files and combine these files by LaTeX's icludegraphics. Maybe there is another more convenient method? Even in MusiXTeX I don't know how to do this. You can pretend the piece has more than one movement, and use PMX to insert a movement break when the number of staves changes. Since the feature is in PMX, you should be able to access it from M-Tx too. From the PMX Reference Card Li Force a line break at line i. Voice #1 only. Start of block only. [Pi] Force a page break at page i. [M] Movement break. Must follow P if present. [+i]Extraverticalspace, \internote. [ix]New indent, decimal fraction of line width. [c] Continue bar numbering, do not reset. [r +,-] Force or suppress reprinting in- strument names. [ni]Change to i instruments. d1d2...di Numbers of instruments. Pre- cede 2-digit numbers with : c1c2...ck Clef symbols. Enter one for every staff in new lineup. Disclaimer: I've never actually tried this. So I'd be quite interested to know if it works. Dirk ___ tex-mu...@icking-music-archive.org mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] M-Tx, number of staves
On Fri, Jun 11, 2010 at 07:05:54AM +0200, Don Simons wrote: 3. (and here's where it gets really ugly) use a special FORTRAN program I wrote to go through the prepmx output file, looking for and deleting every occurrence of rp | rp | PMX and M-Tx both carry heavily the baggage of what programming languages their developers knew back when. In the meantime, some very interesting programming languages have become available. The above job, and indeed everything currently done by PMX and M-Tx, is miles easier in Python than in Fortran or Pascal. (Actually, this job can also be done by even a primitive text editor.) Python can also take care of the whole tex-musixflx-tex cycle. If there are any programmers on the list who would be interested in a Python project for an updated M-Tx, please e-mail me so that we don't have yet another one-person effort. Dirk ___ tex-mu...@icking-music-archive.org mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] PMX upgrade philosophy
Don Simons skryf:
The question before me is whether to have PMX once and for all issue
\setmaxinstruments{24}, thereby requiring all new PMX-generated TeX files to
be processed with eTeX.
Under TeTeX and maybe MikTeX (I wouldn't know) that may have been
true, although I think there used to be a file texmf.cfg that you
could edit to make the sizes bigger.
Under TeXLive tex, etex, pdftex and pdfetex are all the same program.
I don't think one easily runs into size limits. The only difference
between tex and etex is that the latter enables certain extensions.
But can't the pmxa part of pmxab count how many instruments are
actually needed, and the pmxb part issue \setmaxinstruments with
that precise number?
Dirk
___
tex-mu...@icking-music-archive.org mailing list
If you want to unsubscribe or look at the archives, go to
http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] PMX upgrade philosophy
On Thu, Jun 24, 2010 at 02:30:09PM +0200, Bodo Meissner wrote:
Or would it be possible to check for the TeX version and insert
\setmaxinstruments{24} only if eTeX is detected?
Well, this is actually trivial.
\ifx\undefined\eTeXversion\setmaxinstruments{12}
\else\setmaxinstruments{24} \fi
Even better: pmxa counts the number of instruments and pmxb inserts
TeX code to give an error message if there are more than 12 and
eTeX is not detected.
Thanks for the idea, Bodo!
Dirk
___
tex-mu...@icking-music-archive.org mailing list
If you want to unsubscribe or look at the archives, go to
http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] problem with bar spacing
On Sun, Aug 15, 2010 at 10:39:53PM +0200, Don Simons wrote: I wonder if there are some stray non-ascii characters embedded in your original source. That could confuse PMX. I've encountered this. It's usually a null character or tab, or some relic from a different system's end-of-line mechanism. Zipping the file and unzipping it in acommand shell with unzip's -a option often fixes the problem. And/or requesting one's editor to expand all tabs into spaces. Dirk ___ tex-mu...@icking-music-archive.org mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
[Tex-music] The Future of MusiXTeX etc
Recently something has happened to TeX that should change the way we
are thinking. This is the fact that LuaTeX has reached Version 0.50.
In theory, only people living on the bleeding edge use LuaTeX. There
is a warning in the Reference Manual:
Nothing is considered stable just yet. This manual therefore simply
reflects the current state of the executable. Absolutely nothing on
the following pages is set in stone. When the need arises, anything
can (and will) be changed without prior notice.
In practice, the bare necessities are not likely to change after 0.50.
I refer to the TeX command \directlua and the Lua function tex.print.
\directlua takes one argument, a Lua script, which is executed
immediately.
tex.print takes one argument, a string, which is passed to TeX.
The net effect is that the command \directlua{...} acts much like a TeX
macro.
Lua is a minimalist programming language: simple syntax, only eight
types (of which the casual user needs six: nil, boolean, number, string,
table, function), and 21 reserved words. All arithmetic is in IEEE
double precision. It has a string library with powerful pattern-matching
capability. It is just the sort of language that can easily translate
PMX-style notes into MusiXTeX macros, computing note and line spacing
as it goes along.
LuaTeX gives access to all the power of Lua from inside a TeX document.
Currently an M-Tx user relies on:
- A preprocessor written in Pascal, compiled to be a stand-alone
executable, which is different for every operating system
- PMX, which is written in Fortran, compiled etc, different etc
- musixflx, which is written in C, compiled etc, different etc
I have on two occasions asked on this list whether anybody wants to
help me convert M-Tx to Python. Christian Mondrup convinced me that
we shouldn't, as outside the Unix world people don't already have Python
anyway.
The objection does not apply to LuaTeX. All recent TeX distributions
have it, maybe at this stage only as an optional extra, but it is being
billed as the next generation TeX engine.
If we had LuaTex in 1992, musixflx could have been implemented in Lua
and there would be only one TeX pass.
If we had LuaTeX in 1996, PMX could have been implemented in Lua and
there would not have been pmxa and pmxb passes.
If we had LuaTeX in 1999, M-Tx could have been implemented in Lua and
there would not have been a prepmx pass.
Now it is 2010 and we do have LuaTeX.
We can go on as we used to: regard musixflx as cast in concrete, rely
on Don to keep maintaining PMX (nobody else except me, as far as I know,
has contributed even one line of Fortran code to it) and hope that someone
occasionally tweaks M-Tx to take account of some recent PMX feature (that
person is no longer me).
Or we can gradually convert more and more of the functionality of these
packages into LuaTeX, thus taking advantage of the fact that the next
generation of TeX package writers will be fluent in it and will be able
to maintain the software. A single package luamusix.sty will do everything.
I think the choice is obvious. Don't you?
Dirk
PS If you would like to try LuaTeX for yourself, and find the official
documentation a little daunting, you may like to read the story at
http://dip.sun.ac.za/~laurie/luatex
---
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
Re: [Tex-music] M-Tx with 17 voices
On Thu, Nov 18, 2010 at 08:38:32PM +0200, Hermann Hinsch wrote: I am asked to typset a mass with 4 choirs each of 4 voices and 1 instrumental bass. Although pmx now allows up to 24 voices M-Tx gives an error too many groups which is caused by the forth group. If I use pmx with musixlyr I get what I want without any error. As M-Tx is much more convenient is there a possibility to overcome the limitation to 3 groups? In globals.pas, find: maxgroups = 3; change it to what you need, and recompile prepmx. [Caveat: I have not tested this.] Dirk --- 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] WIMA
It is possible that some members of this list have not recently visited WIMA http://icking-music-archive.org itself. There is a discussion on the future of WIMA that we should be aware of. Dirk --- 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
Re: [Tex-music] Making parts of a M-Tx score
On Fri, Apr 08, 2011 at 04:33:39PM +0200, Hermann Hinsch wrote: do you think there would be a possibility to exstract single voices from a M-Tx score of 17 voices? I tried scor2part on the pmx ouput of the M-Tx score. But no chance! It should be fairly easy to write a Lua script that extracts the necessary lines. Since any modern TeX distribution supplies texlua, one should not need any extra software. Send me your M-Tx score and I'll try that. Dirk --- 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
Re: [Tex-music] musixflx in Lua
On Sun, Apr 10, 2011 at 12:55:58PM +0200, David Allsopp wrote: Bob Tennent wrote: It should be functionally identical to musixflx.c (up to round-off error). Is this just a throw-away line or are there actual systemic differences in the precision of the floating point variables used? Floating point calculations are a CPU function - it would be beneficial if the results strived to be *identical* on the same architecture (a guarantee which TeX provides). See Remark 1 below. I'm not terribly familiar with Lua, but I would anticipate that C will be more flexible here - both scripts should use the same floating point representation for calculations which will eliminate all sources of non-algorithmic rounding error (if necessary, the C script could be changed). See Remark 2 below. Are there options available for producing native executables from Lua scripts on at least the major three platforms? If there are, then it would seem an excellent time to look towards dumping the C script entirely - the ability to produce a native executable would mean that anyone using MusiXTeX on a system which doesn't have LuaTeX instead would not have to install a Lua interpreter so it wouldn't make the installation of LuaTeX any harder. See Remark 3 below. 1. Identical results on the same architecture requires switching off *all* optimization in the C compiler. Not even a widely disseminated software package such as BLAS (Basic Linear Algebra Subroutines) promises identical runs nowadays, even for two runs on the same machine. One should not write software that behaves qualitatively differently depending on what happens in the sixteenth decimal place. 2. Lua is written in C; in fact, the C code for a customized version of the Lua interpreter is compiled and linked into the LuaTeX executable. Lua's number and C's double is one and the same. 3. There is a strong possibility that LuaTeX will become the default TeX engine in most distributions. I.e. when you type latex, or etex, or pdftex, or luatex, in all cases the actual executable will be luatex, although what it actually does will depend on which of the four names you used. (If you type tex, you should still get an executable generated from Knuth's cweb source, by the terms of his licence.) I.e. if you have TeX, you will have luatex without lifting a finger. 4. I can find only one place where musixflx may possibly, even though he probability is remote, be roundoff-sensitive: If the overhang is less than half the barlength, include the latest bar in the line, and shrink the line accordingly. It is possible (though the probability is less than that of my winning the lottery if I buy only one ticket) that the overhang on musixflx.c could be 0.4999 and on musixflx.lua 0.5000, or vice versa. I suspect that on PMX-generated scores no decision on line breaking is left to musixflx, so this conditional should not be encountered in that case. Dirk --- 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] [ANNOUNCE] extract.lua: Making parts of a M-Tx score
On Mon, Apr 11, 2011 at 01:02:39PM +0200, Hermann Hinsch wrote:
So Dirk, your suggestion might be easier. As you asked me you will find the
M-Tx score of the Sanctus (which is the smallest part) in the attachment.
I append:
1. The program extract.lua, a rudimentary M-Tx score-to-parts maker,
with just enough features to handle your Sanctus.
2. Your Sanctus.mtx (so others can check that exctact.lua works
on their systems too)
3. The five files made by extract.lua
The coding is to my usual standard, i.e. intelligible to me at the
time of writing. If others can understand it, it is because Lua is
an unusually readable and intuitive language.
We can start talking revision numbers the moment that more than one
version exists.
“It is pointless to generalize unless at least two non-isomorphic
examples of the generalization can be given.” — Nicolas Bourbaki
Dirk
#!/usr/bin/texlua
-- extract.lua DPL 2011-04-13
-- write separate M-Tx scores for each style element
-- Usage (Unix):extract.lua MYFILE.mtx
-- (all systems) texlua extract.lua MYFILE.mtx
-- There must be exactly one style line in the preamble. Each
-- separate entry in that line will get one part.
-- Features:
-- will look for lyrics, uptext and chord lines
-- Bugs:
-- does not look for special lyrics lines, only for those
-- starting with L:
-- only adjacent C or L lines are found (i.e. no intervening
-- comment lines allowed)
-- some convenient abbreviations and utility subroutines
append = table.insert
match = string.match
upper = string.upper
format = string.format
gmatch = string.gmatch
find = string.find
comment = '^%s*%%' -- first non-blank is a comment
lyrics = '^%s*{.*}' -- first word is enclosed in braces
keyword = '^%s*(.*):' -- first word if followed by colon
kwbody = .*:(.*) -- everything after keyword
word = '%s*(%S+)' -- maximal string of non-blanks
styleclause = ';?([^;]*)' -- clauses of style line separated by semicolons
function wordset(line)
local ws = {}
for w in gmatch(line,word) do ws[w]=true end
return ws
end
-- read input and separate into paragraphs
infilename = arg[1]
if infilename then infile = io.open(arg[1]) end
assert (infile, Usage: extract.lua MYFILE.mtx)
base, ext = match(infilename,'(.*)%.(.*)')
lines = {}
index = {}
for l in infile:lines() do
blank = match(l,^%s*$)
if blank and start then append(index,{start,#lines}); start=nil
elseif not (blank or start) then start = #lines+1
end
append(lines,l)
end
if start then append(index,{start,#lines}) end
-- classify paragraphs
function classify(item)
local first
for l=item[1],item[2] do
if not match(lines[l],comment) then first=lines[l] break end
end
if not first then return 'comment' end
if match(first,lyrics) then return 'lyrics' end
for l=item[1],item[2] do
if match(upper(lines[l]),'^%s*STYLE:') then
styleline = lines[l]; return 'style'
end
end
return 'music'
end
for _,item in ipairs(index) do item.class = classify(item) end
-- identify style elements and open part files
assert(styleline,No styleline found)
body = match(styleline,kwbody)
parts={}
partfile={}
partset={}
style={}
for part in gmatch(body,word) do
append(parts,part)
partset[part] = true
partfile[part]=io.open(format(%s-%s.%s,base,part,ext),'w')
end
-- go through file and print relevant lines
function writeln(part,line)
partfile[part]:write(line..'\n')
end
function to_all(line)
for _,part in pairs(parts) do writeln(part,line) end
end
function stylepara(item)
for l=item[1],item[2] do
local line = lines[l]
local kw = match(line,keyword)
if upper(kw)=='STYLE' then
for _,part in ipairs(parts) do
writeln(part,'Style: '..part)
end
elseif partset[kw] then
style[kw] = match(line,kwbody)
writeln(kw,line)
else to_all(line)
end
end
end
function commentpara(item)
for l=item[1],item[2] do to_all(lines[l]) end
end
function musicpara(item,part)
-- write line to file if it matches
function maybe(line,lbl)
if not line then return end
local x = match(line,keyword)
if x and find(lbl,x) then writeln(part,line) end
end
label=voices[part]
for l=item[1],item[2] do
local line = lines[l]
local kw = match(line,keyword)
if label[kw] then -- Aha! this is one of our voices.
maybe(lines[l-1],'U')
writeln(part,line)
maybe(lines[l+1],'CL')
maybe(lines[l+2],'CL')
elseif match(line,comment) then writeln(part,line)
end
end
end
function labels()
-- Identify voice labels for each part
Re: [Tex-music] [ANNOUNCE] extract.lua: Making parts of a M-Tx score
On Fri, Apr 15, 2011 at 05:24:19AM +0200, Don Simons wrote: Here a test drive report. The really good news is that on my somewhat aging Windows XT SP2 system, straight out of the box I got the script to run and extract parts. (I'm a little puzzled why it ran at all since I've never knowingly installed any Lua interpreter). If your TeX is recent enough, there's a Lua interpreter hidden in it. You have texlua if you have luatex. It's the same program, but what it does depends on the name by which it is called. If you call it as texlua, it's just a slightly customized Lua interpreter. PMX 2.603 than ran fine on Sanctus-Q2. But when I next ran etex on the resulting Sanctus-Q2.tex, I got ! sorry, musixuad must be input before musixlyr. l.48 ...y, musixuad must be input before musixlyr} It is needed for Hermann's huge score but not for the extracted ones. I simply made an empty file in the same directory and called it musixuad.sty. It is found in preference to the system-wide one. etex and dvips ran OK, but produced a .ps with one system on the 1st page at the bottom, 1 on the second at the top, and two on the 3rd, and 3 on the 4th. That's caused by the paragraph of pure TeX. Responsibility of the user, not of extract.lua. Bad news is that I couldn't get prepmx to process Sanctus.mtx at all. It complains Too many groups: ERROR on line 5 When Hermann first started this thread, I wondered whether M-Tx could deal with so many voices, and I'm still wondering. Have I missed an upgrade? extract.lua can deal with any number of voices even if M-Tx can't :-) But anyway it's trivial. In globals.pas, omitting the quaint comments on 64K data segments: const PMXlinelength = 128; lines_in_paragraph = 100; max_words = 128; max_notes = 128; max_bars = 16; maxstaves = 15; maxvoices = 15; maxgroups = 3; standardPMXvoices = 12; Just change the ones you need and recompile. Of course, you need a PMX that can handle it, which is not the one documented in pmxdoc.pdf. Dirk --- 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] MusiXflx enhancement: vertical spacing?
I find that I spend a lot of time getting my vertical spacing just right, most of the time by trail-and-error. I'm also not overfond of the PMX benign bug described as follows in the manual: When TEX'ing the output of PMX you will usually get an Underfull \vbox message at the end of each page. This is due to my using \eject at the end of every page, which automatically spaces the systems vertically without having to fiddle with \staffbotmarg. As far as I know, the warning is benign, and may be ignored. How hard would it be to provide information on vertical spacing to MusiXflx so that it can calculate similar vertical spacing as it does for horizontal, making the vertical space available for automatic redistribution equal to zero? Dirk --- 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
Re: [Tex-music] [ANNOUNCE] extract.lua: Making parts of a M-Tx score
On Fri, Apr 15, 2011 at 05:18:24PM +0200, Don Simons wrote: Long ago I built into PMX the Ae option, which equalizes the vertical spaces on a page between the bottoms of one system and the tops of the next. ... I always use the Ae option ... Perhaps there is some way that M-Tx could take advantage of this feature. Line 54 of preamble.pas reads: ( '', '', '', '', '', '', '', '1/4', Change it to ( '', '', '', 'Ae', '', '', '', '1/4', Then M-Tx will also always use the Ae option. You know, backward compatibility is always thought to be a good thing, but if it means go on doing it badly because it has always been done badly I start recalling the proverb Too much of a good thing is also bad. So I think, if I make a new M-Tx release, I'll make that the default. Dirk --- 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
Re: [Tex-music] curlybrackets
curly.tex was submitted by Mthimkhulu Molekwa mmole...@rrs.co.za. That e-mail address no longer works. He is however easy to find via social networks (Facebook, LinkedIn, Google Profile ...). Dirk --- 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
Re: [Tex-music] Compile error in M-Tx documentation
On Mon, May 02, 2011 at 04:03:30PM +0200, Roland Stigge wrote:
upon compiling mtxdoc.tex (from latest m-tx 0.60d), I get the following
error:
pdflatex mtxdoc
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
...
! No room for a new \count .
I use Ubuntu, which has the identical pdfTeX version as you have,
with no problems.
I append my /etc/texmf/texmf.d/95NonPath.cnf, which may differ
from yours. That's where sizes are set.
Dirk
# $progname: kpathsea v. 3.5.3 or later overwrites this at runtime. To
# avoid empty expansions from binaries linked against an earlier
# version of the library, we set $progname and $engine to something
# non-empty:
progname = unset
engine = unset
% Part 2: Non-path options.
% If this option is set to true, `tex a.b' will look first for a.b.tex
% (within each path element), and then for a.b, i.e., we try standard
% extensions first. If this is false, we first look for a.b and then
% a.b.tex, i.e., we try the name as-is first.
%
% Both names are always tried; the difference is the order in which they
% are tried. The setting applies to all searches, not just .tex.
%
% This setting only affects names being looked up which *already* have
% an extension. A name without an extension (e.g., `tex story') will
% always have an extension added first.
%
% The default is true, because we already avoid adding the standard
% extension(s) in the usual cases. E.g., babel.sty will only look for
% babel.sty, not babel.sty.tex, regardless of this setting.
try_std_extension_first = t
% Write .log/.dvi/etc. files here, if the current directory is unwritable.
% TEXMFOUTPUT = /tmp
% If a dynamic file creation fails, log the command to this file, in
% either the current directory or TEXMFOUTPUT. Set to the
% empty string or 0 to avoid logging.
MISSFONT_LOG = missfont.log
% Set to a colon-separated list of words specifying warnings to suppress.
% To suppress everything, use TEX_HUSH = all; this is currently equivalent to
% TEX_HUSH = checksum:lostchar:readable:special
% To suppress nothing, use TEX_HUSH = none or do not set the variable at all.
TEX_HUSH = none
% Enable system commands via \write18{...}. When enabled fully (set to
% 1), obviously insecure. When enabled partially (set to p), only the
% commands listed in shell_escape_commands are allowed. Although this
% is not fully secure either, it is much better, and so useful that we
% enable it for everything but bare tex.
shell_escape = p
% Special: convert is the standard command name for ImageMagick, but it
% is also the name of a dangerous filesystem-changing command on
% Windows. So enable imgconvert (used in w32tex), but not convert.
% No spaces in this command list.
shell_escape_commands = \
bibtex,bibtex8,dvips,epstopdf,epspdf,etex,fc-match,\
imgconvert,\
kpsewhich,makeindex,mkgrkindex,\
pdfluatex,ps2pdf,ps4pdf,pstopdf,pygmentize,\
rpdfcrop,texindy,xindy,ulqda\
% plain TeX should remain unenhanced.
shell_escape.tex = f
% Allow TeX \openin, \openout, or \input on filenames starting with `.'
% (e.g., .rhosts) or outside the current tree (e.g., /etc/passwd)?
% a (any): any file can be opened.
% r (restricted) : disallow opening dotfiles.
% p (paranoid) : as 'r' and disallow going to parent directories, and
% restrict absolute paths to be under $TEXMFOUTPUT.
openout_any = p
openin_any = a
%% Deprecated option
%% % Disable search on multiple suffixes filenames. In many case, when `foo.bar'
%% % is looked for, you do not want to look for `foo.bar.tex' before. This flag
%% % disables searching for standard suffixes if the file name has already an
%% % extension of 3 characters. Default value is true (old behaviour).
%% allow_multiple_suffixes = f
% Allow TeX and MF to parse the first line of an input file for
% the %format construct.
parse_first_line = t
% But don't parse the first line if invoked as tex, since we want that
% to remain Knuth-compatible. The src_specials and
% file_line_error_style settings, as well as the options -enctex,
% -mltex, -8bit, etc., also affect this, but they are all off by default.
parse_first_line.tex = f
% Control file:line:error style messages.
file_line_error_style = f
% Enable the mktex... scripts by default? These must be set to 0 or 1.
% Particular programs can and do override these settings, for example
% dvips's -M option. Your first chance to specify whether the scripts
% are invoked by default is at configure time.
%
% These values are ignored if the script names are changed; e.g., if you
% set DVIPSMAKEPK to `foo', what counts is the value of the environment
% variable/config value `FOO', not the `MKTEXPK' value.
%
% MKTEXTEX = 0
% MKTEXPK = 0
% MKTEXMF = 0
% MKTEXTFM = 0
% MKTEXFMT = 0
% MKOCP = 0
% MKOFM = 0
% Used by makempx to run TeX. We use etex because MetaPost is
% expecting DVI, and not tex because we want first
Re: [Tex-music] Compile error in M-Tx documentation
On Tue, May 03, 2011 at 02:15:39AM +0200, Don Simons wrote: They start with what happens when I try to compile mtxdoc according to Dirk's instructions. I didn't think makefiles had a place in the Windows command window, but to my surprise, when I unzipped mtxD060.zip and blindly typed make dvitarget make config as instructed, I did not get nothing. I don't know what sort of makefile your make.exe expects, but I'd be quite surprised if it works on any version of Windows except when you have cygwin installed. ln -sf make-dvi make-target I'm assuming that the typical user likes either DVI files or PDF files. This step links your default choice to make-target. You could also copy make-dvi or make-pdf to make-target. It will be included into the main Makefile, specifying: which latex to run, how to concatenate output, how to make .ps files. Verry interesting, but from this point on I'm clueless on this path. However, just for laughs I will try to compile the document using commands I do know about such as for %a in (*.mtx) do prepmx %a This won't work. Most of the M-Tx code is split up into two or more files, only one of which is included into the document. You need to concatenate the two parts. The rules to make xxx.mtx are: 1. If xxx.mta and xxx.mtb both exist, concatenate them. 2. For melisma1.mtx etc, concatenate melisma.mta with melisma1.mtb etc. 3. For netsoos.mtx, concate netsoos.mta with all the netsoos.mtb files. At the moment the next mystery is how to similarly send just the basenames as arguments to the musixflx command. Or maybe it'll work on *.mx1 ? musixlfx is run on mtxdoc, not on the separate files. Actually, GNU Makefiles are not too hard to read, if you know the following: 1. A line that looks like an assignment statement defines an abbreviation later referred to by $(...). 2. Backslash at the end joins physical lines into one logical line. 3. a: b means: to make a, check whether everything in b exists and whether any is newer than the current a. The tabbed lines after that give the commands that will be executed in that case. Dirk --- 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
Re: [Tex-music] Compiling mtxdoc in Windows (was RE: Compile error in M-Tx documentation)
On Tue, May 03, 2011 at 12:39:44PM +0200, Bob Tennent wrote: Dirk: Shouldn't you be following your own advice? Re-write the Makefile in Lua (and only use tools available on every platform)! It's on my TODO list, but not at this moment very high up. Dirk --- 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
Re: [Tex-music] Compiling mtxdoc in Windows (was RE: Compile error in M-Tx documentation)
On Wed, May 04, 2011 at 02:44:07AM +0200, Bob Tennent wrote: But you might want to ask Dirk why he set it up the way he did. Back in 2005 I couldn't think of a better way to do it. The best way to see how dated the stuff is, is to notice that there is still a rule for making a LaserJet version in make-dvi. And it's really Dirk's problem, because it's his document. A statement like this is never true for any open-source software. It's all about writing a LaTeX document containing numerous small music excerpts. I'm not the only person who does that. By distributing my Makefile, I'm basically saying to the community: this is how I did it, you're welcome to use some of my ideas if you like. Dirk --- 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] Make (Was: Compiling mtxdoc in Windows
On Wed, May 04, 2011 at 08:41:47PM +0200, Bob Tennent wrote: |GNU make itself is just one .exe and two |supporting .dlls (i.e. you do not have to install a monster like Cygwin |in order to get it). We'll see if Don is willing to do that. It shouldn't be necesary to install utilities that aren't available in MiKTeX or TeXLive just to build documentation. At the risk of labouring a point I have made in another post: it isn't just a question of building documentation. It's about a method for creating a LaTeX document containing plenty of music snippets originally coded in M-Tx. Dirk --- 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
Re: [Tex-music] PMX news: Instrument-wise transposition
On Wed, Jun 01, 2011 at 06:10:57PM +0200, Don Simons wrote: There's a new beta version 2.610 of PMX that has the ability to transpose one or several selected instruments. ... Ki[instrument #][+/-][trans amt.][+/-][new key]. ... The command will override any full-score transposition. This is indeed a major new feature. Comment: MIDI transposition should be independent of the printout. Example 1: Composer writes a piece in C for singer, solo instrument and piano, notated as it should sound. A performing version is made in which the solo is played on a B♭ clarinet. The instrumental part is transposed up by two semitones to a key with two sharps, but the MIDI should stay the same. Example 2: Composer writes the same piece but notates it right from the start with the clarinet part already transposed. The instrumental part is transposed by no semitones to a key with two sharps, but the MIDI should sound two semitones lower. Dirk --- 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
Re: [Tex-music] PMX news: Instrument-wise transposition
On Thu, Jun 02, 2011 at 02:54:22AM +0200, Don Simons wrote: I've been avoiding facing up to the possibility of entering info in the transposed key, let alone working out how to get MIDI to deal with it. I have vague notions of somehow internally doing a reverse transposition. This will take longer to work out. At the syntax level it's easy to dream up something logical: K[+/-][trans amt.][+/-][new key] applies to the whole score Ki[instrument #][+/-][trans amt.][+/-][new key] applies to this instrument, overriding whole score KIi[instrument #][+/-][trans amt.] applies to this instrument's MIDI output (default: no transposition) KSi[instrument #][+/-][sharps/flats] instrument-specific key signature, overriding isig needed at start of score since transposing 0 semitones will print the old and new key signatures. Those terrible piano pieces (Scriabin? Rachmaninov? I forget) that notate the two hands in different keys will have to be notated as one instrument per hand :-) Didn't the formidable Serge occasionally write piano music on three staves, or is that only the poor editor's attempt at making it playable for people with normal hands? Dirk Dirk --- 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
Re: [Tex-music] M-Tx: Repeat at the end ignored
On Sun, Jul 31, 2011 at 09:39:27PM +0200, Simon Dreher wrote: in the example below, the repeat sign at the end of the piece is ignored. M-Tx puts a final / in a separate line after the command Rr. If I remove this line, I get the repeat sign; but of course I don't want to modify the pmx file every time I compile the source. How can I get the repeat sign without modifying the generated pmx file? Viele Grüße, Simon With the following packages (current on Ubuntu Natty) I can't reproduce the error you report. This is TeX, Version 3.1415926 (TeX Live 2009/Debian) (./xxx.tex (/usr/share/texmf/tex/musixtex/m-tx/mtx.tex mtx.tex 0.60 16 March 2005 M-Tx 0.60d (Music from TeXt) 11 October 2008 (/usr/share/texmf/tex/musixtex/base/musixtex.tex MusiXTeX(c) T.114 1 Feb 2009 ) (/usr/share/texmf/tex/musixtex/pmx/pmx.tex PMX, a Preprocessor for MusiXTeX, Version 2.502a 29 March 04 ) (/usr/share/texmf/tex/musixtex/musixtexadd/musixlyr.tex MusiXLYRics 2.1c June 10, 2003 Please supply the corresponding printout on your system. Dirk --- 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
Re: [Tex-music] Wrong lyrics adjustments with hyphens
On Tue, Aug 16, 2011 at 03:55:06PM +0200, Rainer Dunker wrote:
For example, change your M-Tx input line
@-2 a4 } a a a |
to:
\\\def\atnextline{\mtxLyricsAdjust{1}{-9}}\ a4 } a a a |
Ouch! This is definitely the sort of thing that M-Tx was designed
to avoid. Would it in other situations also be right to do that,
or only in this one? If not so, can one identify the situation
automatically so that M-Tx itself puts this in when needed?
Dirk
---
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
Re: [Tex-music] Wrong lyrics adjustments with hyphens
On Thu, Aug 18, 2011 at 04:02:43PM +0200, Rainer Dunker wrote:
Am 16.08.2011 schrieb Dirk Laurie:
On Tue, Aug 16, 2011 at 03:55:06PM +0200, Rainer Dunker wrote:
[...]
\\\def\atnextline{\mtxLyricsAdjust{1}{-9}}\ a4 } a a a |
Ouch! This is definitely the sort of thing that M-Tx was designed
to avoid. Would it in other situations also be right to do that,
or only in this one?
I'd say it would be wrong to do that always.
...
Although this appears to be a really dirty and fragile solution, ...
But I'm far from sure whether this would work in every case and
would not raise unwanted side effects...
Could you please have a look at it and evaluate whether it is generally
feasible?
...
From a pure M-Tx point of view, I'd rather introduce syntax for
postponing something to the next line than special-case code that
may itself have exceptions. E.g. `!@-9` to make `@-9` act later.
In PMX `!` occurs only inside comments, in M-Tx only on uptext
lines.
Would this not be a more versatile solution, maybe even at the PMX
level? Could I have some feedback from people who write a lot of
scores? Just grep for `atnextline` in your .mtx and/or .pmx files.
I know there is a lot of them in André van Ryckeghem's edition of
the Deutsche Messe.
Dirk
---
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
Re: [Tex-music] Wrong lyrics adjustments with hyphens
On Thu, Aug 18, 2011 at 05:52:45PM +0200, Don Simons wrote: I believe you're right that PMX doesn't now use ! at all. And I'd be glad to help however I can. But I'm very unclear on what you are proposing at the PMX level. Would the stuff after ! be PMX command(s), in-line TeX to be put into \atnextline, or something else? And if it is just stuff to go in \atnextline, what would be the advantage over simply using inline TeX within PMX? Maybe in PMX there isn't anything except TeX that one would like to take effect only at the next line, in which case there is no argument. Dirk --- 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] LaTeX vs MusiXTeX (Was: No room for new \dimen)
On Fri, Sep 23, 2011 at 05:48:26AM +0200, Don Simons wrote: 4. LaTeX has nothing to do with any of this. LaTeX is a special set of macros designed to supposedly make TeX easier to use to produce nice text documents. There is absolutely no requirement to use LaTeX together with MusiXTeX; in fact, it just complicates matters to the extent that you should NEVER use them together unless you have a REALLY good reason AND are a pretty advanced user already. I agree, but let me dot some i's and stroke some t's. - TeX is a typesetting program with particularly strong support for mathematical typesetting, where exact two-dimensional positioning is important. TeX is idiosyncratic but powerful, abstruse but conceptually simple, huge but very well supported over almost 30 years. There is nothing that TeX cannot do, but it is not user-friendly. - TeX is also a customizable typesetting language that allows the user to define his own special-purpose instructions for other pernickety typesetting tasks, like music. Don Knuth (the author of TeX) writes a special set of macros for every typesetting task he undertakes and honestly expects other TeX users to be similary diligent. (Instead, they prefer to abuse existing macro libraries.) - MusiXTeX is a music typesetting program written in TeX. The need for exact two-dimensional positioning is even more crucial than in mathematics, extending to whole pages and even whole scores in which a change made in one bar can affect decisions on the appearance of every page. It's not user-friendly any more than TeX itself is, which is why it's much nicer to use it indirectly via PMX. - LaTeX is a markup language written in TeX, i.e. a language that urges you to think abstractly about your document: not indented but quoted, not italics but emphasized, not large boldface with open space above and below but section heading, etc. It's user-friendly (well, compared to TeX it is) and equally well supported, so it has become a de facto standard among scientists. So you see, there are two conflicting tasks: typesetting, in which you care about minute details of appearance; and markup, in which you say broadly want you require and the program takes care of the rest. If you mix MusiXTeX and LaTeX, the two pull against each other, and you spend a lot of time compensating for the things LaTeX has done to your document. The only case where it is useful to mix them, is when a scientist who knows LaTeX well tries to write a document like the M-Tx manual, which is in the first place a structured text document, but has numerous small music inserts. But it is even more idiomatic to do it as in the MusiXTeX manual, where the author did what Knuth wanted and wrote his own special-purpose set of macros for the purpose. Dirk --- 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] Name of M-Tx executable (Was: No room for new \dimen)
On Fri, Sep 23, 2011 at 04:22:22PM +0200, Roland Stigge wrote: Yes. Except that currently, mtx is called prepmx (/usr/bin/prepmx) in Debian. Might by a good idea to rename it to mtx /usr/bin/mtx), though. Any objections? Wikipedia says: MTX - A UNIX Linux command (Quoted: `mtx` is a set of low level driver programs to control features of SCSI backup related devices such as autoloaders, tape changers, media jukeboxes, and tape drives.) The number of installations that still use SCSI must be dwindling fast. Still, if I type `mtx` on my up-to-date Ubuntu system, I get The program 'mtx' is currently not installed. You can install it by typing: sudo apt-get install mtx Debian is more conservative than Ubuntu, so I can't imagine that Debian has chucked away that `mtx`. There is another reason, which is not Unix/Linux specific. Unfortunately the three letters mtx, in the fourteen years of existence of M-Tx, have come to be pretty hard-worked in the TeX world. The extension .mtx is used in modern ConTeXt packages as an abbreviation for 'metrics', doubtless selected with the same smugness at finding three suggestive but apparently available letters with which I chose M-Tx all those years ago. These packages contain executables 'mtxrun' and 'mtxtools', which are rather essential ones. And LuaTeX, the future of TeX, relies on ConTeXt infrastructure, so .mtx will be in mainstream TeX soon. Sorry Mr Macdonald, I don't care whether your little carry-oot shop in Dunoon has been in the family for generations, but if you plan selling burgers there, you'll have to call it something different from Macdonald's. The 'file' command recognizes ConTeXt .mtx files as LaTeX auxiliary file (enough to make Hans Hagen choke in his Heineken, I'm sure) and M-Tx files as FORTRAN program (urggh! there goes some of my Windhoek). ConTeXt doesn't contain an executable 'mtx' just yet, though. But all the same, I have no wish to pip Hans at this post. Suggestion: keep the name prepmx but write a brand-new script mtx2pdf for the whole process so that no one actually ever needs to invoke prepmx pmxab or musixflex directly. In Lua, of course. I may even do it myself. Dirk --- 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
Re: [Tex-music] Name of M-Tx executable (Was: No room for new \dimen)
On Fri, Sep 23, 2011 at 06:28:47PM +0200, Bob Tennent wrote: |Suggestion: keep the name prepmx but write a brand-new script mtx2pdf |for the whole process so that no one actually ever needs to invoke prepmx |pmxab or musixflex directly. In Lua, of course. I may even do it myself. Lua scripts are already written and in use. Check out musixtex/scripts/musixtex/musixtex.lua pmx/scripts/pmx/pmx.lua mtx/scripts/mtx/mtx.lua in http://mirrors.ctan.org/macros/musixtex/musixtex-texmf.zip http://mirrors.ctan.org/support/pmx/pmx-texmf.zip http://mirrors.ctan.org/support/mtx/mtx-texmf.zip respectively. I hesitate to change their names now but will do so if there's general agreement. They're typically used via symbolic links (on Unix-like systems) or .bat wrapper scripts on Windows, which can of course be named anything a user desires. As long as they are .lua, the arguments in my post don't apply. But there _is_ something self-explanatory about the name 'mtx2pdf' which the name 'mtx', even if it is 'mtx.bat', does not convey. Dirk --- 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
Re: [Tex-music] More than one style in a piece.
2011/10/16 Sebastian Canagaratna s-canagara...@onu.edu: Hi: I am trying to code O for a close Walk (SATB voices and organ) in mtx. The first sixteen measures are for soprano and organ, and so requires only three stave. Thereafter the style changes and there are 4 staves to a system, SATB and organ. Can this be coded in mtx, since there is only one preamble to declare the style? Does one have to go to pmx or musixtex to code this/ This can in principle be done with PMX by using the movement change instruction. It's not in M-Tx. Dirk --- 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
Re: [Tex-music] Changing Lyrics position in mid-bar from LB: to L:
2011/10/22 Sebastian Canagaratna s-canagara...@onu.edu: r2 r2 bf24 | r2b r2b f24 | L: I r2b r2b d24 | b0f3 r2 b2 | LB: rest; (??) When I write the above code the program sees to expect the bar to be finished in LB so it puts ? where I should be. Is there any way to tell the program to stop the lyrics line? Easiest is a blank syllable, thus: LB: rest; ~ Dirk --- 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
Re: [Tex-music] m-tx/pmx: ignoring repeats etc. at end of file
2011/10/24 Don Simons dsim...@roadrunner.com:
...
% Paragraph 5 line 26 bar 3
L2
\mtxZchar{10}{3.}\ f4 f4 e4 d4 f2 of c4d ba8 | /
% Paragraph 6 line 30 bar 4
\\\let\ept\endpiece\def\endpiece{\setrightrepeat\ept}\
\mtxZchar{10}{4.}\ a2 g2 f0 of | Rb
/
% Coded by M-Tx
=
I've confirmed that this gives the repeat, although I don't yet understand
why. The PMX syntax ...| Rb / is pretty flakey and I'd have thought either
we'd get a PMX error or the Rd would be ignored. But neither is happening;
the Rd causes \endpiece rather than \Endpiece , and the inline TeX
redefinition of \endpiece does the trick.
This is a very old kludge and all I can remember about it is that I
tried many things before finding something that worked. I'm sure that
PMX has much nicer ways of doing it nowadays, but if I ever revise
M-Tx thoroughly it will be a rewrite in Lua, not a patch to the Pascal
source.
This all kinda makes me wonder how M-Tx users get double bars at the ends of
pieces (since using | after the last line in the M-Tx evidently gave Rd in
the PMX and \endpiece in the TeX) , and that'll be my next investigation.
They do nothing. To get anything except the double bar, you do something.
Dirk
---
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
Re: [Tex-music] 1 natural key signature
Oops, attached wrong file. nat1.pdf Description: Adobe PDF document --- 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
Re: [Tex-music] M-Tx - two lines of text above
2011/12/10 Wojtek Chemijewski wojtek.chemijew...@gmail.com:
Hello,
I am trying to use M-Tx to typeset a couple of songs for someone who
recently started learning to play the violin, using the same notation as her
teacher does - placing numbers of fingers of the left hand above notes, and
string names above these numbers, so the idea is for that to look along
the following lines:
U: D ~ ~ ~ ~ А ~ ~ ~ ~ D ...
U: 0 1 2 3 3 0 2 1 0 0 3 ...
d4 e8 f | g4 g | a8 c b a | a g | ...
L: Lyrics
However, two lines of text above do not seem to be supported. Is there an
easy way to achieve what I need?
The easiest is to use superscripts for the strings. Not quite what you want,
but maybe your violinist can accept it.
U: $0^D$ 1 2 3 3 $0^A$ 2 1 0 0 $3^D$
Beyond that, TeX wizardry is necessary. The first uptext word translates
to \mtxZchar{10}{$0^D$}. You can redefine \mtxZchar. Trivial example:
put a paragraph containing only this:
%% \let\keepZchar\mtxZchar\def\mtxZchar#1#2{\keepZchar{#1}{$#2$}}
between the preamble and the music. That allows you to type
U: 0^D 1 2 3 3 0^A 2 1 0 0 3^D
This modification math-izes all uptext. Not undesirable, for the other
digits will be in the same font. It will clash with other usage though.
But I mean it only as an example of how to set about it.
Dirk
---
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
Re: [Tex-music] Imposition
My problem is to start with individual pages, merge them 2 at a time into larger pages (without scaling) that I can still print one at a time, but that are arranged so I can make a booklet by printing the larger (2-up) pages double-sided. Have you visited this site? http://wiki.scribus.net/canvas/PDF,_PostScript_and_Imposition_tools Dirk --- 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
Re: [Tex-music] Keyboard edition with modern clefs
2012/5/13 Don Simons dsim...@roadrunner.com: But when the bass notes are very low and there are no other notes in the lower staff, it looks stupid to use down-stems there. Isn't the situation completely analogous to SATB chorus music on two staves? Nobody complains about down-stems for the bass part even though they push down the lyrics. --- 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
Re: [Tex-music] Postion of r2 and r0
2012/7/18 Hermann Hinsch hermann.hin...@urz.uni-heidelberg.de: A question to the experts: For PMX or M-Tx: if the rest r2 or r0 is at the start of a bar would it be possible to adjust the rest automatically in the middle of the free space? This is the sort of thing where M-Tx just blindly follows PMX. The only automatic control you have in PMX is on full-bar rests, where centering is default and rpo turns it off. You can't do it with X since that is extra whitespace, not offset. You could put in a PMX feature request, say r2c etc would center any rest. r2c: would also toggle stickyness of centering. At present there are all sorts of ad-hoc offsets. A single general-purpose offset would also do the job, e.g. O0.5n2 could offset the next symbol by 0.5 of a half-note. As an immediate solution, you could redefine the TeX \hpause command to offset the rest by half the remaining distance. This should not be too hard to the real TeXperts since \pnotes causes the required registers to be set, but it's out of my league. That would center all r2 rests though. Or you could just live with the fact that current musical typography practice (not only PMX) does not center rests except whole-bar. --- 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
Re: [Tex-music] Space between systems
2012/8/16 Don Simons dsim...@roadrunner.com: The following slightly modified version of the simple PMX file I posted 8/14 compiles just fine, but if you uncomment \input mtx, the vertical spacing gets messed up. I've gone through mtx.tex line-by-line and don't see anything obvious that would affect vertical spacing. Could one of the TeXperts please have a look and see if you can figure out what's going on here? That's not a good description of me but being a decent numerical analyst I was able to isolate the line concerned by binary search (i.e putting \endinput halfway down, half of that, etc). If you comment out \input musixlyr the phenomenon you describe goes away. If 24 hours from now nobody has found out what goes wrong in musixlyr.tex, I'll apply the same method again. Dirk --- 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
Re: [Tex-music] Space between systems
2012/8/16 Don Simons dsim...@roadrunner.com: Dirk that's great detective work. I understand binary searching, but not how or where to use \endinput. Seems like if you really ended input part way through, the printed page couldn't come out looking the same. \endinput means skip the rest of this file. Only this file. It's extremely useful. 1. Document macros in plain text or Markdown after \endinput instead of cluttering up the TeX source with comment lines. 2. Move stuff to after \endinput instead of just deleting it — you may want to put it back later. 3. Temporarily comment out the rest of the file for debugging. 4. Avoid reading in a macro file twice (see the first non-comment line in mtx.tex). Dirk --- 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
Re: [Tex-music] Space between systems
2012/8/19 Don Simons dsim...@roadrunner.com: Meanwhile, I have a question for Hermann, Rainer, Dirk, or anyone else who cares to jump in: Can you provide an example of an M-Tx source that manages to change the number of instruments in midstream. No, I have never needed it. avoid the extra steps and get M-Tx to directly create a .pmx that reflects the changes in noinst. M-Tx has something I call a control paragraph. It may contain only comments and preprocessor directives. The control paragraphs are at present preamble-only: they must all appear before the first music paragraph. The clean way to do changes in noinst etc would be to allow control paragraphs later too. I have considered allowing this in the past. There seemed to be no PMX way to change the number of instruments except a phony new movement. It would have involved mastering more PMX than I use regularly, which is the sort of knowledge that one loses quickly, and I decided against implementing something I would not understand a few years later. So the present situation is that a user can by cleverly inserting lines starting %%LiM get the required effect, but that user would need to master the required PMX for himself. By the way, I've often cursed the requirement that line numbers and page numbers are compulsory. It forces me to do the complete score, print it out, manually pencil in line numbers, insert the required line breaks, do the score again, adjust those line breaks that now look uncomfortable because the earlier ones affected what follows, etc. Dirk --- 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
Re: [Tex-music] Redefinition of \raisebarno{..}
2012/8/20 Hermann Hinsch hermann.hin...@urz.uni-heidelberg.de:
In the M-Tx-source below the position of the barnumber is set by
\def\raisebarno{5mm}. If
you look into the tex-file you will find a redefinition at line 116 and 118.
Why?
Your own redefinition of \raisebarno has no effect, since it appears
in the tex-file
before `input pmx`. PMX works out that its default of 3.5\internote
will clash with
other stuff and temporarily redefines it to 4.5\internote just for
that one place.
Note that pmx.tex has a comment describing the bar number mechanism as
`messy`. I wouldn't dare to disagree with Don on this issue.
Somewhere in my scores I have something that overrides PMX's way of doing
bar numbers, but I can't find it on my office computer (from which I
am typing this,
but which I seldom use since my retirement.)
There must be others (Christian? André?) who have also done that.
Dirk
---
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
Re: [Tex-music] Redefinition of \raisebarno{..}
2012/8/20 Hermann Hinsch hermann.hin...@urz.uni-heidelberg.de: Am Montag, 20. August 2012, 10:43:12 schrieb Dirk Laurie: Your own redefinition of \raisebarno has no effect, since it appears in the tex-file before `input pmx`. I doubt that this is the reason because it fails in all other of my scores beginning with the same order of instructions. That second paragraph with inline TeX comes right at the start of the PMX file inside the `---` markers, and by definition (see the PMX manual) will appear in the TeX file _before_ `input pmx` does. Since pmx.tex contains its own definition of \raisebarno, it will override the earlier one. --- 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] Panmus: a proposal? a dream?
There should be something for which Panmus would be a logical name. Maybe there is, I just don't know about it. Let me start by describing Pandoc, which is not a dream, but a reality, driven by one superman who does the design and coding and an active mailing-list of users (approximately two new topics per day). Pandoc is a system for converting some precisely specified text-like input format, at present any of six, to a convenient output format, at present any of more than twenty, including all its input formats, as well as PDF via LaTeX. Pandoc has a favourite input format: an extended version of Markdown, the original text-like markup language; and a favourite ouput format: HTML. Pandoc's great strength is its modular design. At the centre sits a Haskell data structure, which has been designed with great logical clarity (the creator is a philosophy professor) to provide abstractions for features that a document is allowed to contain. The text serialization of this structure as valid Haskell source code is the Native format of Pandoc, which is one of its input formats. I use Native loosely to mean not only the serialization but also the internal data structure itself. All input formats have a Reader that converts them to Native; all output formats have a Writer that converts Native to them. How does this relate to us? 1. Pandoc can produce beautiful documents from input source created by a text editor. 2. TeX is the route taken to PDF output. 3. The basic reader - internal structure - writer design is present in the software we use. These are basically our goals too. Where we fall down is that our internal structures (Fortran for PMX, Pascal for M-Tx) are not sufficiently well modularized that we can tell someone who wants to write say an ABC reader or a MIDI writer what to do so that we can just plug it in. We need something which can read PMX, M-Tx or ABC; convert it to a central structure; from that central structure write PMX, M-Tx, ABC, MusiXTeX, Lilypond, MIDI, etc. That central structure obviously must be a Lua table, giving us a Native format of our own, and the readers and writers must be written in Lua. That way, getting it into TeX will be easy. (BTW, LuaTeX has recently reached version 0.80.) We also need a favourite input format (basically the common subset of PMX and M-Tx, with extensions that will only reveal themselves as the design of the central stucture solidifies) and a favourite output format (PDF or Postscript). Is Panmus a proposal? Or just a dream? I don't know. Dirk --- 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
Re: [Tex-music] Back to square one after a long break from typesetting
2013/6/9 Raphaela evarapha...@gmail.com: thank you. I have now installed the full TeXlive package, but the instructions on the page for Unix-like systems are not working for me (all I get is a command 'tlmgr' not found message) and I don't know how to go about installing a package manually. A chicken-and-egg problem. If you already have an older TeXLive it can used to get the new one going, but if you don't, your system can't see the necessary scripts. Find the directory texlive/2012/texmf/scripts (maybe 2013 in your case) and add it to your PATH. Do `hash -r` otherwise your system might remember that it could not find tlmgr. --- 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
Re: [Tex-music] Back to square one after a long break from typesetting
2013/6/10 Raphaela evarapha...@gmail.com: To that end, would someone be kind enough to explain how to add the relevant bin directory to my PATH? Where would I find the PATH and how do I add things to it? Say you have some excutables in /home/raphaela/texmf/bin. $ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games $ PATH=/home/raphaela/texmf/bin:$PATH $ echo $PATH /home/raphaela/texmf/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games --- 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
Re: [Tex-music] Number of voices chenge in MTX
2013/6/18 Luigi Cataldi luica...@gmail.com: I know that M-Tx is not aware of movement breaks and the possibility to change the number of voices (MTX manual p. A-7). The reason for that is that I have never needed the feature myself and therefore did not master how to use it from PMX. I don't think there is any very intrinsic reason why M-Tx can't do it. So please try. Dirk --- 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
Re: [Tex-music] M-Tx, first bar shorter and then a repeat
2014-01-29 Wojtek Chemijewski wojtek.chemijew...@gmail.com: == This is M-Tx 0.60d (Music from TeXt) 11 October 2008 == Input from file panjest.mtx Writing to panjest.pmx Line has 1 bar + 16/64 notes Line does not end at complete bar: ERROR on line 15 f8 g8 |: a4 a8 a8 g8 f8 Please post a complete example file. Your snippet does not contain 15 lines, so there is no way to tell what went wrong. --- 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
Re: [Tex-music] M-Tx, first bar shorter and then a repeat
2014-01-30 Don Simons dsim...@roadrunner.com: So problem solved? Why go any further? Well, actually M-Tx is supposed to be clever enough to do this (and does, when it is a plain barline). So failing to do so when it is a repeat counts as a bug. I'll try to hunt it down (although I've stopped thinking of myself as M-Tx maintainer after some others, notably Christian, have stepped into the breach). Dirk --- 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
Re: [Tex-music] M-Tx, first bar shorter and then a repeat
2014-01-31 Christian Mondrup rec...@icking-music-archive.org: Dirk Laurie wrote: 2014-01-30 Don Simons dsim...@roadrunner.com: So problem solved? Why go any further? Well, actually M-Tx is supposed to be clever enough to do this (and does, when it is a plain barline). So failing to do so when it is a repeat counts as a bug. I'll try to hunt it down (although I've stopped thinking of myself as M-Tx maintainer after some others, notably Christian, have stepped into the breach). I'm afraid I need to disappoint those expecting me to maintain M-Tx. That role should be taken by active users of the software. For some years I've been using MusiXTeX and friends only for fixing bugs in my existing M-Tx engravings while I'm using another open source engraver, MUP for my ongoing projects. I'll put M-Tx on GitHub. Then anyone willing to maintain it can simply fork it. Dirk --- 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
Re: [Tex-music] M-Tx, first bar shorter and then a repeat
2014-02-01 Dirk Laurie dirk.lau...@gmail.com: Until I get this fixed, the best workaround is: 1. Use plain bar lines. 2. Insert an explicit left repeat in what will become PMX's first voice. OK, I have fixed it and the changes are on my GitHub repository, as described in another thread. The actual code change is tiny, but finding the spot required some persistence. Staring at the workaround (just one extra `Rl`), I am not so sure any more that I should have considered this to be a bug. After all, a repeat sign commonly appears in mid-bar later on when the repeat includes the pickup.. Oh, well, it's done now, and I'm sure at least that it is the intuitively right thing to do. If you have a repeat sign in the middle of your pickup, you will be confusing the performer too. --- 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
Re: [Tex-music] musixtex with more than 20 music examples
2014-09-01 18:58 GMT+02:00 Dr. Gerhard Eber ge.e...@arcor.de: I have written a book containing several hundred examples of music, each of them of the size of only one or two lines. When I compile the individual chapters of the book containing less than 20 pieces separately, there is no problem, but when all the chapters are put together, musixtex stops working after 20 pieces of music, and the 2nd latex run stops after the 20th piece (LaTeX is blocked). It seems that there is a limitation to musixtex as far as the number of pieces is concerned. Is it possible to extend this? This looks like some kind of stack overflow. Could you post the log file? --- 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
Re: [Tex-music] Issues with M-Tx
2014-09-20 23:25 GMT+02:00 Don Simons dsim...@roadrunner.com: Instead I manually downloaded mtxP060d.zip from the Icking archive and just extracted prepmx.exe from there. Does your zipfile extractor have an option to convert text files to local format? Otherwise, if your system does not use plain Ctrl-M end-of-lines, netsoos.mtx might not be read correctly. --- 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
Re: [Tex-music] wrong bracket size
Do they look OK if you omit this line: Space: -3 -2 -2 -2 -2 +3 If so, the problem would be that the TeX code emitted by \mtxGroup does not take into account the settings implied by the \mtxInterInstrument commands before it. I won't be able to help any further in that case, apart from quoting from mtx.tex: % All TeX commands put directly into PMX files by M-Tx are defined below, % except the following: % 1. \input mtx % 2. code to achieve a multi-bar rest % 3. User's own inline TeX % 4. \mtxversion and \mtxdate are defined in prepmx itself % 5. Utterly basic TeX commands like \ and % % It is therefore possible for a TeXpert to tune the performance % of M-Tx without touching the preprocessor. Thus, it is quite possible that the problem could be fixed by changing some macros in mtx.tex. Unfortunately, in the 11 years since I last revised mtx.tex, all the necessary musixtex skills that I presumably must have had at the time, have evaporated. 2014-09-21 18:17 GMT+02:00 Simon Dreher simon.dre...@gmx.net: Hi, in the attached m-tx source, the bracket in front of the chorals staves starts too high and is too large. Does anyone have an idea why and how to fix it? Best regards, Simon --- 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
Re: [Tex-music] How can I switch PMX to landscape paper format?
2014-10-20 8:45 GMT+02:00 Andre Van Ryckeghem a...@telenet.be:
Dear all, this is what i use for changing space between staffs for lyrics.
The real space depends of the global def: ie AI0.9
For 1 staff, or for under the lowest instrument, use ie.
\\staffbotmarg=2\Interligne\
Between the instruments ie. above instrument 1:
\\setinterinstrument1{3\Interligne}\
Changing spaces between staffs, redefine interstaff, ie:
\\let\interstaffsav\interstaff\def\interstaff#1{}\interstaffsav{14}\
In M-Tx, `Space` is supposed to avoid the need to do these
with inline TeX.
---
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
Re: [Tex-music] music typesetting question
2014-10-29 2:06 GMT+02:00 Bob Tennent r...@cs.queensu.ca: I'm setting a piece in 2/2 meter. One part consists essentially of quarter notes always off the beat. Is it acceptable to typeset this as in the following: \itieu0o\ca o | \ttie0\ca o\qa o\qa o\qa o\itieu0o\ca o | \ttie0\ca o ... where the | indicates a barline. The reason I ask is that I've seen the same material set as follows: \itieu0o\ca o | \ttie0\ca o\qa o\itieu0o\ca o\ttie0\ca o\qa o\itieu0o\ca o | \ttie0\ca o ... You will have all the classical composers on your side if you do, but maybe some primary school music teachers might be offended. See e.g. http://imslp.org/wiki/Dichter_und_Bauer_(Supp%C3%A9,_Franz_von) page 12, Allegro Strepitoso. --- 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
