File: FAQ

package info (click to toggle)
m-tx 0.30a-3
  • links: PTS
  • area: contrib
  • in suites: hamm
  • size: 568 kB
  • ctags: 536
  • sloc: ansic: 3,624; pascal: 60; makefile: 38; sh: 5
file content (215 lines) | stat: -rw-r--r-- 9,809 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
           Frequently Asked Questions


Before I answer your FAQ, just ask yourself mine:

Q0:  Are you using PMX 1.3 and MusiXTeX at least T.73?
A0:  If not, many M-Tx 0.25 (and later) scores will fail.
     For some of them, there are workarounds below.

Summary:

Q1.  The notes are squished together near the left margin.
Q2.  The lyrics are printed on the bottom line of the stave.
Q3.  [][][][][] appears in my TeX log.
Q4.  pmxa says "TeX string too long"
Q5.  There is a mistake at the pmxb stage.
Q6.  Can't you give us a script to automate the whole process?
Q7.  I'm having a problem with this file that worked before.
Q8.  At the TeX stage it says "Undefined control sequence \setlyrics".
Q9.  At the TeX stage it says "I can't find file `musixlyr'".
Q10. Suddenly for no reason I don't get lyrics any more.
Q11. Just what is the difference between MusiXTeX, PMX and M-Tx?
Q12. The C code supplied gives compilation errors.
Q13. Is there a way to change the font for the lyrics?
Q14. Why do I get "I can handle too few voices but not too many"?
Q15. How can I put in expression markings?
Q16. The examples supplied don't work.
Q17. I need a left repeat immediately after the pickup.
Q18. Why can't I have 14 voices if I have 7 staves?
Q19. At the TeX stage it says "Undefined control sequence \enableauxlyr".
Q20. My MusiXTeX is older than T.73 and does not recognize \grouptop.
Q21. I tried putting in some forced beams, and the alignment between
     lyrics and notes went haywire.
Q22. My output has line breaks at different places to my input.

Q*.  I need advanced features not supported by M-Tx.

-----------------------------------------------------------------------------

Q1. The notes are squished together near the left margin.
A1. You have failed to run musixflx.  See Question 6.

Q2. The lyrics are printed on the bottom line of the stave, not
    below where I want them. 
A2. Use the Space: preamble command.  The reason for this behaviour
    is explained in the User's Manual, Section 6.3.

Q3. I've changed hardly anything in my score, but now there are many
    little boxes like [][][][][] in my TeX log.
A3. You must delete the .mx2 file created by musixflx, otherwise MusiXTeX
    doesn't know you are re-doing the first pass.
    
Q4. I get a message saying something about a TeX string being too long
    at the pmxa stage.
A4. Lyrics lines (except those in lyrics paragraphs) are passed via
    TeX commands.  The total length of a typed lyrics line with its
    label must not exceed a certain limit (80 characters in PMX 1.10,
    128 characters starting at PMX 1.14).

Q5. Everything passes perfectly through prepmx and pmxa, but there is
    a mistake at the pmxb stage.
A5. This should not occur.  Tell Don Simons (dsimons@logicon.com)
    about it.

Q6. Can't you be a bit more helpful and give us a script to automate the
    whole process?
A6. The following script works as a batch file with MSDOS.  
    Unix users should be able to figure out a shell script from it.

@echo off
rem File mtx.bat
prepmx %1 %2 %3 %4 %5 %6 %7 %8 %9
if errorlevel 1 then goto exit
echo %1 | pmxa
if errorlevel 1 then goto exit
pmxb
del %1.mx?
tex %1
if errorlevel 1 then goto exit
musixflx %1
tex %1
:exit

Q7. I'm having a problem under M-Tx 0.22 (M-Tx 0.25) with this file that 
    worked before.
A7. (0.22) The specifications for the dotted note shortcut and lyrics tuning 
    were changed.  You can get M-Tx 0.12 compatibility by putting a line
    Options: dl
    in the preamble.  In the case of lyrics, though, it is worth the effort 
    to convert the score to M-Tx 0.22 specifications: they look better.
    (0.25) M-Tx used to make a NAME.mod file for every NAME.mtx file.  If 
    such files are still lying about, they will still be read in by PMX.  
    Delete them mercilessly.

Q8.  At the TeX stage it says "Undefined control sequence \setlyrics".
A8.  You have not designated any style as "Vocal" or "Choral" but
     are trying to use lyrics.

Q9.  At the TeX stage it says "I can't find file `musixlyr'".
A9.  The file musixlyr.tex should be moved from the M-Tx installation
     directory to a directory in the TeX input path.  E.g. the same
     directory where you keep your own MusiXTeX files.

Q10. Suddenly for no reason I don't get lyrics any more.
A10. If your supply of lyrics is not exhausted, the reason could be:
     1. Each lyrics line starting with L: takes effect at its own
        paragraph.  Unused lyrics from the previous paragraph get thrown 
        away.
     2. The beam-end and slur-end symbols ] and ) must IMMEDIATE follow 
        the note to which they apply, before chordal notes, ornaments etc.
        otherwise the lyrics placement algorithm doesn't see them.

Q11. Just what is the difference between MusiXTeX, PMX and M-Tx?
A11. MusiXTeX is a typesetting system in which you are allowed to do
     anything, but which needs to be told very precisely, in a rather
     cryptic language, just what you want to do.  PMX is a preprocessor
     for MusiXTeX that makes all the layout decisions in a way that 
     looks professional and relieves the user from any need to know
     MusiXTeX.  In addition, PMX offers a simplified input language
     for describing notes and other score elements.  M-Tx is a language
     for representing printed music in text, with the aim of retaining
     as much of the actual two-dimensional look and feel as possible,
     and incorporating lyrics and chords in its design.  The current
     implementation of M-Tx produces a PMX file as output.

Q12. The C code supplied gives compilation errors.
A12. Make sure that the unzipped text files are in the right format
     for your system.  If you have an old unzipper that does not have 
     an auto-convert option (-a or -l), you can try the following:
  1. Maybe your editor has an option called "fix line boundary
     problems" or "save as a DOS file" or words to that effect.
  2. Download the GNU unzip program (probably called something
     like UNZ520X.EXE) from your nearest archive.  It can auto-convert.

Q13. Is there a way to change the font for the lyrics?
A13. You can use any available TeX font-changing command.  
     E.g. put the line
     %% \\\medtype\
     at the start of the paragraph where you need a bigger font.  

Q14. Why do I get "I can handle too few voices but not too many"?
A14. You need to have a blank line between all the voice/lyric systems.
     This is how M-Tx knows to move on.

Q15. How can I put in expression markings?
A15. \\Uptext{D.C.} puts D.C. above the stave.  \ccharnote{10}{\it A~tempo}\ 
     puts "A tempo" where line 10 of the stave would have been if it had
     10 lines instead of 5.

Q16. The examples supplied don't work.
A16. Did you convert the text files to your system's format?  See A12.

Q17. I need a left repeat immediately after the pickup.
A17. Repeat signs may legally appear in the middle of a bar, and are
     therefore not accepted as substitutes for a bar line even though
     they have a `|' in them.  You need to put a bar line in as well
     if you use a pickup.  E.g. "d | |: g b a g".

Q18. Why can't I have 14 voices if I have 7 staves?
A18. PMX allows only 7 "music lines" because some small but not quite
     obsolete computers might have too little memory to run it.  The
     Linux-friendly versions of pmxa.f and pmxb.f on my ftp server
     ftp://calvyn.puk.ac.za/dirk/mtx/pmx-gnu.zip allow 14 voices on
     7 staves.

Q19. At the TeX stage it says "Undefined control sequence \enableauxlyr".
A19. You must use the pre-release version of musixlyr.tex that comes
     with M-Tx.  The latest public version on CTAN does not have all the
     required features.

Q20. My MusiXTeX is older than T.73 and does not recognize \grouptop.
A20. Get up to date -- there are other good things about T.80.  But
     in the meanwhile, put the declarations
     \def\grouptop#1{\songtop}\def\groupbottom#1{\songbottom}
     in a file called BASENAME.mod if your input is BASENAME.mtx.

Q21. I tried putting in some forced beams, and the alignment between
     lyrics and notes went haywire.
A21. Use [[ instead of [ on the left bracket.  This tells M-Tx to
     use a forced beam but still have a syllable to every note. 
     
Q22. My output has line breaks at different places to my input.
A22. This isn't a bug, it's a feature.  Line breaks must be explicitly
     requested, e.g.
     %% L5
     makes line 5 start at the current music paragraph.

-----------------------------------------------------------------------------

Q*. I need MusiXTeX features not supported in PMX, let alone M-Tx.

A*. You can always ask me to put them in, but that might take a long
    time.  So here are a few hints to tide you over. 

(a) Read the PMX manual.  It explains how to put many advanced
    features into the music lines.

(b) It may happen that you need a feature that even PMX does not support.
    There is not much that MusiXTeX cannot do.  If you can find it in the 
    MusiXTeX manual, there is a good chance that you can put it in as an 
    "inline TeX" command.  

(c) If not even inline TeX works, you will have to edit the TeX file itself.  
    Some free advice which you need not take: if your system has 'diff' and 
    'patch' utilities, the following cycle may be useful (at least, it is on 
    my Linux system):
 1. Edit the .mtx file.
 2. Make a .tex file via prepmx and pmx.
 3. Edit the .tex file to put in the advanced features.  This may be PAINFUL.
 4. Make a patch file with diff.
 5. If you need changes in other portions of the score, edit the .mtx
    file and make a .tex file as in steps 1 and 2.
 6. Apply the patch file with patch.  The utility is clever enough to 
    make the changes even if the line numbers have changed.