Re: [Tex-music] PMX: interference betweeen tuplets and dynamic marks
I cannot reproduce the error. What version of PMX are you running? Is the error
from PMX or from MusiXTeX? What is the error message? It might help if you
provide a screen shot of the messages being generated.
--Don Simons
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Dieter
> Sent: Thursday, February 21, 2019 8:29 AM
> To: tex-music@tug.org
> Subject: [Tex-music] PMX: interference betweeen tuplets and dynamic
> marks
>
> Dear PMXperts,
>
> the attached example runs only, when I remove the "Dp" in the bass voice.
>
> The "Dp" in the Alto works fine.
>
> Or in other words I cannot put a dynamic mark after the triplet.
>
> Regards
>
> Dieter
>
> ==
> =
>
> ---
> \input musixtex
> \input pmx
> \def\titlelines{\vbox{\smalltype\hbox{Text: Py B{\"a}ckman}\hbox{Musik:
> Stefan Nilsson}\hbox{K{\"o}rsats: Lars Wallen{\"a}s}}}
> ---
> % PREAMBLE
> % nstaves ninstr mtrnuml mtrdenl mtrnump mtrdenp
>4 4 4 44 4 % npickup (1 = 1/4-Note) nkeys
>0 -2
> % npages nsystems musicsize fracindent
>0 5 20 0.12
> Bass
> Tenor
> Alt
> Sopran
> b8tt
> .\
> % Body
> % Header
> Tc
> \titlelines
> Tt
> Gabriellas s\aa ng
>
> AbepI0.9
>
> %Bars 16-17
> b2x3 Dp b b b2 t | Rd b2 t r2 | /
> b2x3nf b b b2 t | b2 t r2 | /
> f2d Dp r8 b1- c | d4 g f2x3nf d b | /
> d2x3nf d d d2 t | d2 t r2 | /
>
> =
>
>
>
>
>
> ---
> 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
---
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] Musixtex
Hi, Rafael— If you use PMX to input your music, you can make a MIDI file. PMX is a preprocessor for MusiXteX which takes input in a much simpler language and produces a MusiXTeX file. But there are a number of steps you’d need to go through to do that: 1. Install TeX; 2. Install MusiXTeX; 3. Install PMX; 4. Learn the PMX input language. There are links and hints for doing all of that on the Icking web site, starting at http://icking-music-archive.org/software/htdocs/Getting_Started_Four_Scenar.html . If you run into trouble you can always ask for help on this mailing list. If you provide enough specific details about what you did and what went wrong, someone is likely to reply with a solution. You did mention LaTeX. LaTeX is an add-on to TeX, much like MusiXTeX is. There is absolutely no need for LaTeX in order to use MusiXTeX. The truth is that technically PMX can produce a MIDI file by itself, without having installed TeX or MusiXTeX. But you would not be able to see the score, so editing the MIDI file would be very difficult. Good luck! --Don Simons From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On Behalf Of Rafael N. Sent: Thursday, March 21, 2019 11:36 AM To: tex-music@tug.org Subject: [Tex-music] Musixtex Hey, i'm not sure if i should speak english or german, and because of that i will continue in english. I have a question about the musictex and musixtex. How do I get audio files with those packages and i would very appreciate it if you may send me an example code with a step by step guide because im new to latex and very depressed while trying to understand how all these different packages function and then i found out that they can also produce multiple audio-files, so pls i bet you i need help till the 26th March 2019. I hope you will read this fastly enough. have a great day Yours sincerely Rafael Neugebauer --- 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] PMX stem length error on beamed octave chords
This seems to fix it: ... Arb w60m [-6 g83 zg- a8+ za- ] b4+ zb- e4s ze- / b84e a8 g4 g4e // d2+ zd- c4+ zc- / But of course if I ever change the code in this area, then this would probably give a different result. I haven't done lots of checking, but I believe it's been the case since day 1 that beam positions are only based on main notes, and ignore chord notes. That would lead to lots of backward incompatibilities if I did change the code. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Dirk Laurie > Sent: Tuesday, April 09, 2019 9:56 AM > To: Werner Icking Music Archive > Subject: [Tex-music] PMX stem length error on beamed octave chords > > I can't believe I am the first person to report this. Yet the output for PMX > 2.73 > and PMX 2.82 looks the same. The non-beamed octave chords are perfect, > the beamed ones have their stem length wrong and therefore the beam > position too. > > I need this for something I am typesetting right now. i don't need a fix, a > workaround will do. > > > 2 -1 2 3 4 3 4 0.0 -2 1 1 20 0 > > 60 > ./ > Tc > PMX 2.73 > Tt > Beam Error > Arb w60m > g83 zg- a8+ za- b4+ zb- e4s ze- / > b84e a8 g4 g4e // > d2+ zd- c4+ zc- / > > > The attached .pmx file contains the same PMX code. > > -- Dirk --- 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] PMX stem length error on beamed octave chords
Dirk Laurie wrote
> Op Di. 9 Apr. 2019 om 20:00 het Don Simons < <mailto:dsim...@roadrunner.com>
> dsim...@roadrunner.com>
> geskryf:
> >
> > This seems to fix it:
> >
> > ...
> > Arb w60m
> > [-6 g83 zg- a8+ za- ] b4+ zb- e4s ze- / b84e a8 g4 g4e //
> > d2+ zd- c4+ zc- /
>
> Thanks.
>
> > I haven't done lots of checking, but I believe it's been the case since day
> > 1
> that beam positions are only based on main notes, and ignore chord notes.
>
> I don't think that can be the reason. If I change the line to
>
> g82 zg+ a8- za+ b4- zb+ e4s ze+ /
>
> the lower notes are now the main notes, but the result is as attached.
> The stems are to the left of the noteheads, i.e. downward, but they are
> correct for the chord notes, not the main notes.
Hmmm. After a little more checking, I'd say that the beaming commands PMX sends
to MusiXTeX are the same as if the chord notes weren't there. The reason the
stems got shifted to the left is buried somewhere in MusiXTeX's handling of the
chordal notes when they come out on the opposite side of the beam from the main
notes. Here's a slightly modified example.
[ e82 zg+ f8- za+ ] e- f [ e82 zg f8 za+ ]
\pnotes{2.00}\ibu1E1\zq{'G}\qb1{`E}\zq{''A}\tbu1\qb1{``F}\ibu1E1\qb1E%
\tbu1\qb1F\ibu1E1\zq G\qb1E\zq{''A}\tbu1\qb1{``F}\en%
The beam initiation and termination commands are the same for each beam.
Given that this has been going on forever, and because there’s a
straightforward work-around using PMX’s manual beam height and slope tweaks,
I’m not highly motivated to upgrade PMX’s logic to deal with it.
--Don
---
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] PMX: switch to smaller notes type (German "Stichnoten")
I finally figured out that you’re asking about cue notes. Short answer: it’s
not easy. You have to use inline TeX. There are some macros in pmx.tex that
simplify some things a little bit:
\def\smno#1{\off{.17\qn@width}\tinynotesize#1\normalnotesize\off{-.17\qn@width}}%
\def\pmno#1{\roffset{.08}{\smallnotesize#1\normalnotesize}}%
\def\smq#1{\smno{\zql{#1}}}\def\smc#1{\smno{\zcl{#1}}}%
\def\smh#1{\smno{\zhl{#1}}}%
But you’re going to have to do some work to get horizontal spacing right for
your example, since while \smno makes the notes small, it uses the \noteskip
that’s already been set. Here’s a short example you should study, extracted
from my published edition of Nicola Matteis “Ayres for Violin, the Fourth Part”:
=
1 1 2 4 0 6 0 0
1 2 20 0.08
t
.\
\smh0\islurd34\ bd44u [u c1 \tslur36\ d ] /
% Bar 1-5
\\\advance\barno-1\
m4400
\smh0\ c25u r8 [u c su+6-.3 \smq0\ b c1 b s+7+.5 ] |
\smh0\ a2 r1 [u a su+8-.3 b c ] \smq{-1}\ bd8 os-1 a1 s+8+.5 |
\smh{-3}\ gs2 r8 [u b \smc0\ bd s c3 d s ]
\smh0\ c2u r1 [u c s d e ] \smq{-1}\ [u dd8 c1 s ]
\smh{-1}\ b2u r8 [u g85 \smc6\ fd os e1 ] /
% Bar 6-10
\smh5\ e25u r4 \smno{\ibl43{-6}\zqbp45}\ [u ad8 \smno{\tbbl4\tbl4\zqb41}\ a14 ]
\smh1\ b2u r8 \smc0\ [u c \smq{-1}\ cd os b1 ] \smh0\ c2u r4 \smq7\ g45u
\smh6\ g2u r8 gu \smq5\ [u fs s e1 f s ]
\smh4\ g2u r4 \smq4\ [u gd8 s fnc1 s ] /
=
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Wednesday, April 10, 2019 12:46 AM
To: tex-music@tug.org
Subject: [Tex-music] PMX: switch to smaller notes type (German "Stichnoten")
How could I do this in PMX?
Thanks
Dieter
---
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] PMX: switch to smaller notes type (German "Stichnoten")
First, good job simplifying the procedure for making notes smaller.
As for shrinking the spacing, once again I have a klunky answer but not a good
one. The PMX command X can be used with a negative argument, so for example
X-.5 will shrink the local space by 0.5 notehead widths. Problem is that you’d
need to put in a separate one of these in EVERY space you wanted to shrink, and
if you wanted to maintain the right scaling, you’d need different amounts of
shrinkage for different length notes. Maybe Andre can come up with a better way
:).
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Thursday, April 11, 2019 4:56 AM
To: tex-music@tug.org
Subject: Re: [Tex-music] PMX: switch to smaller notes type (German "Stichnoten")
Hi Don,
Thanks for your rapid help.
I 'm sorry for being so imprecise. What I really wanted is this:
This is an excerpt from the 1st violin of the 1st Symphonie of Mahler.
Is there a way to compress the cue notes horizontally?
Regards, Dieter
---
\input musixtex
\input pmx
\let\tny\tinynotesize
---
1 1 4 4 0 6 0 -1
0 2 20 0.08
t
.\
Abep
w120m
h
Pi\`{u} mosso
\tny\ \zcharnote{10}{(trmp.)}\ r8d \tny\ a34 zfs \tny\ a zf \tny\ a4x3n+12 zf
f zd a+ zf \tny\
[u d45x3 zf- a d zf- ] \tny\ [u e45x3 za- d zf- e+ za- ] /
\\\advance\barno-1\
r4 a45 Dff r2+1//
\tny\ [ d85 zfs \tny\ r1 \tny\ f1 za ] r2db /
===
Am 10.04.2019 um 18:12 schrieb Don Simons:
I finally figured out that you’re asking about cue notes. Short answer: it’s
not easy. You have to use inline TeX. There are some macros in pmx.tex that
simplify some things a little bit:
\def\smno#1{\off{.17\qn@width}\tinynotesize#1\normalnotesize\off{-.17\qn@width}}%
\def\pmno#1{\roffset{.08}{\smallnotesize#1\normalnotesize}}%
\def\smq#1{\smno{\zql{#1}}}\def\smc#1{\smno{\zcl{#1}}}%
\def\smh#1{\smno{\zhl{#1}}}%
But you’re going to have to do some work to get horizontal spacing right for
your example, since while \smno makes the notes small, it uses the \noteskip
that’s already been set. Here’s a short example you should study, extracted
from my published edition of Nicola Matteis “Ayres for Violin, the Fourth Part”:
=
1 1 2 4 0 6 0 0
1 2 20 0.08
t
.\
\smh0\islurd34\ bd44u [u c1 \tslur36\ d ] /
% Bar 1-5
\\\advance\barno-1\
m4400
\smh0\ c25u r8 [u c su+6-.3 \smq0\ b c1 b s+7+.5 ] |
\smh0\ a2 r1 [u a su+8-.3 b c ] \smq{-1}\ bd8 os-1 a1 s+8+.5 |
\smh{-3}\ gs2 r8 [u b \smc0\ bd s c3 d s ]
\smh0\ c2u r1 [u c s d e ] \smq{-1}\ [u dd8 c1 s ]
\smh{-1}\ b2u r8 [u g85 \smc6\ fd os e1 ] /
% Bar 6-10
\smh5\ e25u r4 \smno{\ibl43{-6}\zqbp45}\ [u ad8 \smno{\tbbl4\tbl4\zqb41}\ a14 ]
\smh1\ b2u r8 \smc0\ [u c \smq{-1}\ cd os b1 ] \smh0\ c2u r4 \smq7\ g45u
\smh6\ g2u r8 gu \smq5\ [u fs s e1 f s ]
\smh4\ g2u r4 \smq4\ [u gd8 s fnc1 s ] /
=
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Wednesday, April 10, 2019 12:46 AM
To: tex-music@tug.org <mailto:tex-music@tug.org>
Subject: [Tex-music] PMX: switch to smaller notes type (German "Stichnoten")
How could I do this in PMX?
Thanks
Dieter
---
TeX-music@tug.org <mailto: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
--
Dr. Dieter Glötzel
Im Rosengarten 27
64367 Mühltal
Tel.: 06151 / 360 82 72
---
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] PMX: switch to smaller notes type (German "Stichnoten")
I'm not familiar with \boxit or \circleit and I'm not sure what you mean by "rehearsal marks". Maybe an example would help. But if they're text, you can put them anywhere you want using the D"..." command with vertical and horizontal shift options. --Don >Hi Don, >it is amazing how easy it is to use the cue notes with PMX. >I will try and fiddle a bit with the X-command. May I ask another question? >I try using \boxit or \circleit in PMX for rehearsal marks. But they always >drop inside the stave. How could I move these boxes above stave? >Or is there another solution. >Regards, Dieter --- 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] PMX: Changing of numbers of instruments
Excellent bug and bug report! I haven't solved it yet, but it goes away if you
only replace the last line of movement 3 with r0 | c04 /. So there's some very
subtle problem with the way PMX is handling centered whole-bar rests. More as
it develops.
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Dirk Baack
> Sent: Friday, April 12, 2019 3:12 AM
> To: Werner Icking Music Archive
> Subject: [Tex-music] PMX: Changing of numbers of instruments
>
> Hello pmxXperts,
>
> for a very special note-setting project I need to change the (numbers
> of) instruments several times. First - according to appendix B5.8 of
> pmxccn.pdf (of the late Cornelius Noack) - I use a staff with (from lowest to
> top instrument, pseudo-code, ) [ b t ] { b t } t (later to be discarded
> "movement 1",[]/{} different
> accolades: {}: curly, []: angled )
> then
> [ b t ] ("movement 2")
> then
> [ b t ] { b t }("movement 3")
> then finally
> [ b t ] t ("movement 4")
>
> In my example there is a problem with pmx 2.87 and muisixtex 1.29 if I use all
> four movements: musixtex stops with "! Staff number (2) out of specified
> range (1)!." But without movement 3 (example below) everything is fine. If I
> change the first line of "movement 4" to "L4Mcn212bt"
> (with last line uncommented) it works.
>
> Thanks in advance for any help.
> Dirk
>
>
> PMX-code:
> --
> men Instr. log. Takt (Z/N) angez. Takt (Z/N) Auftaktschlaege Vorzeichen
> 5-4 1 1 2 1 4 4 4 40 -3
> % Seitenanzahl Systemanzahl Systemhöhe Ersttakteinrückung
> 2 4 20 0
> %
> Chor
> Chor
> Solochor
> Solo
> btbtt
> ./
> Av
> Ab
> Ar
> %
> \\grouptop{1}{2}\groupbottom{1}{1}\
> AK
> r0 | r0 Rd /
> r0 | r0 /
> r0 | r0 /
> r0 | r0 /
> r0 | r0 /
>
> L2P2Mcn212bt
> r0 | r r r r /
> r0 | r r r r /
>
> %L3Mcn3123btbt
> %r0 | r0 /
> %r0 | r0 /
> %r0 | r0 /
> %r0 | r0 /
>
> L4Mcn3124btt
> %L4Mcn212bt
> r0 /
> r0 /
> r0 /
> %r0 /
>
>
> ---
> 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
---
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] PMX: Changing of numbers of instruments
Dirk, I thought I at least had the cause narrowed down, but after looking at
your latest workaround with r0-1, I'm not so sure. Here's the simplest PMX I’ve
come up with that shows the problem:
==
4 -3 1 2 1 4 4 4 4 0 0
1 2 20 .1
Bottom
Middle2
Top
bbtt
.\
r0 /
r0 /
r0-1 /
r0 /
%
L2Mn213bt
r0 /
r0 /
=
This one works as is, but if you delete the -1 it fails. I had thought the
failure was related to the order that PMX does things between the two
movements. At the end of the first bar, it sets up \atnextbar to put in the
centered rests in that bar as soon as the barline is written. But before it
writes the barline, it changes the staff and instrument assignments to what's
needed for the new movement. So I thought that was what led to the problem. If
you look at the difference file pasted below, the ONLY difference is in one of
the centered rest commands, \liftpausc0 for the one that worked and \pause for
the one that failed. The separators & and | are exactly the same, in the same
order, along with EVERYTHING ELSE. It's only that one item being centered that
differs between the case that works and the one that doesn't.
TeXperts
One other comment: the \liftpausc has an argument of 0 because the PMX argument
for raising a rest is the number of notes, not staff lines, and so gets divided
by 2. Evidently -1/2 gets rounded to 0. If it weren’t for the slight
misalignment both horizontally and vertically in the final image, this would be
a PERFECT workaround.
--Don
> -Original Message-
> From: Dirk Baack [mailto:d...@baack-lamstedt.de]
> Sent: Friday, April 12, 2019 1:15 PM
> To: Don Simons
> Subject: Re: [Tex-music] PMX: Changing of numbers of instruments
>
> Am 12.04.19 um 20:39 schrieb Don Simons:
> > Excellent bug and bug report! I haven't solved it yet, but it goes away if
> > you
> only replace the last line of movement 3 with r0 | c04 /. So there's some very
> subtle problem with the way PMX is handling centered whole-bar rests.
> More as it develops.
> Thanks Don,
>
> and even r0b (instead of r0) and r0-1 in an second voice is a usable
> workaround.
>
> Dirk
>
>
> >
> > --Don
> >
> >> -Original Message-
> >> From: TeX-Music [mailto:tex-music-
> >> <mailto:bounces+dsimons=roadrunner@tug.org>
> >> bounces+dsimons=roadrunner@tug.org] On Behalf Of Dirk Baack
> >> Sent: Friday, April 12, 2019 3:12 AM
> >> To: Werner Icking Music Archive < <mailto:tex-music@tug.org>
> >> tex-music@tug.org>
> >> Subject: [Tex-music] PMX: Changing of numbers of instruments
> >>
> >> Hello pmxXperts,
> >>
> >> for a very special note-setting project I need to change the (numbers
> >> of) instruments several times. First - according to appendix B5.8 of
> >> pmxccn.pdf (of the late Cornelius Noack) - I use a staff with (from
> >> lowest to top instrument, pseudo-code, ) [ b t ] { b t } t (later to
> >> be discarded "movement 1",[]/{} different
> >> accolades: {}: curly, []: angled )
> >> then
> >> [ b t ] ("movement 2")
> >> then
> >> [ b t ] { b t }("movement 3")
> >> then finally
> >> [ b t ] t ("movement 4")
> >>
> >> In my example there is a problem with pmx 2.87 and muisixtex 1.29 if
> >> I use all four movements: musixtex stops with "! Staff number (2) out
> >> of specified range (1)!." But without movement 3 (example below)
> >> everything is fine. If I change the first line of "movement 4" to
> "L4Mcn212bt"
> >> (with last line uncommented) it works.
> >>
> >> Thanks in advance for any help.
> >> Dirk
> >>
> >>
> >> PMX-code:
> >> --
> >> men Instr. log. Takt (Z/N) angez. Takt (Z/N) Auftaktschlaege Vorzeichen
> >> 5-4 1 1 2 1 4 4 4 40 -3
> >> % Seitenanzahl Systemanzahl Systemhöhe Ersttakteinrückung
> >> 2 4 20 0
> >> %
> >> Chor
> >> Chor
> >> Solochor
> >> Solo
> >> btbtt
> >> ./
> >> Av
> >> Ab
> >> Ar
> >> %
> >>
> >> \\grouptop{1}{2}\groupbottom{1}{1}\
> >> AK
> >> r0 | r0 Rd /
> >> r0 | r0 /
> >> r0 | r0 /
> >> r0 | r0 /
> >> r0 | r0 /
> >>
> >> L2P2Mcn212bt
> >> r0 | r r r r /
> >> r0 | r r r r /
&g
Re: [Tex-music] PMX: xtuplets horizontal shift of notes
Finally an easy one. RTFM! (Section 2.3.9) = 1 1 2 4 2 4 0 0 1 1 20 0 t ./ w2i X1: c25x3 c c X: // d25x3 d d / --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Dirk Baack > Sent: Saturday, April 13, 2019 6:55 AM > To: Werner Icking Music Archive > Subject: [Tex-music] PMX: xtuplets horizontal shift of notes > > Hello PMXperts, > > is there any way to shift notes of a tuplet horizontally (e.g. for a two-voice > staff with c2x3 c c in lower voice and d2x3 d d in upper voice)? > > Thanks in advance > Dirk > --- > 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 --- 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
[Tex-music] A mystery for the TeXperts
I had hoped someone would resolve this when it arose in the recent thread
"PMX: Changing of numbers of instruments" but no one did. So I'm trying
again, with a boiled-down version of the puzzle, with all the PMX-specific
stuff stripped away. The following MusiXTeX file works OK as is, but if line
15 is replaced by line 16, it fails. The only thing that changes is the
argument of \centerbar within the \atnextbar command, from \liftpause0 to
\pause . I would very much appreciate having one of the TeXperts explain why
it works in one case but not the other.
--Don Simons
=
\input musixtex
\normalmusicsize%
\hsize=524pt
\vsize740pt
\def\nbinstruments{2}
\setstaffs12
\setclef1{60}
\setstaffs21
\setclef20
\generalsignature{ 0}%
\generalmeter{\meterfrac{4}{4}}%
\startmuflex\startpiece\addspace\afterruleskip%
% Bar count 1
\notes\wh{''C}|&\wh c\en%
\def\atnextbar{\znotes|\centerbar{\liftpause0}&%
%\def\atnextbar{\znotes|\centerbar{\pause}&%
% If above line is uncommented and one above that commented, fails.
\en}%
\setstaffs11%
\setclef10%
\def\nbinstruments{1}%
% Bar count 2
\stoppiece\startpiece
\notes\wh c\en%
\Endpiece
\vfill\eject\endmuflex
\bye
=
---
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] MusiXTeX/pmx sources
Bob Tennent wrote ... > Instead of duplicating IMSLP, for no evident benefit, I suggest that authors > can send sources for M-Tx, PMX, autosp or MusiXTeX processing to me for > inclusion in "contrib" > sub-directories of subsequent CTAN releases of those packages. They will > then be incorporated into TeXLive, MacTeX and (I think) MiKTeX. Hmmm, seems like a lot of extra baggage for Bob and for CTAN. Even if this didn't mean that to download a new release of MusiXTeX one would also have to download all of the sources that have ever been contributed, it still seems to me that the current system is just fine, where anyone who contributes a score to IMSLP can also include the source there if they choose to. --Don --- 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] MusiXTeX/pmx sources
maurizio .mau. codogno wrote >I agree that a section of sources would be very useful: as many have said, > it is easier not to start from scratch if you want to edit a piece of sheet > music. >(I would even accept abc sources!) But I also >think that it would be better >to >have it as a side section of IMSLP, so that all stuff stays in a single place. I'm still not convinced it's worth the effort. If someone has a particular piece in mind that they want the source for, they could just use the existing IMSLP system to look for scores of that piece, and then scan thru the listing so see if any of them comes with source files. However, if anyone really wants spend the effort go forward with this, maybe the goal should be not to create a separate repository for the source files, but simply to create a high-level "Sources" page leading to an index of only those specific scores that have source files, with links to the scores and source files in the current repository. The system could possibly make it possible to do a filtered search by source type. Along that line, I've just discovered that if you use the IMSLP search box and for example search forengraving files PMX , you get a very long list presumably containing all the IMSLP offerings accompanied by PMX source files. --Don --- 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] Problem with pmx file
I can't reproduce that error, and beyond that I'm very confused by it, because it refers to line 25, which appears to properly list the two clefs. It's doubly confusing because in the error message PMX should print out the line up to the point of the error. When I run PMX 2.84, I do get another sequence of errors later on, starting at line 63, where there's an obvious unnecessary and unpaired "[" . Maybe this has something to do with Windows vs UNIX and different line termination characters, in combination with the way that XML2PMX is writing the PMX file. But it still seems like we would have come across it before now. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Wednesday, April 24, 2019 3:57 PM > To: tex-music@tug.org > Subject: [Tex-music] Problem with pmx file > > Hi all... > > I get error when processing a pmx file: > > $ musixtex b_inv_01.pmx > This is musixtex.lua version 0.21. > This is PMX, Version 2.84 , 10 Feb 18 > Opening b_inv_01.pmx > > Starting first PMX pass > > > ERROR in line 25, bar 0 There should be a blank here >v > >^ > !! pmx processing of b_inv_01.pmx fails. > > > I'm attaching the file... Please help whoever can. > > Thanks, > > Rodolfo > --- 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
[Tex-music] Line-length challenge for the TeXperts
Can anyone come up with a cleaner way to shorten a single line…not necessarily
the last one on the page…in PMX (without trial and error)? If so I may
incorporate it into PMX.
--Don
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Thursday, April 25, 2019 10:03 PM
To: 'Dieter'
Subject: RE: PMX with Comments at the end of a line
Dieter--
OK, here's an example of one way to create a blank space at the end of a line
and then put some text in it. Since you need to tailor the width of the white
rectangle by trial and error, this would be tedious if you had to do it more
than once or twice, but it does work, without requiring any changes to the
basic page layout or staff widths. Let me know if you have any questions.
--Don
==
1 1 4 4 4 4 0 0
1 2 20 0
t
.\
\\input pstricks\
\\\def\gap{\
\\\psframe[linestyle=none,fillstyle=solid,fillcolor=white](-17pt,-1pt)(100pt,21pt)}\
c44 d e f g a b c /
L2
c44 d e f g a b c /
RD \gap\ rb0 D"Hello"+8-2 Rz /
==
> -Original Message-
> From: Don Simons [mailto:dsim...@roadrunner.com]
> Sent: Tuesday, April 23, 2019 8:43 AM
> To: 'Dieter' mailto:d.gloet...@web.de> >
> Subject: RE: PMX with Comments at the end of a line
>
> Hi, Dieter--
>
> I wondered why you were emailing me in German. I'm afraid I don't
> understand any of it.
>
> You can do anything with inline TeX, but it's usually difficult.
>
> The first question is whether you want the comments in the margin, or
> whether you want the music staff on that line to stop short. If you want it
> shortened, and if you are using postscript (which I always do) then there is a
> way to draw a solid white box anywhere using a package called pstricks,
> which may be included in MiKTeX. I know I've done this before but I haven't
> yet found the examples. If you want to shorten the staff but are not using
> postscript, then I'm afraid you'd need to figure out a way to end that staff
> early using inline MusiXTeX commands, and that would be tricky.
>
> If you want to pursue this on your own, maybe the above comments will
> help. If you want me to work on it, then please send more details about
> exactly what you want to do.
>
> --Don
>
> > -Original Message-
> > From: Dieter [ <mailto:d.gloet...@web.de> mailto:d.gloet...@web.de]
> > Sent: Tuesday, April 23, 2019 5:44 AM
> > To: Don Simons < <mailto:dsim...@roadrunner.com> dsim...@roadrunner.com>
> > Subject: PMX with Comments at the end of a line
> >
> > Hi Don,
> >
> > my last mail was sent off by mistake. Sorry!
> >
> > I was discussing with a friend, whether PMX would be able to support
> > comments at the end of an input line.
> >
> > Did you ever consider such an idea?
> >
> > Regards,
> >
> > Dieter
> >
> > --
> >
> > Dr. Dieter Glötzel
> > Im Rosengarten 27
> > 64367 Mühltal
> > Tel.: 06151 / 360 82 72
---
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] Line-length challenge for the TeXperts
Hi, Danai--
Thanks so much for looking into this. I've confirmed that I can process your
file and get the desired result. It's interesting to learn about another way to
draw filled boxes, using \vrule. And assuming that it would allow you to go
directly to a pdf from a dvi without using postscript, those people who choose
to bypass postscript will have a way to proceed. But it seems that to set it up
would still require some trial and error with the dimensions, just like my
pstricks version. What I would really like to see is a more basic approach that
would make the typeset staff shorter by a specified amount, and not require a
space-filling blank bar at the end or any other special extra input
information. In other words, a definition of a command
\shortenstaff{[distance]} . Doing that would require a deeper understanding of
the workings of the MusiXTeX commands for staff starts and stops than I have at
my fingertips, so for me it would mean a lot of work digging through
musixtex.tex.
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Danai SAE-HAN
> (???)
> Sent: Monday, April 29, 2019 2:09 PM
> To: Werner Icking Music Archive
> Subject: Re: [Tex-music] Line-length challenge for the TeXperts
>
> Hi Don
>
> You might want to try a simple TeX \vrule, combined with a colour from the
> `colordvi' package.
> I created the "\gapp" definition. You will notice that I have used some
> negative "\hskip" commands.
> Not sure if this was what you were looking for?
>
> =
> 1 1 4 4 4 4 0 0
> 1 2 20 0
>
> t
> .\
> \\input pstricks\
> \\input colordvi\
> \\\def\gap{\
> \\\psframe[linestyle=none,fillstyle=solid,fillcolor=white](-17pt,-
> 1pt)(100pt,21pt)}\
> \\\def\gapp{\
> \\\hskip -16pt\
> \\\White{\vrule height20.6pt width104.2pt depth0.5pt} \hskip -90pt}\
> c44 d e f g a b c /
> L2
> c44 d e f g a b c /
> RD \gapp\ rb0 D"Hello"+8-2 Rz /
> =
>
> You get the attached result.
>
> Regards
>
> --
> Danai
>
> On Sun, 28 Apr 2019 at 23:51, Don Simons
> wrote:
> >
> > Can anyone come up with a cleaner way to shorten a single line…not
> necessarily the last one on the page…in PMX (without trial and error)? If so I
> may incorporate it into PMX.
> >
> >
> >
> > --Don
> >
> >
> >
> > From: Don Simons [mailto:dsim...@roadrunner.com]
> > Sent: Thursday, April 25, 2019 10:03 PM
> > To: 'Dieter'
> > Subject: RE: PMX with Comments at the end of a line
> >
> >
> >
> > Dieter--
> >
> >
> >
> > OK, here's an example of one way to create a blank space at the end of a
> line and then put some text in it. Since you need to tailor the width of the
> white rectangle by trial and error, this would be tedious if you had to do it
> more than once or twice, but it does work, without requiring any changes to
> the basic page layout or staff widths. Let me know if you have any questions.
> >
> >
> >
> > --Don
> >
> >
> >
> > ==
> >
> > 1 1 4 4 4 4 0 0
> >
> > 1 2 20 0
> >
> >
> >
> > t
> >
> > .\
> >
> > \\input pstricks\
> >
> > \\\def\gap{\
> >
> > \\\psframe[linestyle=none,fillstyle=solid,fillcolor=white](-17pt,-1pt)
> > (100pt,21pt)}\
> >
> > c44 d e f g a b c /
> >
> > L2
> >
> > c44 d e f g a b c /
> >
> > RD \gap\ rb0 D"Hello"+8-2 Rz /
> >
> > ==
---
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] Line-length challenge for the TeXperts
Thanks, Andre! I’m glad someone has a much better memory than I do. This is
exactly what I was looking for. I’ll think about building it into PMX. But I
may get lost among all the \egroup, \bgroup, \hsize, and \hsize.
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Andre Van Ryckeghem
Sent: Monday, April 29, 2019 11:52 PM
To: Werner Icking Music Archive
Subject: Re: [Tex-music] Line-length challenge for the TeXperts
In 2017, Olivier Vogel made a coda.pmx file.
It shows a method to make blank at the end of a staff (bar32) and also at the
beginning (bar33).
Andre
From: Don Simons
Sent: Sunday, April 28, 2019 5:51 PM
To: 'Werner Icking Music Archive'
Subject: [Tex-music] Line-length challenge for the TeXperts
Can anyone come up with a cleaner way to shorten a single line…not necessarily
the last one on the page…in PMX (without trial and error)? If so I may
incorporate it into PMX.
--Don
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Thursday, April 25, 2019 10:03 PM
To: 'Dieter' mailto:d.gloet...@web.de> >
Subject: RE: PMX with Comments at the end of a line
Dieter--
OK, here's an example of one way to create a blank space at the end of a line
and then put some text in it. Since you need to tailor the width of the white
rectangle by trial and error, this would be tedious if you had to do it more
than once or twice, but it does work, without requiring any changes to the
basic page layout or staff widths. Let me know if you have any questions.
--Don
==
1 1 4 4 4 4 0 0
1 2 20 0
t
.\
\\input pstricks\
\\\def\gap{\
\\\psframe[linestyle=none,fillstyle=solid,fillcolor=white](-17pt,-1pt)(100pt,21pt)}\
c44 d e f g a b c /
L2
c44 d e f g a b c /
RD \gap\ rb0 D"Hello"+8-2 Rz /
==
---
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] Line-length challenge for the TeXperts
Bob Tennent wrote
> Hi Don.
>
> Here's how to do this in musixtex, based on Olivier's coda.pmx. Notice
there
> are *three* groups of special commands, before and after the "short"
> system, and then after the 2nd short system (or text after the short
system).
With great thanks to Bob, Andre, and Olivier, I've figured out how to get a
shorter line in a much more satisfying way than drawing a white box to
create a blank. Of course if my example below went further on, I'd need to
restore the definition of \alaligne. And other changes would be needed for a
mid-line blank. Now that I understand these techniques better I'll think
about incorporating them directly into PMX, where in response to new PMX
commands I could do it directly (like in Bob's example) rather than
redefining \alaligne.
--Don
==
1 1 4 4 4 4 0 0
1 3 20 0
t
.\
Abp
c44 d e f g a b c /
\\\def\alaligne{\
\\\stoppiece\hbox to\hsize\bgroup\vbox\bgroup\hsize=.6\hsize\
\\\startpiece\addspace\afterruleskip}\
L2
c44 d e f D"Hello"+8+15 Rr /
\\\def\alaligne{\
\\\endpiece\egroup\egroup\
\\\startpiece\addspace\afterruleskip}\
L3
c44 d e f g a b c /
==
---
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] Line-length challenge for the TeXperts
Can anyone figure out how to keep PMX's default bar numbering in the
line-shortening example. Here's a slightly modified version that shows the
problem more clearly. Notice that the bar numbers return after the shortened
line, although the number needs to be corrected.
1 1 4 4 4 4 0 0
1 6 20 0
t
.\
\\let\oldalaligne\alaligne\
Abp
c44 d e f g a b c c b a g f e d c /
\\\def\alaligne{\
\\\endpiece\hbox to\hsize\bgroup\vbox\bgroup\hsize=.6\hsize\
\\\startpiece\addspace\afterruleskip}\
L4
c44 d e f D"Hello"+8+15 Rr /
\\\def\alaligne{\
\\\endpiece\egroup\egroup\
\\\startpiece\addspace\afterruleskip\let\alaligne\oldalaligne}\
L5
c44 d e f g a b c /
c44 d e f g a b c /
===
Thanks,
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Don Simons
Sent: Thursday, May 02, 2019 8:52 AM
To: 'Werner Icking Music Archive'
Subject: Re: [Tex-music] Line-length challenge for the TeXperts
Bob Tennent wrote
> Hi Don.
>
> Here's how to do this in musixtex, based on Olivier's coda.pmx. Notice
there
> are *three* groups of special commands, before and after the "short"
> system, and then after the 2nd short system (or text after the short
system).
With great thanks to Bob, Andre, and Olivier, I've figured out how to get a
shorter line in a much more satisfying way than drawing a white box to
create a blank. Of course if my example below went further on, I'd need to
restore the definition of \alaligne. And other changes would be needed for a
mid-line blank. Now that I understand these techniques better I'll think
about incorporating them directly into PMX, where in response to new PMX
commands I could do it directly (like in Bob's example) rather than
redefining \alaligne.
--Don
==
1 1 4 4 4 4 0 0
1 3 20 0
t
.\
Abp
c44 d e f g a b c /
\\\def\alaligne{\
\\\stoppiece\hbox
to\hsize\bgroup\vbox\bgroup\hsize=.6\hsize\
\\\startpiece\addspace\afterruleskip}\
L2
c44 d e f D"Hello"+8+15 Rr /
\\\def\alaligne{\
\\\endpiece\egroup\egroup\
\\\startpiece\addspace\afterruleskip}\
L3
c44 d e f g a b c /
==
---
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] Problem with pmx file
RTFM. The first of the four numbers is the numerator of the true meter, and it cannot be zero. You would have zero quarter notes per bar. And BTW the 3rd and 4th numbers being 0 and 4 means the printed meter would be a single digit 4, which I don't think I've ever seen used. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Saturday, May 04, 2019 3:28 PM > To: tex-music@tug.org > Subject: Re: [Tex-music] Problem with pmx file > > Please help with this other attached pmx file. Under both Linux and > Windows, when trying to process it with `musixtex test.pmx', I get the > following error: > > This is musixtex.lua version 0.21. > This is PMX, Version 2.84 , 10 Feb 18 > Opening test.pmx > > Starting first PMX pass > > Bar 1 Bar 2 Bar 3 Bar 4 Bar 5 Bar 6 Bar 7 Bar 8 Bar 9 Bar 10 Bar 11 > Bar 12 Bar 13 Bar 14 Bar 15 Bar 16 Bar 17 > > ERROR in line 111, bar 18 Digit 0 not allowed here > v > m0/4/0/4 > ^ > !! pmx processing of test.pmx fails. > > > Thanks, > > Rodolfo > --- 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] strange reaction of PMX 284
Well, I could have created a better error message :). --Don From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On Behalf Of Dieter Sent: Tuesday, May 07, 2019 1:09 AM To: Werner Icking Music Archive Subject: Re: [Tex-music] strange reaction of PMX 284 Sorry Don, I made a stupid syntax error. I did not sleep well last night. Regards, Dieter --- 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] PMX and Trills
Dieter— If you are referring to the black square after the “tr” in bar 15 of the second example, the reason is related (in some mysterious way I can’t understand) to the very short \noteskip caused by the 16th notes in the bass. For me, with the default page width of 524 pt, the black square went away. If you’re worried about something else, please clarify. This report did prompt me to look at the reference table ref284.pdf. where I found an error. Under ornaments, it says T,Tt gives you “Trill (tr) with or without wavy line”. That should read “Arbitrary length wavy line with or without tr”. I’ll try to remember to correct that in the next release. --Don From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On Behalf Of Dieter Sent: Thursday, May 09, 2019 5:41 AM To: Werner Icking Music Archive Subject: [Tex-music] PMX and Trills When I test the Trills with PMX, everything looks as it should. However when I look at the beginning of Mozarts "Sonate Facile" (from MuseScore via MusicXML) it looks differently. I cannot find a reason, why the trill in Bar 4 behaves differently from the one in Bar 15. (PMX attached.) Thanks and regards, Dieter --- 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] Bug in PMX with chord stems
Hi, Danai-- I'm really glad you mentioned the 3rd bar in your text, because when I compiled your source after simply cutting and pasting it from the email without looking at it in detail, it came out with just 2 bars that looked awful. I soon realized that in the email process the first two "/r2d"s had been stuck on the end of their preceding lines, and therefore ignored (since PMX ignores everything after the first "/" in a line.) Anyhow, there is an explanation for what you're seeing and a fairly effective work-around, none of which is explained in the manual. The key fact is that from PMX's perspective, default beam stem directions and lengths are what they would be if you ignore the "z" chord notes. So in your example the default direction was up, and the stems are only as long as needed for the low F's. If you make the highest note in each chord the main note, like this: d82a zd+ [u d8 o. za zf e+ o> za- zf ] [u f+ o_ za- zf e+ o. za- zf d+ op za zf ] / it comes out much nicer. Now you do need to force the beams to be upward because the default would now be downward since the main notes are now all on or above the middle line. As you can imagine, the code logic for beamed, ornamented chords as it stands is quite complex, involving computing the heights and angles of the beams and then the vertical positions of the ornaments. Of course it could conceivably be enhanced to automagically select more pleasing positioning regardless of which note is entered as the main chord note, but that would make the coding even more complicated, plus it would create backward incompatibilities, so I'm not inclined to pursue it. But don't hesitate to raise more questions as they arise! I'm always happy to see people using PMX. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Danai SAE-HAN > (???) > Sent: Friday, May 10, 2019 10:38 PM > To: Werner Icking Music Archive > Subject: [Tex-music] Bug in PMX with chord stems > > Hi > > I have recently rekindled my interest in MusiXTeX / PMX with the sole > purpose of publishing the works of one of my distant forefathers > (Ernemann) in the public domain. > > I think I found a number of bugs, but it is more likely that my understanding > of PMX and MusiXTeX is severely lacking or a sad case of RTM. In due course > I will be sending a few emails to seek enlightenment from some friendly > souls. > > Anyway, the first problem I would like to point out, is a strange default > behaviour in PMX: some chord stems are positioned wrongly (too short), yet > some ornaments seem to be positioned much higher than the beam. > > Attached you will find an example. The first measure shows no issues if the > chords are an octave higher. The second one shows PMX's default > behaviour: the stems are too short, and some ornaments are not positioned > accordingly. > > The third measure shows my manual overrides. > > I am not sure whether it is worth exploring why PMX has this as a default > behaviour. > > === > % nv,noinst,mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig, > 2 1 6 8 6 8 0-1 > % > % npages,nsyst,musicsize,fracindent > 1 1 160.07 > Piano > bt > ./ > d82au zd+ f8 za zd o. f8- za zd o> f8- za zd o_ f8- za zd ou f8- za zd op / > r2d / > > d82au zd+ f8- za zd o. f8- za ze+ o> f8- za zf+ o_ f8- za ze+ ou f8- za zd op > / > r2d / > > d82au zd+ [+4 f8- za zd o. f8- ] za ze+ o> [+5-1 f8- za zf+ o_ f8- za > ze+ ou f8- ] za zd op / > r2d / > > %% Local Variables: > %% mode: plain-tex > %% End: > === > > > Best regards > > > -- > Danai --- 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
[Tex-music] Request, regarding PMX systems with gaps
For the last 3 weeks I've been struggling with revising PMX to insert blank gaps either in the middle or at the end of a line. I do see ways to cover most possible cases in MusiXTeX, but it's proving really tricky to build them all into PMX. Different handling is needed for gaps in the middle or end of a line; in the top, middle, or bottom system on a page; whether it's the line before a new movement or not; and whether it's the very last line of the whole piece or not. Before going much further, I'd like to ask list members to let me know about any real world situations they've encountered requiring such gaps, and even post examples if possible. I can think of several definite categories: 1. A short coda following a gap in the last line of a movement. 2. A last line of a movement, either the tail end of the body of the movement or a coda, starting at the beginning of the line but not going all the way to the end. But I want to be sure not to neglect any other useful cases, so could people please suggest any other real-world uses of gaps? Thanks in advance, --Don --- 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
[Tex-music] Another one for the TeXperts
For me, this file works OK:
===
\input musixtex
\hsize=524pt
\vsize740pt
\def\nbinstruments{1}
\setstaffs11
\setclef10
\generalmeter{\meterfrac{4}{4}}%
\nostartrule
\startmuflex
\parindent 253pt
\startpiece\addspace\afterruleskip%
\notes\wh c\en%
\Endpiece
\vfill\eject\endmuflex
\bye
But if I change 253 to 254 in the 6th line from the end, I get garbage. Why?
And is there any way to allow \parindent > 253pt?
--Don
---
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] Submitting scores to IMSLP
Yep, tricky to figure out. But the good news is that if you don't do exactly what they want, they will usually tell you what's "wrong". > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Wednesday, May 15, 2019 7:56 AM > To: tex-music@tug.org > Subject: [Tex-music] Submitting scores to IMSLP > > Hi all... > > I'm trying to add a score to IMSLP but find it definitely difficult and > complicated... Difficult to understand all the necessary steps... Create a > category page, then... > > I'll try later on and it's going to be hard... > > Thanks, > > Rodolfo > --- > 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 --- 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] Another one for the TeXperts
Bob Tennent wrote ... > > The error message says > > Don't stress \mulooseness too much !!! > > This shouldn't happen ! Too few bars or \mulooseness too large ? > > But there's no problem if you avoid musixflx. > > >|And is there any way to allow \parindent > 253pt? > > You'd have to look at the musixflx code. TeX itself is okay with it. and > More than one bar? Thanks, Bob. I hadn't noticed the error message. If you avoid musixflx, don't you need to calculate \elemskip by hand? If so, that doesn't seem like much of a solution. Adding more bars doesn't seem to matter. 253pt seems to be a magical maximum \parindent. I tried setting \mulooseless=-1 as in the musixdoc example, and got the same result. I also tried removing the \afterruleskip, but that didn't matter either. I'm not up to digging into musixflx. But this limitation is very annoying, as it means without somehow bypassing musixflx, you could not create a short, single-line coda at the end of the last line by using \parindent (which is what happens when you use PMX's new movement command M with the "i" option). And for a normal PMX user, bypassing musixflx is definitely not an option either. In a private email, Dirk Baack recently responded to my request by suggesting PMX allow "A last line starting _not_ a the left hand side, but in the middle of the line (with Coda-sign) and going to the end of the line." I responded saying you could already do this with the M command and the "i" option. Unless someone steps up and fixes this mulooseness problem, my proposal will not work with indents that are above the 253pt threshhold. --Don --- 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] Another one for the TeXperts
Bob Tennent wrote
>...
> The following works for me:
>
> =
>
> \input musixtex
> \hsize=524pt
> \vsize740pt
> \def\nbinstruments{1}
> \setstaffs11
> \setclef10
> \generalmeter{\meterfrac{4}{4}}%
> \nostartrule
> \startmuflex
> \parindent 256pt
> \startpiece\addspace\afterruleskip%
> \notes\wh c\en%
> \bar
> \notes\wh c\en%
> \bar
> \notes\wh c\en%
> \Endpiece
> \vfill\eject\endmuflex
> \bye
>
> ==
Whoa, great find! Works for me too. And keeps working with much larger
\parindent. But when I replace each \bar with \xbar it fails exactly as
before. And when I simply remove the \bar's it also fails. So it seems to
need at least one \bar to work. PMX never uses \bar because it always
decides exactly where all the line breaks go, and \bar allows a line break
if the internal MusiXTeX logic decides there should be one there.
This suggests that PMX could produce short, right-justified codas on lines
of their own, using "Mi", if for that line only PMX used \bar rather than
\xbar. But unfortunately, aside from allowing possible unintended line
breaks in the coda, that still wouldn't admit single-bar codas if they're
too short. So a remaining challenge is how to get it to work without any
\bar's.
--Don
---
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] Another one for the TeXperts
I wrote
>...
> This suggests that PMX could produce short, right-justified codas on lines
of
> their own, using "Mi", if for that line only PMX used \bar rather than
\xbar.
> But unfortunately, aside from allowing possible unintended line breaks in
the
> coda, that still wouldn't admit single-bar codas if they're too short. So
a
> remaining challenge is how to get it to work without any \bar's.
>
Single-bar, short, end-of-line coda! Uses gap method developed 2 weeks ago
by Bob. Avoids the musixflx problem caused by large \parindent.
==
\input musixtex
\hsize=524pt
\vsize740pt
\def\nbinstruments{1}
\setstaffs11
\setclef10
\generalsignature{-1}%
\generalmeter{\meterfrac{4}{4}}%
\parindent 0pt
\nostartrule
\startmuflex
\hbox to\hsize{%
\hfill\vbox{\hsize=.20\hsize%
\startpiece\addspace\afterruleskip
\notes\wh c\en
\Endpiece}}
\vfill\eject\endmuflex
\bye
==
---
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] Submitting scores to IMSLP
> Rodolfo Medina writes: > > > "Don Simons" writes: > > > >> Yep, tricky to figure out. But the good news is that if you don't do > >> exactly what they want, they will usually tell you what's "wrong". > > > > Done...! Waiting for the approval... Lets' hope for the best... > > Submission refused, upload deleted... even more difficult than I thought... > > Rodolfo Did they tell you why it was refused? --- 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] Submitting scores to IMSLP
Rodolfo Medina wrote > "Don Simons" writes: > > >> Rodolfo Medina writes: > >> > >> > "Don Simons" writes: > >> > > >> >> Yep, tricky to figure out. But the good news is that if you don't > >> >> do exactly what they want, they will usually tell you what's "wrong". > >> > > >> > Done...! Waiting for the approval... Lets' hope for the best... > >> > >> Submission refused, upload deleted... even more difficult than I > > thought... > >> > >> Rodolfo > > > > Did they tell you why it was refused? > > > They linked me a large set of possible reasons: > > http://imslp.org/index.php?title=Special:WikiForum&thread=23609 > > , so I have to study hard now to figure out which of them... unless some of > you gentle listers who's already upload scores to IMSLP can help me... > Actually some years ago I uploaded a score but forgot the procedure or > something has changed... Now I want upload the MusiXTeX source of > Christian Petzold's Menuet in G minor together with its PDF output, both files > zipped into one zip file... The reply refers you to reason #3, so it looks like all you have to do is say your edition is a (Re)Typeset and assign it one of the Creative Commons licenses. --- 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] Another one for the TeXperts
Thanks very much, Hiroaki, for looking into this. Unfortunately I'm not
familiar with either lua or C. I simply use an executable musixflx.exe dated
6/28/3013 that came with my MusiXTeX installation. (When it runs it says
Musixflx-0.83.3.lua7). Would you be willing to provide me with a trial
executable with the changes you're suggesting? I'm wondering if it will
still fail my test if I use \xbar. If it does, I would consider revising PMX
to take advantage of the enhancement. If we could find someone who knows lua
and is willing to put the updates in the current version of musixflx, do you
think it would be safe to replace that with one having these modifications?
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Hiroaki
> MORIMOTO
> Sent: Saturday, May 18, 2019 7:21 PM
> To: Werner Icking Music Archive
> Subject: Re: [Tex-music] Another one for the TeXperts
>
> The of this error may be:
>
> if ((x-eff_linewidth) < (lastbar/2)) then
>
> at line 850 and
>
> else
> barsinline=i-1-mark
> if (barsinline < 1) then error_exit(2) end
>
> at line 923-925 in musixflx.lua (0.83.3.lua7).
>
> Note: I tested it with C version musixflx.c 0.83.2 (in T.115 zip archive)
line 720
> and line 790-793, because I'm not familiar with lua.
>
> Hiroaki
>
> - Original Message -
> > From: "Don Simons"
> > To: "'Werner Icking Music Archive'"
> > Date: Wed, 15 May 2019 14:35:37 -0700
> > Subject: Re: [Tex-music] Another one for the TeXperts
> >
> >
> > I wrote
> >
> > >...
> > > This suggests that PMX could produce short, right-justified codas on
> > >lines
> > of
> > > their own, using "Mi", if for that line only PMX used \bar rather
> > > than
> > \xbar.
> > > But unfortunately, aside from allowing possible unintended line
> > > breaks in
> > the
> > > coda, that still wouldn't admit single-bar codas if they're too
> > > short. So
> > a
> > > remaining challenge is how to get it to work without any \bar's.
> > >
> >
> > Single-bar, short, end-of-line coda! Uses gap method developed 2 weeks
> > ago by Bob. Avoids the musixflx problem caused by large \parindent.
> >
> > ==
> > \input musixtex
> > \hsize=524pt
> > \vsize740pt
> > \def\nbinstruments{1}
> > \setstaffs11
> > \setclef10
> > \generalsignature{-1}%
> > \generalmeter{\meterfrac{4}{4}}%
> > \parindent 0pt
> > \nostartrule
> > \startmuflex
> > \hbox to\hsize{%
> > \hfill\vbox{\hsize=.20\hsize%
> > \startpiece\addspace\afterruleskip
> > \notes\wh c\en
> > \Endpiece}}
> > \vfill\eject\endmuflex
> > \bye
> > ==
> >
> > ---
> > 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
>
> ---
> 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
---
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] PMX: problem with shifted dot
Hi, Rodolfo-- Welcome to the club! Your issue with the dot reveals two problems, one with the details in the manual, and the other one a bug. In the instructions for moving dots, I should have included a suggestion to put the dot last in the note command to avoid any confusion. Your command was "c2d-0.7+14l" which literally says C, half note, dot, move down .7, move right 14, lower stem. There is no octave specified, so it gets the octave from the previous note in that voice, which was the low d. What you should have entered was "c24dl-.07+1. Unfortunately you exposed a bug, or maybe we could call it a feature. For mysterious reasons buried deep in the PMX coding, when there are two notes in a chord that are one step apart and one is the main note, PMX will sometimes internally switch their roles. But even after the suggested correction, PMX got confused in your example, and applied the shifts to the dot on the D, not the C. So you could get what I think you want by fooling PMX and entering r4 c24ld zd3 ?-1 zf3 zd4d-2+1 ? / Note that I also shifted the arpeggio symbol to the left. Finally I'll point out that if you had entered the notes from the top down, making the d24 the main note, the dot moving confusion goes away: r4 dd24l ?-1 zcd-2+1 zf- zd ? / That's how I would have entered it. And note that I don't need to enter the octaves or the dot symbol in the chord notes unless needed, but I did need to use "-" to get the F in the right octave. Happy PMXing! --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Sunday, May 19, 2019 6:43 AM > To: tex-music@tug.org > Subject: [Tex-music] PMX: problem with shifted dot > > Hi all. > > As suggested by some listers, I'm finally learning to use PMX, vrey useful and > precious tool. Thanks to Don. In the test file I'm attaching, in bar 3, there's a > problem with a shifted dot. According to the PMX manual p.7, I put `-0.7+1' > after the `d', in order to properly shift it, but I get un undesirable effect as > you can see processing the file with `musixtex text.pmx': the note c4 is > lowered down by 2 octaves and becomes c2. Please help avoiding it. > > Thanks, > > Rodolfo > --- > 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 --- 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] PMX: full-bar rest not centered
Rodolfo-- I think you've exposed a real bug. It seems that whole-bar rests in the first bar are not centered as intended. I'll need to look into this some more and report back later. I'm very surprised it hasn't come up before. As for r0, RTFM. The manual's section on rests starts out "The command for a rest starts with r. Then for a normal rest, in either order come a digit for the basic time value (using same codes as for notes, optional if unchanged from previous value), ..." The digit for a whole note is "0". --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Sunday, May 19, 2019 8:10 AM > To: tex-music@tug.org > Subject: [Tex-music] PMX: full-bar rest not centered > > Hi, Don, hi all. > > In the attached test file the full-bar pause `rp' should be centered according > to PMX manual p.10 but it isn't. Besides, if in place of `rp' I put `r0', the rest is > a bit shifted rightwards. But I don't see any `r0' command in the manual... > > These are my first steps in using PMX, will you please excuse my > inexperience... > > Please help > > thanks > > Rodolfo --- 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] PMX: full-bar rest not centered
Pshew! All is well, no bugs. The non-centering was caused (in some complicated way) by your setting xmtrnum0 to 4. There is absolutely no reason to do that. xmtrnum0 is only there to allow a "pickup" bar at the beginning, with FEWER beats than the basic meter allows. If there's no pickup, as in 97% of all typesets including this one, then xmtrnum0 = 0. If I do anything at all about this, it'll be to have PMX check if xmtrnum0 = mtrnuml, and if it is, issue an error and stop the compilation. --Don > -Original Message- > From: Rodolfo Medina [mailto:rodolfo.med...@gmail.com] > Sent: Sunday, May 19, 2019 10:16 AM > To: Don Simons > Cc: 'Werner Icking Music Archive' > Subject: Re: [Tex-music] PMX: full-bar rest not centered > > "Don Simons" writes: > > > Rodolfo-- > > > > I think you've exposed a real bug. It seems that whole-bar rests in > > the first bar are not centered as intended. I'll need to look into > > this some more and report back later. > > > Surely you'll fix it soon. > > > > As for r0, RTFM. The manual's section on rests starts out "The command > > for a rest starts with r. Then for a normal rest, in either order come > > a digit for the basic time value (using same codes as for notes, > > optional if unchanged from previous value), ..." > > > Sorry, my fault... > > Thanks! > > Rodolfo --- 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] PMX: `sforzando' on grace note?
There's no provision for ornaments on grace notes in PMX. You could put one on the next note and move it as needed: G1m1b1 d03s o>-18-2.4 za3 zc4 zb2 / but this comes out in the main font. If you want one in a smaller font you could get it with the D command, again assigning it to a main note and moving it as needed: G1m1b1 d03s D"\musiceleven\char31"+0-2.2 za3 zc4 zb2 / --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Sunday, May 19, 2019 12:23 PM > To: tex-music@tug.org > Subject: [Tex-music] PMX: `sforzando' on grace note? > > In the attached example, I wish to put a `sforzando' sign upon the grace note > `b1'; is it possible? But I get error both if I do > > G1m1b1o> > > or > > G1m1b1 o> > > > Please help... > > Thanks, > > Rodolfo --- 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] Dots moving
Rodolfo Medina wrote > Is it possible, in MusiXTeX code, to move a note's dot a little right, left, up or > down such as PMX does? In MusiXTeX manual, on p.26, I see \lpt and \lppt > to lower the dot but nothing else. Anything PMX can do must be able to be coded in MusiXTeX, because all PMX does is write MusiXTeX code. If you want to see what the MusiXTeX code is, just set it up in PMX, run PMX, and look at the .tex file that PMX produces. --Don --- 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] pmx - increasing the number of instruments
Andre, this couldn't be more elegant! The inline TeX doesn't require any
dimensioning. If I ever finish my current PMX improvement project (blank
gaps) I may consider trying to build this method into PMX.
But I do wonder exactly what you mean when you say that a dummy page cannot
be used when making a booklet. If you start with a PDF, you can always
manually delete one page from it before processing it further. (Unless of
course that offends your sensibilities.)
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Andre Van
> Ryckeghem
> Sent: Wednesday, May 22, 2019 2:00 AM
> To: Werner Icking Music Archive
> Subject: [Tex-music] pmx - increasing the number of instruments
>
> Dear all,
>
> If i want to increase the number of instruments (ie. starting with 1
> instrument and then go one with 2), pmx must be started with the maximum
> of instruments. I have to made a dummy first page with the maximum of
> instruments and then throw it away. But if making a booklet, this cannot
be
> done.
>
> A method of making it working is putting 2 instruments above each other,
so
> only 1 can be seen. This tex commands ie. are used therefore:
> \\interstaff{13}\setinterinstrument1{-13\Interligne}\
>
> Now i'm trying a more elegant (?) method by setting the size of the
> instrument to 0. This works for 1 staff instruments. I have added an
example
> the clarifies it a little more i hope.
>
> I like to get comments on this or hints to improve.
>
> =
> 3-2 1 24 4 4 4 0 1
> 1 4 20 .05
>
> Man.
> bbt
> ./
> Arbd
> %1
> \\setsize1{0}\setclef18\setsign10\setmeter1{}\
> rbp rbp rbp rbp rbp /
> c44 b8 a b4 g | d+ c8 b c4 a | e+ d8 c d4 b | e c d d- | g0 /
> e44 d8 c d2 | f4 e8 d e2 | g4 f8 e f2 | g.f | g0 // g24.b | a.c | b.d | c4
b a2 | g0r
> / %
> L3M+12r+ci.05
> m6464
> \\\setsize1{\normalvalue}\setclef1{5}\
> \\\setname1{Ped.}\setname2{Man.}\
> d0d- t dd t t dd t t dd t /
> a2d t ad t | ed+ d,c | a0d e2+ d8 e d2,c / f2d t fd t t f0d t t fd t t fd
t //
> e2d+ dS2,cS1 a0d e2+ d8 e d2,c a0d t /
> ==
>
> Thanks
> Andre
>
> ---
> 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
---
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
[Tex-music] TeXperts: Help!
I'm getting close to releasing a version of PMX that enables arbitrary blank
gaps at the beginning or middle of any staff, relying on TeXniques designed
by Olivier Vogel and expanded by Bob Tennet. In modifying PMX it hasn't been
at all easy to account for all the possibilities involving movement breaks,
page breaks, bar numbering, etc., but now I have most of the horizontal
spacing issues worked out. However, there are still some problems with
vertical spacing, illustrated with the attached plain MusiXTeX file
eqprob.tex. It uses Olivier's basic method for shortening a line by putting
it into a \hbox. The file also uses the long-standing PMX method "Av" to try
to get equal vertical spacing. Av works by including very long, equal-length
vertical struts in all lines. This in effect gives all systems equal heights
which add up to more space than available on one page, so when forced into
the actual vertical space in the page, they all end of with the same amount
of blank vertical space being clipped off, leaving equal vertical space
between the bottom line of one system and the top line of the next. If you
compile the example, you'll see that the method breaks down for the
shortened system in line 4, probably related to the fact that the \hbox is
handled differently during the vertical squeezing/trimming process.
The other file uneqprob.tex has all of the struts removed, and represents
what PMX would give without Av. Now the space above line 4 comes out too
small.
I'd be very grateful if someone could figure out a general way to get the
\hbox'ed line handled the same way as the other lines in both cases,
restoring the equal vertical spacing.
I did find that I could manually reduce or expand the size of the unequal
gap using \spread{...} with a positive or negative argument. This command,
defined in pmx.tex, adds a negative \vskip right before the next \contpiece.
But it takes trial and error to find the right value of the argument, so
it's not at all the ideal solution.
--Don
eqprob.tex
Description: Binary data
uneqprob.tex
Description: Binary data
---
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] TeXperts: Help!
Oops! I should have said "...arbitrary blank gaps in the middle or at the
end of any staff". (For gaps at the beginning, I'm still banking on someone
fixing musixflx so it doesn't crash when you use too big of an indent.)
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner....@tug.org] On Behalf Of Don Simons
> Sent: Friday, May 24, 2019 9:09 PM
> To: 'Werner Icking Music Archive'
> Subject: [Tex-music] TeXperts: Help!
>
> I'm getting close to releasing a version of PMX that enables arbitrary
blank
> gaps at the beginning or middle of any staff, relying on TeXniques
designed
> by Olivier Vogel and expanded by Bob Tennet. In modifying PMX it hasn't
> been at all easy to account for all the possibilities involving movement
> breaks, page breaks, bar numbering, etc., but now I have most of the
> horizontal spacing issues worked out. However, there are still some
> problems with vertical spacing, illustrated with the attached plain
MusiXTeX
> file eqprob.tex. It uses Olivier's basic method for shortening a line by
putting
> it into a \hbox. The file also uses the long-standing PMX method "Av" to
try
> to get equal vertical spacing. Av works by including very long,
equal-length
> vertical struts in all lines. This in effect gives all systems equal
heights which
> add up to more space than available on one page, so when forced into the
> actual vertical space in the page, they all end of with the same amount of
> blank vertical space being clipped off, leaving equal vertical space
between
> the bottom line of one system and the top line of the next. If you compile
> the example, you'll see that the method breaks down for the shortened
> system in line 4, probably related to the fact that the \hbox is handled
> differently during the vertical squeezing/trimming process.
>
> The other file uneqprob.tex has all of the struts removed, and represents
> what PMX would give without Av. Now the space above line 4 comes out too
> small.
>
> I'd be very grateful if someone could figure out a general way to get the
> \hbox'ed line handled the same way as the other lines in both cases,
> restoring the equal vertical spacing.
>
> I did find that I could manually reduce or expand the size of the unequal
gap
> using \spread{...} with a positive or negative argument. This command,
> defined in pmx.tex, adds a negative \vskip right before the next
\contpiece.
> But it takes trial and error to find the right value of the argument, so
it's not
> at all the ideal solution.
>
> --Don
---
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] TeXperts: Help!
Brilliant! It fixes the problem with or without Av. I would never have found
this myself. Thank you, Andre!!!
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Andre Van
> Ryckeghem
> Sent: Saturday, May 25, 2019 6:53 AM
> To: Werner Icking Music Archive
> Subject: Re: [Tex-music] TeXperts: Help!
>
> I do not know if this could work, but adding a skip before the macro that
start
> on line 45 (uneqprob.tex) moves the system down
>
> \vskip\parskip\hbox to\hsize{\vbox{\hsize=.70\hsize% \contpiece
>
> Andre
>
> -----Oorspronkelijk bericht-
> From: Don Simons
> Sent: Saturday, May 25, 2019 6:08 AM
> To: 'Werner Icking Music Archive'
> Subject: [Tex-music] TeXperts: Help!
>
> I'm getting close to releasing a version of PMX that enables arbitrary
blank
> gaps at the beginning or middle of any staff, relying on TeXniques
designed
> by Olivier Vogel and expanded by Bob Tennet. In modifying PMX it hasn't
> been at all easy to account for all the possibilities involving movement
> breaks, page breaks, bar numbering, etc., but now I have most of the
> horizontal spacing issues worked out. However, there are still some
> problems with vertical spacing, illustrated with the attached plain
MusiXTeX
> file eqprob.tex. It uses Olivier's basic method for shortening a line by
putting
> it into a \hbox. The file also uses the long-standing PMX method "Av" to
try
> to get equal vertical spacing. Av works by including very long,
equal-length
> vertical struts in all lines. This in effect gives all systems equal
heights which
> add up to more space than available on one page, so when forced into the
> actual vertical space in the page, they all end of with the same amount of
> blank vertical space being clipped off, leaving equal vertical space
between
> the bottom line of one system and the top line of the next. If you compile
> the example, you'll see that the method breaks down for the shortened
> system in line 4, probably related to the fact that the \hbox is handled
> differently during the vertical squeezing/trimming process.
>
> The other file uneqprob.tex has all of the struts removed, and represents
> what PMX would give without Av. Now the space above line 4 comes out too
> small.
>
> I'd be very grateful if someone could figure out a general way to get the
> \hbox'ed line handled the same way as the other lines in both cases,
> restoring the equal vertical spacing.
>
> I did find that I could manually reduce or expand the size of the unequal
gap
> using \spread{...} with a positive or negative argument. This command,
> defined in pmx.tex, adds a negative \vskip right before the next
\contpiece.
> But it takes trial and error to find the right value of the argument, so
it's not
> at all the ideal solution.
>
> --Don
>
>
>
>
>
>
>
> ---
> 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
>
> ---
> 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
---
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] Duration of multirests below the staff?
Bob Tennent wrote
> Sent: Friday, May 24, 2019 10:19 AM
> To: Dieter
> Cc: Werner Icking Music Archive
> Subject: Re: [Tex-music] Duration of multirests below the staff?
>
> >|How could I put the duration of a multirest below the staff?
>
> what are you using to generate the multirest? musixtex.tex, pmx, autosp,
...
>
Dieter, I haven't seen any answer to Bob's question. But I'll try to answer
yours assuming you're using PMX. Unfortunately if you want to use the PMX
command "rm", the answer is not at all simple. In fact, the question may
prompt me to make some changes in PMX. But for now, here's an example PMX
file showing how you could do it, using a redefinition of \mbrest that Bob
suggested.
--Don
=
---
\input musixtex
\input pmx
\def\mbrest#1#2#3{%
\CenterBar{\ccn{\mbrheight}{\meterfont#1}}{#2}{#3}%
\CenterBar{%
\ifcase #1%
\relax%
\or\cpause% 1
\or\cPAuse% 2
\or\cPAuse\mbgap\cpause% 3
\or\cPAUSe% 4
\or\cPAUSe\mbgap\cpause% 5
\or\cPAUSe\mbgap\cPAuse% 6
\or\cPAUSe\mbgap\cPAuse\mbgap\cpause% 7
\or\cPAUSe\mbgap\cPAUSe% 8
\or\cPAUSe\mbgap\cPAUSe\mbgap\cpause% 9
\else
\def\vertpart{\hbox{\vrule width.6pt height1.5\internote
depth1.5\internote}}%
\raise4\internote\hbox{\vertpart%
\vrule width0.7\y@ii height.5\internote
depth.5\internote%
\vertpart}%
\fi}{#2}{#3}}%
---
1 1 4 4 4 4 0 0
1 1 20 0
t
.\
\\\def\mbrheight{-6}\
% The default \mbrheight is 9 and you'll need to change it to
% that value to get numbers above the multibar rest
c44 d e f | rm6 | g a b c /
=
---
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
[Tex-music] New PMX version with gaps
I've produced a new version of PMX (2.90) that lets you put a blank gap at the end or in the middle of a system. It was very challenging and still has known deficiencies, but is at a stage where I would very much appreciate having as many people as possible try it out and report any bugs you find. Until it shows up on WIMA, you can get a zip of the distribution here: www.pchpublish.com/bbbxv/pmx290.zip The file BlankGaps.pdf explains the new syntax. The known deficiencies are (1) It cannot yet be used in the first system of the score; (2) It doesn't yet properly handle automagically inserting extra space when needed for accidentals or other items in the gapped system if it is too crowded (this can temporarily be addressed by manually inserting gaps with the "X" command); (3) You can change the barline symbol from the default one at the end of the segment before or after the gap with an "R" command option on the last note in voice 1, but that command MUST be the very last one before the group-ending "/". Once again, please give it a workout and report any bugs or issues. --Don Simons --- 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] New PMX version with gaps
The package is available from WIMA at the following address: http://icking-music-archive.org/software/pmx/pmx290.zip --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Don Simons > Sent: Saturday, June 01, 2019 3:49 PM > To: 'Werner Icking Music Archive' > Subject: [Tex-music] New PMX version with gaps > > I've produced a new version of PMX (2.90) that lets you put a blank gap at > the end or in the middle of a system. It was very challenging and still has > known deficiencies, but is at a stage where I would very much appreciate > having as many people as possible try it out and report any bugs you find. > Until it shows up on WIMA, you can get a zip of the distribution here: > > www.pchpublish.com/bbbxv/pmx290.zip > > The file BlankGaps.pdf explains the new syntax. > > The known deficiencies are (1) It cannot yet be used in the first system of the > score; (2) It doesn't yet properly handle automagically inserting extra space > when needed for accidentals or other items in the gapped system if it is too > crowded (this can temporarily be addressed by manually inserting gaps with > the "X" command); (3) You can change the barline symbol from the default > one at the end of the segment before or after the gap with an "R" > command option on the last note in voice 1, but that command MUST be the > very last one before the group-ending "/". > > Once again, please give it a workout and report any bugs or issues. > > --Don Simons > > --- > 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 --- 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] PMX cannot influence stem length
That’s an RTFM, but in this case, it’s the MusiXTeX manual, and it wasn’t that
easy to find. You need to enter inline \stdstemfalse\ before the note where you
want it to ignore the standard rule for extending all stems to the middle staff
line.
--Don
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Wednesday, June 05, 2019 8:31 AM
To: Werner Icking Music Archive
Subject: [Tex-music] PMX cannot influence stem length
I have:
---
\input musixtex
\input pmx
---
% nv, -noinst, nostaves per instrument
1 -1 1
% mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig
4 4 4 4 0 -1
%
% npages,nsyst,musicsize,fracindent
0 4 16 0.07
t
./
Abep
\loffset{1}{\Ioctfinup1z}\ a06 /
a /
a /
\Toctfin1\ a2S2.0 r2 /
==
And I get:
It seems that the stem of the halfnote always ends at the middle staffline,
independent of the S-option.
Regards, DIeter
---
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] PMX290: character "o" in meter change
Thanks very much, Luigi. I'm not sure why I messed this up, but it's easy to fix, and will be fixed in the next release. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Luigi Cataldi > Sent: Sunday, June 09, 2019 12:29 PM > To: Werner Icking Music Archive > Subject: [Tex-music] PMX290: character "o" in meter change > > It seems that in meter change PMX290 accepts "m1/8/0/0", but not "mo800". > You can prove this with the following example. > > Regards > > Luigi > > 1 1 12 8 12 8 0 -1 > 1 2 20 0.0 > > t > ./ > Abr > > f8+ g a d- e f g d bs g g+ f / > ef f g c- d e f c a f f+ e / > d ef f b- c d e b e g e g / > c- d ef f g af bs- c d g- c b / > mo800 c Rz / > > --- > 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 --- 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] alignment of \flageolett in \Largenotesize
This is educational...over the years I've noticed some horizontal alignment
issues related to whole notes, but never realized there was a built in macro
to fix them. So naturally PMX doesn't make the whole note correction. I
suppose I could make PMX automatically use \wholeshift when appropriate. But
I did just notice it's not obvious which symbols would need it. Here's an
example with no horizontal corrections:
The last 3 clearly do lose centering over the whole note, but it sure looks
like the fermata is centered. I'm really puzzled how MusiXTeX could do that.
--Don
1 1 7 4 7 4 0 0
1 2 20 0
t
.\
w4i
e45 of e2 of e0 of /
e45 o^ e2 o^ e0 o^ /
e45 ou e2 ou e0 ou /
e45 op e2 op e0 op /
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Bob Tennent
> Sent: Saturday, June 29, 2019 8:23 AM
> To: Dieter
> Cc: tex-music@tug.org
> Subject: Re: [Tex-music] alignment of \flageolett in \Largenotesize
>
> >|Enlarging the \flageolett symbol works fine, but it is >|not exactly
aligned
> with the whole note "a06".
>
> >From musixdoc.pdf:
>
> These marks are horizontally centered relative to
> solid note heads. To compensate for the fact that
> whole notes are wider, you should use \wholeshift{Any
> nonspacing macro} to center accents and other items (e.g.,
> \Fermataup) above a whole note.
>
> Bob
>
> ---
> 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
---
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] alignment of \flageolett in \Largenotesize
> -Original Message-
> From: Bob Tennent [mailto:rdtenn...@gmail.com]
> Sent: Sunday, June 30, 2019 4:40 AM
> To: Don Simons
> Cc: 'Werner Icking Music Archive'
> Subject: Re: Re: [Tex-music] alignment of \flageolett in \Largenotesize
>
> >|This is educational...over the years I've noticed some >|horizontal
> alignment issues related to whole notes, but >|never realized there was a
> built in macro to fix them.
> >|So naturally PMX doesn't make the whole note correction.
> >|I suppose I could make PMX automatically use \wholeshift >|when
> appropriate. But I did just notice it's not obvious >|which symbols would
> need it. Here's an example with no >|horizontal corrections:
> >|
> >|The last 3 clearly do lose centering over the whole note, >|but it
sure
> looks like the fermata is centered. I'm >|really puzzled how MusiXTeX
could
> do that.
>
> Because pmxab generates \Fermataup (rather than \fermataup) and that
> has the \wholeshift built-in.
>
> Bob
>
> >|> >From musixdoc.pdf:
> >|
> >|> These marks are horizontally centered relative to
> >|> solid note heads. To compensate for the fact that
> >|> whole notes are wider, you should use \wholeshift{Any
> >|> nonspacing macro} to center accents and other items (e.g.,
> >|> \Fermataup) above a whole note.
Thanks, Bob. I didn't think to look at the TeX file PMX generated. With my
fading memory, I (re)learn something old every day.
But I will say that the wording in the MusiXTeX manual as quoted above is
misleading...it implies you need to explicitly use \wholeshift to center
\Fermataup over a whole note, while in fact that's one case where
musixtex.tex does it for you.
--Don
---
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] Varying number of instruments
Dieter-- You're not doing anything wrong. You unearthed a very subtle problem that has never come up before. It depends on several specific unrelated things happening in exactly the right sequence. (Reminds me of the kinds of PMX bugs Werner used to find). It is basically caused by the whole-bar rests in the last bar before the movement break. The sequence of events leading to the problem is this: (1) whole bar rests by default are centered; (2) the centering is accomplished by \atnextbar, which isn't executed until a barline is encountered; (3) at the movement break, PMX enters the change in number of instruments BEFORE entering the barline. It turns out MusiXTeX is somewhat flexible here in that it would be OK if no instrument had 2 voices. But it's the bar-centered rest in the 2nd voice of the piano part that kills things...if you replace it with an ordinary note, it goes through just fine even if you leave the full bar rest in the 2nd instrument/3rd staff. If you really want a centered full-bar rest in voice 2 of the piano part right before the decrease in number of instruments, I figured out a rather ugly work-around, but at least there's no inline TeX. I had to RTFM myself to refresh my memory, and I (re)discovered there's a PMX option 'o' on a full-bar rest that will suppress centering. But then you need to manually center it with an 'X' command. So just below is a file that works. I'm very hesitant to try to change PMX to account for this, because whatever I did could mess up existing scores in unforeseen ways due to the complex interactions within and between movement breaks and bar centered rests. --Don == 3 2 4 4 4 4 0 -1 1 2 16 0.07 Piano Voice ttt ./ AbepI0.9 r0 / r0 / r0 / r0 / X24 r0o / r0 / L2Mn12t r0 / r0 / r0 / r0 / r0 / r0 / === > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Dieter > Sent: Wednesday, July 03, 2019 10:39 AM > To: Werner Icking Music Archive > Subject: [Tex-music] Varying number of instruments > > I stumbled across a problem, which was already treated by Dirk Baack and > Don Simons, but the solution is unclear to me. > > I have a configuration with voice and piano. And I want sometime a piano > solo and some other time a vocal solo. > > This works fine for the piano (L2P2Mn11tt). Pls. se attachment. But when I > want to isolate the voice with (L2P2Mn12t), then > > I get an error message: !staff number (2) out of specified range (1)! > > > > % nv, -noinst, nostaves per instrument > 3 2 > % mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig > 4 4 4 4 0 -1 > % > % npages,nsyst,musicsize,fracindent > 2 2 16 0.07 > Piano > Voice > ttt > ./ > AbepI0.9 > %It80ivlvl > %\\input musixper\ > %%w277m > %%h390m > r0 / > r0 / > r0 / > r0 / > r0 / > r0 / > L2P2Mn11tt > r0 / > r0 / > r0 / > r0 / > r0 / > r0 / > > > > -- > > Dr. Dieter Glötzel > Im Rosengarten 27 > 64367 Mühltal > Tel.: 06151 / 360 82 72 --- 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] Trills in pmx
Andre, thanks for discovering this bug. I don't have a solution yet. This will be pretty difficult. The basic reason is that for normal moved dots, I got them to move by redefining \C@Point , which musixtex includes in the dotted note macros \qup etc. But for 2-note tremolos, I use a different mechanism for inserting any dots, explicitly using \pt together with an undotted note macro, and that procedure ignores any redefinition of \C@Point. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Andre Van > Ryckeghem > Sent: Tuesday, August 13, 2019 2:19 AM > To: Werner Icking Music Archive > Subject: [Tex-music] Trills in pmx > > Dear Don > > Since the 'the dot on the right note' correction in chords, this trill compiles > correct: > > e2dxT12 ?-2.4 zgn zasd ? as- > > and this trill gives a segmentation error: > > e2dxT12 ?-2.4 zgnd+0+1 zasd ? as- > > Thanks to look at it, > > Andre > > --- > 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 --- 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
[Tex-music] Moving dots in 2-note tremolos (was RE: Trills in pmx)
Update: I tentatively decided to redo the dotted 2-note tremolos to use the basic dotted chord note macros \qbp etc., rather than explicitly posting the dot with \pt. This would then allow me to use the same mechanism for moving dots as with normal dotted notes, beamed or not. But it seems there is no "etc.". In other words, you can add an open notehead to a beam with \hb, which is analogous to \qb for closed noteheads. But while there is \qbp for dotted solid beamed notes, there is no analogous \hbp for dotted open beamed notes. It would be nice if some TeXpert would volunteer to define \hpb; I tried looking in musixtex.tex at \qbp but it's awfully complicated. Otherwise, I may have to work out a way of moving the \pt dots. Even if I do manage to convince anyone to define \hbp, there will still be an issue with the order of operations when trying to move dots on dotted chord notes in 2-note tremolos (which was Andre's original problem). The redefinitions of C@point would have to come before the intended chord note with no other note commands in between. But I'll cross that bridge if I ever come to it. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner....@tug.org] On Behalf Of Don Simons > Sent: Tuesday, August 13, 2019 11:11 AM > To: 'Werner Icking Music Archive' > Subject: Re: [Tex-music] Trills in pmx > > Andre, thanks for discovering this bug. > > I don't have a solution yet. This will be pretty difficult. The basic reason is that > for normal moved dots, I got them to move by redefining \C@Point , which > musixtex includes in the dotted note macros \qup etc. But for 2-note > tremolos, I use a different mechanism for inserting any dots, explicitly using > \pt together with an undotted note macro, and that procedure ignores any > redefinition of \C@Point. > > --Don > > > -Original Message- > > From: TeX-Music [mailto:tex-music- > > bounces+dsimons=roadrunner@tug.org] On Behalf Of Andre Van > > Ryckeghem > > Sent: Tuesday, August 13, 2019 2:19 AM > > To: Werner Icking Music Archive > > Subject: [Tex-music] Trills in pmx > > > > Dear Don > > > > Since the 'the dot on the right note' correction in chords, this trill > compiles > > correct: > > > > e2dxT12 ?-2.4 zgn zasd ? as- > > > > and this trill gives a segmentation error: > > > > e2dxT12 ?-2.4 zgnd+0+1 zasd ? as- > > > > Thanks to look at it, > > > > Andre > > > > --- > > 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 > > --- > 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 --- 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] Moving dots in 2-note tremolos (was RE: Trills in pmx)
Thanks, Hiroaki! That works just fine. I'll see if I can use it to help
getting PMX to move dots on open-headed 2-note tremolos.
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Hiroaki
> MORIMOTO
> Sent: Thursday, August 15, 2019 6:57 AM
> To: Werner Icking Music Archive
> Subject: Re: [Tex-music] Moving dots in 2-note tremolos (was RE: Trills in
> pmx)
>
> Hi Don,
>
> I just found that the difference between \hb and \qb is only specifying
the
> character number assignment of notehead.
> \hb delegates all the further algorithm to \@qb, just like \qb does.
>
>
> \def\qb{\q@symbol\@qb}
> \def\qbp{\q@symbol\@qbp}
> \def\qbpp{\q@symbol\@qbpp}
>
> \def\hb{\h@symbol\@qb}
>
> \def\h@symbol{\def\q@u{\musixfont\@ight}}
> \def\q@symbol{\def\q@u{\musixfont\s@v@n}}
>
>
> That means - although I don't make any test at all and I'm afraid I can't
> understand enough what you are desiring - I guess that just following
> definitions will do what you desire:
>
>
> \makeatletter
> \def\hbp{\h@symbol\@qbp}
> \def\hbpp{\h@symbol\@qbpp}
> \makeatother
> ====
>
> I should say sorry if my guess is wrong.
>
> regards,
> Hiroaki
>
>
>
> - Original Message -
> > From: "Don Simons"
> > To: "'Werner Icking Music Archive'"
> > Date: Wed, 14 Aug 2019 10:08:29 -0700
> > Subject: [Tex-music] Moving dots in 2-note tremolos (was RE: Trills in
> > pmx)
> >
> >
> > Update:
> >
> > I tentatively decided to redo the dotted 2-note tremolos to use the
> > basic dotted chord note macros \qbp etc., rather than explicitly
> > posting the dot with \pt. This would then allow me to use the same
> > mechanism for moving dots as with normal dotted notes, beamed or not.
> But it seems there is no "etc.".
> > In other words, you can add an open notehead to a beam with \hb, which
> > is analogous to \qb for closed noteheads. But while there is \qbp for
> > dotted solid beamed notes, there is no analogous \hbp for dotted open
> beamed notes.
> > It would be nice if some TeXpert would volunteer to define \hpb; I
> > tried looking in musixtex.tex at \qbp but it's awfully complicated.
> > Otherwise, I may have to work out a way of moving the \pt dots.
> >
> > Even if I do manage to convince anyone to define \hbp, there will
> > still be an issue with the order of operations when trying to move
> > dots on dotted chord notes in 2-note tremolos (which was Andre's
> > original problem). The redefinitions of C@point would have to come
> > before the intended chord note with no other note commands in
> between.
> > But I'll cross that bridge if I ever come to it.
> >
> > --Don
> >
> > > -Original Message-
> > > From: TeX-Music [mailto:tex-music-
> > > bounces+dsimons=roadrunner@tug.org] On Behalf Of Don Simons
> > > Sent: Tuesday, August 13, 2019 11:11 AM
> > > To: 'Werner Icking Music Archive'
> > > Subject: Re: [Tex-music] Trills in pmx
> > >
> > > Andre, thanks for discovering this bug.
> > >
> > > I don't have a solution yet. This will be pretty difficult. The
> > > basic
> > reason is that
> > > for normal moved dots, I got them to move by redefining \C@Point ,
> > > which musixtex includes in the dotted note macros \qup etc. But for
> > > 2-note tremolos, I use a different mechanism for inserting any dots,
> > > explicitly
> > using
> > > \pt together with an undotted note macro, and that procedure ignores
> > > any redefinition of \C@Point.
> > >
> > > --Don
> > >
> > > > -Original Message-
> > > > From: TeX-Music [mailto:tex-music-
> > > > bounces+dsimons=roadrunner@tug.org] On Behalf Of Andre Van
> > > > Ryckeghem
> > > > Sent: Tuesday, August 13, 2019 2:19 AM
> > > > To: Werner Icking Music Archive
> > > > Subject: [Tex-music] Trills in pmx
> > > >
> > > > Dear Don
> > > >
> > > > Since the 'the dot on the right note' correction in chords, this
> > > > trill
> > > compiles
> > > > correct:
> > > >
> > > > e2dxT12 ?-2.4 zgn zasd ? as-
> > > >
> > > > and this trill gives a segmentation error:
> > > >
> > > > e2dxT12 ?-2.4 zgnd+0+1 zasd ? as-
> > > >
> > > >
Re: [Tex-music] lcharnote of a "personal" character and vertical alignment
Jean-Pierre--
I'm having a hard time understanding what you're saying and doing. But I'm
quite sure your MusiXTeX coding is inserting some "unrecorded" horizontal
space somewhere, because when I process it I get the dreaded "underfull box"
(see below), and that doesn't happen with Bob's solution, nor with any other
well-behaved musixtex file.
--Don
-
c:\Users\Don\Documents\PMX>gobigtex bachorna
c:\Users\Don\Documents\PMX>echo off
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9 64-bit)
entering extended mode
(c:\Users\Don\Documents\PMX\bachorna.tex
(C:\Users\Don\Documents\musixtex116\tex\generic\musixtex\musixtex.tex
MusiXTeX(c) 1.24PRE2 <2017-01-01>
maxinstruments=6 max128beams=6 maxgroups=3 maxslurs=6 maxtrills=6
maxoctlines=6)
\startmuflex launched by \startpiece
bar 1 bar 2 bar 3 [1] )
Output written on bachorna.dvi (1 page, 2180 bytes).
Transcript written on bachorna.log.
Musixflx-0.83.3.lua7 (bachorna.mx1)
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9 64-bit)
entering extended mode
(c:\Users\Don\Documents\PMX\bachorna.tex
(C:\Users\Don\Documents\musixtex116\tex\generic\musixtex\musixtex.tex
MusiXTeX(c) 1.24PRE2 <2017-01-01>
maxinstruments=6 max128beams=6 maxgroups=3 maxslurs=6 maxtrills=6
maxoctlines=6) (bachorna.mx2)
\startmuflex launched by \startpiece
< 1> bar 1 bar 2 bar 3
Underfull \hbox (badness 1248) in paragraph at lines 19--25
[][][][][][][][][][][][] [][][][][][][][][][][][][][][][][]
[1] )
(see the transcript file for additional information)
Output written on bachorna.dvi (1 page, 2184 bytes).
Transcript written on bachorna.log.
--
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Jean-Pierre
> Coulon
> Sent: Saturday, August 24, 2019 8:26 AM
> To: Werner Icking Music Archive
> Cc: Werner Icking Music Archive ; Jean-Pierre Coulon
>
> Subject: Re: [Tex-music] lcharnote of a "personal" character and vertical
> alignment
>
> On Sat, 24 Aug 2019, Bob Tennent wrote:
>
> > I'm not sure what you mean by "horizontal shift" or exactly
>
> Don't you notice the vertical misalignment between notes at measure 2 ?
>
> > what you want but the following would seem to be easier and more
> > flexible:
> >
> > \loff{\islurd1h}\tslur1e\qa{cdfe}
>
> Well, true with font-based slurs, but musixps manages very steep slurs in
its
> manner. :-) Or can I temporarily disengage musixps once I said \input
> musixps?
>
> Jean-Pierre Coulon
> ---
> 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
---
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] Please help with two-staves beam
One solution...the best in my book :) ... is simply to use PMX: == 2 1 11 16 0 0 0 0 1 1 20 0 tt .\ rb4 rb1 [j e14 ]j rb8 rbd8 / [ f15 g- c g+ ] [-3 e ]j rb[ju a- b b+ a g ] / == (To be honest, I did have to go back and tweak the starting height of beam 2 and the up-downness of the last segment). --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Friday, October 25, 2019 8:03 AM > To: tex-music@tug.org > Subject: [Tex-music] Please help with two-staves beam > > Hi, dear friends... > > in the example I'm attaching (to be processed with simply : tex file; musixflx > file; tex file) I want to share a beam (the beam number 1) between the two > staves but a strange undesired effect occurs, as you can see, that I don't > understand why... > > Please help whoever can... > > Thanks in advance, > > Rodolfo --- 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] Is it possible to put accompaniment chords above each bars in PMX?
Hi, Aki--
I'm afraid there no direct way to do this in PMX. There are two
work-arounds, illustrated in the code below. You could write a TeX macro to
slightly simplify the input for the \zcharnote approach.
--Don
% nv noinst mtrnuml mtrdenl mtrnump mtrdenp xmtrnum0 isig
1 1 4 4 0 6 00
% npages nsyst musicsize fracindent
1 120 0
t
./
Tt
Twinkle little star
Tc
Traditional
c4 D"\medtype C"+20 c g+ g |
a D"\medtype F"+17 a \zcharnote{12}{\medtype C}\ g2 |
f4 f e e | d d c2 /
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Akihiro
> Moriguchi
> Sent: Monday, December 16, 2019 5:09 AM
> To: tex-music@tug.org
> Subject: [Tex-music] Is it possible to put accompaniment chords above each
> bars in PMX?
>
> Hello all.
>
> I have a question about if I can put accompaniment chords on each bars.
>
> As I consult "Typesetting with PMX"pdf, there's "h" which introduce text
> above a system. But it can be only once used per a system and there's no
> mentioning about chords above bars on the document.
>
> Since maybe my English is poor to be understood, I paste a link to a score
> which I want to achive. (because I'm Japanese.)
> https://static.wixstatic.com/media/681c10_3ac4ce50489a4ec088dda4b6b820
> 91f7~mv2.png/v1/fill/w_740,h_198,al_c,q_90,usm_0.66_1.00_0.01/681c10_3
> ac4ce50489a4ec088dda4b6b82091f7~mv2.webp
>
> Can I make the score of above link with PMX?
>
> Best regards,
> Aki
>
> ---
> % nv noinst mtrnuml mtrdenl mtrnump mtrdenp xmtrnum0 isig
> 1 1 4 4 0 6 00
>
> % npages nsyst musicsize fracindent
> 1 4 20 0
>
> t
> ./
>
> Tt
> Twinkle little star
> Tc
> Traditional
>
> c4 c g+ g | a a g2 | f4 f e e | d d c2 /
>
>
>
>
>
>
>
> ---
> 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
---
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] PMX: problem with changing the number of instruments
As “huge” as it may be, you should attach the full PMX file or I probably won’t be able to help. --Don Simons From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On Behalf Of Dieter Sent: Tuesday, January 07, 2020 4:11 AM To: tex-music@tug.org Subject: [Tex-music] PMX: problem with changing the number of instruments I am a great fan of this feature in PMX and I am using it extensively over many pages and systems. But now I am stuck. I am working on the violin voice of the Ibert Flute Concerto. It compiles until the last few lines: % wieder einstimmig L22Mi.0cn12t m c85 za+ zf+ r8 r8 c85 za+ zf+ r4 c85 za+ zf+ r8 | / %m3434 rm1 | / %m f46x3 a- c- f8- r8 f46x3 a- c- f8- r8 | f46x3 a- c- f8- r8 f46x3 a- c- f8- r8 | / %f84 zc+ za+ r8 f84 zc+ za+ r8 f84 zc+ za+ r8 f84 zc+ za+ r8 | r4 f84 zc+ za+ r8 f84 zc+ za+ r8 f84 zc+ za+ r8 | / %f44 zc+ r2db // %a05 | / % a8 a r4 r2 === BUt when it hits the "L22"-Statement, then I am getting the error message: Somehow I have a déjà-vue feeling, but do not remember what I did to solve the problem. If I counted properly , the "L22" is the 10th statement of this kind. Of course I will not bother you with the huge code, but if somebody had similar experiences, I would be interested. Regards, Dieter --- 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] PMX: problem with changing the number of instruments
Dieter-- I managed to narrow this down to the full bar rests right before the change from 2 instruments to 1 . Then déjà vu did strike. I searched emails for \atnextbar and found that you had uncovered exactly the same problem in July. It was very tricky to nail down and there’s still no perfect solution, but there are work-arounds. Here’s what I wrote in a 7/3/19 posting, and it mostly still applies: “You're not doing anything wrong. You unearthed a very subtle problem that has never come up before. It depends on several specific unrelated things happening in exactly the right sequence. (Reminds me of the kinds of PMX bugs Werner used to find). It is basically caused by the whole-bar rests in the last bar before the movement break. The sequence of events leading to the problem is this: (1) whole bar rests by default are centered; (2) the centering is accomplished by \atnextbar, which isn't executed until a barline is encountered; (3) at the movement break, PMX enters the change in number of instruments BEFORE entering the barline. It turns out MusiXTeX is somewhat flexible here in that it would be OK if no instrument had 2 voices. But it's the bar-centered rest in the 2nd voice of the piano part that kills things...if you replace it with an ordinary note, it goes through just fine even if you leave the full bar rest in the 2nd instrument/3rd staff. “If you really want a centered full-bar rest in voice 2 of the piano part right before the decrease in number of instruments, I figured out a rather ugly work-around, but at least there's no inline TeX. I had to RTFM myself to refresh my memory, and I (re)discovered there's a PMX option 'o' on a full-bar rest that will suppress centering. But then you need to manually center it with an 'X' command. So just below is a file that works. “I'm very hesitant to try to change PMX to account for this, because whatever I did could mess up existing scores in unforeseen ways due to the complex interactions within and between movement breaks and bar centered rests.” --Don From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On Behalf Of Dieter Sent: Tuesday, January 07, 2020 4:11 AM To: tex-music@tug.org Subject: [Tex-music] PMX: problem with changing the number of instruments I am a great fan of this feature in PMX and I am using it extensively over many pages and systems. But now I am stuck. I am working on the violin voice of the Ibert Flute Concerto. It compiles until the last few lines: % wieder einstimmig L22Mi.0cn12t m c85 za+ zf+ r8 r8 c85 za+ zf+ r4 c85 za+ zf+ r8 | / %m3434 rm1 | / %m f46x3 a- c- f8- r8 f46x3 a- c- f8- r8 | f46x3 a- c- f8- r8 f46x3 a- c- f8- r8 | / %f84 zc+ za+ r8 f84 zc+ za+ r8 f84 zc+ za+ r8 f84 zc+ za+ r8 | r4 f84 zc+ za+ r8 f84 zc+ za+ r8 f84 zc+ za+ r8 | / %f44 zc+ r2db // %a05 | / % a8 a r4 r2 === BUt when it hits the "L22"-Statement, then I am getting the error message: Somehow I have a déjà-vue feeling, but do not remember what I did to solve the problem. If I counted properly , the "L22" is the 10th statement of this kind. Of course I will not bother you with the huge code, but if somebody had similar experiences, I would be interested. Regards, Dieter --- 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] bar crossing beam causes error message
PMX can’t yet handle bar-crossing beams. Here’s a way you could get that with
inline TeX. I’ve used numerical values for the note levels to avoid any
possible later confusion about which octave later notes are in. And that’s the
same reason I put rests rather than notes in the original PMX, in place of the
notes you want to connect.
--Don
=
1 1 2 4 2 4 0 0
1 1 20 0
t
.\
\\let\dst\ds\
rd4
\def\ds{\ibu130\qb13\let\ds\dst}\
r8 |
\def\ds{\tbu1\qb13\let\ds\dst}\
r8 rd4 /
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Thursday, January 16, 2020 3:26 AM
To: Werner Icking Music Archive
Subject: [Tex-music] bar crossing beam causes error message
This short extract from Beethoven's Elise produces the notes in the attachment.
---
\input musixtex
\input pmx
---
% nv, -noinst, nostaves per instrument
2 -1 2
% mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig
3 8 3 8 0 0
%
% npages,nsyst,musicsize,fracindent
0 5 16 0.07
bt
./
Abepl
%%w277m
%%h390m
%K-1-1
% ( 1| 2| 5) 13
[l e12l e13l e14l ] r1 r1 Ct (B e14l | e15l )B r1 r1 [l d15sl e15l ] r1
| /
% ( 1| 1| 1) 13
b84l r1 [u e14u e15u ] r1 | r1 [l e15l e16l ] r1 r1 d15sl | /
==
Trying to make a beam in the left hand from 1st to 2nd bar, I add the brackets.
---
\input musixtex
\input pmx
---
% nv, -noinst, nostaves per instrument
2 -1 2
% mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig
3 8 3 8 0 0
%
% npages,nsyst,musicsize,fracindent
0 5 16 0.07
bt
./
Abepl
%%w277m
%%h390m
%K-1-1
% ( 1| 2| 5) 13
[l e12l e13l e14l ] r1 r1 Ct (B [ e14l | e15l ] )B r1 r1 [l d15sl e15l ]
r1 | /
% ( 1| 1| 1) 13
b84l r1 [u e14u e15u ] r1 | r1 [l e15l e16l ] r1 r1 d15sl | /
===
When I run it, I get :
C:\Users\Glötzel>d:
D:\>cd musix
D:\MUSIX>cd jonah
D:\MUSIX\Jonah>Call "c:\programme\miktex 2.9\miktex\bin\pmx284.exe" withbeam
This is PMX, Version 2.84 , 30 Dec 17
Opening withbeam.pmx
Starting first PMX pass
Bar 1 Bar 2
Done with first pass
Starting second PMX pass
Bar 1
Timing problem w/ forced beams
At line 19134 of file pmx284_180208.for
Fortran runtime error: End of record
D:\MUSIX\Jonah>pause
Drücken Sie eine beliebige Taste . . .
Regards, Dieter
--
Dr. Dieter Glötzel
Im Rosengarten 27
64367 Mühltal
Tel.: 06151 / 360 82 72
---
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] bar crossing beam causes error message
Dieter--
Here’s your file with the method applied.
I used rests rather than notes, as well as numbers rather than letters for the
note levels in the in-line TeX, for exactly the reason I stated in my last
post. If you use letters for note names, MusiXTeX has a complicated way of
keeping track of which octave they should be in, depending sometimes but not
always on the previous note level entered. I avoid worrying about any of that
by using numbers for note levels, and by using a rest rather than a note as the
thing for which I substitute the desired TeX.
I may at some point enable PMX to handle this situation, but please don’t hold
your breath. It could be very complicated, plus I’m currently hung up working
on the issues raised earlier about moving dots on 2-note tremolos.
But if you have any more questions about this in-line TeX band-aid, please let
me know.
--Don
==
% nv, -noinst, nostaves per instrument
2 -1 2
% mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig
3 8 3 8 0 0
%
% npages,nsyst,musicsize,fracindent
0 5 16 0.07
bt
./
\\global\let\qst\qs\
Abepl
%%w277m
%%h390m
%K-1-1
% ( 1| 2| 5) 13
[l e12l e13l e14l ] r1 r1 Ct
\def\qs{\ibbl134\qb10\global\let\qs\qst}\ r1 |
\def\qs{\tbl1\qb17\global\let\qs\qst}\ r1
r1 r1 [l d15sl e15l ] r1 | /
% ( 1| 1| 1) 13
b84l r1 [u e14u e15u ] r1 | r1 [l e15l e16l ] r1 r1 d15sl | /
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Thursday, January 16, 2020 10:25 AM
To: tex-music@tug.org
Subject: Re: [Tex-music] bar crossing beam causes error message
Don--
I do not understand enough TeX and MusiXTeX to follow your working example. In
particular I do not understand, why you must use rests in order to print eighth
notes. I do not see, how I could extend this example to solve my real life
problem.
Have you been working on this problem?
--Dieter
Am 16.01.2020 um 18:14 schrieb Don Simons:
1 1 2 4 2 4 0 0
1 1 20 0
t
.\
\\let\dst\ds\
rd4
\def\ds{\ibu130\qb13\let\ds\dst}\
r8 |
\def\ds{\tbu1\qb13\let\ds\dst}\
r8 rd4 /
--
Dr. Dieter Glötzel
Im Rosengarten 27
64367 Mühltal
Tel.: 06151 / 360 82 72
---
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] bar crossing beam causes error message
Dieter--
Spurred by a private email from Bob Tennent, I’ve thought some more about the
inline TeX, and came up with this slightly less complicated version. I’m still
more comfortable using numbers rather than letters for pitch levels in inline
TeX, and that’s no problem if you don’t plan to transpose. In the new version,
rather than redefining the rest macro, I use PMX blank rests and direct
MusiXTeX commands for the start and end of the beam. It’s necessary to
backspace after each group of inline commands to make up for the forward
spacing that PMX inserts for the blank rests. It was also necessary to do trial
and error to get the slur in the right place (as it will often be in cases like
this).
An unrelated observation: I’m a bit puzzled why you bothered to explicitly
input musixtex.tex and pmx.tex in a type 4 inline TeX block at the beginning.,
when PMX does this automatically.
--Don
=
---
\input musixtex
\input pmx
---
% nv, -noinst, nostaves per instrument
2 -1 2
% mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig
3 8 3 8 0 0
%
% npages,nsyst,musicsize,fracindent
0 5 16 0.07
bt
./
Abepl
%%w277m
%%h390m
%K-1-1
% ( 1| 2| 5) 13
% [l e12l e13l e14l ] r1 r1 Ct (B e14l | e15l )B r1 r1 [l d15sl e15l ] r1
| /
[l e12l e13l e14l ] r1 r1 Ct (Bu-5-1
\ibbl103\qb10\bsk\
rb |
\tbl1\qb17\bsk\
rb )B+2 r1 r1 [l d15sl e15l ] r1 | /
% ( 1| 1| 1) 13
b84l r1 [u e14u e15u ] r1 | r1 [l e15l e16l ] r1 r1 d15sl | /
===
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Thursday, January 16, 2020 2:45 PM
To: 'Werner Icking Music Archive'
Subject: RE: [Tex-music] bar crossing beam causes error message
Dieter--
Here’s your file with the method applied.
I used rests rather than notes, as well as numbers rather than letters for the
note levels in the in-line TeX, for exactly the reason I stated in my last
post. If you use letters for note names, MusiXTeX has a complicated way of
keeping track of which octave they should be in, depending sometimes but not
always on the previous note level entered. I avoid worrying about any of that
by using numbers for note levels, and by using a rest rather than a note as the
thing for which I substitute the desired TeX.
I may at some point enable PMX to handle this situation, but please don’t hold
your breath. It could be very complicated, plus I’m currently hung up working
on the issues raised earlier about moving dots on 2-note tremolos.
But if you have any more questions about this in-line TeX band-aid, please let
me know.
--Don
==
% nv, -noinst, nostaves per instrument
2 -1 2
% mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig
3 8 3 8 0 0
%
% npages,nsyst,musicsize,fracindent
0 5 16 0.07
bt
./
\\global\let\qst\qs\
Abepl
%%w277m
%%h390m
%K-1-1
% ( 1| 2| 5) 13
[l e12l e13l e14l ] r1 r1 Ct
\def\qs{\ibbl134\qb10\global\let\qs\qst}\ r1 |
\def\qs{\tbl1\qb17\global\let\qs\qst}\ r1
r1 r1 [l d15sl e15l ] r1 | /
% ( 1| 1| 1) 13
b84l r1 [u e14u e15u ] r1 | r1 [l e15l e16l ] r1 r1 d15sl | /
From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On
Behalf Of Dieter
Sent: Thursday, January 16, 2020 10:25 AM
To: tex-music@tug.org <mailto:tex-music@tug.org>
Subject: Re: [Tex-music] bar crossing beam causes error message
Don--
I do not understand enough TeX and MusiXTeX to follow your working example. In
particular I do not understand, why you must use rests in order to print eighth
notes. I do not see, how I could extend this example to solve my real life
problem.
Have you been working on this problem?
--Dieter
Am 16.01.2020 um 18:14 schrieb Don Simons:
1 1 2 4 2 4 0 0
1 1 20 0
t
.\
\\let\dst\ds\
rd4
\def\ds{\ibu130\qb13\let\ds\dst}\
r8 |
\def\ds{\tbu1\qb13\let\ds\dst}\
r8 rd4 /
--
Dr. Dieter Glötzel
Im Rosengarten 27
64367 Mühltal
Tel.: 06151 / 360 82 72
---
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] Can MusiXTeX input guitar chokings?
If all you want is "cho." and a small note with slur, that's very easy in
PMX:
=
1 1 1 4 1 4 0 0
1 1 20 0
t
.\
w1i
Gsxg5 a4 D"cho."+19 /
=
which produces
The TeX input is
\input pmx
.
\pnotes{2.83}\ast{.31}\shlft8{\islurd0{'g}\grcu g\off{-\noteskip}}%
\ts0{'a}{-.6}\txtdyn{14}{-.5}{\medtype\it cho.}\ql a\en%
--Don Simons
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Akihiro
> Moriguchi
> Sent: Friday, January 24, 2020 7:01 AM
> To: tex-music@tug.org
> Subject: [Tex-music] Can MusiXTeX input guitar chokings?
>
> Hello all.
>
> I'm looking for a way to input guitar choking like this.
> <https://www.instagram.com/p/B7tNcMTgqsd/>
https://www.instagram.com/p/B7tNcMTgqsd/
>
> "cho." and small note with slur on the score is the guitar choking.
> With PMX and M-Tx, as much as I learned, there's no measure to input
guitar
> choking.
>
> Do MusiXTeX have the way to input guitar choking?
>
> Best regards,
> Aki
> ---
> <mailto:TeX-music@tug.org> 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>
https://tug.org/mailman/listinfo/tex-music
---
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] Can MusiXTeX input guitar chokings?
PMX didn't know that either, but it does know how to do grace notes, with or
without slashes through the flag or slurs.
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Akihiro
> Moriguchi
> Sent: Friday, January 24, 2020 2:40 PM
> To: tex-music@tug.org
> Subject: Re: [Tex-music] Can MusiXTeX input guitar chokings?
>
> I didn't know that PMX could add guitar choking.
> Thanks.
>
> Here's a corrected pic by orientation of 90 degree.
> https://www.instagram.com/p/B7uBoEJp8Jk/
>
> Aki.
>
> On 2020/01/25 1:24, Don Simons wrote:
> > If all you want is "cho." and a small note with slur, that's very easy
> > in PMX:
> >
> > =
> >
> > 1 1 1 4 1 4 0 0
> >
> > 1 1 20 0
> >
> > t
> >
> > .\
> >
> > w1i
> >
> > Gsxg5 a4 D"cho."+19 /
> >
> > =
> >
> > which produces
> >
> > The TeX input is
> >
> > \input pmx
> >
> >
> >
> > \pnotes{2.83}\ast{.31}\shlft8{\islurd0{'g}\grcu g\off{-\noteskip}}%
> >
> > \ts0{'a}{-.6}\txtdyn{14}{-.5}{\medtype\it cho.}\ql a\en%
> >
> > --Don Simons
> >
> > > -Original Message-
> >
> > > From: TeX-Music [mailto:tex-music-
> >
> > > bounces+dsimons=roadrunner@tug.org] On Behalf Of Akihiro
> >
> > > Moriguchi
> >
> > > Sent: Friday, January 24, 2020 7:01 AM
> >
> > > To: tex-music@tug.org
> >
> > > Subject: [Tex-music] Can MusiXTeX input guitar chokings?
> >
> > >
> >
> > > Hello all.
> >
> > >
> >
> > > I'm looking for a way to input guitar choking like this.
> >
> > > https://www.instagram.com/p/B7tNcMTgqsd/
> >
> > >
> >
> > > "cho." and small note with slur on the score is the guitar choking.
> >
> > > With PMX and M-Tx, as much as I learned, there's no measure to
> > input guitar
> >
> > > choking.
> >
> > >
> >
> > > Do MusiXTeX have the way to input guitar choking?
> >
> > >
> >
> > > Best regards,
> >
> > > Aki
> >
> > > ---
> >
> > > TeX-music@tug.org <mailto: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
> >
> >
> > ---
> > 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
> >
> ---
> 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
---
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] 8va position is too low
Aki--
Congratulations on finding this guidance in CCN's expanded PMX manual.
However, I'd caution you (and others) that that manual has not been updated
in quite some time. So you should also keep handy the latest version of the
basic PMX manual, which I update with every official release. (And I'll soon
be posting version 2.94).
I don't understand "differences are little." Using \Ioctfinup allows you to
put the symbol at any height. Again a caution: using letters for note levels
in inline TeX within a PMX input is risky, since it could change the octave
of later notes. It's always safer to use numbers for pitch levels in inline
TeX. This will never cause problems unless you later want to transpose the
input.
So in this case \Ioctfinup1{18}\ will do the job.
Other comments:
I assume the \toctfin1\ command in your example is a leftover from a larger
file from which you extracted the example. Otherwise I don't see any reason
for it.
If you want to continue to use PMX's default bar numbering, you may want to
shift some of the bar numbers to the left. This can be done with inline TeX
using the macro \bnrs defined in pmx.tex, inserted before the linebreak. For
example \bnrs1{-4}\ will shift the next bar number 1\internote up and 4
notehead widths to the left.
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Akihiro
> Moriguchi
> Sent: Sunday, January 26, 2020 7:24 AM
> To: tex-music@tug.org
> Subject: Re: [Tex-music] 8va position is too low
>
> Hi Hiroaki,
>
> Thank you.
> All works well though differences are little.
> I've also read the section describing about \Ioctfin* in musixdoc.pdf, but
> couldn't understand well for the time being.
> I need more study about MusiXTeX and musical English jargon.
>
> Thanks anyway.
> Arigatou.
> Aki
>
>
> On 2020/01/26 23:20, Hiroaki MORIMOTO wrote:
> > Hi Aki,
> >
> > Say \Ioctfinup1r\ or \Ioctfinup1s\ or \Ioctfinup1t\ instead of
> > \Ioctfinup1d\ .
> > r, t, or u may be adjusted as you like.
> > For details, search the word "Ioftcin" in musixdoc.pdf.
> >
> > Best regards,
> >
> > Hiroaki
> >
> >
> >
> > - Original Message -
> >> To: tex-music@tug.org
> >> From: Akihiro Moriguchi
> >> Date: Sun, 26 Jan 2020 15:21:58 +0900
> >> Subject: [Tex-music] 8va position is too low
> >>
> >>
> >> Hello again all,
> >>
> >> Now I can handle guitar choking with grace note of PMX.
> >>
> >> But I have another problem.
> >> According to "E1.3 Clef octaviation" of "Typesetting music with
> >> PMX", http://icking-music-archive.org/software/pmx/pmxccn.pdf
> >> I can put "8va" to the score, but the position is too low like
> >> following pic.
> >> https://www.instagram.com/p/B7xbFFzJzbE/
> >>
> >> How can I reposition "8va" to higher place?
> >>
> >> Best regards,
> >> Aki
> >>
> >> ---
> >> \input musixtex
> >> \input pmx
> >> \input musixlyr
> >> \input chords
> >> \input tuplet
> >>
> >> \setlyrics{code}
> >> {
> >> }
> >> ---
> >> % nv noinst mtrnuml mtrdenl mtrnump mtrdenp xmtrnum0 isig
> >> 1 1 4 4 0 6 00
> >>
> >> % npages nsyst musicsize fracindent
> >> 1 4 20 0
> >>
> >> t
> >> ./
> >> %AeI10
> >> %It100ipi
> >> \\def\octnumber{8$^{va}$}\
> >>
> >> % 1-4
> >> r2 r8 c8 [ ( d1 e ) D"\t h."-1-1 g8 ] | [ g1 a ( c8 ] [ c ) Gsxd
> >> D"\ cho."+19-0 e ] r ( c [ c ) ( a1 g ) D"\t
> >> p."-0-1 ] |
> >> a4 c ze r2 |
> >> r8 [ ( a8 D"\t u."+19-0 g D"\t C.D."+19-1.5 ) Gsxg D"\t cho."+21+2 (
> >> a ]
> >> a2 ) \toctfin1\ /
> >>
> >> % 5-8
> >> r4 r1 f8 [ ( e1 ( f ) e ) D"\t h.p."+19-2.5 d8 ] [ c8 b ] | [ D"\t
> >> s."+19+5 ( c8 d ) r ( g- ] g ) g4 g8 | [ D"\t s."-0+5.5 D"\t s."-0+8
> >> ( g ( a ) g ) ( g ] g2 ) |
> >> r2 ( r8 [ a8+ ) c ] r8 /
> >>
> >> % 9-12
> >> \Ioctfinup1d\
> >> Gsxd- e8 D"\t cho."+16-1 c4 a8 [ c8 c ( d e ) ] |
> >> r2 r8 [ a8 g ] r8 |
> >> ( a4 g8 ) r8 [ ( e8 ( d ) ] [ d ) ( c1 d ) ] |
> >> c4 ( a r2 ) /
> >>
> >> % 13-16
> >> r4 r1 f8+ [ ( e1 ( f ) e ) c8 ] [ g8 ( a ] |
> >> b2 ) r8 c4 b8 |
> >> b4d c8 ( c2 |
> >> c0 ) /
> >>
> >>
> >>
> >> ---
> >> 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
> >
> > ---
> > 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
> >
> ---
> 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
---
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
[Tex-music] New PMX version
I've just created a new full release of PMX (Version 2.94), and it's available from the archive at https://icking-music-archive.org/software/htdocs/index.html . No major external changes, but I did a lot of internal tweaking on moving dots, focused on main and chordal notes in dotted 2-note tremolos. I'd appreciate any feedback in case I've introduced any bugs. Bob Tennent will soon be preparing it for submission to TeXLive to make it more easily available to platforms other than Windows. --Don Simons --- 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] New PMX version
With help from Christian Mondrup and Bob Tennent I've addressed a few FORTRAN bugs, and reposted the entire zip file under the same name. FYI these were very subtle, not showing up with my gfortran compiler but they did occur with several other compilers that Christian and Bob used. Hopefully they're now fixed. If you downloaded the older one from yesterday, to be safe please replace it with today's version. Happy PMX'ing! --Don Simons From: Don Simons [mailto:dsim...@roadrunner.com] Sent: Monday, January 27, 2020 7:30 AM To: 'Werner Icking Music Archive' Subject: New PMX version I've just created a new full release of PMX (Version 2.94), and it's available from the archive at https://icking-music-archive.org/software/htdocs/index.html . No major external changes, but I did a lot of internal tweaking on moving dots, focused on main and chordal notes in dotted 2-note tremolos. I'd appreciate any feedback in case I've introduced any bugs. Bob Tennent will soon be preparing it for submission to TeXLive to make it more easily available to platforms other than Windows. --Don Simons --- 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] New PMX version
Since last Tuesday I've had some more interaction with Bob and Christian about other issues compiling version 2.94 of PMX. I think Bob's are resolved without any further revisions, but I believe Christian is still unable to create a functioning executable using fort77 under Linux. I'd very much appreciate it if some more folks would download the zip, compile pmx294.for, and report back on what system and compiler you used and whether the resulting executable runs OK. Thanks, --Don Simons From: Don Simons [mailto:dsim...@roadrunner.com] Sent: Tuesday, January 28, 2020 8:19 PM To: 'Werner Icking Music Archive' Subject: RE: New PMX version With help from Christian Mondrup and Bob Tennent I've addressed a few FORTRAN bugs, and reposted the entire zip file under the same name. FYI these were very subtle, not showing up with my gfortran compiler but they did occur with several other compilers that Christian and Bob used. Hopefully they're now fixed. If you downloaded the older one from yesterday, to be safe please replace it with today's version. Happy PMX'ing! --Don Simons From: Don Simons [mailto:dsim...@roadrunner.com] Sent: Monday, January 27, 2020 7:30 AM To: 'Werner Icking Music Archive' mailto:tex-music@tug.org> > Subject: New PMX version I've just created a new full release of PMX (Version 2.94), and it's available from the archive at https://icking-music-archive.org/software/htdocs/index.html . No major external changes, but I did a lot of internal tweaking on moving dots, focused on main and chordal notes in dotted 2-note tremolos. I'd appreciate any feedback in case I've introduced any bugs. Bob Tennent will soon be preparing it for submission to TeXLive to make it more easily available to platforms other than Windows. --Don Simons --- 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] New PMX version
It's frustrating not having any Linux version in which I can personally investigate the problems people are reporting with compiling and running PMX294. As far as I recall, we've never had problems like this before. So if it's possible to make it run alongside or under my Windows 7 OS, I'm willing to download and install one version of Linux. Can anyone advise me (1) whether that's possible; (2) if so, which Linux system would be the one that would be most useful for the problem at hand (i.e., resolving FORTRAN compilation issues); (3) where to go to get the download; (4) is a FORTRAN compiler included in the download; (5) if not, which fortran compiler should I download and install and where should I go to get it? --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Christian > Mondrup > Sent: Wednesday, February 05, 2020 7:27 AM > To: tex-music@tug.org > Subject: Re: [Tex-music] New PMX version > > Den 03.02.2020 kl. 07.59 skrev Luigi Cataldi: > > Dear Don, in my Fedora 30 Linux I'm able to compile pmxab.for only > > with 'f2c'. With the previous pmx version I had made several attempts > > with 'gfortran' and 'g77' but all of them failed. As far as I know, > > however, 'f2c' no longer exists in Ubuntu and this is a problem. > > 'f2c' is indeed distributed with linux mint 19.3 based on Ubuntu 18.04 bionic > > > > On Fedora 30 I have used the following command: > > > > 'f2c -g -\!bs < pmx294.for > pmxab.c' > > > > The compilation returned me only one warning message: > > > > 'Warning on line 11244: local variable gotclef never used' > > > > There was no problem with compiling via 'gcc' with the command: > > > > gcc pmxab.c -lf2c -lm -o pmxab > > > > It happens nearly the same with 'scor2prt': > > > > f2c -g -\!bs < scor2prt.for > scor2prt.c > > > > 'Warning on line 783: local variable dumq never used' > > > > As far as I could see, 'pmx294' works well. > > Compiling pmx294.for with f2c and gcc in my Ubuntu 18.04 based > environment completes with no errors and warnings. The compiled binary > doesn't work, however. When I launch it on a pmx files I get no output at all - > no error messages, no output file. > > Contrarily a binary compiled with gfortran from pmx294.for works perfectly. > > Greetings > -- > Christian Mondrup > WIMA: Werner Icking Music Archive > http://imslp.org/wiki/Category:WIMA_files > > --- > 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 --- 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] IMSLP Chopin's mazurka pmx engraving files
Jean-Pierre wrote > > BTW does anybody know why are MusiXTeX and pmx files downloaded > about 10 % as many times as the pdf? Who finds something useful in them? > How does one find out how many time a particular file on IMSLP has been downloaded? --Don Simons --- 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] PMX: \starteq and \endeq
Rodolfo et al-- The purpose of those two commands is to adjust the vertical spacing between systems on a page so that the distance between the bottom line of the last staff in each system and the top line of the first staff in the next system are all equal. \starteq must be entered somewhere in the first system on the page and \endeq somewhere in the next to last. You would only insert these near the end of the editing process when all the line breaks and page breaks have been finalized. The reason for having these is that normally MusiXTeX tries to equalize the vertical gap between the lowest object in the bottom staff of each system and the highest object in the top staff of the next. If either of those is a note or rest outside the staff, that will make the space between the bottom staff line in that system and the top one in the next larger than what it would otherwise be. And (to my eye) sometimes that's not necessary and I'd prefer ignoring any protruding notes when equalizing the vertical spaces between systems. The way the macros work is that they insert very long, invisible, vertical struts below every system except the last, and above every system except the first. When MusiXTeX initially sets up the page it considers those struts as visible objects, and after stacking up the systems it finds that it is much taller than the available space. When it scales down the vertical gaps between staves (which are now large and equal) it leads to the desired result. --Don > -Original Message- > From: TeX-Music [mailto:tex-music- > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo Medina > Sent: Tuesday, June 30, 2020 11:26 PM > To: tex-music@tug.org > Subject: [Tex-music] PMX: \starteq and \endeq > > Hi Don, hi Bob, hi everyone: > > I wish to know the meaning and the role of the two PMX internal commands > \starteq and \endeq... Can you please help me...? Thanks. > > Cheers, > > Rodolfo > --- > 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 --- 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] PMX: \starteq and \endeq
Rodolfo et al-- I sent this message 4 hours ago and it seems like it never got posted, so I'm trying again. The purpose of those two commands is to adjust the vertical spacing between systems on a page so that the distance between the bottom line of the last staff in each system and the top line of the first staff in the next system are all equal. \starteq must be entered somewhere in the first system on the page and \endeq somewhere in the next to last. You would only insert these near the end of the editing process when all the line breaks and page breaks have been finalized. The reason for having these is that normally MusiXTeX tries to equalize the vertical gap between the lowest object in the bottom staff of each system and the highest object in the top staff of the next. If either of those is a note or rest outside the staff, that will make the space between the bottom staff line in that system and the top one in the next larger than what it would otherwise be. And (to my eye) sometimes that's not necessary and I'd prefer ignoring any protruding notes when equalizing the vertical spaces between systems. The way the macros work is that they insert very long, invisible, vertical struts below every system except the last, and above every system except the first. When MusiXTeX initially sets up the page it considers those struts as visible objects, and after stacking up the systems it finds that it is much taller than the available space. When it scales down the vertical gaps between staves (which are now large and equal) it leads to the desired result. --Don > > > -Original Message- > > From: TeX-Music [mailto:tex-music- > > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo > Medina > > Sent: Tuesday, June 30, 2020 11:26 PM > > To: tex-music@tug.org > > Subject: [Tex-music] PMX: \starteq and \endeq > > > > Hi Don, hi Bob, hi everyone: > > > > I wish to know the meaning and the role of the two PMX internal > > commands \starteq and \endeq... Can you please help me...? Thanks. > > > > Cheers, > > > > Rodolfo > > --- > > 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 --- 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] PMX: \starteq and \endeq
Well, another example of my fading memory. The explanation of what the
macros do was correct, but the way you get PMX to use them is not by
entering them explicitly as inline TeX; it's to insert the option Ae before
the first input block of the page where you want the corrections it to
start, then PMX does the work. And it turns out there's a fine explanation
of that in the PMX manual, section 2.3.9 (version 2.94). The explanation
also points out that if you want to override the equalization you can insert
he macro \spread{n}\, and the space after that line will be increased by n
\internotes.
Attached is a sample file. The first page has no vertical adjustments and
shows how MusiXTeX gives unequal vertical spacing after the 2nd system. The
vertical corrections due to Ae start on the second page, which otherwise has
exactly the same PMX input as the first page. The 3rd page shows how
\spread{10}\ overrides the equalization after the 5th system.
Evidently, although it's OK to start Ae after the first page, once it's
started, there's no easy way to turn it off.
Sorry for my confused memory.
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner....@tug.org] On Behalf Of Don Simons
> Sent: Wednesday, July 01, 2020 1:06 PM
> To: 'Werner Icking Music Archive'
> Subject: Re: [Tex-music] PMX: \starteq and \endeq
>
> Rodolfo et al--
>
> I sent this message 4 hours ago and it seems like it never got posted, so
I'm
> trying again.
>
> The purpose of those two commands is to adjust the vertical spacing
> between systems on a page so that the distance between the bottom line of
> the last staff in each system and the top line of the first staff in the
next
> system are all equal. \starteq must be entered somewhere in the first
> system on the page and \endeq somewhere in the next to last. You would
> only insert these near the end of the editing process when all the line
breaks
> and page breaks have been finalized.
>
> The reason for having these is that normally MusiXTeX tries to equalize
the
> vertical gap between the lowest object in the bottom staff of each system
> and the highest object in the top staff of the next. If either of those is
a note
> or rest outside the staff, that will make the space between the bottom
staff
> line in that system and the top one in the next larger than what it would
> otherwise be. And (to my eye) sometimes that's not necessary and I'd
prefer
> ignoring any protruding notes when equalizing the vertical spaces between
> systems.
>
> The way the macros work is that they insert very long, invisible, vertical
struts
> below every system except the last, and above every system except the
> first. When MusiXTeX initially sets up the page it considers those struts
as
> visible objects, and after stacking up the systems it finds that it is
much taller
> than the available space. When it scales down the vertical gaps between
> staves (which are now large and equal) it leads to the desired result.
>
> --Don
> >
> > > -Original Message-
> > > From: TeX-Music [mailto:tex-music-
> > > bounces+dsimons=roadrunner@tug.org] On Behalf Of Rodolfo
> > Medina
> > > Sent: Tuesday, June 30, 2020 11:26 PM
> > > To: tex-music@tug.org
> > > Subject: [Tex-music] PMX: \starteq and \endeq
> > >
> > > Hi Don, hi Bob, hi everyone:
> > >
> > > I wish to know the meaning and the role of the two PMX internal
> > > commands \starteq and \endeq... Can you please help me...? Thanks.
> > >
> > > Cheers,
> > >
> > > Rodolfo
> > > ---
> > > 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
>
> ---
> 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
eqtest.pdf
Description: Adobe PDF document
eqtest.pmx
Description: Binary data
---
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
[Tex-music] Attention postscript MusiXTeX font users!
Since the original release of the Type 1 fonts by Takanori Uchiyama, he has made two coreections, first in February 2002 (7 files) and then February 2003 (1 file). If you haven't updated, you should (If you don't, your computer might explode). To spare you the 4.5 MB download of the whole package, I've set up links from the software page to separate files for each upgrade: http://icking-music-archive.org/software/musixtex/xslz20.pfb for Feb 03, and http://icking-music-archive.org/software/musixtex/xslhdFeb02.zip for Feb 02. After renaming your old files for safety, just copy the files into wherever you keep .pfb's . You probably don't even need to update the filename database. --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] New member and question1
Francois--
On my Win98 system, I go to Start|Programs|MiKTeX|MiKTeX Options. After
clicking on (i.e., running) "MiKTeX Options", the very first screen
("General" tab) has a button labelled "Refresh Now".
--Don Simons
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Francois
> Planiol-Auger
> Sent: Sunday, November 16, 2003 1:21 PM
> To: Typesetting music with TeX
> Subject: AW: [Tex-music] New member and question1
>
>
> Hi Eva!
>
> Almost done!
>
> I did again from the beginning all your recommandations in
> http://icking-music-archive.org/software/musixtex/musixwinst12.pdf
> but:
>
> 1.
> I dont understand here: 2.2.5.
> >>>>>Schnipps>>>>>>>>Go to the MiKTEX Options dialogue and
> refresh the File
> Name Database to tell MiKTEX about all
> its beautiful new les.>>>>>>>Schnapps>>>>>>>>>
> Where do I find this "MikTex Options dialogue" ???
>
> 2.
> I have really very much remains (see the whole List in PS) and I
> am not sure
> at all, that some do not have to be somewhere else??
>
> Thanks again in advance for your answer(s), or to anybody that helps!
>
> François
>
> PS: prepmx (from mtx*/bin)
> 28 Files, most C or H-files (from mtx*/prepmx)
> mtx and mtxlatex.sty from mtx*/tex
> 73 .tfm files (from Musixtex/fonts/tfm)
> copying (from Musixtex)
> pmxab and scor2prt (from pmx240/bin)
> mxsk.mf (from psslur-K/metafont)
>
> -> -Ursprüngliche Nachricht-
> -> Von: [EMAIL PROTECTED]
> -> [mailto:[EMAIL PROTECTED] Auftrag von
> -> [EMAIL PROTECTED]
> -> Gesendet: Samstag, 15. November 2003 17:13
> -> An: TeX-Music
> -> Betreff: Re: [Tex-music] New member and question1
> ->
> ->
> -> On Friday, November 14, 2003 at 10:31:34 AM, you wrote:
> ->
> -> > I have to work with a PC, so my
> -> > - Question 1 is: What editor works certainly with Windows ME? I tried
> -> > TexnicCenter (doesnt accept MusixTex), THE (ever makes error),
> -> WinTex 2000
> -> > (seems ok but dont know how to install MusTeX), Ultraedit-32
> -> (seems ok but
> -> > dont know how to install MusTeX), still without success. And
> -> how install
> -> > MusixTex on it and install preprocessors?
> ->
> -> François,
> ->
> -> For installing the preprocessors, the first thing you should do is
> -> visit the Icking Archive's software pages and download the UPDATED
> -> version of the Install Guide for Windows. This version takes into
> -> account the changes in the structure of the zip file which contains
> -> the installation files for everything except raw MusixTeX.
> ->
> -> After you've followed the instructions in that guide, both MusixTeX
> -> and the preprocessors will be installed and ready to use on your
> -> computer.
> ->
> -> You do not need to "install" either MusixTeX and the preprocessors in
> -> the actual editor. All you need to do is tell the editor where the
> -> TeX programs are that you want to run on your files.
> ->
> -> I sent you a mail off-list a couple of weeks or so ago in which I
> -> mentioned how to do this in WinTeX 2000. Here's a repeat in case
> -> you no longer have that message:
> ->
> -> To create a link to Musixflex:
> ->
> -> Go to the View menu, click Options, select the TeX Programs tab, click
> -> Add underneath the list of installed TeX programs.
> ->
> -> Next, on the right side of the tab, type "musixflex" in the name
> -> field.
> ->
> -> In the Commandline field, type the path to your copy of musixflx.exe
> -> in the following format: c:\localbin\musixflx.exe %f (you will need to
> -> change this to reflect the exact location of musixflx.exe on YOUR
> -> system. Don't forget the "%f" at the end.
> ->
> -> Select a function key from the drop-down list in the Shortcut field.
> ->
> -> Check the "force execution on current file" check box.
> ->
> -> Check the "show button" checkbox.
> ->
> -> Click OK at the bottom left of the dialogue box to save the changes.
> ->
> -> To make the preprocessors available, go through the same procedure for
> -> pmxab.exe and mtx.exe.
> ->
> -> (Note: You may need to do this for tex.exe as well. I can't remember
> -> whether WinTeX 2000 comes preconfigured with a shortcut for TeX as
> -> well as f
RE: [Tex-music] PMX dynamic strings and hairpins
Christian Mondrup wrote >... I've run into a problem with a string > argument to > the PMX dynamics command D"bla bla". > > The string in question is "dolce sempre e col pedale" which is > applied on a > chord in the right hand piano staff. Well that's the problem. PMX was written for harpsichords, and they don't have pedals :-) > I appended it to the main > note of the > chord and got an M-Tx error message on note duration errors! I realize, > however, that this must be due to a bug in the prepmx parsing: > when I enter > the string expression directly into the PMX file resulting from prepmx > processing I don't get _that_ error any more. But the last > character of the > string is stripped! Did I encounter an (undocumented?) PMX limit on > dynamics string lengths? All seriousness aside, the limit is now 24 characters. How big do you want me to make it? > And then to hairpins. According to Don's original PMX > documentation and to > Cornelius Noack's new English version of Luigi Cataldis PMX tutorial > hairpin dynamics can't extend a PMX input block. The above mentioned song > contradicts that! Prepmx inevitably creates a new PMX block for each > measure. But that doesn't prevent me from typesetting a crescendo hairpin > in the vocal staff starting in bar 5 and continuing in bar 6. I > enjoy that > as an undocumented feature:-) There was some reason I included that restriction in the docs, but at the moment I can't recall what it was. I just tried two simultaneous cross-block postscript hairpins and they did work, even across a linebreak. I'll offer a free copy of the upcoming PMX 2.5 to the first person who can break this undocumented capability. --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] RE: staff jumping beams
Christian Mondrup wrote > ...In #4 of the Laub songs, 'Han læser sedlen' (just published) there are 2 > beam groups across bar lines in bar 24-25. I've fooled M-Tx/PMD > to do this > by merging these bars into one 'technical' 4/4 bar and then inserting > barlines 'by hand' (using a musixtex trick contributed by Olivier Vogel > several months ago, see accompanying source file). However, I haven't > succeeded in, _on PMX level_, to get the lower of these beam > groups to jump > to the left hand staff with the final note only. PMX doesn't like > a jumping > beam group consisting of a single note! I can live with the current > typesetting solution but would like to improve it with the staff jumping > feature. I'll be able to achieve that by means of inline > musixtex. But I'd > prefer a PMX level solution. In other words I (probably) ask for > a new PMX > feature. I downloaded ritornel4.mtx from the archive but I can't get it to compile. I get the message c:\my documents\pmx>prepmx ritornel4 ==> This is M-Tx pre0.54c (Music from TeXt) <15 August 2003> Writing to ritornel4.pmx No music paragraphs!: ERROR on line 1 Any idea what's wrong? --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] RE: staff jumping beams--my own problem solved
I wrote > I downloaded ritornel4.mtx from the archive but I can't get it to > compile. I > get the message > > c:\my documents\pmx>prepmx ritornel4 > ==> This is M-Tx pre0.54c (Music from TeXt) <15 August 2003> > Writing to ritornel4.pmx > No music paragraphs!: ERROR on line 1 > > Any idea what's wrong? > It was the d*#@ line-ending characters! Why doesn't everyone just use Windows? :-) --Don ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] PMX dynamic strings and hairpins + staff jumping beams
Olivier wrote
> Dear Christian,
>
> Would you like to get that?
>
> % 24-25
> m4400 b8 o> g c4 \MB{1.5}\ r4 r8 c |
> L: fri-ske Kys, Pe-
> m4400 (d bu4- Dmf-3+1 zg zd cu8+ )f-7 zg zc- [ g8++ o. e o. c o.
> a o. ] cu za ze o. |
> m4400 r4db [+2-2 g8 Df-2+1 o.-10 e o.-10 c o.-9 ]j r4b |
> m4400 r2b r4b [jl a8 o. ] r8b |
> m4400 Cb (u f4- e8 )f r8+0 rd4+0 f8s o. |
After translating this back to PMX :-) I see that it works exactly as
advertised, no new features required. Christian, I'm curious what syntax you
tried that did not work.
On the stylistic front, I wonder why staff-jumping would be preferred to
ledger lines in this case.
--Don
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] Transposition in pmx
Kurt, you've stumbled where many others have stumbled. If you want to transpose, you must use relative accidentals. You've gone half way by entering "Ar". To go the rest of the way, you also have to change the way you enter the notes, because "Ar" changes the meanings of "s", "f", and "n". If you want what you would ordinarily read as "B-flat, a B-natural, and a B-sharp" you should enter "bn bs bss", or just "b bs bss" if you don't want a flat to appear explicitly on the first b. When using relative accidentals, "n" means "leave it right where it is according to the key signature" and "s" means "raise it 1/2 step from where it would be according to the key signature", etc. --Don Simons > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Kurt > Kehler > Sent: Friday, December 05, 2003 5:03 PM > To: [EMAIL PROTECTED] > Subject: [Tex-music] Transposition in pmx > > > Am I overlooking something very simple here? > > In the key of F, here is a B-flat, a B-natural, and a B-sharp. > When I transpose this up a whole-step to the key of G, I end up > with a C, a C-natural, and a C-sharp instead of a C, a C-sharp and > a C-double-sharp. > > I am using pmx version 2.415, and musixtex version T.112 > > Thanks, > Kurt Kehler > > > % nv,noinst,mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig, >11 4 4 4 4 0 -1 > % npages,nsyst,musicsize,fracindent >1 1 20 0 > > t > ./ > Ar K+1+1 > b2 bn | bs0 / > > > ___ > Tex-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] PMX nested slur limitation
Olivier, I don't think you were involved back in the "(good) old days." What Dirk said is right: there were only two types of slurs. What he didn't mention was that you could only have one of each type turned on at a time. But this was REALLY old. The oldest version of PMX I can find is 1.36 dated 4/98, and it allows slur ID numbers, so the "s&t only" days were before that. The oldest M-Tx I find is 0.52 dated 10/98, but it may have started earlier. --Don Simons > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Olivier > Vogel > Sent: Friday, December 05, 2003 10:38 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: [Tex-music] PMX nested slur limitation > > > Dear Dirk, > > you wrote: > > M-Tx does allow only two levels of slurs. Back in the old days > PMX had only s and t. It will probably be quite tricky to increase > this --- that portion of the code is ancient. > > I don't understand the coherence of your explanation. As I > understand it, one can have only two levels of nested slurs, > because there are only two types of slurs (s and t). In my > opinion, the sujects of numeric limitation are very different. On > the one hand, the TYPES of slurs, which is limited to 2 (s and > t); and, on the other hand, the number of LEVELS of nested slurs, > whatever is their type. > > Thus, in the following example, there are three levels of nested > slurs, all of type s. Why can't M-Tx code it like PMX? > > Style: SOLO > Meter: C > Pages: 1 > Systems: 1 > > %%Ap > %%w100m > % PMX style: works fine > c4 sAhu+8 sBu+6 sC d sC e sC f sC sB+6 | g sBu+6 sC f sC e sC d > sC sB+6 sA+8 | c0 > > % M-Tx style: doesn't work > %(Au+8 (Bu+6 (C c4 d )C (C e f )C )B+6 | (Bu+6 (C g f )C (C e d > )C )B+6 )A+8 | c0 > > Olivier > ___ > Tex-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] pmx - key change in the second voice
Andre Van Ryckeghem wrote > To Olivier : i did not test if the midi is not right, but i suppose, if > using in line tex for the keychange, the midi will not see it. I haven't looked at this yet. But maybe you could use midi-only accidentals after the in-line TeX key change. --Don ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] RE: fine tuning PMX ornaments
> Christian Mondrup wrote > ...The ritornel 'Søde Narcisse' published today > illustrates that, for example in bar 4 where I have vertically offset the > RH staccato dots to positions above and below the beams. The PMX syntax > allows fractionwise vertical offset, but typesetting result demonstrates > that fraction values are rounded to integers before being applied. That > prevents me from achieving equal distances between dots and beam. Your right that fractions are dropped. You can do a little better with the vertical positioning, using this very special work-around: == 1 1 2 4 2 4 0 -1 1 1 20 0 t .\ w2.5i % Paragraph 8 line 63 bar 4 f84 ou+2 g8 ou+3 a8 ou+4 f8a | // a84 o.-9 b8 o.-9 c8 o.-9 ef8a o. zc | / == The problem with the method you used---which was the obvious method---is that MusiXTeX moves some of the dots because it thinks there are ledger lines to be avoided. The reason is quite convoluted, and the work-around took a lot of trial and error. But it's still less work and safer than adding code to recognize and correct for the situation. > Furthermore pmxab accepts additional staccato dot horizontal offset > arguments (eg. 'o.+2+.5'). But since I may enter arbitrary horizontal > offset values without seing any visual effect I suppose they're simply > ignored. That prevents me from aligning staccato dots with stems > as I would > like to do:-( As of now PMX can't shift ornaments horizontally except oc and ob. The fact pmxa accepted a second signed number is an oversight. I'll think about adding the option. --Don ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] Transposition in pmx
Kurt Kehler wrote > I think > this means that the only way to keep a B-natural in a concert pitch > parent score, and a C-sharp in a scor2prt transposed Bb trumpet score, > would be something like this: > > % nv,noinst,mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig, >11 4 4 4 4 0 -1 > % npages,nsyst,musicsize,fracindent >1 1 20 0 > > t > ./ > %1Ar K+1+1 > %% > b2 bn | bs0 / > %1 b2 bs | bss0 / > That's one way, but not the only way. When you use the system the way it was intended to be used, you don't have to enter anything twice: % nv,noinst,mtrnuml,mtrdenl,mtrnmp,mtrdnp,xmtrnum0,isig, 11 4 4 4 4 0 -1 % npages,nsyst,musicsize,fracindent 1 1 20 0 t ./ Ar %1 K+1+1 b2 bs | bss0 / --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] PMX: dotted rests with vertical shift
Thanks for pointing this out, Hiroaki. There is an error here, but I don't think it's the one you had in mind. The first and last vertical shift assignment in the second bar are being observed. In the middle two, the shift assignments immediately follow "d" and therefore--- according to PMX's syntax rules---should apply to the dots only, not the rest symbols. So if anything should be shifted on those rests, it is the dots, but they are not shifted. I haven't chased down the exact reason, but it clearly suggests that at some deep level dots on rests work differently from dots on notes. Before I go to the effort of fixing this behavior and making it possible to shift dots on rests, I would like to hear from someone that they would ever find a use for that feature. In the entire life of PMX as far as I can recall, no one has ever requested it or even mentioned it. I suppose that's because the most common reasons for shifting dots have to do with chords or slur or tie ends, none of which applies to rests. --Don Simons > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Hiroaki > MORIMOTO > Sent: Thursday, December 11, 2003 6:29 AM > To: [EMAIL PROTECTED] > Subject: [Tex-music] PMX: dotted rests with vertical shift > > > Hello Don and all, > > In following PMX example, vertical shift assignments '+6' > in the second bar are ignored. > > -- > 1 -1 1 4 4 4 4 0.0 0 1 1 20 0 > > 0 > ./ > r2+6 r4+6d r1+6d r3+6 / > > r2+6 r4d+6 r1d+6 r3+6 / > > -- > > Best regards, > > > Hiroaki MORIMOTO <[EMAIL PROTECTED]> > > ___ > Tex-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] pmx - \rwp and \lwp
Olivier Vogel wrote
> The problem is due to PMX. If a whole note is shifted to the
> left, respectively to the right, PMX introduces the code
> \loff{\wh *}, respectively \roff{\wh *}.
>
> I consider that as a bug of PMX, because the width of whole notes
> equals 1.25 width of other notes (half, quarter,...) [look at
> line 1509 of musixtex.tex]. So, Don, is it possible to modify PMX
> so that it produces the code \loffset{1.25}{\wh *}, respectively
> \roffset{1.25}{\wh *}?
Anything is possible.
If a whole note is shifted to the left, then I agree. But if to the right,
the proper distance depends on the width of whatever is in the way, and
that's not necessarily another whole note. I can do it the way Olivier
suggests, and it will cover chords of whole notes, but it will not cover all
possible situations. Any comments?
--Don>
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] RE: pmx - \rwp and \lwp
Thanks to Andre, Christian, and Olivier for contributions to this thread.
Let me try to summarize the situation. Then I'll suggest a few changes.
Whole notes are 25% wider than non-whole notes.
When any main note or non-whole chord note is explicitly shifted in PMX with
"l" or "e", \loff or \roff is used and the note is shifted by a non-whole
notehead width.
When a whole chord note is explicitly shifted in PMX with "l" or "e", \lw or
\rw is used, thereby shifting by 1.25 times a non-whole notehead width.
When PMX is left alone to deal with whole note chords, all necessary shifts
are automagically inserted. They use either \lw or \rw, according to whether
the stem would go down or up if there were a stem.
All of the same statements apply to dotted whole notes, with two caveats:
First, PMX will issue commands \rwp or \lwp but there is currently no
definition for them in either musixtex.tex or pmx.tex; as of now one must be
supplied by the user. Second, there is no automatic shifting of dots, but
the dots can be shifted manually with the usual PMX options.
I believe that no changes are called for in pmxab.exe. It is true that in a
whole note chord, if a main note is explicitly shifted, it will not be
shifted far enough. But if that is ever needed at all, it would occur so
rarely that it's not worth the time or risk to correct it automatically in
PMX. Similarly, if whole notes need to be shifted to avoid crashes between
two voices on the ame staff, the user can easily patch things up with XS as
in Olivier's example below.
However, the commands \rwp,\lwp should be defined either in musixtex.tex or
pmx.tex. I propose to Olivier that they be included in musixtex.tex, as well
as the corresponding commands for shifted, dotted, non-whole notes that are
now included in pmx.tex. However, if there is some reason why they shouldn't
be in musixtex.tex, I can put them into pmx.tex.
Thanks to Olivier's insights, I've noticed what appear to be misstatements
in musixdoc: in Section 2.5.3, p.27 of Version T.111, it lists the
horizontal shifts as all being about 6 pt. First, the shifts for whole notes
described in this section should be 25% larger than for non-whole notes, and
second, the absolute distance depends on musicsize; 6pt only applies to
non-whole notes at 20pt musicsize.
--Don Simons
> -Original Message-
> From: Olivier Vogel [mailto:[EMAIL PROTECTED]
> Sent: Sunday, December 14, 2003 4:23 AM
> To: Typesetting music with TeX; [EMAIL PROTECTED]
> Subject: pmx - \rwp and \lwp
>
>
> Dear Don,
>
> I realize that the code produced by PMX is perfectly coherent.
> The macros \lw and \rw occur when one knows that the other notes
> which provoke the collision are whole notes too.
>
> The macros \loff{\wh } and \roff{\wh } occur when one doesn't
> know the values of the other notes. They can be whole notes or
> maybe not. In the first case, one has to adjust manually the spacing.
>
> 8<-
> 1 1 4 4 4 4 0 0
> 1 1 20 0
>
> t
> ./
> w120m
> XS-.25 f04e | f0 | f2e e | f e //
> g04 | XS+.25 g0r | g0 | g0r /
> 8<-
>
> In clear, don't modify PMX, its coding is perfect!
>
> Olivier
>
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] more PMX 2.40 beaming
Olivier wrote
>
> I succeeded to correct it, but with a MusiXTeX trick:
>
> 8<-
> 2 1
> 3 4
> 3 4
> 0 1
> 0 2
> 20 0
>
> bt
> ./
> ApebI 10
> B
> %
> % Bar 20
> %
> a83 f ds1 b d f [l+0+7 b ]j rbd8 | /
> rb2 rb1 [uj ds14 f a ] | //
This is exactly the method I would use to fix the first staff-jumping beam,
and it is mentioned in the PMX manual. But in this case it only works
properly after altering the later staff-jumping beams!
> [ f15 e ds cs ] b2 t | /
> %
> % Bars 20-21
> %
> r2b g8d d1 //
> r4b r8bd [lj \raise-3\internote\hbox{\tbbu2}\ f1 ] r1b [lj d1s e ] r1b /
> g8d f1 [+0-2 g8d ]j r1b rb4 //
> b14 t ds e8 t e1 t ds- e8 t [ e1 t ]j rb8d /
> 8<-
>
> So I have a question too. In the second bar, the first note of
> the left hand is coded with the MusixTeX trick. I don't
> understand why [m2lj f1 ] doesn't work. Does it mean that the
> multiplicity can not be forced for staff-jumping beams?
I've looked at the issue of changing multiplicity of staff-jumping beams in
the past, and thrown up my hands in frustration. I'll have another look this
weekend; maybe I can teach PMX to use Olivier's trick with \raise.
--Don Simons
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] pmx - Grace notes with double flags and slash
I never considered the possibility that anyone would want to have a slash on a single grace with 2 flags. You are probably the first person in history to try this, so there is no "normal". Is this a notation you really want? --Don Simons > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Andre > Van Ryckeghem > Sent: Saturday, January 03, 2004 10:50 PM > To: Typesetting music with TeX > Subject: [Tex-music] pmx - Grace notes with double flags and slash > > > When i change Gm2g to Gm2xg then only 1 flag is left over. > > Is this a normal behaviour? > > Tanks > > Andre > > ___ > Tex-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] pmx-restrictions
Simon Dreher wrote > in PMX-manuals there are some restrictions "under user control". How can > I change these values? Is there any guide what to do? > Thanks for any tip, In pmx240.pdf the relevant section is entitled "Limits on quantities that a user can control." I've racked my brain to try to find a better way to get the point across, but I've failed to find a concise way to state it clearly enough: the user can control the number of these items that he enters into the score, but he cannot alter the limits without recompiling the FORTRAN source. As stated in the text: "Any of these can be increased on request." By this I mean a request to the code developer, i.e., me. The text goes on "However, before making such a request, it will usually be possible to work within existing limits by breaking the input into smaller blocks." And I believe that's the truth. If anyone would like to suggest a better way to state all this in the PMX manual compared to what's there now, fire away. BTW, as I just suggested, ANY user with access to a FORTRAN compiler is free to fiddle with the dimensions in the source code and recompile it himself. --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] Strange PMX behaviour
Karsten Mekelburg wrote > PMX doesn't accept systems at the end of a file, not followed by > at least one empthy line. If you stops a pmx file by a valid line > (with notes, beams, slurs ...) the last system will be ignored by > PMX. In PMX's current state, I cannot reproduce this problem on my system (Win98). Furthermore, no one else has mentioned it for a very long time. However, the issue has indeed come up in the distant past, and I attempted a fix at that time by modifying PMX so that it would internally insert a blank line in its image of the input file. But for some reason, sometime in the interim I removed that modification (it must have caused some other problem somewhere). I do not plan to address this any further at this time. However, if someone can provide a clean analysis of exactly what is happening, example files that reproduce the error, and a specific fix that works in both DOS/WIN and Linux systems without causing any other problems in either case, I'll revisit the matter. Let me suggest another possible cause of the behavior Karsten observed, due to a flaw in PMX's input checking. If the last input block contains fewer voices than it should, but if each voice within the last input block is otherwise OK (meaning syntactically correct and containing the same number of bars as all the others in that input block), then PMX will silently ignore all of that input without any error messages. --Don Simons If you inserts an empty line after the last valid line, the > last system will be read. For a pmx beginner, like me, this is > unexpected and shout be documented in the manual as an > restriction or as a note. > > >From the developers point of view (I don't understand the > FORTRAN code, I'am C++ programmer) it may be a bug, during the > proceessing the End Of File Token. Usually, a developper will be > used some buffers to read all lines/voices of a system. In my > code I forgot to flush this buffers on the End Of File Token and > had nearly the same effect. > > Regards > -- > > Karsten Mekelburg > Developer > > REALTECH system consulting GmbH > Industriestraße 39c > 69190 Walldorf > Germany > > Fax: +49.6227.837.837 > mailto:[EMAIL PROTECTED] > http://www.realtech.de > > > > > ___ > Tex-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] Strange PMX behaviour
Thanks to all who commented about the end-of-file issue, and for your understanding about the complexities of cross-platform compatibility. I'll definitely add a comment in the manual for the soon-to-appear version 2.5. Karsten's example highlights another issue I plan to visit soon: appending comments to the end of a line. It's not now officially legal; comments are supposed to start with something in column 1. But empirically, it usually seems to be OK to append comments. I'll see if I can make that official. That was one of many PMX topics that Cornelius Noack and I discussed when he came to visit me for a few days last weekend in S. Cal on the way to a meeting in Berkeley. Another suggestion he made was to allow a global .mod file, containing PMX commands to be inserted after the setup data in every file. I now have a version of this working in Win98 and plan to check it in RH Linux 9 today. It was surprisingly tricky due to several factors; (1) At ccn's suggestion I'm using an environment variable to define the path to the file; (2) I need to enable syntax checking and error reporting for the contents of the file, necessitating some serious juggling to get the reported line numbers to come out right for the mod file as well as the main one. Cornelius and I didn't spend the whole time PMX'ing. A highlight was a visit to the Getty center, an absolute must-do for any tourist in So. Cal. If you haven't heard, it's a museum and research center sitting on a hillside above LA. It houses a fabulous collection of paintings, sculpture, and photographs, and its architecture is almost as impressive as its art. To top it off, the weather was perfect, with summer-like temperatures and the clearest skies I've ever seen. The view over the LA basin was jaw-dropping, from the ocean to downtown to the mountains. We could see snow-covered peaks over 100 miles away. --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] Environment variables in RH Linux with g77
I know this seems off topic, but not really...We need to straighten this out
if Linux users are are to be able to use the global .mod file that I already
have working in Windows.
My approach is to require the user to store the path to pmx.mod in an
environment variable PMXMODDIR (Cornelius Noack's suggestion). From within
PMX, I use the FORTRAN statment
call getenv('PMXMODDIR',pathq)
to transfer the name of the path into the character variable pathq, then go
on from there to open pmx.mod and insert the PMX commands it contains into
the virtual pmx file that PMX processes. It all works fine when I run PMX
from a DOS window in Win98. But it doesn't work in RH Linux 9.0. The program
compiles OK with g77 (with the usual 2 changes), and the g77 docs say that
the syntax for getenv() is the same as the Windows version. But on
execution, PMX can't find the environment variable. I both set the
environment variable and run the program from the same bash shell. I think
this has something to do with shell levels and such, and maybe there's a
compiler switch to make it work, but I'm too dumb to figure it out. If
anyone has RH Linux 9.0 and can figure out how to make this work, that would
be great. It might also be useful if someone with another flavor of Linux
could test it out and let me know what's up. The worst case is that only
Windows users will be able to use this feature. I'm not going to drop it, as
I have too much energy invested. Here's a program you could try with g77 to
test the concept:
character*80 pathq
call getenv('PMXMODDIR',pathq)
print*,'PMXMODDIR: ',pathq
end
Before running the test, you can set the environment variable by entering
PMXMODDIR=/whatever/whenever/
on the command line.
--Don Simons
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] Include files in PMX
I'm now educated about "export"ing environment variables in Linux...thanks to the collective and individual experience of our distinguished list. I've confirmed that it works in RH Linux 9.0. So it appears that my initial proposal for the configuration file will work in both Windows and Linux systems. I also appreciate all the suggestions for enhancements and modifications. After thinking about all of this, here's how I now plan to proceed (and of course I welcome further comments). I'm going to start calling these things "include" files rather than "configuration," because after all they're just arbitrary sets of ordinary PMX commands. There will be two kinds of such files, global and normal. The global one (there can only be one) will operate exactly as I outlined earlier. It will be named pmx.mod. An environment variable PMXMODDIR (case-sensitive in Linux) will have to contain the path to the file. If PMXMODDIR is defined and if the file exists, then its contents will be added (in a virtual sense) to every .pmx file right after the setup data. The contents will be syntax-checked, and echoed to the screen and to the .pml file. True, there will be no record in the .pmx file of what was included in this way, but there will be in the .pml, and it will have required two specific actions by the user---defining PMXMODDIR and creating pmx.mod---to initiate this activity. The normal include files will be allowed at the beginning of any input block. The only thing a user will need to do to read one in will be to insert a pmx command. The effect will be exactly like \input in TeX (except I double if they can be nested). The argument of the command will be the name of the file including any necessary path information. For this type of include file, there will be a record in the .pmx file. Anyone who doesn't like the lack of traceablity of pmx.mod can accomplish the same purpose with a normal include file entered right after the setup data. Those who suggested multiple such files can use this method to select which one they want in each particular case. The syntax that comes to mind is AR[filename] (R stands for read; "I" is already taken, either as an option to "A" or as a stand-alone command). It's not too late to change this if anyone has a better suggestion. I didn't want to create a default path to pmx.mod because (1) that would only have required one positive action (creating pmx.mod) to initiate, making it more likely that a user would lose track of things, and (2) that would be difficult to make compatible across different OS's. --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] PMX 2.416, including include files
The new beta version 2.146 at http://icking-music-archive.org/software/pmx/pmx2416.zip has a hack at enabling include files. Please do some testing of these capabilities, including purposely introducing errors in syntax, file names, or file locations. The length of the following description is a small clue about how many twists and turns I encountered in trying to code this up. Include files are separate text files containing arbitrary (but contextually appropriate) sequences of valid PMX commands. The commands will be inserted at a particular place in the virtual PMX file that the code processes. They will always be syntax-checked. There are two types, "global" and "normal". There can only be one global include file and it must be named pmx.mod. If activated, its contents will always be inserted right after the setup data. To activate it, two conditions must be met: (1) an environment variable PMXMIDDIR must be defined to contain a valid path, ending with "/" or "\"; (2) a file named pmx.mod must be present in the directory so defined. If PMXMODDIR is not set, or if it is defined but there is no file pmx.mod, then processing will proceed as usual. Normal include files can have any name and do not require any environment variable to be set. They are activated by the PMX command AR[filename] , placed in the .pmx file at the location where the included lines are to go. PMX will first check for the file as pointed to by [filename], which may contain a complete or partial pathname preceding the actual file name. If [filename] is not found, then PMX will look for %PMXMODDIR[filename], i.e., it will check the directory defined by PMXMODDIR if PMXMODDIR has been set. However, it is not necessary to define PMXMODDIR to use a normal include file. There may be any number of normal include files. The same file may be used multiple times. Include files cannot contain references to other include files via the "AR" command; if you do that your computer will explode. The following information regarding all activated include files will be printed both to the screen and to the .pml file: notice of opening or closing, echo of the contents, error messages pertaining to syntax errors in the included PMX commands, and an error message if PMX cannot find a referenced normal include file. In the latter two cases PMX will stop. ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] PMX - adding "tacet" lines
You can do this with part-specific comments. I've appended an example. (To process this you'll need version 2.416--which I just revised and uploaded--since I had to increase the allowable length of test-dynamic strings). But of course there may be more than one way to do this; it won't surprise me at all if Olivier or Andre comes up with a more elegant solution :-) And I'm really looking forward to Lully! --Don Simons = 3 3 4 4 4 4 0 0 3 6 20 .1 Basso Viola Violin bat .\ %1S5P1 %3S5P1 %2S4P1 h Movement I c03 d e f g a b c / c04 d e f g a b c / c05 d e f g a b c / %% h Movement II %1h %1Movement II % % In the 2nd part, commands placed here will take effect AFTER % the start of the 3rd movement, so put in put in header % for movement III here, and a special % header for Movement II in part II using text-dynamics % down below. % %2h %2Movement III %3h %3Movement II %% L3P2Mn213bt %1L3M %3L3M c03 d e f g a b c / c05 d e f g a b c / h Movement III %% L5P3Mn3123bat %1L4M %3L4M %2L3M c03 d e f g a b c / c04 %2D"\bigfont\kern-27pt Movement II"+53 %2D"\BIgfont\kern40pt Tacet"+40 d e f g a b c / c05 d e f g a b c / > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Diane > Blaurock > Sent: Sunday, January 18, 2004 7:27 AM > To: MusiXTeXList > Subject: [Tex-music] PMX - adding "tacet" lines > > > Hi all, > > I am almost done PMXing an instrumental suite from Lully's "La Grotte de > Versailles" as a test balloon before I tackle "Phaeton." Both switch back > and forth between a 5-part and a 3-part setting. So far no problem. When I > run the score through scor2prt, the viola parts will simply skip over the > 3-voice movements. > > My question: Is there any way that I can add the movement title > followed by > a "tacet" in those parts that skip movements? I see that Johan > Tufvesson did > something like what I want to do in his Lully suites, and got it > centered to > boot. Johan, was that an in-line TeX command? Teach me your magic trick! > Anybody else with some good suggestions? > > Thanks in advance! > > Diane > > * > Diane Blaurock > Melanchthonstr. 39 > 72074 Tuebingen > Germany > Tel. +49 (7071) 22374 > Fax +49 (7071) 551 589 > Email: [EMAIL PROTECTED] > > > ___ > Tex-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] PMX I/O error in second PMX pass
Cornelius Noack wrote >(i) Are you sure that is what you really want in your score ? Do > you expext any organ player to be able to play these notes on > sight-reading ?? ... to which Karsten Mekelburg replied >... the answer of (i) is > NO. I ask my wife (the composer) an she tell me: > > "The suite isn't written for playing prima vista (vom Blattspiel > sagt man in Deutsch). I expect that an organ player have enough > time to practise this suite at least 2 weeks, before he is able > to play it. Very good manual and pedal technical skills are provided." In Karsten's example, originally posted 1/19, it is true that PMX choked in bar 25. But bar 22 reaches 8 ledger lines above the treble staff; bar 23 goes 11 ledger lines above, and bar 24 goes 12 ledger lines above. PMX gamely deals with all this, not questioning for an instant whether someone inadvertantly went up an octave when he meant to go down, nor questioning where there is any organ in the world that has such high notes on its keyboard. But evidently by bar 25 PMX got exhausted and gave up. I think we should all give PMX a round of applause for hanging in there as long as it did! --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] PMX2.417
http://icking-music-archive.org/software/pmx/pmx2417.zip Increased maximum number of text dynamics per input block from 12 to 41. Increased maximum length of a text dynamic from 24 to 128 characters. "Ap+c", "Ap-c" will now increase or decrease the default curvature of Type-K postscript slurs. Such commands can be used at the start of any input block and the result is cumulative. More than one suboption "+c" or "-c" may be used in a single command to increase or decrease by more than one notch. If the cumulative change goes above "HH" or below "f" a warning will be issued, the default will be set to "HH" or "f", and processing will continue. Local curvature options in individual slur commands will take precedence over the global default but will not change the default. The local option "n" in a slur command will cause the slur to have the normal curvature (between "f" and "h"). --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] trios on 6/8 mesure, how many beams ?
Andre wrote > I known > that Don (always) is right ... I appreciate the thought, but I disagree with it. But if I'm not always right, maybe I'm wrong about this, and maybe therefore I really am always right. And I know a barber who shaves everyone in town except himself. Here's one argument why 4 notes in 3 quarters should have no flags: If you had three notes in three quarters, like the first bar in Andre's example, each one has length 1.0 quarters and 0 flags. If you had 3 notes in 2 quarters, like the 7th bar in Andre's example, each one has length 0.667 quarters and 0 flags. With 4 notes in three quarters, each note has length 0.75 quarters. That's BETWEEN the lengths of notes in two cases where no one (except maybe Andre's friends) would argue that there should be no flags. In case anyone is interested, the formula that PMX uses to compute the number of flags in an xtuplet is INT(13.429+(0.952*LN(nnotes)-LN(32*wholes))/0.69315)-10 where "wholes" is the fractional number of whole notes duration for the entire xtuplet, and nnotes is the number of notes. I derived this formula myself. If anyone wants to know why it doesn't depend directly on wholes/nnotes (the length of each individual note), I'll have to get back to you because I don't remember exactly, but I think I have a record somewhere. --Don ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] pmx - path of readmod in windowsxp
Andre wrote
> I want to typeset a booklet and make a .bat file to compile files from
> several directories.
> This is an example of a line in the batch file:
>
> echo ..\..\vlzingt\vlzingtpmx\savobei | pmxab
>
> The pmx compiles ok, but the TeX has an error on
>
> \readmod{..\..\vlzingt\vlzingtpmx\savobei}
>
> (! Too many }'s
> \.#1->{\accent 95 #1}
> .
>
> Is there a way out for this error (without putting all files in 1
> directory)?
>
Try using forward slashes in the path name. TeX may be confused by the
backslashes.
--Don Simons
___
Tex-music mailing list
[EMAIL PROTECTED]
http://icking-music-archive.org/mailman/listinfo/tex-music
[Tex-music] PMX Version 2.5
I've just uploaded the full package for a new "official" version to http://icking-music-archive.org/software/pmx/pmx250.zip There are NO changes in the code from version 2.417, but the manual has been updated and a few examples have been edited. Using methods I lifted largely from Cornelius Noack's tutorial, the new version of the manual http://icking-music-archive.org/software/pmx/pmx250.pdf has clickable internal and external hyperlinks, including a fully linked table of contents. BTW I hope everyone realizes that PDF's are text-searchable. That's the main reason I didn't bother to create an index. (The other is just laziness). --Don Simons ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
RE: [Tex-music] PMX Version 2.5
Robin-- Thanks for keeping your eyes open :-) --Don Simons > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Robin > Fairbairns > Sent: Sunday, February 15, 2004 3:19 PM > To: Typesetting music with TeX > Subject: Re: [Tex-music] PMX Version 2.5 > > > don simons writes: > > > I've just uploaded the full package for a new "official" version to > > > > http://icking-music-archive.org/software/pmx/pmx250.zip > > > > [and] > > > > http://icking-music-archive.org/software/pmx/pmx250.pdf > > and in a probably vain attempt to keep ctan up to date, i've manually > installed both as (the sole content of) ctan support/pmx > > unfortunately, it is no longer possible to perform mirror operations > from the icking archives, so updates of the material on ctan (and hence > on user group systems such as texlive) rely on me spotting announcements > of software updates on this list. (no one else of ctan management reads > the list afaik.) > > robin fairbairns > ___ > Tex-music mailing list > [EMAIL PROTECTED] > http://icking-music-archive.org/mailman/listinfo/tex-music > ___ Tex-music mailing list [EMAIL PROTECTED] http://icking-music-archive.org/mailman/listinfo/tex-music
