Re: [Tex-music] MusiXTeX/pmx sources

[Bodo Meissner]

On 20.04.2019 13:38 Rodolfo Medina  wrote:

> The difference is that a source file can be easily converted into MusiXTeX
> format and so edited at pleasure; a PDF final output can't, or it can but with
> much more difficulty.

As Christian Mondrup already wrote it would be better to have the source file *in addition* to a PDF. The PDF not only allows checking the score easily it also keeps the original result in case of later modifications in the typesetting systems.

I don't know if this might happen with PMX or MusiXTeX, but a long time ago I created a vocal music sheet with ABC, and when I tried to modify it about 10 years later the result looked very different. I had to modify the source to get a result similar to the original one.

If this is not yet the case the users should be encouraged to upload the source files as well when they are uploading a PDF.

Instead of a separate repository an extended search might be better with options to filter results that include a source file in selectable formats.

Best regards,
Bodo---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to 
https://tug.org/mailman/listinfo/tex-music

Re: [Tex-music] Does anybody know of a .wma to midi converter?

[Bodo Meissner]

Zitat von Jean-Pierre Coulon :


On Wed, 6 Apr 2016, Bodo Meissner wrote:



Sometimes I import MIDI files into a WYSIWYG notation software.


Then which one? I accept one without MusiXTex conversion! :-)


Sometimes I use "NoteWorthy Composer". This program can only write its  
proprietary format in binary or text form, but there are external  
tools or online services to convert the text format to musicxml.


---
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] Does anybody know of a .wma to midi converter?

[Bodo Meissner]

Zitat von Jean-Pierre Coulon :

How do those who create a MIDI with their keyboard work to make a  
score afterwards work? Of course they make no rubato!


Sometimes I import MIDI files into a WYSIWYG notation software.
I have to choose the note and rest resolutions, so all durations will  
get rounded to the nearest match. That means if there are slight  
variations of the note duration and I choose the resolution wrong, I  
get unreasonable results, for example lots of double dotted notes or  
rests after every note.


Bodo

---
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] gregorian music sheets in pmx

[Bodo Meissner]

Am 26.06.2015 21:48 schrieb Andre Van Ryckeghem :

> Perhaps (i hope) this work is useless, because someone else has a easy way 
to make gregorian sheets.

Hello Andre,

some years ago I used OpusTeX to produce some sheets of gregorian chants with lyrics for our local choir. The gregorian support of OpusTeX has a specific feature to align the neumes with the lyrics where the layout is mainly defined by the lyrics.
I have to dig up the examples.
You will surely find examples by searching for keywords opustex and gregorian.

Bodo---
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] Lyrics and Chord Symbols

[Bodo Meissner]

Zitat von Don Simons :


But I will mention that the last note came out with lyrics "???". I'm
guessing that for some reason my setup thinks there are one too few
syllables in the text. Can anyone else reproduce this behavior?


Dieter's attached PDF file has the same "???", so it seems to be a  
problem in the PMX source.
I guess there is a missing '_' in the lyrics or something wrong with  
the notes (missing tie?) at "na-tum". Compare with

http://imslp.org/wiki/Ave_verum_corpus,_K.618_%28Mozart,_Wolfgang_Amadeus%29


Bodo



---
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] xtuplet composed of notes with different duration

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 08.08.2014 um 09:58 schrieb Dieter:
> I am trying to typeset the upper triplet construct with PMX. The  lower one 
> works fine, using the "D"-symbol. Does anybody have a solution?

Hello Dieter,

this remembers me of an old score with partially beamed Triplets I wanted to 
reproduce some years ago. It is a score for choir where the beams indicate 
melismas.
This could be solved with inline TeX. I did not analyze the code, so I don't 
know if it is useful for your case.

Extract from my M-Tx file:

% Bar 0-2
% inline TeX trick to get partially beamed triplets as proposed by Olivier Vogel
\let\oldcu\cu\ibu4{4}{-2}\def\cu#1{\qb4{#1}}\ b4ax3 \def\cu#1{\tbu4\qb4{#1}}\ g 
\let\cu\oldcu\ b | e4d d8 c g | b2 
\let\oldcu\cu\ibu4{4}{-2}\def\cu#1{\qb4{#1}}\ c4ax3 \def\cu#1{\tbu4\qb4{#1}}\ 
bs \let\cu\oldcu\ c |
\let\oldcl\cl\ibl3{4}{-2}\def\cl#1{\qb3{#1}}\beginmel\ b4ax3n+1 
\def\cl#1{\tbl3\qb3{#1}}\endmel\ g \let\cl\oldcl\ b | e4d d8 c g | b2   
a4x3Dn+1   a |
L: {vers}
\let\oldcu\cu\ibu2{9}{-2}\def\cu#1{\qb2{#1}}\ b4ax3nf-1 
\def\cu#1{\tbu2\qb2{#1}}\ g \let\cu\oldcu\ b | e4d d8 c g | b2   f4x3D XS-1 f |
\let\oldcl\cl\ibl1{9}{-2}\def\cl#1{\qb1{#1}}\ b4ax3nf \def\cl#1{\tbl1\qb1{#1}}\ 
g \let\cl\oldcl\ b | e4d d8 c g | b2 f4x3Dn-2s+2e |
%

I try to attach the resulting PDF file.


Bodo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlPknc4ACgkQnMz9fgzDSqc7GQCfY6RscohxA/eDwCimHI4z2EeT
mI8An1HYHow59O3UPoMEWho25r8qxtJ6
=S8p3
-END PGP SIGNATURE-


berggeboren.pdf
Description: Adobe PDF document
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

Re: [Tex-music] No room for new \dimen.

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 23.09.2011 20:05, schrieb Sebastian Canagaratna:

>Thanks for the various suggestions. As a temporary solution, I changed
> $texprog="tex" to $texprog="etex" in /usr/bin/musixtex. Now when I run
> prepmx (.i.e. mtx) on a file,
> the Debian scritpt runs tex on the .tex file produced earlier.  Now I run
> musixtex on the .tex file and everything

You could change the two lines

tex $BASE || exit 1

in /usr/bin/pmx to

etex $BASE || exit 1



Bodo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk6GSk0ACgkQnMz9fgzDSqejnQCeOJX2TJHuWyVePALZhGft9MaN
AZwAn0I8tQ9YcanwFzjaHtpoCkFSdQdh
=0X4e
-END PGP SIGNATURE-
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

Re: [Tex-music] [ANNOUNCE] extract.lua: Making parts of a M-Tx score

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I just tested it on Ubuntu Lucid. I installed the latest Debian packages 
musixtex, pmx and m-tx because Ubuntu does not yet have the latest versions.

Am 15.04.2011 05:24, schrieb Don Simons:

> PMX 2.603 than ran fine on Sanctus-Q2.

The same here with Sanctus-Q1

> But when I next ran etex on the resulting Sanctus-Q2.tex, I got
> 
> ! sorry, musixuad must be input before musixlyr.
> l.48 ...y, musixuad must be input before musixlyr}

Where does musixuad come from?
On my system it is not present and I did not find it in the musixtex 1.15 .zip 
file.

MusiXADDitional instruments T.115 <19 Nov 2010>
maxinstruments=9 maxgroups=4 maxslurs=9)
! I can't find file `musixuad'.
l.14  \input musixuad


> After commenting out the two lines
> 
> % \input musixadd
> % \input musixuad
> 
> etex and dvips ran OK, but produced a .ps with one system on the 1st page at 
> the bottom, 1 on the second at the top, and two on the 3rd, and 3 on the 4th. 

The same here for Synctus-Q1 displayed with xdvi.

> ==> This is M-Tx 0.60d (Music from TeXt) <11 October 2008>
> ==>> Input from file Sanctus.mtx
> Writing to Sanctus.pmx
> Too many groups: ERROR on line 5

The same here.

I get another error for Sanctus-Bass:

==> This is M-Tx 0.60d (Music from TeXt) <11 October 2008>
==>> Input from file Sanctus-Bass.mtx
Writing to Sanctus-Bass.pmx
No music paragraphs!: ERROR on line 0

The resulting .pmx file is empty (0 bytes).

I used the file Sanctus-Bass.mtx attached to Dirk's mail.


Bodo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk2n09gACgkQnMz9fgzDSqdprgCgjEriIhJD9ud36RS6jeMI/kJF
BNQAnR+K1q6Zx6O9nEA8W5hnH8Vll5YW
=5LAk
-END PGP SIGNATURE-
---
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 and Windows ME

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 15.02.2011 22:00, schrieb David Allsopp:
> Myscha Aiken wrote:

>> DOS reports "Bad command or filename" unless I navigate manually to the 
>> directory
>> where the program is installed and invoke it from there.
> 
> This sounds like your PATH is wrong in some way...

Hello Myscha,

I agree with David.

>> I have checked that the PATH variable includes the directory where musixflx 
>> and
>> companions reside, so am mystified that WinME cannot find the program unless 
>> it
>> is invoked from the same directory 'o'

I must admit that I never used TeX on a Windows system, so I can only guess:
Is musixflx a .exe or .bat file?
Do you have any other musixflx.bat or .com or .exe files anywhere in your PATH? 
(DOS/Windows will call the first one it finds and it will always check the 
current directory first before the directories in PATH.)
Can you call musixflx with an absolute path from the directory containing your 
MusiXTeX files?
(something like C:\foo\bar\baz\musixflx inputfile)


Bodo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk1a9YUACgkQnMz9fgzDSqesmACeOLlV/Lhpfj/5A+EJw4gOTsmC
hQ0An16criJIHECckAIBimJvT1zeVVGF
=Gh/o
-END PGP SIGNATURE-
---
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

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 27.11.2010 17:18, schrieb Jean-Pierre Coulon:
> On Sat, 27 Nov 2010, Bob Tennent wrote:
> 
>> 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?

No. setlinecap is a switch how the line ends should look like.

extract from PostScript language reference manual:

0 Butt cap—the stroke is squared off at the endpoint of the path. There is
   no projection beyond the end of the path.
1 Round cap—a semicircular arc with diameter equal to the line width is
   drawn around the endpoint and filled in.
2 Projecting square cap—the stroke continues beyond the endpoint of the
   path for a distance equal to half the line width and is squared off.


Bodo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkzyO2wACgkQnMz9fgzDSqcERgCgiMcvuZj4YmSRu+NeLxfF17M9
4/sAniWd6hSx857i0j/pWE/LZZmAOeQf
=C/NJ
-END PGP SIGNATURE-
---
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 upgrade philosophy

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 24.06.2010 13:33, schrieb Dirk Laurie:
> Don Simons skryf:
>>
>> The question before me is whether to have PMX once and for all issue
>> \setmaxinstruments{24}, thereby requiring all new PMX-generated TeX files to
>> be processed with eTeX. 

> But can't the pmxa part of pmxab count how many instruments are 
> actually needed, and the pmxb part issue \setmaxinstruments with 
> that precise number?

Or would it be possible to check for the TeX version and insert 
\setmaxinstruments{24} only if eTeX is detected?


Bodo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkwjT9EACgkQnMz9fgzDSqeN9QCggitOBcZHusWGAwZsMN+6eA6W
pk4An3DJKRlBaTnPPT0EhvLIUl9b3Me0
=AlX7
-END PGP SIGNATURE-
___
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] FOR in Windows (was: Making PostScript files with a virtual PostScript printer, .pdf)

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jean-Pierre Coulon schrieb:

> Forgive my lazyness to find the appropriate Usenet group for this: undex
> XP,
> can you use the FOR command to automate a series of commands like this,
> if you
> have a number of images to process:
> 
> eps2eps p1.ps p1.eps
> eps2eps p2.ps p2.eps etc.

for %i in ( *.ps ) do eps2eps %i %~ni.eps

see http://www.robvanderwoude.com/ntfor.php

Note: I did not run this command as I don't have Windows here.


Bodo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpCdlwACgkQnMz9fgzDSqe9zQCgpHsRvGIStgoGLbDEV+wXLmqV
FU0An2UMW7zWjHdNv008IW3uqhHhP04T
=Q2Ks
-END PGP SIGNATURE-
___
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] musixpss: linux compilation problem

[Bodo Meissner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Luigi Cataldi schrieb:

> if I try to compile musixpss 0.52 with
> 
> 'gcc musixpss.c -o musixpss'
> 
> I have this warning message:
> 
> '/tmp/ccKkXscu.o: In function `process_clean':
> musixpss.c:(.text+0x83c): warning: the `gets' function is dangerous and
> should not be used.'

Hello Luigi,

I think this warning has absolutely nothing to do with the other errors.
Function gets is dangerous because it leads to a buffer overflow when the input 
line is longer than expected.

If in musixpss.c the removing of an intermediate EPS file fails, it will print 
an error message. In this case you have to type an answer and press Enter.
If you type more than 1022 characters you might get strange behavior of the 
program because of a buffer overflow.

(For all other purposes, especially for reading files, the program uses 
fgets().)

> The risulting musixpss program works, but with errors.

You should tell more details about the errors.


Bodo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm5hO0ACgkQnMz9fgzDSqcAJgCdFIyOt6AG6kFzP6YwOX5ac8w/
7C0AoJvjQ4sHVPEHH9cvQ/qDVIYN0H0H
=UwTT
-END PGP SIGNATURE-
___
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 - beamed xtuplets on 2 staffs

[Bodo Meissner]

Am 13.09.2006 14:32:29 schrieb(en) Andre Van Ryckeghem:

I have here a piece full of 6-tuplets in the accompaniment. some of  
them are over 2 staves, and although not necessary some of them must  
be in
the form [ ax6 a a ][ a a a] what is not allowed in tuplets. Also  
some of them must be in a form [ ax6 a ] aa  a [ a a] (corresponding  
to melsimas in the voice staff.
In short: is it possible to have the same possibilities in a typlet  
as in normal notes?


Hello Andre,

I had a similar problem with special beaming of tuplets two years ago.  
IIRC the solution was proposed by Olivier Vogel.

(I don't completely understand the inline TeX code.)

Look at bars 0 and 2 in the attached file berggeboren.mtx.


Bodo
Title: Berggeboren
%Composer: 
%Poet: 
Style: TTBB
TTBB: Voices T1,T2 B1,B2; Choral; Clefs G8 F;
Name: \vbox{\hbox{T$\,$1}\hbox{T$\,$2}} \vbox{\hbox{B$\,$1}\hbox{B$\,$2}}
%Name: T B
Indent: 0.05
Flats: 3
Meter: 3/4
Pages: 1
Systems: 3
Space: 8 6
Start: ;@+2
%%\input plainenc\relax\inputencoding{latin1}
%%\voffset=-2cm
%%\font\eightrm=pncr at 8pt\font\eightit=pncri at 8pt
%%\font\tenrm=pncr at 10pt\font\tenit=pncri at 10pt 
%%\font\twelverm=pncr at 12pt\font\twelvebf=pncb at 12pt\font\BIGfont=pncb at 
18pt\font\Bigfont=pncr at 12pt
%%\twelverm\setlyrstrut
%%\def\myverA{{\tenit M-Tx} \mtxversion\ {\eightrm\mtxdate}, PMX \pmxversion\ 
{\eightrm<\pmxdate>} und }
%%\def\myver{\myverA\musixtex\ \mxversion\ {\eightrm<\mxdate>}}
%%\def\myft{\tenrm Notensatz: Bodo Meißner mit \myver}
%%\let\sav\Endpiece
%%\def\Endpiece{\sav\vfill\noindent\myft\def\vfill{\vskip5mm}}

{vers}
Berg-ge-bo-ren ist mein Lied,
wie ein Sturz-bach reißt es mit
je-des Hemm-nis, je-den Schmerz.
Sin-ge nur, sin-ge nur! 
Sin-ge, sin-ge mein Herz!

%%w195m
%%h290m
%%Iipipit70
%%ArpT
% Bar 0-2
\let\oldcu\cu\ibu4{4}{-2}\def\cu#1{\qb4{#1}}\ b4ax3 \def\cu#1{\tbu4\qb4{#1}}\ g 
\let\cu\oldcu\ b | e4d d8 c g | b2 
\let\oldcu\cu\ibu4{4}{-2}\def\cu#1{\qb4{#1}}\ c4ax3 \def\cu#1{\tbu4\qb4{#1}}\ 
bs \let\cu\oldcu\ c |
\let\oldcl\cl\ibl3{4}{-2}\def\cl#1{\qb3{#1}}\beginmel\ b4ax3n+1 
\def\cl#1{\tbl3\qb3{#1}}\endmel\ g \let\cl\oldcl\ b | e4d d8 c g | b2   
a4x3Dn+1   a |
L: {vers}
\let\oldcu\cu\ibu2{9}{-2}\def\cu#1{\qb2{#1}}\ b4ax3nf-1 
\def\cu#1{\tbu2\qb2{#1}}\ g \let\cu\oldcu\ b | e4d d8 c g | b2   f4x3D XS-1 f |
\let\oldcl\cl\ibl1{9}{-2}\def\cl#1{\qb1{#1}}\ b4ax3nf \def\cl#1{\tbl1\qb1{#1}}\ 
g \let\cl\oldcl\ b | e4d d8 c g | b2 f4x3Dn-2s+2e |
%
% simpler version with slurs instead of beams
%( b4ax3   g ) b | e4d d8 c g | b2 ( c4ax3 bs )c |
%( b4ax3   g ) b | e4d d8 c g | b2   a4x3D a |
%L: {vers}
%( b4ax3nf g ) b | e4d d8 c g | b2   f4x3Dn+1 XS-1 f |
%( b4ax3nf g ) b | e4d d8 c g | b2   f4x3Dn-2s+2   e |

% Bar 3-4
f4d d8 c8d b1 | g+2 g8 f |
a4d a8 a8d a1r | b2 d8f d |
[ f8 e d ] f f8d f1 | e2 b+8 b |
[ d8 c b ] b c8d d1 | e2 e8 f |

% Bar 5-7
f4  es e8n df | c2  r4+0 |   ( c4   f4d )   d8 |
d4f c  b8  b  | b2r r4b  |  (t a2 a8 )t a |
b4  b  g8  g  | g2  r4+0 | ( [ f8 e f e ] g )+0+0-1   f |
g4  g  g8  f  | e2s r4b  | ( [ f8 e d c ] b )   b |

% Bar 8-10
( c4 b ) r+0 |   g+2g4   | ( g   f ) r4+0 |
  a2 r4b | ( b4  e )  [ d8 d8f ] |   c2  r4b  |
( e4 d ) r+0 | ( e4  b+ )   b| ( b   a ) r+0  |
  b2 r4b |   e2re4   |   a-2 r4b  |

% Bar 11-13
rpb|   b2  g8d of  f1 | e2 |]
( f4d e8 ) [ d c ] |   d2  d8d d1 | b2 |]
rp+0   | ( f4 c+ ) b8d a1 | g2 |]
rpb|   b2  b8d ofd b1 | e2 |]
%
%%%
%
% Note:
%
% I changed the definition of \setlyrstrut in my copy of musixlyr.tex 
% (version MusiXLYRics 2.1c )
%
% \def\setlyrstrut{% set up strut according to currently active font
%   \setbox0=\hbox{(\"Ag)}%
%   \setbox\lyrstrutbox=\hbox{\vrule height 1.1\ht0 depth 1.1\dp0 [EMAIL 
PROTECTED]
%
% The original had \hbox{()} which does not work for pncr font.
%
% Without this change in musixlyr.tex you might need the following
% TeX command in a line before \setlyrstrut (with only 2 % instead of 3)
%
%%%\def\setlyrstrut{\setbox0=\hbox{(g)}\setbox\lyrstrutbox=\hbox{\vrule height 
1.1\ht0 depth 1.1\dp0 width 0pt}}
%
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] pmx installation under SuSE Linux 9.3

[Bodo Meissner]

Am 2005.12.11 10:04 schrieb(en) Christian Mondrup:

There is no such executable 'musixtex' coming with the MusiXTeX  
distribution. Compiling a musixtex source file, say my_music.tex, is  
done as a series of tex- and musixflx runs


Hello Hartmut,

the MusiXTeX Debian package has a program /usr/bin/musixtex.

These are the first comment lines of the script:

#!/usr/bin/perl -w
#
# This musixtex Perl script automates the three-pass TeX compilation
# of a MusiXTeX music score file.  It basically runs the command:
#   $ tex filename.tex ; musixflx filename ; tex filename.tex
#
# Adapted by Anthony Fok <[EMAIL PROTECTED]> for Debian GNU/Linux
# from the DOS batch file in the MusiXTeX User Manual by MusiXTeX's  
authors.

# Improvements copyright 2003, Julian Gilbey <[EMAIL PROTECTED]>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.

Maybe the SuSE package has a similar script. You can try to use the  
script from the SuSE MusiXTeX package.



If you have difficulties with the manual installation of MusiXTeX and  
related software and would prefer to install pre-packaged programs, you  
might consider switching your Linux distribution.


Debian has
MusiXTeX  stable and testing: T.112
PMX   stable: 2.504  testing: 2.507
M-Tx  stable: 0.55c testing: 0.60

The Debian maintainers are fairly quick in packaging new upstream  
versions.



Bodo
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] M-TX ignores PMX MIDI macros after last bar

[Bodo Meissner]

Hello all,

I want to use PMX MIDI macros to implement repeats and D.C. al Fine for  
MIDI output.


Because the last bar has a "D.C. al Fine" I tried to insert the  
appropriate MIDI macro play commands after the last bar.


When the macros are a separate input block after the last bar they are  
ignored by M-Tx.


I found this problem in the piece I included in my message with subject  
"anyone knows this a-capella march?"


It can be reproduced with this simple example:

Title: MIDI macro test
Style: Singer
Sharps: 1
Meter: 3/4
Pages: 1
Systems: 2
Size: 16
%%\nobarnumbers

%%Iipit120
%%IMR1
|: g4 b d | d b g | c a f

%%IM
V1 g b d |

%%IMP1
%%IMR2
U: ~ ~ !ppff Fine
Vb2 g- b g :|

%%IM
Vb g b d | g- b d | g- b d |

U: \vbox{\hbox{D.C.}\hbox{al~Fine}}
d2d |]

%%IMP1
%%IMP2


These are the last lines of the generated PMX file:

%Bar 8
g4- b4 d4 | /

% Paragraph 6 line 25 bar 9
\mtxZchar{10}{\ppff{\vbox{\hbox{D.C.}\hbox{al~Fine\ d2d /

 RD
% Coded by M-Tx


When I remove the empty line before these commands they will be  
inserted before the last bar like this:


% Paragraph 6 line 25 bar 9
IMP1
IMP2
\mtxZchar{10}{\ppff{\vbox{\hbox{D.C.}\hbox{al~Fine\ d2d RD
 /

% Coded by M-Tx


This replays the recorded parts before the last bar, not after this bar.

When I manually add the MIDI commands at the end of the .pmx file or  
just before the " RD" line, PMX generates MIDI output as intended.



I think, M-TX should not ignore PMX commands in %% comments after the  
last notation block.



Bodo
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] Zigzag lyrics

[Bodo Meissner]

Am 2005.10.26 11:33 schrieb(en) Dirk Laurie:


the comments at the bottom caught my eye:

Bodo Meissner skryf:
>
> % Note:
> %
> % I changed the definition of \setlyrstrut in my copy of  
musixlyr.tex

> % (version MusiXLYRics 2.1c )

[...]


This is a useful tip.  I have also experienced problems with zigzag
lyrics in non-Knuthian fonts.


Hello Dirk,

I once had a problem with zigzag lyrics lines and asked for help on  
this mailing list. Rainer Dunker told me how to change setlyrstrut to  
make it work with pncr font.


I just found this in my archive.
Am 2004.04.30 11:09 schrieb(en) Rainer Dunker:


A little addition: In the pncr font used here, the parentheses seem
to have a smaller depth than some characters extending under the
baseline; I saw this by replacing "Äh-ren-wo-gen," by  
"Äh-ren-wo-(gen,)" and closely comparing the character depths of the  
last syllable.
For this reason, the vertical alignment is even more precise if you  
use somthing like \hbox{(g)} instead of \hbox{()} as the font  
dimension reference.


(It's probably exactly that reason why musixlyr's internal definition
of the \lyrstrutbox doesn't work properly for this font. The next
musixlyr release should handle this situation better.)


I added \"A to the set of characters in case there might be fonts with  
the letter Ä higher than parentheses.



Bodo
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] anyone knows this a-capella march?

[Bodo Meissner]

Hello all,

I started to typeset an a-capella march for our choir. The only source  
I have is a hadwritten notation. Nobody seems to know a composer or  
publisher or where this piece came from. It's not even clear if the  
name "Trottelmarsch" is correct.


(It's a work in progress, the M-TX source still needs some fine-tuning.)

Does anyone know this march?


Bodo


Title: Trottelmarsch
%Composer: unbekannt
Style: TTBB
TTBB: Voices T1,T2 B1,B2; Choral; Clefs G F
Name: \vbox{\hbox{T$\,$1}\hbox{T$\,$2}}  
\vbox{\hbox{B$\,$1}\hbox{B$\,$2}}

Indent: 0.05
Flats: 3
Meter: 2/4
Size: 20pt
Pages: 2
Systems: 10
%Bars/line: 5
Space: -2 6
Size: 16
%%\voffset=-2cm
%%\font\eightrm=pncr at 8pt\font\eightit=pncri at 8pt
%%\font\tenrm=pncr at 10pt\font\tenit=pncri at 10pt
%%\font\twelverm=pncr at 12pt\font\twelvebf=pncb at  
12pt\font\BIGfont=pncb at 16pt\font\Bigfont=pncr at 12pt

%%\font\elevenrm=pncr at 11pt\font\elevenbf=pncb at 11pt
%%\tenrm\setlyrstrut
%%\def\myverA{{\tenit M-Tx} \mtxversion\ {\eightrm\mtxdate}, PMX  
\pmxversion\ {\eightrm<\pmxdate>} und }

%%\def\myver{\myverA\musixtex\ \mxversion\ {\eightrm<\mxdate>}}
%%\def\myft{\eightrm Notensatz: Bodo Mei\ss{}ner mit \myver}
%%\let\sav\Endpiece
%%%\def\Endpiece{\sav\vfill\noindent\myft\def\vfill{\vskip5mm}}
%%\def\Endpiece{\sav\vskip5mm\noindent\myft}
[EMAIL PROTECTED]


%%w195m
%%h285m
%%Iipipit100
Apr
%%Ar
%%AK
% Bar 1-4
%%IMR6
b-4d [[ b1 b ] | b4d [[ b1 b ] | b8 r+0 b r+0 | b8 r+0 b r+0 |:
@-2 b-4d [[ b1 b ] | b4d [[ b1 b ] | b8 rb b rb | b8 rb b rb |:
L: Ram pa-da bam pa-da bam bam bam bam
rpb | rpb | b8 r+0 b r+0 | b8 r+0 b r+0 |:
b4d [[ b1 b ] | b4d [[ b1 b ] | b8 rb ar rb | g8 rb f rb |:

% Bar 5-6
%%L2
%%IM
%%IMR1
@+3 [[ g+8 g1 g ] g8 r+0 | [[ g8 g1 g ] g8 r+0 |
LT1: ram-da-da da ram-da-da da
[[ b8 b1 b ] c8 rb | [[ b8 b1 b ] c8 rb |
@-4 r8 b r b | r8 b r b |
LB1: di di di di
@-6 e8 r b r | e8 r b r |
L: bam bam bam bam

% Bar 7
[[ g8 g1 g ] [[ g8 gr ] |
LT1: ram-da-da dam-pam
[[ b8 b1 b ] [[ e8 f ]  |
r8 b r b |
LB1: di di
e8 r b r |
L: bam bam

% Bar 8
(( a4 a ) |
LT1: pa-da
(( e4 d ) |
@+2 r [[ b1 b ] [[ b8 b ] |
LB1: di-di di-di
f+ r b- r |
L: bam bam

% Bar 9
[[ a8 a1 a ] a8 r+0 |
LT1: ram-da-da da
[[ b8 b1 b ] c8 rb |
@-2 r8 f r b |
LB1: di di
b8 r b r |
L: bam bam

% Bar 10
[[ a8 a1 a ] a8 r+0 |
LT1: ram-da-da da
[[ b8 b1 b ] c8 rb |
r8 f r b |
LB1: di di
b8 r b r |
L: bam bam

% Bar 11
[[ a8 a1 a ] [[ a8 b ] |
LT1: ram-da-da dam-pam
[[ b8 b1 b ] [[ f+8 g ] |
r8 f r b |
LB1: di di
b8 r b r |
L: bam bam

% Bar 12
(( a4 g8 ) r+0 |
LT1: pa-da
(( f4 e8 ) rb |
@+2 r [[ b1 b ] [[ b8 b ] |
LB1: di-di di-di
e r [[ b8 g ] |
L: bam bam-bam

% Bar 13-14
[[ g8 g1 g ] g8 r+0 | [[ g8 g1 g ] g8 r+0 |
LT1: ram-pa-da bam ram-pa-da bam
[[ b8 b1 b ] c8 rb | [[ b8 b1 b ] c8 rb |
@-2 r8 b r b | r8 b r b |
LB1: di di di di
e+8 r b r | e8 r b r |
L: bam bam bam bam

% Bar 15
[[ g8 g1 g ] [[ g8 gr ] |
LT1: ram-da-da dam-pam
[[ b8 b1 b ] [[ e8 f ] |
r8 b r b |
LB1: di di
e8 r b r |
L: bam bam

% Bar 16
(( f4 [[ f8d ) f1 ] |
LT1: pa dam-pa
@+6 (( e4r d ) |
L: pa da
r8 b r b |
LB1: di di
b8 r b r |
L: bam bam

% Bar 17
(( f4 a8s ) r
LT1: da da
c2
L: da
a2s
f+2
L: bam

% Bar 18-19
f4d f8 | [[ f8 e d c ] |
LT1: da da ram-pam-pam-pam
c4d f8 | [[ f8 e d c ] |
%L: da da ram-pam-pam-pam
a4ds f8 |  [[ f8 e d c ] |
f4d f8 |  [[ f8 e d c ] |
L: da da ram-pam-pam-pam

% Bar 20
%%IM
V1 @-2 b8 r+0 r4+0 :|
LT1: pa
V1 b8 rb r4b :|
@-4 V1 b8 r r4 :|
LB1: pa
@-4 V1 [[ b8 a g f ] :|
L: pam-pam-pam-pam

% Bar 21
%%IMP1
%%IMR7
Vb2 b8 r+0 b4 |:
LT1: pam da
Vb2 b8 rb b4 |:
@+2 Vb2 b8 r+0 b+4 |:
LB1: pam di
@+4 Vb2 b8 rb b+4 |:
L: pam da

%Space: -2 4
%Bar 22-23
%L6P2
%%IM
%%IMR2
Vb @+2 c4 c+ | b a |
LT1: da da da da
Vb c4 a+ | g f |
@+2 Vb c2 | d |
LB1: di di
Vb (( a4 a- ) | (( b d )
L: da da da da

% Bar 24
[[ g8d g1 ] [[ g8 g ] |
LT1: ram-da da-da
[[ e8d e1 ] [[ e8 b ] |
r8 b r b |
LB1: di di
e8 r b r |
L: bam bam

% Bar 25
b4d g8 |
LT1: da da
g+4d e8 |
r8 [[ b1 b ] b4 |
LB1: di-di di
e8 r b r |
L: bam bam

% Bar 26-27
[[ a8d a1 ] [[ a8 a ] | b4dr a8 |
LT1: ram-da da-da da da
[[ d8d d1 ] [[ d8 b ] | a+4d d-8 |
r8 b r b | r [[ b1 b ] b4 |
LB1: di di di-di di |
f+8 r b- r | f+ r b- r |
L: bam bam bam bam

% Bar 28
[[ g8d g1 ] [[ g8 g ] |
LT1: ram-da da-da
[[ e8d e1 ] [[ e8 b ] |
r8 b r b |
LB1: di di
e8 r b r |
L: bam bam

% Bar 29
Space: 8 12
b4 r8+0 g8 |
LT1: da da
g+4 r8b b-8 |
r8 [[ b1 b ] b4 |
LB1: di-di di
e8 r e4 |
L: bam da

% Bar 30-31
(( a4 c ) | (( b a ) |
LT1: da-da da-da
(( c4 a+ ) | (( g f ) |
c2 | d |
LB1: di di
a-2 | b4 d |
L: da da da

% Bar 32
[[ g8d g1 ] [[ g8 g ] |
LT1: ram-a da-da
[[ e8d e1 ] [[ e8 b ] |
r8 b r b |
LB1: di di
e8 r b r |
L: bam bam

% Bar 33
b4d b-8 |
LT1: da da
g+4d b-8 |
r8 [[ b1 b ] [[ a8 g ] |
LB1: di-di di-di
e8 r e4 |
L: bam da

% Bar 34-35
c4d c8 | d4d d8 |
LT1: da da da da
c4d c8 | d4d d8 |
a4d a8 | a4d a8 |
LB1: di di di di
a-2 | b2 |
L: da da

% Bar 36
e8 r8+0 d4 |
LT1: ram da
e8 r8b d4 |
g8 r+0 a4 |
LB1: ram da
e8 rb b4 |
L: r

Re: [TeX-music] Fw: Duette, obscure requests.

[Bodo Meissner]

Am 2005.07.29 08:07 schrieb(en) Don Simons:

Am I missing something? What's so sinister about these requests? Is
there something in the tone of the language? I don't know German at  
all.


Hello Don,

there there are only slight signs that IMHO make the message look  
suspicious:
From name does not match signature name, mail from an unknown person,  
sender knows little or nothing about recipient, a list of 5 commercial  
notation programs but not TeX


And the message remembers me of a story from 1992/1993 that is well  
known in the German computer scene:
Many young male home computer users received a letter with photo from a  
girl who asked to exchange copies of home computer software.
Everybody who answered and agreed did not get software from this  
non-existing girl but a cease and desist letter from a lawyer and  
should pay the lawyer's fees.

Look at this
http://www.domes-dos.de/private/cpc/oddities/oddities_e.php
or search for "gravenreuth" and "tanja", but nearly all results will be  
in German.



Bodo
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] Fw: Duette

[Bodo Meissner]

Am 2005.07.24 19:12 schrieb(en) Veronica Brandt:

Can anyone help with this?  Due to my woefully deficient education I
can barely read it.


Hello Veronica,

this request looks a bit suspicious:
The sender's address is a free e-mail provider in Germany.
The name at the From address does not match the name below the message.
A personal message from an unknown person and not related to your  
mailing list messages or website.

I, personally, would probably not answer.

Basically the sender of this message wants to get some unusual or less  
known sheet music pieces for soprano and alto voices and piano in one  
of several listed notation program formats.


Maybe you were sent this because your name (Brandt) seems to be German.


 Would it be possible (or even desirable) to put
the mailing list email address up along with the other email
addresses?


Sorry, I don't understand this question.


Bodo
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] Type 1 fonts for Opustex

[Bodo Meissner]

Am 2005.06.15 09:10 schrieb(en) Robin Fairbairns:


Veronica Brandt writes:
> And when is Opustex v1.0 being released?


Andreas popped up somewhere (was it here?) a few months back, and  
said he was working on it again.


I just looked into my archive:

On 2004.10.29, Andreas Egler wrote:


Next version comes in two weeks.


and on 2004.10.30:

There is already a testversion with fully automatic beams. But it  
isn't ready yet.

[...]
I decided to "hide" the unofficial version until V1.0 is reached and  
no more changes (not additions) will be done.


From time to time I looked around but could not find a new version of  
Opustex. Maybe you have to ask Andreas for it.


A bit more than 3 weeks after the announcement I asked about the new  
version on this list, but did not get a reply.



Bodo
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] OpusTeX (was: Gregorian chant: MusiXTeX?)

[Bodo Meissner]

Am 2004.10.30 18:30 schrieb(en) Andreas Egler:
> > Next version comes in two weeks.
[...]
I decided to "hide" the unofficial version until V1.0 is reached and  
no more changes (not additions) will be done.
Hello Andreas,
will the new version have any advantages for Gregorian chant compared  
to version 0.93?

Is the new version already available?
Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] PMX Beta 2.505: New option for default rest positions in 2-voice staves

[Bodo Meissner]

Am 2004.11.15 16:36 schrieb(en) Don Simons:
The option is available with a bit of user tweaking: enter e.g. r4+0
in one voice and r4b in the other.
Hello Don,
that's the way I do it now. But this is problematic if I extract or  
rearrange voices or change the M-Tx style (e.g. SATB to SATB4).
Maybe I can avoid the problems if I write r4+0 in both voices.

My wish is to have a PMX-option to change the default. This would save  
some typing. I thought it might not be too difficult to integrate it  
into your latest changes.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] PMX Beta 2.505: New option for default rest positions in 2-voice staves

[Bodo Meissner]

Am 2004.11.13 20:13 schrieb(en) Don Simons:
If there are simulataneous rests in both voices, the old rule is  
applied.
Hello Don,
the automatic placement of rests sounds good. I'll try it when I have a  
suitable piece.

I'd wish another option: If there are simultaneous rests with the same  
length in both voices, I'd like to have only one rest sign at the  
single-voice default position. This notation is common for choir music.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] Re: M-Tx/MusiXLYR long words centered at melisma?

[Bodo Meissner]

Hello Rainer!
Bodo Meissner wrote:
> Would it be possible to implement the placing of a syllable below a
> group of notes as follows?
I add numbers to reference these instructions and notes describing the  
different cases.

1. (preparation)
> At the start of a melisma save the current position and the
> syllable.
2. (melisma complete without line break, syllable wider than note  
spacing -> center syllable below complete melisma phrase)

> If the end of the melisma is reached and the syllable is not yet
> placed, try to center it below the group of notes.
Am 2004.11.03 23:06 schrieb(en) Rainer Dunker:
Objection: Consider long melismas, like baroque 'Koloraturen' (don't
know the English word) which may easily span more than one line.  
Centering the syllable unter the melisma would place it too far away  
from the melisma beginning
...
In this case the syllable will already have been placed left justified  
according to instruction 4. So instruction 2 will not apply.

3. (line break during melisma, syllable wider than note spacing on  
first line -> center syllable below this first part)

> If a line break is reached and the syllable is not yet placed, try
> to center it below the notes from the start of the melisma up to
> the last note before the line break. Start a line or hyphens
> (lyrrule) at the first note after the line break until end of
> melisma.
4. (no line break until now, note spacing wider than syllable -> left  
justify with first note)

> If the note spacing up to the current note is wider then the space
> needed for the syllable, left justify the syllable at the saved
> position of the first note. Continue with line or hyphens (lyrrule)
> until end of melisma.
Instructions 2, 3 and 4 will compute the default position of the  
syllable depending on the note spacing and the space needed for the  
syllable. This default position, regardless if centered or left  
justified, may collide with the syllable to the left.

> (If there is a collision on the left side, the syllable must be
> shifted to the right as usual.)
I see what you're aiming at. I agree it should be feasible to delay
the syllable placement until the ending position of the melisma  
phrase is known, but I keep insisting that making the syllable  
placement dependent on subsequent syllables is too complicated.
I agree.
My wish is a default placement based solely on the width of the  
syllable and the note spacing of the melisma phrase or it's first part  
up to a line break. The centering of syllables wider than the note  
spacing should always be done, not depending on a possible collision on  
the right side. No left shifting to avoid a collision on the right  
side. IMHO it simply looks bad even if no collision occurs.

I'll put your suggestion on the wish list, but please don't ask when
it will be implemented ... :-) Should you become impatient, please  
feel free to go ahead yourself!
I wish I could do that. I'm happy that I partially understand TeX code  
and can make simple changes. Since I don't know which variables or  
macros are available, I would need some example code or good  
documentation covering internals of MusiXTeX.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] Re: M-Tx/MusiXLYR long words centered at melisma?

[Bodo Meissner]

musixlyr has no idea about the notes spacing surrounding the  
attachment of a specific syllable. All it knows is the horizontal  
position of the related note, the width of the current syllable and  
the available space to the previous syllable.
Hello Rainer,
thank you for the explanation.
If I understand it correct, this means at the start of a melisma  
musixlyr does not know the position of the ending note of this melisma.

It's
...
unfortunately impossible to anticipate collisions that will take
place on the right side of the current syllable.
Avoiding or reducing collision was not my primary intention, although  
the left justification leads to more collisions.

IMHO it does not look good if long syllables are left justified at a  
melisma while normally syllables are centered at single notes, even  
without collisions.

You may either resort to a generally wider music spacing (e.g. by  
requesting a greater \linegoal) or, if that's not feasible, by manual  
corrections to the lyrics or notes spacing.
I think I will use manual corrections if necessary, because I have to  
fulfill two somewhat contradictory requirements: Use as little pages as  
possible to avoid turning over the pages while singing and use large  
text and notes size because several choir members' eyesight is not so  
good.

I looked at musixlyr.tex and think I partially understand how it works.
Would it be possible to implement the placing of a syllable below a  
group of notes as follows?
At the start of a melisma save the current position and the syllable.
If the end of the melisma is reached and the syllable is not yet  
placed, try to center it below the group of notes.
If a line break is reached and the syllable is not yet placed, try to  
center it below the notes from the start of the melisma up to the last  
note before the line break. Start a line or hyphens (lyrrule) at the  
first note after the line break until end of melisma.
If the note spacing up to the current note is wider then the space  
needed for the syllable, left justify the syllable at the saved  
position of the first note. Continue with line or hyphens (lyrrule)  
until end of melisma.
(If there is a collision on the left side, the syllable must be shifted  
to the right as usual.)

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] Gregorian chant: MusiXTeX?

[Bodo Meissner]

Am 2004.10.29 11:22 schrieb(en) Olivier Vogel:
Le ven 29/10/2004 à 01:12, Guido Milanese a écrit :

> But it's really impossibile to write texts with Gregorian chant
using MusiXTeX?
You can add lyrics with MusiXTeX with the macros \zsong, \lsong and
\csong.
OpusTeX has some specific macros for Gregorian chant with lyrics. These  
are not available for MusiXTeX. I think it's possible with MusiXTeX,  
but it will be more work since you have to type more or make your own  
macros.

I think a package for MusiXTeX which has the same macros as opusgre  
would have to be implemented nearly from scratch because of the  
incompatibilities between MusiXTeX and OpusTeX.
Maybe opusgre is based on musixgre but it has a lot of new macros while  
musixgre seems to be in the state it was when OpusTeX separated from  
MusiXTeX.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] Re: M-Tx/MusiXLYR long words centered at melisma?

[Bodo Meissner]

Am 2004.10.29 11:26 schrieb(en) Olivier Vogel:
Your attachment doesn't come with your mail.
Hello Olivier,
thanks for indicating this. I think before sending my mail the 
attachment was shown as text/plain but in my sentbox it is 
application/octet-stream. Maybe a problem with my mail reader.

I include the M-Tx source as inline text, trying not to insert 
line breaks. If you get errors check for line breaks inserted by 
your mail reader or something in between.

The structure must be:
notes line
chord line
4 lyrics lines
2 notes lines
Bodo
Title: Fein sein, beinander bleibn
Composer: aus dem Alpenland
Style: TTBBx
TTBBx: Voices T12,B1 B2; Choral; Clefs G8 F
%%\def\ttbname{\vbox{\hbox{T$\,$1}\hbox{T$\,$2}\hbox{B$\,$1}}}
Name: \ttbname \vbox{\hbox{B$\,$2}}
Indent: 0.05
Sharps: 1
Meter: 3/4
Size: 20pt
Pages: 1
Systems: 3
Space: 14 -2
%%\voffset=-2cm
%%\input musixcho
%%\braceheight5\Interligne\relax
%%\input plainenc\relax\inputencoding{latin1}
%%%\def\setlyrstrut{\setbox0=\hbox{(g)}\setbox\lyrstrutbox=\hbox{\vrule height 1.3\ht0 
depth 1.3\dp0 width 0pt}}
%%%\def\setlyrstrut{\setbox0=\hbox{()}\setbox\lyrstrutbox=\hbox{\vrule height 11pt 
depth 3pt width 0pt}}
%%\voffset=-2cm
%%\font\eightrm=pncr at 8pt\font\eightit=pncri at 8pt
%%\font\tenrm=pncr at 10pt\font\tenit=pncri at 10pt
%%\font\twelverm=pncr at 12pt\font\twelvebf=pncb at 12pt\font\BIGfont=pncb at 
16pt\font\Bigfont=pncr at 12pt
%%\font\elevenrm=pncr at 11pt\font\elevenbf=pncb at 11pt
%%\elevenrm\setlyrstrut
%%\def\myverA{{\tenit M-Tx} \mtxversion\ {\eightrm\mtxdate}, PMX \pmxversion\ 
{\eightrm<\pmxdate>} und }
%%\def\myver{\myverA\musixtex\ \mxversion\ {\eightrm<\mxdate>}}
%%\def\myft{\tenrm Notensatz: Bodo Meiner mit \myver}
%%\let\sav\Endpiece
%%\def\Endpiece{\sav\vfill\noindent\myft\def\vfill{\vskip5mm}}
%%\nobarnumbers
%%w195m
%%h290m
%%Iipipit80
Apr
%%Ar
% Bar 1-3
[ \verses{,\lyroffset{-1},,}\ d8 b+ ] b4d c8 | b4d a8 a4 | g2 r4+0 |
C: d  gg   ag  f  fd  rb   
L: 1. Fein sein, bei-nan-der blei-bn,
L: 2. Gscheit sein, nit ei-ni-tap-pn,
L: 3. Frisch sein, nit um-ma-mok-kn,
L: 4. Treu sein, nit au-\ss{}i-gra-sn,
 d4  d4d e8 | d4d c8 c4 | b2 r4+0 |
 g4  g4d g8 | d4d d8 d4 | g2 r4b  |

% Bar 4-5
[ \verses{,\lyroffset{-1},,}\ b8 d ] d4d e8 | d4d c8 c4 |
C: g  b   b   cb   a  a  
L: fein sein, bei-nan-der blei-
L: gscheit sein, nit ei-ni-tap-
L: frisch sein, nit um-ma-mok-
L: treu sein, nit au-\ss{}i-gra-
[ d8 g ] g4d g8 | f4d d8 d4 |
 g4 g4d g8 | d4d d8 d4 |

% Bar 6a
m2400 b2 ||
C:g  
L: bn,
L: pn,
L: kn,
L: sn,
m2400  d2 ||
m2400  g2 ||

%%L2
% Bar 6b
m2800 g4 |
C:g  
L: mags
L: es
L: und
L: denn_die
m2800  g4 |
m2800  g4 |

% Bar 7-10
m3400 [ g8 e+ ] e4d d8 | \verses{,,,\beginmel}\ ((b d4 \verses{,,,\endmel}\ c4d ) \verses{,\beginmel,,}\ ((b aa1 \verses{,\endmel,,}\ aa ) | a4 d c | b2d ||
C:  g  cc   bb  a   f  f   f  b a   g 
L: regn o-der win-dn o-der a-ber schnei-bn,
L: steckt oft der Fuchs in der Zip-fl-kap-pn,
L: gehr a dein H\"au-sl und die Liab in Brok-kn,
L: Liab is so zart  wiar a Soa-fn-bla-sn,
m3400   g4  g4d f8 | \verses{,,,\beginmel}\ ((b f4 \verses{,,,\endmel}\ e4d ) \verses{,\beginmel,,}\ ((b da1 \verses{,\endmel,,}\ da ) | d4 f d | d2d ||
m3400   c-4 c   c  | \verses{,,,\beginmel}\ ((b d4 \verses{,,,\endmel}\ d4d ) \verses{,\beginmel,,}\ (b da1 \verses{,\endmel,,}\ da1 ) | d+4 d- d | g2d ||

%%L3
% Bar 11-13
[  \verses{,\lyroffset{-1},,}\ d-8 b+ ] b4d c8 | b4d a8 a4 | g2 r4+0 |
C: d   gg   ag   f  fd  rb  
L: fein sein, bei-nan-der blei-bn,
L: gscheit sein, nit ei-ni-tap-pn,
L: frisch sein, nit um-ma-mok-kn,
L: treu sein, nit au-\ss{}i-gra-sn,
 d4  d4d e8 | d4d c8 c4 | b2 r4+0 |
 g4  g4d g8 | d4d d8 d4 | g2 r4b  |

% Bar 14-16
[  \verses{,\lyroffset{-1},,}\ b8 d ] d4d e8 | d4d c8 c4 | b2 |]
C: g  b   b   cb   a  ag  
L: fein sein, bei-nan-der blei-bn.
L: gscheit sein, nit ei-ni-tap-pn.
L: frisch sein, nit um-ma-mok-kn.
L: treu sein, nit au-\ss{}i-gra-sn.
[ d8 g ] g4d g8 | f4d d8 d4 | d2 |]
 g4 g4d g8 | d4d d8 d4 | g2 |]
%%%
%
% Note:
%
% I changed the definition of \setlyrstrut in my copy of musixlyr.tex
% (version MusiXLYRics 2.1c )
%
% \def\setlyrstrut{% set up strut according to currently active font
%   \setbox0=\hbox{(\"Ag)}%
%   \setbox\lyrstrutbox=\hbox{\vrule height 1.1\ht0 depth 1.1\dp0 [EMAIL PROTECTED]
%
% The original had \hbox{()} which does not work for pncr font.
%
% Without this change in musixlyr.tex you may get zigzag lyrics lines.
% The following TeX command in a line before \setlyrstrut will help.
%
% %%\def\setlyrstrut{\setbox0=\hbox{(\"Ag)}\setbox\lyrstrutbox=\hbox{\vrule height 1.1\ht0 depth 1.1\dp0 width 0pt}}
%
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] M-Tx/MusiXLYR long words centered at melisma?

[Bodo Meissner]

Hello all,
as you can see in the result from attached file, the left adjustment of  
syllables at melismas does not look good if the syllable or word is  
longer than the space for the corresponding notes.

If you have problems with the TeX code after the Space: line you can  
remove it. I recommend leaving the following two lines because with the  
smaller default font the problem is not as good to see.

%%\font\elevenrm=pncr at 11pt\font\elevenbf=pncb at 11pt
%%\elevenrm\setlyrstrut
I fixed the positioning manually by shifting single lyrics lines with
\verses{,\lyroffset{-1},,}\
Unfortunately this does not work at the first word with the verse  
number. The \lyroffset shifts the verse number, not the word.

How can I left shift the word, leaving the number at it's position?
Suggested change for MusiXLYR:
The syllable or word at a melisma should be centered if it's longer  
than the space for the notes and if there is space to the left.
If the space is to small for centering, it should be left shifted as  
much as possible.

Bodo___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] increase vertical space lyrics

[Bodo Meissner]

Am 2004.06.04 10:55 schrieb(en) Brendan Macmillan:
I was thinking: maybe older releases of M-TX will compile OK - so I
should try the archives first, before putting you to trouble.
Hello Brendan,
if I have access to a machine with your OS (or a compatible one) it  
will take me only a few minutes to compile M-Tx.

BTW: I tried double-spacing the lyrics with the follow technique -  
but
it
didn't affect the lyric's vertical spacing either:
\linespread{1.4}
The lyrics lines are not typeset like lines of text in a [La]TeX  
document. I think the spacing of lyrics is affected only by the  
setlyrstrut macro which in it's default version is based on the size of  
characters ( and ) in the current font.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] increase vertical space lyrics

[Bodo Meissner]

Am 2004.06.04 05:19 schrieb(en) Brendan Macmillan:
I couldn't get M-Tx to compile - however, I have managed to get your
suggestion working (or half working) in another way:
Hello Brendan,
what OS do you have? I have access to some UNIX systems. Maybe I can  
compile it for you.

Unfortunately, it only affected the position of the lyrics without
affecting
the staves below - the result being a larger spacing between the
lyrics, but
now overlapping with the following stave (or the following paragraph
of text).
You can insert Space: commands in your M-Tx source to increase or  
decrease space between staves. (Or change the values if already  
present.)

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] Re: M-Tx bug in 0.54b and c (Was: horizontal shifting and partial beaming ?)

[Bodo Meissner]

Am 2004.05.06 16:08 schrieb(en) Olivier Vogel:

I tried to compile it with p2c (I typed make prepmxc),
but got an error. I join the message of error.
...
cc globals.o mtx.o preamble.o lyrics.o analyze.o mtxline.o status.o
uptext.o files.o notes.o prepmx.o cfuncs.o multfile.o utility.o
control.o -o prepmx
status.o(.text+0xbd4): In function `beginSlur':
: undefined reference to `strpos2'
status.o(.text+0xdc0): In function `endSlur':
: undefined reference to `strpos2'
collect2: ld returned 1 exit status
make: *** [prepmxc] Erreur 1
This seems to be an incompatibility between p2c, Makefile and
module cfuncs.c.
p2c procuces calls to function strpos2() when translating status.pas.  
This function is in libp2c.a. (Maybe an earlier version of p2c did not  
use this function or the Pascal code did not use a construction which  
gets translated to this function.)
When I try to link the program with -lp2c I get errors about multiple  
definition of PASCAL_MAIN, P_eof, _Escape, _EscIO and _EscIO2 which are  
defined in cfuncs.c and in libp2c.a.

I think either these functions should be removed from cfuncs.c and the  
program be linked with -lp2c or the missing function should be added to  
cfuncs.c and cfuncs.h.

I solved this on my system by using an additional file strpos2.c with  
the missing function which I created after looking at the source code  
of p2c.

#include 

int strpos2(char *s, char *pat, int pos)
{
   char *cp, *cp2;
   if (--pos < 0) return 0;
   if(strlen(s) < pos) return 0;
   cp = s + pos;
   cp2=strstr(cp, pat);
   if(cp2 == NULL) return 0;
   return cp2-s+1;
}
This function could be inserted into cfuncs.c and a prototype into  
cfuncs.h.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] M-Tx bug in 0.54b and c (Was: horizontal shifting and partial beaming ?)

[Bodo Meissner]

Am 2004.05.06 13:41 schrieb(en) Olivier Vogel:
Le jeu 06/05/2004 à 13:33, Bodo Meissner a écrit :

> I think this is a bug in M-Tx 0.54. It occured to me with M-Tx
> 0.54b and c last week. It seems to be fixed in 0.55. That's why I
> didn't tellit on the mailing list.
>
> Source:( c4 b ) r+0
> results
> M-Tx 0.52: c4 s b4 s r4+0
> M-Tx 0.54b/c:  c4 s b4 s r0+
> M-Tx 0.55: (S c4 b4 )S r4+0
That's strange, because I use M-Tx 0.55 too! And the error is  
deplored
by M-Tx: it displays:

==> This is M-Tx 0.55 (Music from TeXt) <30 April 2004>
==>> Input from file essai.mtx
Writing to essai.pmx
instrumentNames = TRUE
In voice "T1" near word 5:
  V
   Bar end occurs in mid-note: ERROR on line 64
( c4 b4 ) r0+
This error is printed by M-Tx in the original score because it thinks  
this is a whole rest instead of a quarter rest. For testing I made this  
input file:

Style: Singer
Flats: 3
Meter: 0/4
c4

( c4 b ) r+0

With this input M-Tx does not care about note lengths and always
produces a .pmx file. PMX prints an arror with the file generated by
M-Tx 0.54.
My version of M-Tx 0.55 which I compiled myself on Linux with p2c  
1.21alpha2-2 and gcc 3.3.3 does not print an error and produces a  
correct .pmx file.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] Fwd: Re: horizontal shifting and partial beaming ?

[Bodo Meissner]

Am 2004.05.06 12:47 schrieb(en) Olivier Vogel:

I just got a problem for typesetting your code: I had to change the
code r+0 to r4+0 in the measure 8.
Hello Olivier,

I think this is a bug in M-Tx 0.54. It occured to me with M-Tx 0.54b  
and c last week. It seems to be fixed in 0.55. That's why I didn't tell  
it on the mailing list.

Source:( c4 b ) r+0
results
M-Tx 0.52: c4 s b4 s r4+0
M-Tx 0.54b/c:  c4 s b4 s r0+
M-Tx 0.55: (S c4 b4 )S r4+0
Personally, I prefer to code the following for the names of the  
voices:

Name: \vbox{\hbox{T$\,$1}\hbox{T$\,$2}}
\vbox{\hbox{B$\,$1}\hbox{B$\,$2}}
(all must be on the same line of course)
Great! I always wanted to have that but didn't find out how to code it  
and didn't find an example.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] Re: Triplets: horizontal shifting and partial beaming ?

[Bodo Meissner]

Hello Olivier,

thank you for your help.
Attached (I hope) is my result with your suggestions included.
I copied the inline TeX code to one more place and used a negative hard
space to left shift the other note.
BodoTitle: Berggeboren
%Composer: 
%Poet: 
Style: TTBB
TTBB: Voices T1,T2 B1,B2; Choral; Clefs G8 F;
Name: T B
Indent: 0.05
Flats: 3
Meter: 3/4
Pages: 1
Systems: 3
Space: 8 6
Start: ;@+2
%%\input plainenc\relax\inputencoding{latin1}
%%\voffset=-2cm
%%\font\eightrm=pncr at 8pt\font\eightit=pncri at 8pt
%%\font\tenrm=pncr at 10pt\font\tenit=pncri at 10pt 
%%\font\twelverm=pncr at 12pt\font\twelvebf=pncb at 12pt\font\BIGfont=pncb at 
18pt\font\Bigfont=pncr at 12pt
%%\twelverm\setlyrstrut
%%\def\myverA{{\tenit M-Tx} \mtxversion\ {\eightrm\mtxdate}, PMX \pmxversion\ 
{\eightrm<\pmxdate>} und }
%%\def\myver{\myverA\musixtex\ \mxversion\ {\eightrm<\mxdate>}}
%%\def\myft{\tenrm Notensatz: Bodo Meißner mit \myver}
%%\let\sav\Endpiece
%%\def\Endpiece{\sav\vfill\noindent\myft\def\vfill{\vskip5mm}}

{vers}
Berg-ge-bo-ren ist mein Lied,
wie ein Sturz-bach reißt es mit
je-des Hemm-nis, je-den Schmerz.
Sin-ge nur, sin-ge nur! 
Sin-ge, sin-ge mein Herz!

%%w195m
%%h290m
%%Iipipit70
%%ArpT
% Bar 0-2
\let\oldcu\cu\ibu4{4}{-2}\def\cu#1{\qb4{#1}}\ b4ax3 \def\cu#1{\tbu4\qb4{#1}}\ g 
\let\cu\oldcu\ b | e4d d8 c g | b2 \let\oldcu\cu\ibu4{4}{-2}\def\cu#1{\qb4{#1}}\ c4ax3 
\def\cu#1{\tbu4\qb4{#1}}\ bs \let\cu\oldcu\ c |
\let\oldcl\cl\ibl3{4}{-2}\def\cl#1{\qb3{#1}}\beginmel\ b4ax3n+1 
\def\cl#1{\tbl3\qb3{#1}}\endmel\ g \let\cl\oldcl\ b | e4d d8 c g | b2   a4x3Dn+1   
a |
L: {vers}
\let\oldcu\cu\ibu2{9}{-2}\def\cu#1{\qb2{#1}}\ b4ax3nf-1 \def\cu#1{\tbu2\qb2{#1}}\ g 
\let\cu\oldcu\ b | e4d d8 c g | b2   f4x3D XS-1 f |
\let\oldcl\cl\ibl1{9}{-2}\def\cl#1{\qb1{#1}}\ b4ax3nf \def\cl#1{\tbl1\qb1{#1}}\ g 
\let\cl\oldcl\ b | e4d d8 c g | b2 f4x3Dn-2s+2e |
%
% simpler version with slurs instead of beams
%( b4ax3   g ) b | e4d d8 c g | b2 ( c4ax3 bs )c |
%( b4ax3   g ) b | e4d d8 c g | b2   a4x3D a |
%L: {vers}
%( b4ax3nf g ) b | e4d d8 c g | b2   f4x3Dn+1 XS-1 f |
%( b4ax3nf g ) b | e4d d8 c g | b2   f4x3Dn-2s+2   e |

% Bar 3-4
f4d d8 c8d b1 | g+2 g8 f |
a4d a8 a8d a1r | b2 d8f d |
[ f8 e d ] f f8d f1 | e2 b+8 b |
[ d8 c b ] b c8d d1 | e2 e8 f |

% Bar 5-7
f4  es e8n df | c2  r4+0 |   ( c4   f4d )   d8 |
d4f c  b8  b  | b2r r4b  |  (t a2 a8 )t a |
b4  b  g8  g  | g2  r4+0 | ( [ f8 e f e ] g )+0+0-1   f |
g4  g  g8  f  | e2s r4b  | ( [ f8 e d c ] b )   b |

% Bar 8-10
( c4 b ) r+0 |   g+2g4   | ( g   f ) r4+0 |
  a2 r4b | ( b4  e )  [ d8 d8f ] |   c2  r4b  |
( e4 d ) r+0 | ( e4  b+ )   b| ( b   a ) r+0  |
  b2 r4b |   e2re4   |   a-2 r4b  |

% Bar 11-13
rpb|   b2  g8d of  f1 | e2 |]
( f4d e8 ) [ d c ] |   d2  d8d d1 | b2 |]
rp+0   | ( f4 c+ ) b8d a1 | g2 |]
rpb|   b2  b8d ofd b1 | e2 |]
%
%%%
%
% Note:
%
% I changed the definition of \setlyrstrut in my copy of musixlyr.tex 
% (version MusiXLYRics 2.1c )
%
% \def\setlyrstrut{% set up strut according to currently active font
%   \setbox0=\hbox{(\"Ag)}%
%   \setbox\lyrstrutbox=\hbox{\vrule height 1.1\ht0 depth 1.1\dp0 [EMAIL PROTECTED]
%
% The original had \hbox{()} which does not work for pncr font.
%
% Without this change in musixlyr.tex you might need the following
% TeX command in a line before \setlyrstrut (with only 2 % instead of 3)
%
%%%\def\setlyrstrut{\setbox0=\hbox{(g)}\setbox\lyrstrutbox=\hbox{\vrule height 1.1\ht0 
depth 1.1\dp0 width 0pt}}
%___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] Triplets: horizontal shifting and partial beaming ?

[Bodo Meissner]

Hello all,

is it possible to horizontally shift a note in an triplet?
(I use PMX 2.501 / M-Tx 0.55)
When I try option "r" (Right offset by one notehead) PMX complains with

ERROR in line 47, bar 2 Illegal option on xtuplet note
v
b2 f4x3Dn-2s+2 er | //
relevant parts of preamble:

Style: TTBB
TTBB: Voices T1,T2 B1,B2; Choral; Clefs G8 F;
Flats: 3
Meter: 3/4
input block without the "r" option:

%%ArpT
% Bar 0-2
( b4ax3   g ) b | e4d d8 c g | b2 ( c4ax3 bs )  c |
( b4ax3   g ) b | e4d d8 c g | b2   a4x3D   a |
L: Berg-ge-bo-ren ist mein Lied, wie ein
( b4ax3nf g ) b | e4d d8 c g | b2   f4x3Dn+1f |
( b4ax3nf g ) b | e4d d8 c g | b2   f4x3Dn-2s+2 e |
Second question:
Is it possible to partially beam a triplet?
I would like to reproduce an old handwritten original which in bar 0  
and 2 have beams instead of slurs with triplet brackets above/below two  
beamed and one unbeamed note like this:

_
|3|
 ___
|   |   |\
|   |   |
o   o   o
Berg - ge - bo - ren ...

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] zigzag lyrics lines with M-Tx

[Bodo Meissner]

Am 2004.04.30 09:17 schrieb(en) Christof Biebricher:

I had plenty of errors in processing your file. Some are obvious:
\Satz: instead of /Satz.
Hello Christof,

I can compile this file without errors. Maybe I used some code which  
does not work in all environments.

In my version with "\\Satz" I get
Johann Hedwig
 Satz: E. H. Chrestel
which is what I want. When I replace it with /Satz, I get
 Johann Hedwig/Satz: E. H. Chrestel
Furthermore, I converted the German umlaut
into the usual Tex-encoding and everything processed normally, and
the lyric alignment was fine.
I intentionally used German umlauts in combination with "\input  
plainenc\relax\inputencoding{latin1}" as described in  
http://icking-music-archive.org/software/pmxtricks/accents.pdf

Maybe you would need some package files
I just converted all umlauts to TeX-encoding in a copy of my file and  
get zigzag lyrics lines as well.

Maybe the problem depends on the program and macro package versions.

Could you, please, send me your changed version of my source and the
.log file of your compilation.
Bodo

___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [TeX-music] zigzag lyrics lines with M-Tx

[Bodo Meissner]

Hello Olivier,

it's much better with your version of the lyrstrutbox code.
The important thing seems to be that \setlyrstrut is called after  
changing the font. (With increased spacing looks better.)

But the zigzag problem is not completely solved. I can still see it  
when I use a ruler on the printed score or in xdvi with full size.
(Christian Mondrup also told me this in personal mail.)

It might be that the problem is related to the version of the programs  
and macro packages used. I will do some comparisons of scores I  
produced one or two years ago compiled with current and older versions.

Bodo
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

[TeX-music] zigzag lyrics lines with M-Tx

[Bodo Meissner]

Hello all,

in the attached example the lyrics lines are not vertically aligned.  
It's the first time this problem occurs to me. It seems to be specific  
to this score, because I cannot reproduce it with other scores I made  
before.

I tried a lot of things which do not help:
- remove the font selection
- change font size
- change values in Space: and Start:
- increase spacing between lyrics lines with \lyrstrutbox
The wrong positioning is most obvious in bar 5 at
"Gür-tel der Kar-pa-ten" or "in dei-ner Schö-ne"
It seems to get worse when increase spacing between lyrics lines.

Is there something wrong with my code?

Bodo

-
Program and package versions:
==> This is M-Tx pre0.54c (Music from TeXt) <15 August 2003>
...
=== RUNNING PMX  ===
This is PMX, Version 2.501, 26 Feb 04
...
=== RUNNING MUSIXTEX: 1st pass (tex) ===
This is TeX, Version 3.14159 (Web2C 7.4.5)
(./siebenbuergen.tex (/usr/share/texmf/tex/musixtex/mtx/mtx.tex
mtx.tex 0.54c <15 August 2003>
M-Tx pre0.54c (Music from TeXt) <<15 August 2003>>
(/usr/share/texmf/tex/musixtex/base/musixtex.tex
MusiXTeX(c) T.112 <3 Jan. 2003>
) (/usr/share/texmf/tex/musixtex/pmx/pmx.tex
PMX, a Preprocessor for MusiXTeX, Version 2.5a <15 February 04>
) (/usr/share/texmf/tex/musixtex/musixlyr/musixlyr.tex
MusiXLYRics 2.1c 
)
=== end of mtx.tex ===
) (/usr/share/texmf/tex/generic/vietnam/plainenc.tex
(/usr/share/texmf/tex/generic/babel/plain.def)
(/usr/share/texmf/tex/latex/base/inputenc.sty))
(/usr/share/texmf/tex/latex/base/latin1.def)
(/usr/share/texmf/tex/musixtex/base/musixtex.tex)
(/usr/share/texmf/tex/musixtex/pmx/pmx.tex)
(/usr/share/texmf/tex/musixtex/base/musixmad.tex
(/usr/share/texmf/tex/musixtex/base/musixadd.tex
MusiXADDitional instruments T.99 <24 March 2000>
)
MusiXMore ADditional instruments T.99 <24 March 2000>
) bar 0 bar 1 bar 2 bar 3 bar 4 bar 5 bar 6 bar 7 bar 8 bar 9 bar 10  
bar 11
bar 12 [1]
Memory usage before: 18502&34564; after: 243&33689; still untouched:  
943457
)
Output written on siebenbuergen.dvi (1 page, 12016 bytes).
Transcript written on siebenbuergen.log.
Discarding siebenbuergen.dvi
=== RUNNING MUSIXTEX: 2nd pass (musixflx) ===

<<< musixflex 0.83/T.63dt+jh.2 >>>
...
Title: Siebenbürgen
Composer: Johann Hedwig\\Satz: E. H. Chrestel
Poet: Max Moltke
Style: SATB
Name: S/A T/B
Indent: 0.05
Sharps: 1
Meter: 3/4
Pages: 1
Systems: 3
Space: 12 6
Start: ;@+1
%%\input plainenc\relax\inputencoding{latin1}
%% vertical alignment of lyrics gets worse with this extra spacing %%
%\setbox\lyrstrutbox=\hbox{\vrule height 1.3em width 0pt}
%%\voffset=-2cm
%%\font\tenrm=pncr at 10pt\font\tenit=pncri at 10pt
%%\font\twelverm=pncr at 12pt\font\twelvebf=pncb at 12pt
%%\font\BIGfont=pncb at 20pt\font\Bigfont=pncr at 14pt
%%\twelverm
%% commented out, not necessary to reproduce problem %%
%\def\myfoot{\tenrm Notensatz: Bodo Meißner mit {\tenit M-Tx}, PMX und \musixtex}
%\let\sav\Endpiece
%\def\Endpiece{\sav\vskip5mm\input siebenb-text\vfill\noindent\myfoot}

{vers1}
1. Sie-ben-bür-gen, Land des Se-gens,
Land der Fül-le und der Kraft, 
mit dem Gür-tel der Kar-pa-ten
um das grü-ne Kleid der Saa-ten,
Land voll Gold und Re-ben-saft,
Land voll Gold und Re-ben-saft!

{vers2}
2. Sie-ben-bür-gen, Mee-res-bo-den
ei-ner längst ver-floss-nen Flut,
nun ein Meer von Äh-ren-wo-gen,
des-sen U-fer, wald-um-zo-gen,
an der Brust des Him-mels ruht,
an der Brust des Him-mels ruht.

{vers7}
7. Sie-ben-bür-gen, sü-ße Hei-mat,
un-ser teu-res Va-ter-land,
sei ge-grüßt in dei-ner Schö-ne
und um al-le dei-ne Söh-ne
schlin-ge sich der Ein-tracht Band,
schlin-ge sich der Ein-tracht Band!

%%w195m
%%h290m
%%Iipipit70
%%Ar
% Bar 0-1
b8 g | d+4 d a8 b | 
b8 g | f4  f f8 f | 
L: {vers1,vers2,vers7}
b8 g | a4  a c8 d | 
b8 g | d4  d d8 d | 

% Bar 2-3
g4 d g8 a |   b4d [ c1 b ] a8 g |
g4 d e8 f | ( d4 g8 ) [ a1 g ] e8 d |
b4 b b8 d | [ g8- b ] d4   c8 b |
g4 g e8 d |   g4  gg8 g |

% Bar 4-5
a2 d8- d |   g4d   b8  d  e |
f2 d8  d | [ d c ] [ b d ] g  g |
d2 a8  f |   g4d   g8  b  c |
d2 d8  c | [ b a ]   g4g8 g |

% Bar 6-7
[ d8 c ] b4 d8 e  |   c4d a8 d  c |
  f4 g  g8 g  | [ g e ] f4   a8 a |
[ b8 a ] d4 b8 c  |   a4d d8 d  d |
  d4+g  g8 a- |   d4df8 d |

% Bar 8-9
[ b8 c ] d4 g8- a | b4 b b8  b  |
[ g8 a ] b4 e8- f | g4 g f8  ds |
  d4 d  c8  d | d4 e b8  b  |
  g4 g  e8  d | g4 e ds8 b  |

% Bar 10-12
b2 [ g1 a ] [ b c ] | d4 d a8 b | g2 |]
g2 [ e1 f ] [ g a ] | f4 g f8 f | d2 |]
b2   b8   b | a4 b c8 d | b2 |]
e2   e8   e | d4 d d8 d | g2 |]
___
TeX-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music

Re: [Tex-music] Environment variables in RH Linux with g77

[Bodo Meissner]

Am 2004.01.14 13:55 schrieb(en) Bernhard Lang:

On UN*X systems it is more or less common practice to have user-local  
configuration files in the user's home directory as hidden files like  
".pmxrc".
...
By the way, I would let the choice to the user, how to name the  
config file, expecting the entire name including path to be given in  
the environment variable.
Hello Don,

maybe you should explain in detail how it's supposed to work.

If a single file is included in every .pmx input file without changing  
the input file I would agree with Bernhard's suggestion.
But I think a .pmx file depending on other files but not showing which  
one is not a good idea. It would be hard to find out what you need to  
compile such a file. That's why I'd prefer the second interpretation:

If you specify the file name to be included in the PMX input file then  
a variable telling the directory is perfect.
To me this seems similar to a "-I directory" option of a C compiler in  
combination with an "#include " in the C source code.
In this case the .pmx file does not contain the complete information  
needed to get the result, but it shows where to look for the missing  
parts.

Additional suggestions:

Maybe you should allow specifying more than one directory for .mod  
files similar to the PATH variable or similar to several "-I directory"  
options for a C compiler. (PMXMODPATH variable ?)
When searching for a .mod fiel it might be useful to first look in the  
directory where the .pmx is located and then in the specified directory  
(or path).

What about nested includes?

Seeing this as a simple preprocessor included in PMX, I think that  
conditional compilation depending on environment variables or PMX  
internal variables (e.g. number of voices) might be useful as well.

Bodo
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music