Re: [Tex-music] AcroReader Handel Meine Seele
>|One more file, that doesnt work with Acrobat6 is: >|Meine Seele from Haendel (Martin Straeten). I tried to compile from source. >|The answer was: >| file not found.> The tfm may be found at CTAN: fonts/psfonts/adobe/agaramon/tfm/padr8r.tfm but you'll also need the corresponding type 1 font (Adobe Garamond). Bob T. ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] \lastbarno
I believe this counter is not being properly reinitialized in musixtex.tex. I've recently started to use \barnumbers and finding that, in a sequence of pieces, I was getting spurious bar numbers in the first system of the 2nd, 3rd, etc. of the pieces. The problem was fixed by adding \lastbarno0 before those \startpiece commands. I'll leave it to the musixtex experts to figure out where the appropriate reinitialization should go, but I notice that the first thing \startextract does is to set \lastbarno to zero and there doesn't seem to be a comparable command in the code for \startpiece. Bob T. ___ TeX-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Re: \lastbarno
>|Could you provide the source giving the problem you describe, since I
>|can't reproduce it.
\input musixtex.tex
\barnumbers\def\freqbarno{5}
\startpiece\addspace\afterruleskip%
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\Endpiece%
\startpiece\addspace\afterruleskip%
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\bar
\notes\ql j\enotes
\Endpiece%
\end
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] parisitic music archive
>|The other possibility I see is to write to pianofiles.com stating that >|there is a breach of copyright, but I doubt that something could come >|from this line of action :-( I'm not sure why you think so. Copyright violation can draw substantial penalties. Availability on a web site does *not* mean public domain. ___ TeX-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] Barnumbers
>|do you know what is the reason to put the barnumbers into a box as >|default for MusixTeX and PMX although this seems to be quite unusual? Probably just an idiosyncracy of Daniel Taupin and/or Andreas Egler. Bob T. ___ TeX-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] normalsized cautionary accidentals in musixtex
The commands \cna, \cfl, \csh, etc. in musixtex produce parenthesized *small* accidentals. Is it possible to produce parenthesized *normalsized* accidentals? No combination of \bigaccid, \bigna, etc. seems to work for me. The following is one of the definitions in musixtex.tex: [EMAIL PROTECTED] \smallna} Where do the parentheses come from? Bob T. ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] normalsized cautionary accidentals in musixtex
>|From [EMAIL PROTECTED] Mon Aug 8 09:15:55 2005 >|Date: Mon, 8 Aug 2005 15:09:35 +0200 >|From: Rainer Dunker <[EMAIL PROTECTED]> >|To: Typesetting music with TeX >|Subject: Re: [TeX-music] normalsized cautionary accidentals in musixtex >|Content-Type: text/plain; charset=us-ascii >| >|On Thu, Jul 21, 2005 at 02:31:30PM -0400, Bob Tennent wrote: >|> The commands \cna, \cfl, \csh, etc. in musixtex produce parenthesized >|> *small* accidentals. [...] >|> >|> [EMAIL PROTECTED] \smallna} >|> >|> Where do the parentheses come from? >| >|It seems that this question has not yet been answered; so, just for >|the fun to see how MusiXTeX works ... :-) >| >|The following macros are involved in a \cna call, in the order given: >| >|[EMAIL PROTECTED] \smallna} >|[EMAIL PROTECTED] [EMAIL PROTECTED]@Na [EMAIL PROTECTED]@ur [EMAIL >PROTECTED] >|[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@ [EMAIL PROTECTED]@xl } >|[EMAIL PROTECTED]@[EMAIL PROTECTED]@sa\kern\accshift}} >|[EMAIL PROTECTED]@vii=\maxdimen [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL >PROTECTED] >| \else [EMAIL PROTECTED] \fi [EMAIL PROTECTED]@} >|[EMAIL PROTECTED]@iv} >| >|That is: \cna sets [EMAIL PROTECTED] to \maxdimen. This is used just as a >switch >|that is later queried by [EMAIL PROTECTED]; if the switch is set, [EMAIL >PROTECTED] is called >|which in turn typesets character number [EMAIL PROTECTED] from the music >symbol >|font. [EMAIL PROTECTED] has been set to 5 by macro [EMAIL PROTECTED] before, >and the music >|character with that number happens to be just the pair of parentheses. >| >|Best regards, >| >|Rainer >|___ >|TeX-music mailing list >|TeX-music@icking-music-archive.org >|http://icking-music-archive.org/mailman/listinfo/tex-music >| ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Re: normalsized cautionary accidentals in musixtex
>|> The commands \cna, \cfl, \csh, etc. in musixtex produce parenthesized >|> *small* accidentals. [...] >|> >|> [EMAIL PROTECTED] \smallna} >|> >|> Where do the parentheses come from? >| >|It seems that this question has not yet been answered; so, just for >|the fun to see how MusiXTeX works ... :-) >| >|The following macros are involved in a \cna call, in the order given: >| >|[EMAIL PROTECTED] \smallna} >|[EMAIL PROTECTED] [EMAIL PROTECTED]@Na [EMAIL PROTECTED]@ur [EMAIL >PROTECTED] >|[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@ [EMAIL PROTECTED]@xl } >|[EMAIL PROTECTED]@[EMAIL PROTECTED]@sa\kern\accshift}} >|[EMAIL PROTECTED]@vii=\maxdimen [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL >PROTECTED] >| \else [EMAIL PROTECTED] \fi [EMAIL PROTECTED]@} >|[EMAIL PROTECTED]@iv} >| >|That is: \cna sets [EMAIL PROTECTED] to \maxdimen. This is used just as a >switch >|that is later queried by [EMAIL PROTECTED]; if the switch is set, [EMAIL >PROTECTED] is called >|which in turn typesets character number [EMAIL PROTECTED] from the music >symbol >|font. [EMAIL PROTECTED] has been set to 5 by macro [EMAIL PROTECTED] before, >and the music >|character with that number happens to be just the pair of parentheses. Thanks. And now I see why it's so hard to produce "normalsized" cautionary accidentals: the parentheses used come in pairs in the musix fonts and are either too close together or too far apart for a normalsized accidental. I suppose the "separate" left and right parentheses in character positions 3 and 4 could be used but that would involve significant re-coding. Bob T. ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] Re: normalsized cautionary accidentals in musixtex
>|I had already responded to the original query with a PMX solution. Maybe
>|"significant re-coding" is in the eye of the re-coder:
>|
>|===
>|1 1 4 4 4 4 0 0
>|1 1 20 0
>|
>|t
>|.\
>|c24 \loffset{1.5}{\lpar5}\loffset{1.5}{\rpar5}\ c+s<.4 /
>|===
Thanks, Don. Unfortunately, I don't use PMX. If I extract what I recognize
as being musixtex
\loffset{1.5}{\lpar5}\loffset{1.5}{\rpar5}
I get good parentheses; to put the accidental in the proper place
between them I can use
\loffset{0.4}{\na5}
and add extra space before. It'll do.
Bob T.
>|> >|> The commands \cna, \cfl, \csh, etc. in musixtex produce parenthesized
>|> >|> *small* accidentals. [...]
>|> >|>
>|> >|> [EMAIL PROTECTED] \smallna}
>|> >|>
>|> >|> Where do the parentheses come from?
>|> >|
>|> >|It seems that this question has not yet been answered; so, just for
>|> >|the fun to see how MusiXTeX works ... :-)
>|> >|
>|> >|The following macros are involved in a \cna call, in the order given:
>|> >|
>|> >|[EMAIL PROTECTED] \smallna}
>|> >|[EMAIL PROTECTED] [EMAIL PROTECTED]@Na [EMAIL PROTECTED]@ur [EMAIL
>PROTECTED]
>|> >|[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@ [EMAIL
>PROTECTED]@xl }
>|> >|[EMAIL PROTECTED]@[EMAIL PROTECTED]@sa\kern\accshift}}
>|> >|[EMAIL PROTECTED]@vii=\maxdimen [EMAIL PROTECTED] [EMAIL PROTECTED]
>[EMAIL PROTECTED]
>|> >| \else [EMAIL PROTECTED] \fi [EMAIL PROTECTED]@}
>|> >|[EMAIL PROTECTED]@iv}
>|> >|
>|> >|That is: \cna sets [EMAIL PROTECTED] to \maxdimen. This is used just as
>a switch
>|> >|that is later queried by [EMAIL PROTECTED]; if the switch is set,
>[EMAIL PROTECTED] is called
>|> >|which in turn typesets character number [EMAIL PROTECTED] from the
>music symbol
>|> >|font. [EMAIL PROTECTED] has been set to 5 by macro [EMAIL PROTECTED]
>before, and the music
>|> >|character with that number happens to be just the pair of parentheses.
>|>
>|> Thanks. And now I see why it's so hard to produce "normalsized"
>|> cautionary accidentals: the parentheses used come in pairs in the
>|> musix fonts and are either too close together or too far apart for
>|> a normalsized accidental. I suppose the "separate" left and right
>|> parentheses in character positions 3 and 4 could be used but that would
>|> involve significant re-coding.
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] musixlyr
I've just added lyrics to a piece for the first time using what was apparently available, according to the musixtex documentation. It was quite a chore. I now see there is an add-on package musixlyr available which promises an easier experience. Would it be possible to at least mention the existence of musixlyr in the musixtex documentation? Bob T. ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] musixlyr
>|Did you already consider to use PMX/Mtx? It makes typesetting music >|_much_ easier, especially adding lyrics. Thanks for the suggestion. I'm already very familiar with plain musixtex but if I ever need to add lyrics again, I'll consider PMX/Mtx. Perhaps that should be added to the musixtex documentation as well. Bob T. ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] musixlyr
>|Have a look at the very last musixtex documentation (Foreword p.3): >| >|http://icking-music-archive.org/software/musixtex/musixdoc.pdf Thanks. Actually the note in the Foreword is less important in my opinion than the reference in Section 2.20.7 (Lyrics), which is exactly what I was hoping for. >|The musixlyr documentation is kept separated from the MusiXTeX >|documentation, according the desire of its author Rainer Dunker. That's fine. As long as someone (like myself) who is for the first time trying to add lyrics is referred to musixlyr, the documentation (which is indeed excellent!) is easy enough to find. Bob T. ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-music] I'll never understand TeX fonts.
>|I wanted to test this out in my own MiKTeX system. I did not remember ever >|downloading or installing any ptmr7t.*, so I searched for such files in CTAN >|and came up empty. Undaunted, I just tried inserting "\font\tenrm=ptmr7t" >|into a musixtex file and using the font, and (lo and behold) it worked, all >|the way through to creating a pdf using gsview. According to Acrobat >|document info, the font so created had these characteristics: >| >|Original font: Times-Roman >|Type: Type 1 >|Encoding: Standard >|Used Font: TimesNewRomanPSMT >| >|In contrast, the corresponding characteristics of cmr10 are CMR10, Type 1, >|Built-in, Embedded Subset. >| >|To further confuse myself, I searched my MiKTeX texmf directory for ptmr7t, >|finding >|only ptmr7t.tfm and ptmr7t.vf. In contrast, a search for cmr10.* yielded >|cmr10.afm, cmr10.tfm, cmr10.pfb, and cmr10.mf. >| >|Finally I notice that when running dvips, I get the following on the screen: >|== >|This is dvips(k) 5.94a Copyright 2003 Radical Eye Software >|(www.radicaleye.com) >|' TeX output 2005.12.13:1459' -> JUNK.ps >|<8r.enc>. >|[1] >|== >| >|When the ptmr7t font is not included, the output is the same except that >|"<8r.enc>" is not present. >| >|I think I understand the handling of cmr10 and the roles of all related >|files except for cmr10.afm. I understand that .afm is some sort of alternate >|version of .tfm, but I have no idea when or how it is used instead of .tfm. >|Can someone explain that? >| >|I also have no idea at all what's going on with the ptmr7t font. Can someone >|explain it, explain the roles of ptmr7t.vf, 8r.enc, and how I can get a >|postscript version of this font without having a .pfb file??? Don: LaTeX distributions use free URW clones of the standard Adobe Times/Helvetica/Courier etc. But because every PDF Reader is supposed to have these fonts available, your dvi to ps to pdf converters are *not* embedding them. Instead the Acrobat Reader is using its own Type1 fonts, in this case, TimesNewRoman. ptmr7t is a "virtual" font; if used, it will eventually access the relevant pfb files. Look for files fonts\type1\urw\times\*.pfb. 8r.enc is an encoding transformation. Hope this helps. Bob T. ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] tacet
A publisher wants me to add "tacet alto" on the first page of a score.
The first movement is for STB recorders and the alto joins in for the
second movement. My question is: where does such an indication go? It
seems to me the most likely place is below the lowest staff of the first
system. Is that right? And if so, how do I put it there in musixtex
(there is no \downtext{} macro)?
Bob T.
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music
[TeX-music] End of upper beams
>|It seems upper beams miss a length of one pixel when they end: the >|last stem seem to go up to only half the beam thickness: >| >| >|Beam: >|* <--- look here with a magnifying glass >|* >|** >|** >| * >| * >| last stem * >| * Did you intend the following? * * ** ** * * last stem * * The problem could be the positioning of the stem, the length of the beam, or that the last stem isn't long enough. I'm noticing the same problem with *lower* beams in some old scores. Look for example at the three beams in the instrument3 part of measure 5 of http://icking-music-archive.org/scores/bach/bwv988/quod.pdf The problem with lower beams seems less severe when I re-process the source now; presumably some change in musixtex since 2001 accounts for this, which may provide a clue as to the cause. Bob T. ___ TeX-music mailing list TeX-music@icking-music-archive.org http://icking-music-archive.org/mailman/listinfo/tex-music
Re: [TeX-Music] Dotted rests
>|What am I supposed to do to get dotted rests of quarter notes (\qp)?
\def\qpp{\pt 5\qp}
\def\dsp{\pt 5\ds}
\def\qsp{\pt 5\qs}
\def\hpp{\pt 5\hpause}
Bob T.
___
TeX-music mailing list
[EMAIL PROTECTED]
http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] Dotted rests
>|> Hello. I am still a beginner with MusiXTeX and I am needing some >|help. What >|> am I supposed to do to get dotted rests of quarter notes (\qp)? The >|command >|> \pt does not work with rests and there is no command \qpp or something >|like >|> that in MusiXTeX documentation. >|> >|If I am not mistaken, musixmad.tex, the addition to musixtex, >|has these macros built-in; i.e. >| \input musixmad >|, and you can simply use \qpp for a dotted 4th rest. grepping for \def\qpp (actually "\\def\\qpp") in musixtex-T112/tex/* turns up nothing, so I believe you are mistaken. Bob T. ___ TeX-music mailing list [EMAIL PROTECTED] http://mailman.daimi.au.dk/mailman/listinfo/tex-music
[TeX-Music] correcting J.S. Bach bug
Hi all. It's not every day one gets a chance to correct a mistake by JSB! I sent a colleague a link to Bach's "Explication": http://icking-music-archive.org/scores/bach/explica.pdf He pointed out that the last two examples don't "add up". This is not the fault of Jean-Pierre Coulon, who faithfully typeset Bach's notes: http://www.jsbach.net/images/ornaments.jpg But now the question for you is: what did Bach *intend* to write? My colleague thought the first note should be shortened, but my opinion is that that note is an appogiatura and should take half the apparent note value; rather, the four "trill" notes should be 64ths instead of 32nds. What say all of you? Bob T. ___ TeX-music mailing list [EMAIL PROTECTED] http://mailman.daimi.au.dk/mailman/listinfo/tex-music
Re: [TeX-Music] \setcounter{page}
>|\setcounter is indeed a latex command; the corresponding plain tex usage
>|would look like
>|
>| \count0=99\relax
>|
>|(99 being the page number, of course. i wouldn't claim that 99 is the
>|only such number possible...)
In case the OP is confused: the analogue of \setcounter{\page}{2} is
\pageno=2\relax
Bob T.
___
[EMAIL PROTECTED] mailing list
http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
Re: [TeX-Music] Making MIDI better
>|Perhaps someone with some programming experience would like to >|consider writing a stand-alone MIDI file generator from scratch, >|starting just with a valid PMX input file. It would surely be more efficient to write a module to allow pmx (or musixtex) to be imported into a program like rosegarden: http://www.rosegardenmusic.com/ Bob T. ___ [EMAIL PROTECTED] mailing list http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
[TeX-Music] figured-bass font
Hi all. Is anyone aware of a freely-available good-quality font suitable for basso-continuo figures, specifically the "stroked" digits that abbreviate 6+, 4+, etc.? Bob T. ___ 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] figured-bass font
>|Does "stroked" mean this? I personally find 4+ etc. more attractive than that but what I meant was the conventional "ligatures" for such combinations. I'm sure you know what I mean and if not, check out the table in http://www.robertkelleyphd.com/FiguredBass.pdf Bob ___ 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] figured-bass font
>|> I personally find 4+ etc. more attractive than that but what I meant was
>|> the conventional "ligatures" for such combinations. I'm sure you know
>|> what I mean and if not, check out the table in
>|
>|Then I would still use a combination of \zcharnote's. If necessary a
>|\zcharnote can be raised at a height other than normal like this:
>|
>|\raise.2\Interligne\hbox{\roffset{.3}{\zcharnote g{your_stuff}}}
>|
>|BTW \BIGtype, \smalltype etc. don't affect the size of $\backslash$.
>|The example in my previous mail is not aware of this :-)
This is always the problem with ad hoc composites. If no existing
solution is suggested, I'll have a go at using fontforge or metafont to
do it right.
Bob T.
___
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] PMX problems
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 at the end of the second pass, or a segfault in the second pass. The only successes on those two files came from using f2c followed by gcc34. I've tried various versions of pmx, from 2.5.0 to 2.5.21. I converted text files using recode or dos2unix. I'm not sufficiently knowledgeable in either PMX or Fortran (and not sufficiently interested) to analyze this any further, but perhaps some of you may wish to report whether you can confirm these observations. Bob T. P.S. The link to the version 2.504 Linux tarball at http://icking-music-archive.org/software/indexmt6.html#pmx is dead, but 2.5.10 and 2.5.15 are available at http://http.us.debian.org/debian/pool/main/p/pmx/ ___ 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 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. It doesn't solve *these* problems. I used -a when unzipping fairy_queen.zip and pmx2521.zip and had the issues described above when pmxab was compiled with f77 or f95 but success when using f2c and gcc34. One of the issues was a segfault, which shouldn't happen no matter how bad the input. Bob T. ___ 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 problems
>|I'm equally mystified by line-ending character issues, but >|1. I confirmed that score.pmx compiles OK under WinXP/MiKTeX with >|the latest >|PMX, with no errors or warnings, But how did you produce your pmxab.exe binary? It's beginning to look like the problem arises from an inconsistency between your Fortran compiler and the Gnu Fortran compiler(s). Perhaps "undefined" behaviour resolved one way by one compiler and another way by the others. Again, let me emphasize that stable software shouldn't segfault, no matter how bad the input is. Bob T. P.S. If I run f77 on pmaxab.for with -Wall -Wextra -pedantic-errors options, I get a long list of warnings like this: Warning: Mixed CHARACTER and non-CHARACTER types via COMMON/EQUIVALENCE -- for example, `ipbuf' and `bufq' Warning: Mixed CHARACTER and non-CHARACTER types via COMMON/EQUIVALENCE -- for example, `mult' and `sepsymq' ... Is that of any help? >|>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 >|> >|>at the end of the second pass, or a segfault in the second pass. >|> >|>The only successes on those two files came from using f2c followed by >|>gcc34. >|> >|>I've tried various versions of pmx, from 2.5.0 to 2.5.21. I converted >|>text files using recode or dos2unix. >|> >|>I'm not sufficiently knowledgeable in either PMX or Fortran (and not >|>sufficiently interested) to analyze this any further, but perhaps some >|>of you may wish to report whether you can confirm these observations. ___ 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 problems
>|With some pretty laborious debugging, I've identified the source of the >|error Thanks Don. I wish I could have helped more but it's been 40 years since I've done any Fortran development and I'm a beginner at PMX. You might however want to experiment with the "warning" options in gfortran. Using an uninitialized variable should be detectable. The main problem is to find the significant warnings among all the insignificant ones. Perhaps Visual Fortran has static-analysis options? Bob T. ___ 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
>|Don't you think it would be interesting to have an IDE for PMX? Any existing IDE for music could export PMX. Some do: http://noteedit.berlios.de/ http://vsr.informatik.tu-chemnitz.de/staff/jan/nted/nted.xhtml http://developer.berlios.de/projects/canorus Bob T. ___ 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] TeXWorks
>|I decided to try using TeXWorks. It was pretty easy to get it to >|produce a pdf from my LaTeX file (evidently using pdfLaTeX), but it >|did not >|leave behind a .dvi or .ps. As MusiXTeXers know, pdfTeX cannot handle >|postscript slurs in music documents; for music documents with postscript >|slurs you pretty much have to run dvips, then generate a pdf from the >|postscript however you want. Does anyone know if TeXWorks can EASILY >|be made >|to do this? I've built Version 0.1 (r425). I didn't change the default configuration. It's easy enough to add LaTeX to the typesetting menu: Edit -> Preferences -> Typesetting -> Processing Tools Presumably dvips and ps2pdf can be added too, but I didn't try. AFAIK, there's no notion of a sequence of typesetting steps, so one would have to select each of these in turn. The program is definitely PDF-centric. Bob T. ___ 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] Converting images to MIDI
>|I saw that NoteEdit imports MIDI and exports PMX, MusiXTeX etc. Does >|anybody know a good image to MIDI converter? This would be the step before >|NoteEdit. Do you mean score images? The big proprietary score editors like Finale have score-scanning addons. Very expensive but work quite well. I was astonished once how quickly a publisher was able to convert from the musixtex PDF I'd sent him to their "internal" format; of course they'd used a scanner. Bob T. ___ 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] beams
Why are the long beams overshooting the last stem in the following
sequences of notes inégales?
\Notesp\ibl2g1\qb2{.h}\en
\notes\tbbl2\qb2j\en
\Notesp\qb2{.i}\en
\notes\tbbl2\qb2k\en
\Notesp\qb2{.j}\en
\notes\tbbl2\tbl2\qb2k\en
\Notes\ibu0h1\qb0{.g}\roff{\tbbu0\qb0h}\en
\Notes\qb0{.^g}\roff{\tbbu0\qb0i}\en
\Notes\qb0{.h}\roff{\tbbu0\tbu0\qb0i}\en
I used both upper and lower beams and both explicit spacing
(Notesp/notes) and shifts (roff) to demonstrate that the same issue
arises with all variants.
Bob T.
___
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] beams
>|Why are the long beams overshooting the last stem in the following
>|sequences of notes inégales?
>|
>|\Notesp\ibl2g1\qb2{.h}\en
>|\notes\tbbl2\qb2j\en
>|\Notesp\qb2{.i}\en
>|\notes\tbbl2\qb2k\en
>|\Notesp\qb2{.j}\en
>|\notes\tbbl2\tbl2\qb2k\en
>|\Notes\ibu0h1\qb0{.g}\roff{\tbbu0\qb0h}\en
>|\Notes\qb0{.^g}\roff{\tbbu0\qb0i}\en
>|\Notes\qb0{.h}\roff{\tbbu0\tbu0\qb0i}\en
>|
>|I used both upper and lower beams and both explicit spacing
>|(Notesp/notes) and shifts (roff) to demonstrate that the same issue
>|arises with all variants.
This seems to be an xdvi issue! There is no overshoot when the dvi is converted
to Postscript or pdf, nor when the dvi is viewed in yap.
Bob T.
___
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] beams
>| >|Why are the long beams overshooting the last stem in the following
>| >|sequences of notes inégales?
>| >|
>| >|\Notesp\ibl2g1\qb2{.h}\en
>| >|\notes\tbbl2\qb2j\en
>| >|\Notesp\qb2{.i}\en
>| >|\notes\tbbl2\qb2k\en
>| >|\Notesp\qb2{.j}\en
>| >|\notes\tbbl2\tbl2\qb2k\en
>| >|\Notes\ibu0h1\qb0{.g}\roff{\tbbu0\qb0h}\en
>| >|\Notes\qb0{.^g}\roff{\tbbu0\qb0i}\en
>| >|\Notes\qb0{.h}\roff{\tbbu0\tbu0\qb0i}\en
>| >|
>| >|I used both upper and lower beams and both explicit spacing
>| >|(Notesp/notes) and shifts (roff) to demonstrate that the same issue
>| >|arises with all variants.
>|
>|This seems to be an xdvi issue.
Or, more specifically, a t1lib issue. The overshoots disappear if the
-not1lib option of xdvi is used.
Bob T.
___
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] beams
>|Why are the long beams overshooting the last stem in the following
>|sequences of notes inégales?
>|
>|\Notesp\ibl2g1\qb2{.h}\en
>|\notes\tbbl2\qb2j\en
>|\Notesp\qb2{.i}\en
>|\notes\tbbl2\qb2k\en
>|\Notesp\qb2{.j}\en
>|\notes\tbbl2\tbl2\qb2k\en
>|\Notes\ibu0h1\qb0{.g}\roff{\tbbu0\qb0h}\en
>|\Notes\qb0{.^g}\roff{\tbbu0\qb0i}\en
>|\Notes\qb0{.h}\roff{\tbbu0\tbu0\qb0i}\en
For the record, this was caused by two bugs in xdvi; a fix from Paul
Vojta can be found at
https://sourceforge.net/tracker/?func=detail&atid=377580&aid=2914532&group_id=23164
Bob T.
___
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] scope of cautionary accidentals
Why are the accidentals on the 2nd and 4th notes of the following
"cautionary"?
\input musixtex
\smallaccid
\instrumentnumber1
\startpiece\addspace\afterruleskip%
\Notes\ibu2i0\cna i\qb2i\fl i\qb2{ii}\tbu2\fl h\qb2h\en
\endpiece
\end
Bob T.
___
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] scope of cautionary accidentals
>|>Why are the accidentals on the 2nd and 4th notes of the following
>|>"cautionary"?
>|>
>|>\input musixtex
>|>\smallaccid
>|>\instrumentnumber1
>|>\startpiece\addspace\afterruleskip%
>|>\Notes\ibu2i0\cna i\qb2i\fl i\qb2{ii}\tbu2\fl h\qb2h\en
>|>\endpiece
>|>\end
>|
>|Seriously, without any context it is impossible to answer or
>|speculate. For
>|example, if there had been a flat in the key signature, and if the
>|last note
>|in the previous bar had been a b-natural, and if it were a baroque piece,
>|then according to most interpretations of baroque conventions, the
>|first two
>|b's in the example should both be naturals, but not so according to modern
>|convention. Or, if there were no b-flat in the key signature, and if
>|the 99
>|bars leading up to this one had been in a tonality that did have a b-flat,
>|then a cautionary natural might be warranted. It's hard to think of any
>|circumstances where the a-flat should be cautionary, whether or not
>|there's
>|an a-flat in the key signature.
>|
>|There's also some confusion between the notation of cautionary and
>|editorial
>|accidentals. (A cautionary one has no real effect relative to the
>|convention
>|in place; an editorial accidental proposes a deviation from the convention
>|in effect, to correct an obvious or perceived error in the source). Since
>|they have completely different meanings, there should be consistently
>|different notations for them. In my published editions I ALWAYS put
>|cautionary accidentals in the staff, with parentheses, and editorial ones
>|above it, without parentheses, and usually explain that in a preface. But
>|Gardner Read says "On occasion the accidental-as-reminder [cautionary
>|accidental] is placed not before but over the note in question, with or
>|without parentheses."
Don: I think you've mis-understood my question. There's no reason
for those parentheses to be inserted according to the coding. And if
\smallaccid is removed, they are *not* inserted. This is a musixtex
*bug* and I was asking those who know the TeX coding better than I
do where the bug is (with the implicit suggestion that it should be
fixed).
The context of the music is as follows: it's a Purcell sonata in C but
he's taking us through a series of modulations on his way back to C. The
first note is definitely chromatic *in context* and that's why I thought
a cautionary accidental would be appropriate (though perhaps not really
necessary because of the following flat); but the two other accidentals
should *not* be cautionary and were not coded as such.
Bob T.
___
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] scope of cautionary accidentals
>|here is a quick fix:
>|
>|code {\cna i} instead of simply \cna i
>|
>|In short, add the braces.
Thanks Olivier. I had actually tried {\cna i\qb2i} but that killed the beam.
Bob T.
___
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] scope of cautionary accidentals
>|Cautionary accidentals work by setting \...@vii to \maxdimen (cf. \...@sa).
>The
>|final operation in \...@sa is to reset \...@vii to zero.
>|
>|*But* \...@sa when executed within \w...@sa inside an \llap - i.e. within a
>|group. So the assignment is lost at the end of the group. This has been
>|probably been missed up to now because \notes..\en is a group and flags
>|would therefore reset within each musixtex group making this a rarer
>|example.
>|
>|Two fixes:
>|
>|a) (very bad idea, but would work) Change the assignment to \...@vii\z@ in
>|\...@sa to be \global
>|b) (better) Change \...@sa, \w...@sa and \w...@ua to be:
>|[the change to \...@sa is simply to remove the \...@vii\z@ from the end - it
>is
>|only used in musixtex.tex]
>|\d...@sa{\ifnum\n@vii=\maxdimen \...@char \musixcha...@v \kern.3...@width
>| \else \musixcha...@v \fi }
>|\def\w...@sa{\pl@base\rais...@i\llap{\@sa\kern\accshift...@vii\z@}
>|\def\w...@ua{\advance\n@i\thr@@
>|\zcha...@i{\kern\qu@rt...@width\@sa...@vii\z@}
>|
>|In the short term, Bob can fix his local sources by inserting:
>|
>|\catco...@=11
>|\def\w...@sa{\pl@base\rais...@i\llap{\@sa\kern\accshift...@vii\z@}
>|\def\w...@ua{\advance\n@i\thr@@
>|\zcha...@i{\kern\qu@rt...@width\@sa...@vii\z@}
>|\catco...@=12
>|
>|immediately after \input musixtex
Thanks. I can confirm that this does work on my example. But I'm
wondering why \smallaccid was essential in producing the incorrect
behaviour.
Bob T.
___
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] flatter Postscript ties
According to T.114, You can control the shape of Type K slurs with variants of the termination command. To make the slur a bit flatter than default use \tfslur0f ... All of the foregoing Type K slur commands have counterparts for ties. Simply replace "slur" with "tie", and for terminations omit the pitch parameter. But there is no \tftie0 command so the second statement is false. So how do I get flatter Postscript ties? Bob T. ___ 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] flatter Postscript ties
>|Too bad no one has responded with a solution. Obviously, a search in >|musixps.tex for tftie comes up empty, so I guess I lied when I wrote >|that in >|musixdoc. I'd bet you could somehow change the curvature with some tex >|commands that alter the parameters, but that's one for the TeXperts. I've looked through musixps.tex and discovered that re-defining \pstiehgt can "flatten" the ties. There doesn't seem to be a way of doing that for an individual tie (except by local re-definition of \pstiehgt) but global re-definition will suffice for me. I've tried e-mailing Stanislav Kneifl (sta...@hiero.cz) but have had no response. Bob T. >|>-Original Message- >|>From: icking-music-archive.org-tex-music-boun...@mailman.nfit.au.dk >|>[mailto:icking-music-archive.org-tex-music-boun...@mailman.nfit.au.dk] >|>On Behalf Of Bob Tennent >|>Sent: Friday, July 16, 2010 6:32 PM >|>To: icking-music-archive.org-tex-music@mailman.nfit.au.dk >|>Subject: [TeX-Music] flatter Postscript ties >|> >|>According to T.114, >|> >|> You can control the shape of Type K slurs with variants of the >|> termination command. To make the slur a bit flatter than default use >|> \tfslur0f >|> >|> ... >|> >|> All of the foregoing Type K slur commands have counterparts for ties. >|> Simply replace "slur" with "tie", and for terminations omit the pitch >|> parameter. >|> >|>But there is no \tftie0 command so the second statement is false. So how >|>do I get flatter Postscript ties? ___ 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] flatter Postscript ties
>|I am afraid you can't. I did not research too much and it's a long time
>|since I wrote the code, but I fear that the slur parameters are
>|hardcoded in the line-break routine and are not affected by the
>|\psslurght parameter. However, you can try to break the slur manually -
>|just insert \tfslur after the last note on the staff (of course you have
>|to make sure the break really occurs) and then reopen the slur on the
>|beginning of the next bar.
OK, thanks. I'm Ccing to tex-music for the record and because this
should be added to the documentation.
Best,
Bpb T.
>|Bob Tennent wrote:
>|>
>|> Another issue: I've done
>|>
>|> \def\psslurhgt{0.6}
>|>
>|> which gives me flatter slurs by default, except for *broken* slurs,
>|> which are not flatter. How do I adjust the central height of broken
>|> slurs?
___
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] CTAN
Hi all. I was asked by Don Simons to re-organize MusiXTeX-related files at CTAN, so that users and TeX distributions such as TeXLive and MikTeX will be able to easily find and install the most recent stable versions. Please check out the packages for musixtex (including musixlyr, psslurs and psfonts), pmx and mtx now at CTAN. Peter Breitenlohner, a TeXLive developer, has suggested a number of small improvements to musixflx.c, along the following lines: + allow \ as a directory separator in file names on DOS and Windows + allow file names up to 512 characters + use ANSI C function declarations consistently + initialize lastbar + make indentation more consistent Some of these have already been in use in teTeX and TeXLive distributions. I've prepared a musixflx-0.83.2 tarball that incorporates these improvements. Ross Mitchell has agreed that this can be distributed. I intend to replace the musixflx-0.83.tar.gz file in the CTAN distribution of musixtex by this new version but for now you can find it at ftp://linus.cs.queensu.ca Please report any problems to me. Also, for CTAN I need at least Windows and MAC OS-X binaries. If you can compile the new version of musixflx.c and test the binary on these platforms, I'd be grateful for your help. Thanks. Bob Tennent ___ 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] musixflx, PMX for Mac OS X
>|I would like to provide a zip file for musixflx, because the current >|package is musixflx.pkg.sit, while StuffIt Expander isn't a standard >|anymore and boring to download. Who should I send it to? Jill-Jênn: Please try the musixflx binary at CTAN: http://mirror.ctan.org/macros/musixtex/OSX/musixflx >|The current binary for pmxab is for PowerPC, Try this one: http://mirror.ctan.org/support/pmx/OSX/pmxab Bob Tennent --- 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, PMX for Mac OS X
Hi again Jill-Jênn. >|The current binary for pmxab (at WIMA) is for PowerPC, and at CTAN too apparently. >|I wanted to recompile the Fortran sources to get an Intel >|binary but I got the following errors: >|[...@pixar:~/pmx2521]$ gfortran pmx2521.f -o pmxab >|gfortran: error trying to exec 'as': execvp: No such file or directory >|[...@pixar:~/pmx2521]$ gfortran pmx2521.for -o pmxab >|pmx2521.for:685.72: >| >|call getarg(1,jobname,idum) ! May need to replace this w/ next l >|1 >|Error: Too many arguments in call to 'getarg' at (1) >|pmx2521.for:698.72: >| >| call getarg(2,jobname,idum) ! May need to replace this w/ next >|1 >|Error: Too many arguments in call to 'getarg' at (1) >| >|What should I do? Thanks in advance. Look for call getarg(1,jobname,idum) ! May need to replace this w/ next line c call getarg(1,jobname) and move the c (in two places). Please send me the binaries and I'll install them at CTAN. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] The Future of MusiXTeX 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. That may have been the case when you asked but it isn't now: Python is everywhere. >|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? No. Is Don willing to re-write PMX in Lua or anything else? I doubt it and as PMX is still being developed, his cooperation is essential. As for choosing Lua, I have my doubts. It sounds like a simple scripting language with bindings to TeX. Could not such bindings be written for Python? The TeX community seems again to be doing something completely idiosyncratic. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] PostScript hairpins i.e. \icresc{n} \tcresc{n}: thickness
>|How can I make these hairpins as thick as the font-based hairpins, i.e. >|about as thick as a staff line? Look at the crescendos section of psslurs.pro: 1 AR ceiling setlinewidth % line thickness: this results 1 setlinecap % to exactly 2 pixels in 300 dpi Change the 1s to 2s (and, to be consistent, adjust the comment). Fractional values (1.5, say) don't seem to work. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] PostScript hairpins i.e. \icresc{n} \tcresc{n}: thickness
>|> Look at the crescendos section of psslurs.pro: >|> >|>1 AR ceiling setlinewidth % line thickness: this results >| >|If I change this line only I obtain what I want. >| >|>1 setlinecap % to exactly 2 pixels in 300 dpi >| >|Is it useful to change this line too? I'm guessing that the "linecap" is a round cap on the end of the line. Presumably, its size should match the linewidth. Experiment, looking closely at the ends of the lines. >|Can I redefine /DC in my MusiXTeX source instead of hacking into >|psslurs.pro? /DC is a Postscript command, not a TeX command. It may be possible to do it in a \special but that's well outside my competence. Try e-mailing the author: stanislav.kne...@hieronymus.cz Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] jh
Someone who identified him/herself as "jh" made several substantial additions to the musixflx code available at WIMA (to deal with \xbar signature changes and \linegoal). Does anyone on this list claim to be this jh or have any idea who jh is? Ross Mitchell (the original author) doesn't. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] jh
>|> Someone who identified him/herself as "jh" made several substantial >|> additions to the musixflx code available at WIMA (to deal with \xbar >|> signature changes and \linegoal). Does anyone on this list claim to be >|> this jh or have any idea who jh is? Ross Mitchell (the original author) >|> doesn't. >| >|I had a look in the archive of our list. The only result of a 'jh-2' >|search is >|a mail beginning with: >| >|From: "Hunsbergers" >|To: "MusiXTex Mailing List" >|Subject: [Long] How to Compile Musixflx using FREE Turbo C >|Date: Fri, 24 Mar 2000 18:06:52 -0500 >| >|At the bottom of the mail is the signature Joel Hunsberger >|jhunsber...@i2k.com Thanks. >|Do you want me tu cut-paste this mail.? I have reached him at that address. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] Dotted tie makes everithing dotted!
>|My PostScript file is OK. If I type ps2dpf -sPAPERSIZE#a4 corinand.ps >|corinand.pdf then the pdf is OK. >| >|If I type ps2dpf -sPAPERSIZE#a4 -r300 corinand.ps corinand.pdf then the >|pdf has the flaw I am talking about. >| >|Should I drop this -r300 option? I don't recall the details but I think this is a PDF rendering bug in some library on Linux. I reported this as a bug in one of the PDF viewers a few years ago and was told it was a bug at a lower level in the stack. Try other PDF viewers such as xpdf and acroread. On my system (Centos 5.5), there doesn't seem to be problem using xpdf. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] universal OS-X binaries
If you're a pmx/musixtex user on any variety of Mac, I'd be grateful if you could test the pmxab, scor2prt and musixflx binaries at ftp://linus.cs.queensu.ca/musixtex/ These should be usable on *any* version of OS-X, including Tiger, Leopard and SnowLeopard, PPC and Intel, 32 and 64 bit. Please report any problems to me. Thanks. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] universal OS-X binaries
>|If there's a possibility to get binaries linked in a way that they >|don't get broken at a change of the OS version I'd be interested to >|know how that works. Probably by compiling and linking with some >|special Apple software XCode or so? Who has compiled and linked these >|binaries? >From the Makefile I used: musixflx: musixflx.c gcc-4.0 -arch ppc -arch i386 -mmacosx-version-min=10.3 musixflx.c -lf2c -lm -o musixflx I was advised by a colleague with a lot of experience distributing MAC binaries. Best, Bob >|On Dec 2, 2010, at 5:29 , Bob Tennent wrote: >| >|> If you're a pmx/musixtex user on any variety of Mac, I'd be grateful if >|> you could test the pmxab, scor2prt and musixflx binaries at >|> >|> ftp://linus.cs.queensu.ca/musixtex/ >|> >|> These should be usable on *any* version of OS-X, including Tiger, >|> Leopard and SnowLeopard, PPC and Intel, 32 and 64 bit. >|> >|> Please report any problems to me. >|> >|> Thanks. >|> >|> Bob T. >|> --- >|> TeX-music@tug.org mailing list >|> If you want to unsubscribe or look at the archives, go to >|http://tug.org/mailman/listinfo/tex-music >| >| >|--- >|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] Making PDF files from PS with gsview32 from command line or batch file.
>|Does anyone know how to do it? >| >|I'm using Windows XP, gsview 4.8, ghostscript 8.60, and MiKTeX 2.6. I >|don't believe I can use pdftex because I don't think it handles Type >|K postscript slurs. ps2pdf .ps ps2pdf is a script that uses ghostscript to convert postscript to PDF. gsview uses ghostscript but is primarily for displaying postscript. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] Quarter-Tone-Accidentals
>|If you're patient you can also research macros to imitate the accidentals >|of >|the more modern Sechstelton-Notation image: I would suggest creating a small type1 font similar to the figbas fonts for these kinds of things. The glyphs would be scaleable. The fontforge program is free software that will allow you to edit graphically the programs for glyphs taken from, for example, musix11.pfb. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] PMX: Octave change at first triplet note
>|I tested the new binaries contributedby Bob Tennent via
>|this list on December 2nd 2010.
>|
>|the other "tex command problem" is definitely not solved.
I've tested your pmx file with
:
h297m
w190m
\\setsign2{-2}\
:
as suggested by Olivier on a MAC using the pmxab binary I contributed
to CTAN and WIMA and it produced a valid .tex file with
\setsign2{-2}%
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] New full MusiXTeX distribution now available
>|With lots of effort by Hiroaki Morimoto and Andre van Ryckeghem, we >|now have >|a new, complete distribution of MusiXTeX 1.15 at >| >|http://www.icking-music-archive.org/software/musixtex/musixtex.zip . Don: musixtex.tex announces itself in logs etc. as T.115-beta4 <1 Jan 2011>. Are we still in betas or is this a minor slip? Best, Bob --- 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] MusiXTeX at CTAN
The new version of MusiXTeX (1.15), together with up-to-date documentation, musixflx, Postscript slurs, type 1 fonts, musixlyr, musixcrd, etc. has been at CTAN for about a week. This distribution can be easily installed using an unzipper on any TDS (TeX Directory Structure) compliant TeX system, including MikTeX, TeXLive, teTeX, and MacTeX. >From there, it was picked up by TeXLive and is now available for updating from TeXLive servers. TeXLive is a multi-platform distribution maintained by the TeX Users Group. It can be installed on any of nineteen platforms, including i386-linux, win32, MacOSX, etc. And today I received a message from Christian Schenk (lead developer of MikTeX) that the musixtex at MiKTeX is up-to-date. (I don't see this yet at the mirrors, but likely by tomorrow.) Our success at getting up-to-date versions of MusiXTeX into mainline distributions of TeX is very gratifying. I'm grateful for the assistance and cooperation of (in no particular order) Don Simons, Ross Mitchell, Robin Fairbairns, Takanori Uchiyama, Stanislav Kneifl, Peter Breitenlohner, Karl Berry, Bernd Jantzen, Norbert Preining, Jean-Pierre Coulon, Jill-Jênn Vie, and Joel Hunsberger. Bob Tennent --- 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 in Lua
Last November, Dirk Laurie suggested that we should be porting the M-Tx/PMX/musixtex/musixflx toolchain to LuaTeX. I won't review his arguments here, but I'm pleased to report that Nikhil Helferty, a student here, has successfully converted musixflx.c (version 0.83.3) to musixflx.lua (version 0.83.3.luaN, currently N=1). This is available by anonymous ftp from here: ftp://linus.cs.queensu.ca/musixflx/musixflx.lua It should be functionally identical to musixflx.c (up to round-off error). It's been tested on hundreds of examples but there may be bugs lurking in rarely-exercised parts of the code so please test it on your most complex and unusual scores, and report problems to me (attach problematic .mx1 files). Usage: musixflx.lua is a lua script and so is used essentially as follows: lua musixflx.lua basename This requires a lua interpreter; for example, from here: http://lua-users.org/wiki/LuaBinaries Or you can use texlua, which is included in the basic LuaTeX package in most modern TeX distributions. LuaTeX is a version of TeX that supports use of lua scripting within a TeX document; texlua is just a lua interpreter. If your operating system supports the use of #! in the first line of a script, you can edit the path to your lua interpreter and simply use musixflx.lua basename Or modify the paths in your favorite multi-pass processing script, or set up a symbolic link or shortcut, etc., etc. What's it For? musixflx.lua has no advantage over traditional musixflx except that it should now be possible to merge the conventional three-pass tex-musixflx-tex processing (using a platform-dependent musixflx binary) into a single multi-platform LuaTeX pass. That's the aim, though we're not there yet; it seems prudent to get all the bugs out of musixflx.lua before trying to integrate it into musixtex.tex. Bob Tennent --- 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
>|i had, in fact, vaguely thought of making musixflx into a separate ctan >|package (it's already separate from musixtex in the distributions, >|brought in by their "requirement" directives[*]). >| >|doing that would involve breaking your structure, but i think it would >|add clarity to the distribution, and would also allow mirrored >|distribution of this excellent script. I combined musixflx and musixtex into a single package because the former is *essential* to the proper use of the latter; also there is a version compatibilty issue. Ultimately, the musixflx code should be incorporated into musixtex, so it seems premature to separate them now. Bob --- 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
>|> 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). That's because TeX doesn't do floating-point! One of the reasons (the other being the lack of arrays) that a separate musiflx program was introduced. The differences are in the last digit and since there are no significant numerical calculations involved, I'm guessing the differences arise from differences in the output formatting. >|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). I think that's called moving the goalposts :+) The differences are of no practical significance. What I'm looking for are significant differences, such as the lua script crashing because of a typo. >|Most of the work I do involves a lot of regression tests against >|reference copies of known output so I'm always particularly sensitive >|to statements about rounding "errors" ;o) The script was produced by a line-by-line translation of the C code. It doesn't use different calculational algorithms. >|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. ^^ I'm guessing you meant to write MusiXTeX there. That would simply perpetuate the maintainance problems of requiring platform-dependent executables. I think it would be much better to incorporate the musixflx calculations into musixtex.tex and make LuaTeX a requirement for MusiXTeX. Bob --- 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
>|Possibly, but if two scripts were being maintained then I'd maintain >|that identical output is the more critical thing to have (and, yes, in >|the 16th decimal place - no optimising compiler re-orders floating point >|instructions without being told that unsafe optimisations are allowed >|precisely because the results can differ, the same algorithm over the >|same precision of floating point representation should produce *exactly* >|the same output regardless of language) David: I'm pleased to report that after replacing Nikhil's own formatting function (which truncated decimal parts rather than rounding!) by string.format(%.., ...) I'm getting exact matches with musixflx.c output. It seems Nikhil didn't find the string.format( ) function in the manual :+) Bob --- 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 from musixtex.tex
The version of musixflx.lua now at
ftp://linus.cs.queensu.ca/musixflx/musixflx.lua
has been adapted to be callable from musixtex.tex. To try it out, copy
musixflx.lua and musixtex.tex into a working directory and re-define
\endmuflex (line number 4823 in version 1.15) in musixtex.tex as
follows:
\def\endmuflex{%
\immediate\closeout\outmux%
\ifx\undefined\directlua \else \directlua {
name_of_file = tex.jobname
musixflx = kpse.find_file("musixflx.lua")
dofile(musixflx)}%
\fi%
}%
Note that there must be another closing } immediately after to close the
definition of \pass@I (starts on line 4748).
Then you can process a file basename.tex (containing a call to
\endmuflex just before the \end or \bye) as follows:
luatex --output-format=dvi basename
The --output-format=dvi option is only necessary if you're using
Postscript slurs; the default is to output pdf.
You should see that basename.mx1 is produced as usual but then
musixflx.lua is called and it will produce basename.mx2; most of the
usual musixflx output messages have been suppressed (except in debug
mode). A second call to luatex will yield a usable dvi file.
If you use a standard tex or don't have \endmuflex in your score file,
musixflx.lua won't be called and you'll have to run a separate musixflx
as usual. The newest musixflx.lua isn't really usable for this purpose
unless you assign the name_of_file variable youself.
Note that luatex is still beta and I've found that it fails to process
some examples; this has nothing to do with calling musixflx *after*
conventional processing and such issues should be reported to the luatex
developers, not to me.
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] musixflx in Lua
>|> I'm getting exact matches with musixflx.c output.
>|
>|Marvellous - and as per the subsequent emails, it looks like longer-term
>|we'll be heading towards retiring musixflx.c completely.
I have a question to musixtex-ers about how to do this. It's possible
to add a few lines to musixtex.tex so that *if* processed by luatex
*and* musixflx.lua is accessible, the latter will be called directly
by luatex. Check out
http://icking-music-archive.org/software/musixtex/musixflx-lua.zip
if you want to try this yourself. It's a nice party trick but I've
come to the realization that this approach is mistaken.
Firstly, there are disadvantages to requiring luatex. PDF output is
the default and so an ugly option is needed to force DVI output when
Postscript slurs are used. Also UTF-8 input and OTF fonts are expected,
which will be problematical unless the traditional representations
like \'{e} are used for accents.
Secondly, although it's likely that musixflx.lua can re-invove luatex,
and musixtex.tex can be further extended to call dvips and then ps2pdf
after the second pass, this approach seems clumsy and inflexible.
I now think a better approach is to use a lua wrapper script to
successively call etex, musixflx[.lua], etex, dvips and ps2pdf. I'm sure
most of you use a similar such script now: a bat script in Windows or
a shell script on other platforms. A platform-independent *lua* script
could replace these. Pmx and M-Tx packages could provide extended
versions to incorporate pre-processing.
Is this a good idea?
Bob Tennent
---
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
>|I would like to use curlybrackets (input curly) in my score but I always >|get a bracket which >|is too large independent of the musicsize or number of staves in a system. curly.tex was submitted by Mthimkhulu Molekwa . Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] dvipdfm/musix.map
This file, which dates from August 2001, is in the latest MUSIXTEXdistribution. It is apparently useless: in most distributions dvipdfm never used such files and in any case dvipdfm has effectively been replaced by dvipdfmx which uses pdftex.map. Having more than one musix.map file is problematic. Is there any reason why it can't be removed? Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] psslurs
I recently asked whether dvipdfm/musix.map could be removed. As part of the resulting discussion (off-line), Don and Reinhard Kotucha had the following exchange (forwarded with their permission): >| > I personally have a hard time getting very worked up >| > about any of this. I don't ever use either dvipdfm or dvipdfmx >| > myself. Not only do I have no problem at all with first making a >| > .ps, then a .pdf if needed, but my understanding is that neither >| > dvipdfm nor dvipdfmx processes postscript slurs. If that is the >| > case, it astounds me that any musixtex user would ever use them, >| > since the bitmapped slurs have various drawbacks and limitations >| > (summarized and illustrated in musixdoc) that are all overcome by >| > Type K postscript slurs. >| >|Well, the file psslurs.pro can indeed be used with dvips only. >|However, another, more versatile way to create slurs on-the-fly is to >|use LuaTeX's built-in Lua engine in order to calculate the shapes of >|the slurs, and the pgf package in order to insert graphic elements >|into the output file. This would work with plain TeX, LaTeX, and >|ConTeXt, and could produce PostScript and PDF, and with tex4ht even >|SVG. The Lua code would be much easier to maintain than the PostScript >|code in psslurs.pro. I think Reinhard's suggestion is well worth exploring. In another domain, I re-wrote a pstricks-based package to an equivalent one based on pgf so that users would not have to depend on dvips/ps2pdf processing, which is increasingly rare in the larger TeX world. Bob T. P.S. BTW, Don's reference to "bitmapped slurs" is misleading. He meant *font*-based slurs, independent of whether the fonts are bit-mapped or type 1. "Postscript slurs" are based on Postscript curves, not type 1 fonts. --- 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)
>|(Lack of) progress report:
>|
>|1. In a Windows command window, I've succeeded in creating *.tex for
>|all of
>|the *.mtx, using only commands starting with
>|
>|"for %a in (*."
>|
>|In the process I figured out how to pass only the basenames of all
>|*.pmx to
>|musixflx with
>|
>|"for %a in (*.pmx) do musixflx %~na"
>|
>|2. I've succeeded in creating *.ps for all those tex files, again using
>|"for" commands. But evidently my TeX system lacks the control sequence
>|\textit.
>|
>|3. I got the latex compilation started. During that I had to let MiKTeX
>|install a bunch of packages it was missing. Then it even seemed to process
>|some of the inserted tex files after I included \usepackage{etex} as
>|suggested. But it choked on "\input netsoos1.tex". Looking in the makefile
>|it appears that this and various other *.tex are created on the fly by
>|merging various *.mta and *.mtb files.
>|
>|At that point it transitioned from adventure to slog, and I threw in the
>|towel, leaving the keys to this forbidden kingdom to the Unix gurus
>|for the
>|time being.
Don: Why are you doing this? I wouldn't think that Windows users would
have any interest in constructing mtxdoc.pdf from scratch. And if this
is considered important for some reason, a batch file isn't the right
way to do it.
Dirk: Shouldn't you be following your own advice? Re-write the Makefile
in Lua (and only use tools available on every platform)!
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] Compiling mtxdoc in Windows (was RE: Compile error in M-Tx documentation)
>|>... I wouldn't think that Windows users would >|>have any interest in constructing mtxdoc.pdf from scratch. >| >|I've been responsible for creating extensive revisions of musixdoc, >|which is >|a more complex document than mtxdoc, and I did all the work in >|Windows. So I >|have more than a passing interest in learning as much as I can about the >|process. And one thing I've learned is that the process can be simpler and >|the files required much less numerous if you just embed the musical >|examples >|in the document, much less breaking individual examples into more than one >|file each. Don: I wasn't thinking of you as the typical "Windows user". If you just want to learn about how Dirk sets up his compilation, that's fine. But you might want to ask Dirk why he set it up the way he did. >|>And if this is considered important for some reason, a batch file >|>isn't the right way to do it. >| >|I'm puzzled why you would say that, partly because I don't think you >|mean "Why waste the effort on writing a batch script if you're only >|going to do the compilation once or twice". The response by David >|seems to show how to fill in the pieces. The problem with a batch script is that, like a Makefile, it's platform dependent. Instead of trying to emulate the Makefile in Windows, we should be replacing it by a platform-independent script in Lua. (This is similar to what's been done with musixflx: we no longer need to compile separate binaries for Window, Macs, Linux, Solaris, etc. because musixflx.lua will work everywhere.) I don't think every mtx user will want to re-build mtxdoc.pdf for themselves so this isn't high priority. And it's really Dirk's problem, because it's his document. Bob --- 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)
>|make (or derivatives) is the only logical system to use for the build >|system of code-based projects - the difference between make and a >|shell script is that make only rebuilds files which need to be rebuilt >|(so, for example, if you changed mtxdoc.tex, Dirk's Makefile would >|not rebuild all of the examples from the .mta and .mtb files and if >|you changed just one .mta or .mtb file then it would only rebuild the >|examples which depend on that specific file, not all of them). While >|the difference is irrelevant if you're building a project from scratch >|(i.e. for a deployment/installation script), that's very useful when >|you're actually working on it as you don't have to recompile absolutely >|everything each time you want to see a change. But this is hardly a "code-based project". It's documentation. A make -B takes only 2 seconds on my system so the performance benefits of make are not significant. >|The only big (Windows) problem with the Makefile is the use of >|ln which, despite proper underlying support in Windows Vista >|onwards is an awkward command because it requires an elevated >|command prompt to use it. make is trivially easy to install - you >|install http://gnuwin32.sourceforge.net/downlinks/make.php and then >|http://gnuwin32.sourceforge.net/downlinks/coreutils.php as this gives >|you Windows versions of commands like cp (the equivalent of copy) and rm >|(the equivalent of del), etc. 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. Bob --- 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] Make (Was: Compiling mtxdoc in Windows
>|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. But the document in question *is* the main documentation for mtx. Would everybody be happy if there were *both* a Makefile (to demonstrate how to create a LaTeX document containing etc.) *and* a platform-independent script to build the documentation from scratch without using any "foreign" tools? Bob --- 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] TeX Compiling
>| MiKTeX 2.9 with TeXWorks (includes MusiXTeX package ; downloaded in April) Try musixtex file at the command line. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] musixps and extracting separate parts
>|To print the score for each string instrument, I suppress the other
>|instruments by assigning them zero staffs.
If you already have a musixtex score and don't want to start again using
pmx, you can "suppress" instruments as follows:
\instrumentnumber1
\startpiece
\makeatletter%
\def\vnotes#1\elemskip#2|#3\en{\noteskip#1\@l@mskip\@vnotes#4\enotes}%
\makeatother%
Just be careful that you haven't omitted any | or & separators.
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] musixps and extracting separate parts
>|On Sun, 19 Jun 2011, Bob Tennent wrote:
>|
>|> If you already have a musixtex score and don't want to start again using
>|> pmx, you can "suppress" instruments as follows: [...]
>|
>|Could you please provide an example with 3 or 4 instruments and 3 or 4
>|measures?
The original source is in
http://icking-music-archive.org/scores/bach/bwv988/quod.zip
Note that the other parts are indeed suppressed, but the note spacing
has to be corrected in the resulting part score. Also multiple-bar
rests.
Bob
__
\input musixtex.tex
\input musixsty.tex
\def\tr#1{\zcharnote{#1}{\ppff tr}}%
\def\pince#1{\shake{#1}}%
\vsize9.75in
\voffset-0.5in
\hsize7.0in
\hoffset-0.25in
\smallmusicsize
\bigaccid
\advance\parindent by 10pt
\def\writebarno{\llap{\ninebf\the\barno\barnoadd}}%
\def\raisebarno{4\internote}%
\def\shiftbarno{1.5\Interligne}%
\nobarnumbers
\geometricskipscale
\def\omit#1{}%
\def\tql#1#2{\tbl{#1}\qb{#1}{#2}}
\def\tqu#1#2{\tbu{#1}\qb{#1}{#2}}
\def\nbbqu#1#2{\nbbu{#1}\qb{#1}{#2}}
\def\nbbql#1#2{\nbbl{#1}\qb{#1}{#2}}
\def\nqql#1#2{\roffset{0.25}{\tbbl{#1}\tbbl{#1}\qb{#1}{#2}}}
\def\nqqu#1#2{\roffset{0.25}{\tbbu{#1}\tbbu{#1}\qb{#1}{#2}}}
\def\tqql#1#2{\roffset{0.25}{\tbbl{#1}\tbl{#1}\qb{#1}{#2}}}
\def\tqqu#1#2{\roffset{0.25}{\tbbu{#1}\tbu{#1}\qb{#1}{#2}}}
\def\tqqql#1#2{\roffset{0.25}{\tbbbl{#1}\tbl{#1}\qb{#1}{#2}}}
\def\tqqqu#1#2{\roffset{0.25}{\tbbbu{#1}\tbu{#1}\qb{#1}{#2}}}
\instrumentnumber1
%\setclef1\bass\setbassclefsymbol1\bassoct
%\setclef4\treble\settrebleclefsymbol4\trebleoct
\catcodesmusic
\generalsignature{+1}
\generalmeter\meterC
\setname1{A}
%\setname2{T}
%\setname3{A}
%\setname4{S}
%\songtop4
%\songbottom1
\fulltitle{Quodlibet}
\subtitle{Variation 30 of the Goldberg Variations for Clavier}
\title{Quodlibet}
\author{J. S. Bach (1685-1750)}
\shortauthor{J. S. Bach}
\othermention{Arranged for Recorders by R. D. Tennent}
\maketitle
\startbarno=0
\nobarnumbers
\stafftopmarg=4.0\Interligne%
\staffbotmarg=4.0\Interligne%
%\setinterinstrument3{2.5\internote}%
\startpiece\addspace\afterruleskip%
\makeatletter
\def\vnotes#1\elemskip#2\en{\noteskip#1\@l@mskip\@vnotes#4\en}%
\makeatother
\systemnumbers%
\Notes\ds&\cu d&\ds&\ds\en
\bar%1
\Notes\hl N&\ibu1g2\qb1{ghi}\tqu1j&&\hpause\en
\Notes\hl M&\ibl1k{-2}\qb1k&&\en
\notes&\nbbl1\qb1j\tql1i&&\qp\en
\Notes&\ibu1h0\qb1h&&\ds\en
\notes&\nbbu1\qb1g\tqu1h&&\cu d\en
\def\atnextbar{\znotes&&\centerpause&&\en}%
\bar%2
\Notes\hl L&\ibu1i{-2}\qb1i\tqu1h&\ql n&\ibu3g2\qb3{gh}\en
\Notes&\itied1g\qu g&\ql n&\qb3i\tqu3j\en
\Notes\ql{.K}&\ttie1\qu g&\ql o&\ibl3k{-2}\qb3k\en
\notes&&&\nbbl3\qb3j\tql3i\en
\Notes&\ibu1f0\pince{n}\qb1f&\cl o&\cu h\en
\notes\cu J&\nbbu1\qb1e\tqu1f&\ds&\ds\en
\bar%3
\Notes\hu I&\qu g&\ibl2n{-1}\qb2{no}&\ql k\en
\Notes&\ds\cl k&\qb2{n}\tql2{=m}&\ql k\en
\Notes\hu J&\ibu1j{-2}\qb1{ji}&\ibl2j{0}\qb2{lk}&\ql l\en
\Notes&\qb1h\tqu1g&\qb2j\tql2p&\ql l\en
\bar%4
\Notes\hl K&\itied1f\pince{n}\qu f&\ibl2o{-1}\qb2{on}&\ibl3k{-1}\qb3{kl}\en
\notes&\ttie1\ibbu1e{-2}\qb1f\tbbu1\qb1e&\qb2o&\qb3k\en
%\vnotes1.5\elemskip&\nbbbu1\qb1e\tbbu1\qb1f&&\en
\Notes&\itied1d\tqu1d&\tql2m&\tql3j\en
\Notes\qu G&\ttie1\qu d&\ibl2n{-2}\qb2n\tql2m&\ibu3h{-1}\pince{p}\qb3i\tqu3h\en
\Notes\ds&\qp&\ibl2n{-5}\qb2n&\qu g\en
\notes\ibbl0b{-1}\qb0b\tql0a&&\tql2k&\en
\bar%5
\endpiece%
\eject
\end
---
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] musixps and extracting separate parts
>|> >|Could you please provide an example with 3 or 4 instruments and 3 or 4 >|> >|measures? >|> >|> The original source is in >|> >|> http://icking-music-archive.org/scores/bach/bwv988/quod.zip >| >|Sorry, quod.tex compiles nicely, but it provides the score and doesn't >|include >|the \def\vnotes... of your message. How can I "suppress" some instruments? The example was in the rest of the message (after the _... ). Bob --- 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] musixps and extracting separate parts
>|Now I >|obtain the Alto part. How can I switch to another part? For example, to get the S part, change #4 to #5 on the right of the \def\vnotes and adjust the \setname1 and \setclef1 accordingly. Bob --- 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] musixps and extracting separate parts
>|Neat; it works!
>|
>|But what would you change to print one of the other three parts instead?
>|(Yes, I am treating this as a magic incantation of which I understand
>|little, and yes, I do feel like the sorcer's apprentice.)
Answered in a previous post. But here's a brief explanation:
>|> \makeatletter
>|> \def\vnotes#1\elemskip#2\en{\noteskip#1\@l@mskip\@vnotes#4\en}%
>|> \makeatother
makeatletter/makeatother allows one to use @ in a macro definition.
\vnotes is a low-level macro that all the other notes/Notes/NOtes/ etc
macros expand into.
The part up to { is the pattern that will be looked for. Note that it
looks for \en and not \enotes as the closing bracket.
The part within the { } is what that pattern of macro call expands into.
If the part after \noteskip#1\@l@mskip\@vnotes were #2#5, the
re-defined macro would work like the built-in vnotes macro. By using
just #4, only that one instrument is used.
Bob
---
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] fwd: question about musixflx
>|Non sprechen sie Deutsche Neither do I but it looks I need to read it (I recognize musixflx.lua). Can someone please translate? >|- Forwarded message from Mátyás Seress - >| >|Date: Tue, 28 Jun 2011 14:21:47 +0200 >|From: Mátyás Seress >|To: v...@brandt.id.au >|Subject: musixflx >| >|Sehr geehrte Frau Brandt, >| >|ich schreibe an Sie, weil ich einige Probleme mit musixflx, und musixtex >|habe. >|Ich bin ganz neu im Gebrauch von musixtex, und deshalb weiß ich nicht, >|wie ich >|eigentlich musixflx gebrauchen sollte. Nämlich, wenn ich das Notenblatt >|beendige, und den Quelltext mit XeLaTeX übersetzen lasse (ich benutze >|TexWorks, >|heruntergeladen von TexLive), sind die Reihen nicht geordnet - das würde >|musixflx tun, aber das kann ich nicht gebrauchen. >| >|Ich habe alle nötige Files, (musixflx.bat, musixflx.lua) aber ich >|weiß nicht, >|in welches Verzeichnis ich sie platzieren sollte. Zum Beispiel: >|...\texlive\ >|2010\texmf-dist\... oder was. Ich habe die Führer gelesen (.pdf), aber >|das hat >|mir nicht genug geholfen um dieses Problem zu lösen. >|Bitte, wenn Sie mir helfen können, antworten Sie. >| >|Wenn Sie möchten, kann ich das .tex File beilegen. >| >|Mit freundlichen Grüßen, >| >|Mátyás Seress (aus Ungarn) >| >|PS.: ich habe Ihre E-Mailadresse von >| >|http://www.123people.ca/ext/frm?ti=personensuche%20telefonbuch&search_term= >|bob%20tennent&search_country=CA&st=suche%20nach%20personen&target_url= >|http%3A%2F%2Ficking-music-archive.org%2Femail-addresses.php§ion=bing&wrt_id >|=430 >| >|kennen gelernt. >|[cleardot] >| >|- End forwarded message - --- 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] fwd: question about musixflx
>|bob tennent asked for a translation. i can _read_ this stuff, but it >|comes out as a sort of stream of consciousness in my brain, not easy >|to write down. so i used google translate from the text of the mail: >| >|=== >| >|I am writing to you because I have some problems with musixflx and >|musixtex. I am quite new in the use of musixtex, so I do not know how I >|should actually use musixflx. Namely, if I score sheet had brought, and >|let the code compile with XeLaTeX (I use texworks, downloaded from TeX), >|the rows are not ordered - that would musixflx do, but I can not use. >| >|I have all the necessary files, (musixflx.bat, musixflx.lua) but I do >|not know in which directory should I place them. For example: ... \ >|texlive \ 2010 \ texmf-dist \ ... or what. I have read the guide >|(. Pdf), but that has not enough to help me solve this problem. Please >|if you can help me, please reply. >| >|If you want, I can. Tex file attach. Can anyone translate the following to German: The file musixflx.bat has to be placed in any directory on the executable PATH. The directory in which you are processing the .tex file should do. There are instructions in http://mirror.ctan.org/macros/musixtex/musixtex-install.pdf for adding a folder to the executable PATH in Windows. Then do > musixflx at a command-line after moving to that directory. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] fwd: question about musixflx
>|1.) I copied musixflx.bat, musixflx.lua, musixflx.exe, musixflx.mx1 and >|musixflx.mx4 into the directory, where the .tex file is, just to make >|sure, >|that every needed file is at hand for LaTeX. Mátyás: Please remove musixflx.mx1 and musixflx.mx4; I don't know what they are but they're not what you want. You shouldn't need both musixflx.exe and musixflx.lua. The first is a Windows binary compiled from a C program; the second is an architecture-independent Lua script. Either should work. musixflx.bat is a script that calls musixflx.lua using texlua. >|2.) In Total Commander I typed into the command line: musixflx >|watzullenwe. >|Here watzullenwe is the basename of the .tex file. That should have produced watzullenwe.mx2, one way or the other. Did you have watzullenwe.mx1 initially? >|3.) Now, I opened watzullenwe.tex in TexWorks, and compiled it with >|XeLaTeX >|(is it the last step of the three-pass-system?). And then I got this >|message: I very much that XeLaTeX will work. If watzullenwe.tex is a LaTeX file, use LaTeX; otherwise use just TeX or eTeX. If you have musixtex.lua and musixtex.bat scripts installed, you should be able to just do > musixtex watzullenwe and everything will be done for you. And you can configure TeXWorks to use musixtex.bat as a TeX processor. Please consult the latest version of http://mirror.ctan.org/macros/musixtex/musixtex-install.pdf Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX file locations in Windows
>|The basic question here is how to avoid reinstalling MusiXTeX if you >|upgrade >|your TeX system. Suppose you are using Windoze and MiKTeX 2.8, with >|TeX root >|path is the default c:\Program Files\MiKTeX 2.8 . If you had followed the >|default MusiXTeX installation procedure given in mxinsuse.pdf which is >|included with musixtex.zip (1.15) in WIMA, your MusiXTeX files would be >|somewhere else. Now to upgrade to MiKTeX 2.9, no matter how you replace >|the >|TeX files, MusiXTeX would be intact---still somewhere else---and at most >|you'd have update some path variables and (new) TeX config files. >| >|On the other hand, suppose you had followed the instructions included with >|the CTAN, TDS-compliant MusiXTeX version. Then as I understand it the >|MusiXTeX files would be intermingled with the TeX files in various >|subfolders below the TeX root at c:\Program Files\MiKTeX 2.8 . No. *Either* one uses MikTeX package management to install MusiXTeX (as recommended) *or* one installs from CTAN in a *separate* local or private texmf tree. >|Now it >|seems >|there are several options, among them (1) Rename the existing root >|to MiKTeX >|2.9; then perform the default MiKTeX 2.9 installation; or (2) Use the new >|default MiKTeX root c:\Program Files\MiKTeX 2.9. Questions: >| >|1. In case (1), will the old MusiXTeX files still be there? >|2. In case (2) is there any better choice than to completely redo >|the entire >|MusiXTeX (TDS-compliant) installation process? >|3. Is there any better way to upgrade MiKTeX (while keeping the same >|MusiXTeX) than either case (1) or case (2)? If one uses MikTeX packagement, one simply installs MusixTeX in the new MikTeX tree. If one installs from CTAN, the existing files are still there. Of course, all this is also true for TeXLive. BTW, to "completely redo the entire MusiXTeX (TDS) installation process" involves little more than unzipping a zip file. Bob --- 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 file locations in Windows
>|>BTW, to "completely redo the entire MusiXTeX (TDS) installation process" >|>involves little more than unzipping a zip file. >| >|Doesn't the process involve locating and manually editing various >|configuration files? Not if you are "re-do"-ing. It's a little more complicated the first time. The details are in Section 2 of http://mirror.ctan.org/macros/musixtex/musixtex-install.pdf On MikTeX or TexLive one does not have to "locate" the one configuration file to which a line must be added. Bob --- 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.zip: 3 versions ?
>|By now I can avail myself of 3 different versions of >|musixtex.zip: >| >| (1) the official WIMA version: >| http://icking-music-archive.org/software/musixtex/musixtex.zip >| , >| >| (2) the Bob Tennent version, recommended in WIMA "for users >| whose installation is compliant with the TDS" with a >| link to "here": >| http://CTAN.org(tex-archive/macros/musixtex/musixtex.zip , >| >| (3) the CTAN version: >| http://CTAN.org(tex-archive/macros/musixtex/musixtex-texmf.zip >| >| As far as I can gather, (1) is what mxinsuse.pdf (DSimons et >| al.) refers to, and (2) is what goes with your installation >| guide. >| >| But what does (3) refer to ? (looks to me that's also >| 'yours' ...) That's the TDS-compliant part; it's now everything except the README, the ChangeLog, the installation doc and the licence. Please at least read the README and if possible musixtex-install.pdf. It wouldn't kill you to actually do an installation somewhere. >| And are the 3 versions -- they are all different from another >| -- compatible/incompatible when used for the various >| installion guides/install scripts ? I must admit that I am a >| bit confused, and I believe that's not entirely due to my >| slow conception ... There are two versions. The CTAN version is derived from the "official" WIMA version but uses an distribution-independent approach to installation. This is what MikTeX and TeXLive use because they understand this approach. The WIMA method is mostly Windows or even MiKTeX-dependent and is far more complicated. >| As I am presently writing the MiKTeX 1.15 Installation part >| of my PMX tutorial and am engulfed in discussions with Don >| about all that, this is not an academic questions, but >| clarity will help many readers.; so your help will be >| appreciated! I'm just working on updating pmx at CTAN (to version 2.6.03, because that seems to be the best compromise between bug-fixes and unstable and/or incomplete features). Unfortunately, TeXLive won't take pmx because the source is in Fortran but perhaps MiKTeX will. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] PMX 2.6.03 in MiKTeX
>|From: Christian Schenk >|To: Bob Tennent >|Subject: Re: PMX (MusiXTeX preprocessor) >| >|On 13.07.2011 13:56, Bob Tennent wrote: >|> Christian: Most MusiXTeX users use PMX. There's a new version at >|> CTAN. Would it be possible for MiKTeX to package it? >| >|thank you. I have added two new packages: pmx (contents of >|pmx-texmf.zip) and miktex-pmx-bin (contains the two binaries). >| >|Both packages will be available with the next update. --- 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] figbas
Don has replaced figbas.zip at WIMA by a "new" version. The only change is in the Fontname information embedded in plrj.pfb. In ignorance of the rules for Type 1 fonts and the fact that Palatino is trademarked, I had used "Palatino". Apart from any legal problems that might arise, the fontconfig application on Unix-like systems will actually use plrj.pfb as a text font! This should have been done last January when I updated at CTAN but I forgot about the file at WIMA. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] prepmx for OS-X
Christian asked me to compile a prepmx binary for OS-X. I've done so on a server that identifies itself as follows: Darwin 10.8.0 Darwin Kernel Version 10.8.0; root:xnu-1504.15.3~1/RELEASE_I386 i386 The binary works on this machine. The file program identifies it as a Mach-O executable i386 Will this work on current OS-X machines? Anyone who wants it can get it from ftp://linus.cs.queensu.ca/prepmx Test by doing prepmx -h Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] mtx-0.60d
Christian asked me to compile a prepmx binary for OS-X. I've done so on a server machine that identifies itself as follows: Darwin chinook.cs.queensu.ca 10.8.0 Darwin Kernel Version 10.8.0 --- 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] No room for new \dimen
>|In the Debian distribution I just run mtx file, and then run pmx file. I >|think pmx runs a a script which does the texing. >|So the question of my using tex or etex does not arise. The question does arise because I'm guessing you are actually using a script that calls pmx and then tex and then musixflx and then tex again. If you have updated to a recent version of musixtex that requires etex instead of tex, it won't work. I don't use Debian but I suspect that if you update musixtex *and* pmx (and, if you're using it, mtx), your problems will disappear. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] No room for new \dimen
>| >|In the Debian distribution I just run mtx file, and then run pmx >| file. I >| >|think pmx runs a a script which does the texing. >| >|So the question of my using tex or etex does not arise. >| >|The question does arise because I'm guessing you are actually using a >|script that calls pmx and then tex and then musixflx and then tex again. >|If you have updated to a recent version of musixtex that requires etex >|instead of tex, it won't work. I don't use Debian but I suspect that >|if you update musixtex *and* pmx (and, if you're using it, mtx), your >|problems will disappear. I just checked the Debian pmx repository and in fact the most recent (February 2004!) package has a script that calls tex. I've sent a note to the Debian maintainer. Until it gets fixed, Debian users of pmx and m-tx should install those packages from CTAN: http://mirror.ctan.org/support/pmx.zip http://mirror.ctan.org/support/mtx.zip or at least replace their pmx and mtx scripts by the scripts available there (or call pmxab, etex, etc. "by hand"). Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] No room for new \dimen
>|Thank you very much, the note was very appreciated! I'm attaching the >|proposed changes to Debian's "pmx" and the respective changes from the >|latest version in Debian in a patch. >| >|Any objections? pdfetex isn't satisfactory if Postscript slurs are used: etex followed by dvips and ps2pdf are essential. >|PS: You proposed using the CTAN versions of mtx and pmx when pulling new >|versions to be released in Debian. Until now, I preferred the canonical >|location at WIMA as the reference source. What do the authors of pmx and >|mtx propose? WIMA is the reference source for musixtex, pmx, mtx etc., but, like Debian, CTAN provides user-friendly scripts to automate the multiple passes. You might want to look at those scripts to avoid issues like tex/etex and etex/pdfetex. TeXLive and MikTeX have found the CTAN distributions more convenient than the WIMA packages because most files are pre-organized in TDS-compliant tree hierarchies. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] Name of M-Tx executable (Was: No room for new \dimen)
>|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. Bob --- 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] No room for new \dimen
>|> pdfetex isn't satisfactory if Postscript slurs are used: etex followed >|> by dvips and ps2pdf are essential. >| >|OK, thanks for the hint. I can remember this issue again, now. :-) >| >|Will just use etex instead of pdfetex or tex in the script. "Just" that won't do. The script announces that it converts pmx to pdf. So either that is changed or processing by dvips and ps2pdf is added (after the *second* etex pass). Are there similar scripts in the musixtex and m-tx packages? Bob --- 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)
>|> 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. Yes, but all of my scripts have options that allow processing to *stop* at dvi or, for mtx and pmx, at tex (and midi) or, for mtx, at pmx. I often stop at dvi because xdvi works well enough on Postscript slurs and works better than any pdf viewer over a network. Bob --- 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] Lily Pond?
>|Can anyone tell me, why I should use musixtex rather than Lily Pond? If you're satisfied with the engraving quality that lilypond produces, then use it. I prefer having more control and so I use musixtex. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
[Tex-music] 1 natural key signature
In one movement of a Boyce trio sonata, there is a key signature of one sharp for one part and no sharps/flats for the others (it's a strict canon); I can typeset that OK. But in the next movement, he uses a key signature with one *natural* on the m line for the relevant part. Is there a way to typeset that in musixtex? The natural has to be placed between the clef and the time signature. Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] 1 natural key signature
Looking again at the original score, I see that the natural appears only
at the *beginning* of the next movement, not all the way through; that
is, it's treated as a *change* of key signature. That should make it
easier: we just need to put a single natural sign between the clef and
the time signature in one place. In fact, perhaps the simplest approach
is to use
\generalsignature{0}%
\zchangecontext%
at the *end* of the canon movement. Does anyone have any experience with
modern music-typesetting conventions in such cases?
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] Alignment of stems with beam and noteheads in MusiXTeX
>|http://www.icking-music-archive.org/scores/rossi/toccata-settima.pdf, >|e.g., >|first group of 16ths in bar 5 bass clef. Looks OK to me. Which PDF viewer are you using? Try another one. For Windows, I recommend Sumatra PDF: http://blog.kowalczyk.info/software/sumatrapdf/free-pdf-reader.html Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] Alignment of stems with beam and noteheads in MusiXTeX
>|Adobe Acrobat Standard 8.3.0 Try 9.4. >|See if this come thru. It's a screen capture from the posted PDF, >|blown up. I can definitely see that. But I don't get anything like that using 9.4 or any other PDF viewer. >|And here's a corresponding blown-up screen capture from the .ps I produced >|with default dvips settings, viewed in gsview32 version 4.8 at >|"resolution" >|166 166 is going to give you pixelation effects. You can see how the beams are now sawtoothing. >|And here's a screen capture of the PDF from Sumatra: >| >|I agree it looks better, but it's still not perfect. All of these views >|suggest that the beams don't extend far enough to the right. I think there are two effects here. The musixtex type 1 fonts are *not* well-hinted. Karl Berry has pointed out to me that t1lint, a program to test validity of type 1 fonts, generates lots of error messages on the musixtex fonts. Apparently the hinting wasn't done right and some PDF viewers may not be using the hinting at all. That might explain the differences between the PDF views. That said, I agree that when a beam uses a steep angle, the join with the last stem isn't quite right. I avoid angles greater than 5 altogether; then the effect isn't really visible till 1600% magnification. >|I think someone did address this in the past, and provided some sort of >|software fix. I vaguely remember something too but not whether there was a fix. >|But even if we can't dredge that up or solve it anew, >|I'm not >|going to stop using either MusiXTeX or Adobe Acrobat. If you must use the Adobe Reader, a recent version might give you better results. Bob >|>From: tex-music-boun...@tug.org [mailto:tex-music-boun...@tug.org] On >|Behalf Of >| >|>Bob Tennent >| >|>Sent: Saturday, November 12, 2011 2:18 PM >| >|>To: Werner Icking Music Archive >| >|>Subject: Re: [Tex-music] Alignment of stems with beam and noteheads in >|MusiXTeX >| >|> >|http://www.icking-music-archive.org/scores/rossi/toccata-settima.pdf, >| >|> >|e.g., >| >|> >|first group of 16ths in bar 5 bass clef. >| >|>Looks OK to me. Which PDF viewer are you using? Try another one. For >| >|>Windows, I recommend Sumatra PDF: >| >|>http://blog.kowalczyk.info/software/sumatrapdf/free-pdf-reader.html >| >|>Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] Mystery musixflx.exe
>|A puzzling thing happened when I tried a clean installation of MiKTeX 2.9 >|and latest MusiXteX (from musixtex.zip) in Windows XT. I used instmus.bat >|with all the defaults. In testing the install, the first pass of etex >|went fine. But just typing "musixflx test" from my work folder, I got a >|message from MiKTeX telling me that musixflx.lua is missing and offering >|to download it from a random repository. ??? Further snooping revealed >|there were two copies of musixflx.exe, one in the MiKTeX bin folder and >|one in my MusiXTeX tools folder. The former must have been higher up in >|the search path; explicitly running the one in my tools folder did not >|cause the error. >| >|I sure don't remember and can't figure out where the copy in the MiKTeX >|bin folder came from, and that's the one that causes the problem. Does >|anyone remember or know what's happening? MiKTeX now provides a complete musixtex stack, including musixflx, which in MiKTeX is a script that calls musixflx.lua. If you don't have musixflx.lua, MiKTeX will download it for you, just like any other missing package. What is the "problem"/"error"? If you don't want to use the MikTeX versions, just un-install them using the MiKTeX package manager. But for years there have been complaints that TeX distributions can't be relied on to support MusiXTeX; I suggest you at least try MiKTeX's musixtex before you do that. That is, try a "clean installation of MiKTeX 2.9" *before* installing the "latest MusiXteX" separately. Bob --- 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] Mystery musixflx.exe
>|Bob, thanks for the explanation. Would it make sense to ask the MikTeX >|people to also include musixflx.lua in the package? I suppose I should >|also consider including it and the modified version of musixflx.exe >|in musixtex.zip (after I verify they don't give me any problems). Does >|anyone have any objections? Don: I just installed MikTeX-2.9 on a new Windows 7 box. I installed the musixtex package using the package manager and ran the update wizard (always do this if there are binaries) and everything worked, including automatic installation of the musixtex-fonts package. I'm not sure why musixflx.lua wasn't found in your installation but it's definitely in the package. The musixflx.exe binary in MiKTeX isn't what I distribute at CTAN. I think that, for security reasons, MiKTeX generates its own binaries which probably won't work on any other system. But you can certainly distribute the bat script at CTAN, which uses a technique suggested by Tomasz Luczak to find and call musixtex.lua. It's in the musixtex-texmf.zip file in scripts/musixtex/Windows Bob >| Bob Tennent wrote: >|> >|A puzzling thing happened when I tried a clean installation of >|MiKTeX 2.9 >|> >|and latest MusiXteX (from musixtex.zip) in Windows XT. I used >|instmus.bat >|> >|with all the defaults. In testing the install, the first pass of etex >|> >|went fine. But just typing "musixflx test" from my work folder, >|I got a >|> >|message from MiKTeX telling me that musixflx.lua is missing and >|offering >|> >|to download it from a random repository. ??? Further snooping >|revealed >|> >|there were two copies of musixflx.exe, one in the MiKTeX bin >|folder and >|> >|one in my MusiXTeX tools folder. The former must have been higher >|up in >|> >|the search path; explicitly running the one in my tools folder >|did not >|> >|cause the error. >|> >| >|> >|I sure don't remember and can't figure out where the copy in >|the MiKTeX >|> >|bin folder came from, and that's the one that causes the >|problem. Does >|> >|anyone remember or know what's happening? >|> >|> MiKTeX now provides a complete musixtex stack, including musixflx, >|> which in MiKTeX is a script that calls musixflx.lua. If you don't have >|> musixflx.lua, MiKTeX will download it for you, just like any other >|> missing package. What is the "problem"/"error"? If you don't want to >|> use the MikTeX versions, just un-install them using the MiKTeX package >|> manager. But for years there have been complaints that TeX distributions >|> can't be relied on to support MusiXTeX; I suggest you at least try >|> MiKTeX's musixtex before you do that. That is, try a "clean installation >|> of MiKTeX 2.9" *before* installing the "latest MusiXteX" separately. >|> >|> Bob >|> --- >|> 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
[Tex-music] independent cello/continuo
I'm typesetting a baroque trio sonata in which there are sections with separate notes/rests specified for the cello and the keyboard in the basso part. Is it the convention that after these lines merge (a note with both up and down stems), subsequent notes are to be played by *both* instruments until the next section with explicit independent notes/rests? Bob T. P.S. I'm surprised that there don't appear to be *non-spacing* variants of \qp, \ds, etc. in MusiXTeX. --- 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
