Re: [Tex-music] PMX: \starteq and \endeq

[Don Simons]

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

Re: [Tex-music] PMX: \starteq and \endeq

[Don Simons]

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

[Don Simons]

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] IMSLP Chopin's mazurka pmx engraving files

[Don Simons]

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] New PMX version

[Don Simons]

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] New PMX version

[Don Simons]

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

[Don Simons]

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

[Tex-music] New PMX version

[Don Simons]

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] 8va position is too low

[Don Simons]

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

Re: [Tex-music] Can MusiXTeX input guitar chokings?

[Don Simons]

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] bar crossing beam causes error message

[Don Simons]

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] bar crossing beam causes error message

[Don Simons]

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] PMX: problem with changing the number of instruments

[Don Simons]

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] PMX: problem with changing the number of instruments

[Don Simons]

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] Is it possible to put accompaniment chords above each bars in PMX?

[Don Simons]

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] Please help with two-staves beam

[Don Simons]

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] lcharnote of a "personal" character and vertical alignment

[Don Simons]

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] Moving dots in 2-note tremolos (was RE: Trills in pmx)

[Don Simons]

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-
> > > >
> > > > Thanks to look at it,
> > > >
> > > > Andre
&g

[Tex-music] Moving dots in 2-note tremolos (was RE: Trills in pmx)

[Don Simons]

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] Trills in pmx

[Don Simons]

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

Re: [Tex-music] Varying number of instruments

[Don Simons]

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] alignment of \flageolett in \Largenotesize

[Don Simons]

> -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] alignment of \flageolett in \Largenotesize

[Don Simons]

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] PMX290: character "o" in meter change

[Don Simons]

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] PMX cannot influence stem length

[Don Simons]

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] New PMX version with gaps

[Don Simons]

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

[Tex-music] New PMX version with gaps

[Don Simons]

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] Duration of multirests below the staff?

[Don Simons]

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

Re: [Tex-music] TeXperts: Help!

[Don Simons]

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] TeXperts: Help!

[Don Simons]

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

[Tex-music] TeXperts: Help!

[Don Simons]

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] pmx - increasing the number of instruments

[Don Simons]

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

Re: [Tex-music] Dots moving

[Don Simons]

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: `sforzando' on grace note?

[Don Simons]

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] PMX: full-bar rest not centered

[Don Simons]

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: full-bar rest not centered

[Don Simons]

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: problem with shifted dot

[Don Simons]

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] Another one for the TeXperts

[Don Simons]

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] Submitting scores to IMSLP

[Don Simons]

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=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] Submitting scores to IMSLP

[Don Simons]

> 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] Another one for the TeXperts

[Don Simons]

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] Another one for the TeXperts

[Don Simons]

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

[Don Simons]

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] Submitting scores to IMSLP

[Don Simons]

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

[Tex-music] Another one for the TeXperts

[Don Simons]

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

[Tex-music] Request, regarding PMX systems with gaps

[Don Simons]

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

Re: [Tex-music] Bug in PMX with chord stems

[Don Simons]

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

Re: [Tex-music] PMX and Trills

[Don Simons]

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] strange reaction of PMX 284

[Don Simons]

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] Problem with pmx file

[Don Simons]

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] Line-length challenge for the TeXperts

[Don Simons]

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] Line-length challenge for the TeXperts

[Don Simons]

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

[Don Simons]

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

[Don Simons]

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

[Tex-music] Line-length challenge for the TeXperts

[Don Simons]

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] Problem with pmx file

[Don Simons]

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

Re: [Tex-music] MusiXTeX/pmx sources

[Don Simons]

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] MusiXTeX/pmx sources

[Don Simons]

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] PMX: xtuplets horizontal shift of notes

[Don Simons]

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

Re: [Tex-music] PMX: Changing of numbers of instruments

[Don Simons]

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 /

> >>

> >> %L3Mcn31

Re: [Tex-music] PMX: Changing of numbers of instruments

[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.

--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: switch to smaller notes type (German "Stichnoten")

[Don Simons]

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: switch to smaller notes type (German "Stichnoten")

[Don Simons]

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")

[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
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 stem length error on beamed octave chords

[Don Simons]

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 stem length error on beamed octave chords

[Don Simons]

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] Musixtex

[Don Simons]

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: interference betweeen tuplets and dynamic marks

[Don Simons]

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] Problem accessing WIMA

[Don Simons]

Well, I finally figured out how to explicitly stop McAfee Firewall from
blocking my access to WIMA. But I still wonder if anyone besides me has had
this problem, and also whether there's anything that should be done by
Christian to track down a fix whatever was causing it. 

 

--Don

 

From: Don Simons [mailto:dsim...@roadrunner.com] 
Sent: Saturday, January 26, 2019 9:52 PM
To: 'Werner Icking Music Archive' 
Subject: RE: Problem accessing WIMA

 

I had McAfee Firewall turned on. When I turned it off, I could access WIMA
OK. This is obviously not a good solution. I haven't yet found a way to only
turn it off for selected sites.

 

--Don

 

From: Don Simons [mailto:dsim...@roadrunner.com] 
Sent: Saturday, January 26, 2019 9:32 PM
To: 'Werner Icking Music Archive' mailto:tex-music@tug.org> >
Subject: Problem accessing WIMA

 

This problem just started, and I don't know of anything I've done to cause
it. When I use IE to try to go to http://icking-music-archive.org I get a
message saying "This page can't be displayed." With Chrome I get "Your
Internet access is blocked, Firewall or antivirus software may have blocked
the connection." From this computer I have no such problem with any other
regular web sites. From a different computer using VPN to through a
different network, I have no problem with either browser.

 

Any idea how to fix this?

 

--Don Simons

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

Re: [Tex-music] Problem accessing WIMA

[Don Simons]

I had McAfee Firewall turned on. When I turned it off, I could access WIMA
OK. This is obviously not a good solution. I haven't yet found a way to only
turn it off for selected sites.

 

--Don

 

From: Don Simons [mailto:dsim...@roadrunner.com] 
Sent: Saturday, January 26, 2019 9:32 PM
To: 'Werner Icking Music Archive' 
Subject: Problem accessing WIMA

 

This problem just started, and I don't know of anything I've done to cause
it. When I use IE to try to go to http://icking-music-archive.org I get a
message saying "This page can't be displayed." With Chrome I get "Your
Internet access is blocked, Firewall or antivirus software may have blocked
the connection." From this computer I have no such problem with any other
regular web sites. From a different computer using VPN to through a
different network, I have no problem with either browser.

 

Any idea how to fix this?

 

--Don Simons

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

[Tex-music] Problem accessing WIMA

[Don Simons]

This problem just started, and I don't know of anything I've done to cause
it. When I use IE to try to go to http://icking-music-archive.org I get a
message saying "This page can't be displayed." With Chrome I get "Your
Internet access is blocked, Firewall or antivirus software may have blocked
the connection." From this computer I have no such problem with any other
regular web sites. From a different computer using VPN to through a
different network, I have no problem with either browser.

 

Any idea how to fix this?

 

--Don Simons

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

Re: [Tex-music] Volta positioning and maybe a bug with voltas combined with a line break and a meter change

[Don Simons]

Dirk Laurie wrote

> Op Di. 15 Jan. 2019 om 12:58 het Andre Van Ryckeghem 
> geskryf:
> >
> > This is a somewhat dirty trick to get Volta 2 on the next line.
> 
> Inline TeX, except direct (plain TeX) markup, in PMX source code is always
"a
> somewhat dirty trick" :-)

Sometimes you have to pick your poison: Inline TeX, or a marked up TeX file
that can then never be regenerated or edited from the original PMX source. I
would always choose the inline, but it's good to have clever folks like
Andre who are willing to do the "dirty" work.

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

Re: [Tex-music] Volta positioning and maybe a bug with voltas combined with a line break and a meter change

[Don Simons]

Thanks to Dirk, Jean-Pierre, and Bob for explaining \raisevolta. On the 
end-of-line question, I never considered this combination of events at a line 
break, so PMX really has no "intended" behavior...frankly I'm surprised (and 
happy) that the TeX code worked at all! And I'm not sure what a purist 
typesetter would want here (does anyone else know for sure?). If it's different 
than what did come out, unfortunately to change things around with inline TeX 
could get very complicated. But if all want is to add a number 2 above the 
staff at the start of the new line, you could do that easily within PMX with a 
dynamics command something like D"\elevenrm 2."+18-4 after the first note in 
the second line.

--Don Simons

> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Simon Feiler
> Sent: Monday, January 14, 2019 4:40 AM
> To: Werner Icking Music Archive 
> Subject: [Tex-music] Volta positioning and maybe a bug with voltas combined
> with a line break and a meter change
> 
> Dear M-Tx/PMX/MusicTeX-perts,
> 
> I usually write notes to rock-, pop-, folk- and childrens-songs in Arragements
> for guitar / keyboard / piano / accordeon and am using
>   - M-Tx 0.63
>   - musixcrd.tex v1.7
>   - PMX Version 2.83
>   - musixtex.lua version 0.19
>   - pdfTeX Version 3.14159265-2.6-1.40.16 from MiKTeX 2.9 64-bit for that
> purpose at the time.
> 
> My first question is, whether there is a possibility to raise Voltas higher 
> above
> the staffs than their default position is.
> As you can see in the attached pdf - which is a compilation of the M-Tx-code
> stated below the signing of this e-mail - the Volta-line crushes into the 
> chord-
> symbols and the g-Note in bar 4.
> I didn't find any hints about raising Voltas in the M-Tx and PMX-
> documentation so far and would be clad if somebody could help me with that
> task.
> 
> Another problem occurs, when a volta-change, a meter-change and a line-
> break are neccessary at the same bar-break.
> As you can see, the volta-number "2." can be found at the end of line 1,
> where the meter-change is (of course correctly) stated, instead of the
> beginning of line 2, where the first bar of Volta 2 starts.
> In my interpretation this is not the intended behaviour, or am I wrong in
> that? If I'm right, is there a bug-fix or a work-around for that situation?
> 
> Thanks for your great job for musictex and your help!
> 
> Greetings
> 
> Simon
> PS: I also attached the M-Tx-made pmx-file cause I assume it could be
> helpful.
> 
> PPS: I already tried to send this mail two weeks ago, but did not receive it
> myself, although my account-settings say, I'm supposed to.
> It also doesn't appear on
> https://www.mail-archive.com/tex-music@tug.org/
> So I assume, something did go wrong.
> I hope, you did not receive this former mail, and apologize in the case, you
> did, for the double mailing.
> 
> 
> 
> Volta.mtx:
> 
> 
> Title: Volta
> Style: Singer
> Sharps: -1
> Meter: 6/8
> Pages: 1
> Systems: 2
> 
> %%\input musixcrd
> %%\def\crddefaultheight{14}
> %%\special{papersize=210mm,297mm}
> %%\hoffset -1in\advance\hoffset 30mm
> %%\voffset -1in\advance\voffset 20mm
> 
> %%w150m
> %%h270m
> V1 \c Dm \ c8 d e f g b |
> 
> \c Am \ b g f e d c :|
> 
> 4/8 Vb2 \c F \ c+ f a c |
> 
> \c C \ c g+ e c |]
> 



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

Re: [Tex-music] Cancel meter printout at movement change.

[Don Simons]

Thanks, Andre, it does work! I can’t believe I didn’t think of that (since I 
invented the m command). 

 

From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On 
Behalf Of Andre Van Ryckeghem
Sent: Saturday, November 03, 2018 9:42 PM
To: Werner Icking Music Archive 
Subject: Re: [Tex-music] Cancel meter printout at movement change.

 

Perhaps this could work?



2 2 4 4 4 4 0 0

1 2 20 0

I

II

bt

.\

g03 g g Rb /

g04 g g /

L2Mn11b

m4400

g03 g g /



Andre

 

From: Don Simons 

Sent: Saturday, November 3, 2018 8:51 PM

To: 'Werner Icking Music Archive' 

Subject: [Tex-music] Cancel meter printout at movement change.

 

Here’s a simple PMX file with a meter change:

 

==

2 2 4 4 4 4 0 0

1 2 20 0

I

II

bt

.\

g03 g g Rb /

g04 g g /

L2Mn11b

g03 g g /

==

 

Can someone tell me how to get MusiXTeX to skip writing the meter at the 
movement break?

 

--Don

  _  

---
TeX-music@tug.org <mailto:TeX-music@tug.org>  mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

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

[Tex-music] Cancel meter printout at movement change.

[Don Simons]

Here's a simple PMX file with a meter change:

 

==

2 2 4 4 4 4 0 0

1 2 20 0

I

II

bt

.\

g03 g g Rb /

g04 g g /

L2Mn11b

g03 g g /

==

 

Can someone tell me how to get MusiXTeX to skip writing the meter at the
movement break?

 

--Don

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

Re: [Tex-music] Per-note MIDI in PMX

[Don Simons]

For various reasons, this would be very, very difficult for me to implement.
Since I haven't even thought about midi technical details for at least 10
years, I'd have to spend lots of time re-educating myself with midi-file
basics and with the way PMX deals with it. Beyond that, some pretty major
data handling mods would probably be needed to allow note-specific midi-data
to be input, stored, and processed.

But PMX is freeware, and if anyone else wants to dig into the source code
and work something out (like Dirk did once long ago for an alternate tie
notation), I'd be glad to do what I can to help.

--Don

> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Dirk Laurie
> Sent: Friday, November 02, 2018 12:03 AM
> To: Werner Icking Music Archive 
> Subject: [Tex-music] Per-note MIDI in PMX
> 
> I know PMX offers MIDI support only so that you can check for wrong notes
> by listening. So it does not support MIDI features that require control
> messages like expression or channel volume. [1]
> 
> But that does not mean that one can't exploit PMX's MIDI support to its
> fullest extent to make the sound as realistic as possible. Those MIDI
files
> might for example be handed to singers who can't sight-read so they can
> practise their parts at home.
> 
> In doing so, I'm running afoul of a restriction that might be an easy one
to lift.
> 
> "I commands can appear later in the file as well, but only at the start of
an
> input block."
> 
> I can see the point of that restriction for instrument choice (and it
> corresponds to instructions by composers: "nimmt Klarinette in Bes"
> etc), and I have an open (even a blank) mind on balance, but the other two
> parameters, tempo and velocity, affect things sent to MIDI on every note.
> 
> Now I may be wrong in assumimg it's easy, but my guess is that after the
> initial I that opens a file, the I command merely computes and stores
> numbers that will later be used in generating MIDI events.
> 
> It would be great if one could do an accelerando or a crescendo in the
MIDI
> file.
> 
> "The command I containing only options t and/or v, with only one number
> per option, may appear before any note. This will change the specified
> option as from that note, for that instrument only."
> 
> [1] I don't really have any expertise. Everything I know comes off John
> Garside's site, especially http://midi-tutor.proboards.com/thread/12/9-
> controlling-midi-volume
> ---
> TeX-music@tug.org mailing list
> If you want to unsubscribe or look at the archives, go to
> http://tug.org/mailman/listinfo/tex-music

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

[Tex-music] New PMX beta, version 2.87

[Don Simons]

I've just generated a new PMX beta version 2.87
<http://icking-music-archive.org/software/pmx/pmx287.zip>  that should be
able to handle most cases of staff-jumping beams that change multiplicity at
the staff jump. Thanks go to Andre for pointing out the issue. Please see
psb.pdf and psb.pmx for more details.

 

--Don Simons

 

 

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

Re: [Tex-music] Using font-based slurs and ties with musixchar.

[Don Simons]

I can't image why you would want to do that. But given that you do, I'd
guess there's some way of locally and temporarily redefining \isluru,
\islurd, and \tslur to their font-based versions as defined in musixtex.tex.
I tried doing an example but ran into problems trying to restore the
definitions to the postscript versions, due to the fact that the arguments
do not appear at all in the basic definitions.

--Don

> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of
> coulon...@free.fr
> Sent: Tuesday, October 09, 2018 6:36 AM
> To: Werner Icking Music Archive 
> Subject: [Tex-music] Using font-based slurs and ties with musixchar.
> 
> I am using musixps but for some reason I want to put a font-base slur
> somewhere. The right one for me is in xslz20.pfb and by typing tex
fontchar,
> xslz20 I know the right character number for me.
> 
> How can I tell musixchar to fetch the character in xslz20 instead of
musix20?
> I though it was by saying \font\mytie=xslz20 at 10pt and zcharnote
> c{\mytie\musixchar} but this keeps the musix20 characters.
> 
> Bye,
> --
> Jean-Pierre Coulon
> ---
> TeX-music@tug.org mailing list
> If you want to unsubscribe or look at the archives, go to
> http://tug.org/mailman/listinfo/tex-music

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

Re: [Tex-music] more staff crossing beams

[Don Simons]

Using Andre’s PMX file (see below), the latest full public distro of PMX, 
Version 2.84, gives this:

 



I’ve been working on this on and off for a month now, and I’m ready to throw in 
the towel. I’ve managed to modify the PMX code to solve the first problem (bar 
2), but not the second (bar 3). More broadly, the legacy coding is already so 
complex that I just cannot find a clear path forward to deal with all the 
possible variations: upness or downness of the first or second member of the 
jump beam, increase or decrease in the multiplicity, and whether the change in 
multiplicity comes before, at, or after the staff jump. Here is what my 
development version gives:

 



With the new PMX version, the following inline coding fixes the problem in the 
3rd bar:



2 2 2 8 2 8 0 0

1 1 20 0

 

 

bt

./

[l+14 a13 ]j rbd8 /

rb1 \let\tbbut\tbbu\def\tbbu#1{\tbbl#1\let\tbbu\tbbut}\ [ju e14 g8 ] /

===

yielding this:



It was necessary to change the first part to a lower beam to make the 
horizontal bar that we want to terminate early come out above the other one. 
That could be done in PMX. But then the termination command for that 2nd bar 
had to be changed from \tbbu to \tbbl to make it end at the right horizontal 
position, and that required inline TeX.

 

I believe that any related situation can be handled similarly, with some 
combination of alterations of upness and downness within PMX, together with 
inline TeX as needed. I’m not saying it’s easy…a fair amount of trial and error 
may be needed.

 

Unless I come across backward incompatibilities or stumble across a major 
breakthrough, I’ll be posting the new PMX version soon.

 

--Don

 

From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On 
Behalf Of Andre Van Ryckeghem
Sent: Thursday, September 06, 2018 5:28 AM
To: Werner Icking Music Archive 
Subject: [Tex-music] more staff crossing beams

 

Hi all,

 

I know, we already discussed this, but perhaps this problem can be solved?

In each bar in the example, the last note of the staaf crossing beam should be 
an 8th. It happen only in the 1st bar.

 

Andre

===

2 2 3 8 3 8 0 0

1 1 20 0

 

 

bt

.\

Abpe

w5i

[l+14 g1- cs ]j rb4 | [ d1 d+ ]j  rb4 | [u a1 za- ]j rb rb4 /

rb8 [ju g1+ g zb g8 ] | rb8 [ju d8 zf ] rb |  rb1 [ju e c8 ze ] rb //

r4d r4d r4d /

===

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

Re: [Tex-music] PMX: Segno or Coda sign within dynamic text

[Don Simons]

In PMX (not LaTeX!) this seems to work:

=
1 1 4 4 4 4 0 0
1 1 20 0

t
.\
g24 D"Coda \musixchar85"+14 g /
=

You can use spaces inside the "..." to shift the symbol to the right. You
would need to use {\musixchar85} if you wanted to put any text after the
symbol, to keep from changing the font. 

--Don

> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Dieter
> Sent: Thursday, October 04, 2018 12:29 AM
> To: Werner Icking Music Archive 
> Subject: [Tex-music] PMX: Segno or Coda sign within dynamic text
> 
> Hi Don,
> 
> is it possible to include a special symbol like "segno" or "coda"
> 
> inside dynamic text like
> 
> D"some text \coda p\ some more text" ? Where p is the pitch to place the
> symbol.
> 
> It is no problem toB  generate a coda sign somewhere around the text.
> 
> But it does not reserve horizontal space for it.
> 
> I am sure if I were more fluent in TeX, I should be able to resolve this
> problem myself.
> 
> Thanks and regards
> Dieter
> 
> ---
> TeX-music@tug.org mailing list
> If you want to unsubscribe or look at the archives, go to
> http://tug.org/mailman/listinfo/tex-music

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

Re: [Tex-music] trio with "d" option

[Don Simons]

Andre—

 

No need to apologize. Thanks again for the report. I’ve been looking at your 
last one but without much success…the logic for staff-jumping beams is 
complicated, spread out, and not very well documented in the source code which 
I wrote many years ago, and I still haven’t thought of a way to “look ahead” to 
identify a change it multiplicity at the same place as the jump. This one may 
be a little easier since it’s all in one voice. I see what I can do.

 

--Don

 

From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On 
Behalf Of Andre Van Ryckeghem
Sent: Saturday, September 22, 2018 12:28 AM
To: Werner Icking Music Archive 
Subject: [Tex-music] trio with "d" option

 

Dear Don, 

 

I am sorry to bother you again, but i encountered this problem:

The 3th note of the trio with flags sometimes does not appear (as in the song i 
was typing). In this test file here it comes as an 8th note in stead of a 16th, 
and with a wrong hight.

 

===

2 2 2 4 2 4 0 0

1 1 20 0

 

 

bt

.\

w5i

b42ax3 gd b b42x3 gd b /

b44ax3 gd b b44x3 gd b /

=

 

Thanks for helping

Andre

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

Re: [Tex-music] more staff crossing beams

[Don Simons]

Jean-Pierre, I'm sorry but I don't understand the question. The staff-jumping 
problem is not from the Soler quintet. Andre posted his original question to 
the MusiXTeX list on 6 September with this subject line (see below), and I 
responded the same day with a TeX fix.

> -Original Message-
> From: TeX-Music [mailto:tex-music-
> bounces+dsimons=roadrunner@tug.org] On Behalf Of Jean-Pierre
> Coulon
> Sent: Tuesday, September 18, 2018 11:17 PM
> To: Werner Icking Music Archive 
> Subject: Re: [Tex-music] more staff crossing beams
> 
> At which page and measure of the Anglès edition do you have this?
> 
> On Tue, 18 Sep 2018, Don Simons wrote:
> 
> > I’ve more or less finished the Soler quintet transcription so now I’m
> > looking into this. But so far I’m hung up, because PMX needs to insert
> > the
> > \tbbl1 before the 1/16 note just before the staff jump, so it would
> > somehow have to look into the future to know that the multiplicity of
> > the beam was going to decrease right at the jump. It’s probably possible,
> but tricky.
> > After all, PMX has no trouble decreasing multiplicity when needed
> > within a non-staff jumping beam. So it must look ahead there, although
> > it is in the same voice. I’ll have to review that logic.
> >
> >
> >
> > --Don
> >
> >
> >
> > From: Don Simons [mailto:dsim...@roadrunner.com]
> > Sent: Thursday, September 06, 2018 5:36 PM
> > To: 'Werner Icking Music Archive' 
> > Subject: RE: [Tex-music] more staff crossing beams
> >
> >
> >
> > Andre, thanks very much for the report. I’ve compiled this with PMX 2.87
> and see that only minor corrections are needed to make it come out OK (see
> attachment). I’ll definitely put this on my PMX to-do list but I won’t be able
> to get serious about it until next week…I’m working on transcribing a Soler
> quintet for strings+harpsichord into a 2-harpsichord version, and I have
> another harpsichordist coming over on Saturday to play thru the first draft.
> >
> >
> >
> > --Don
> >
> >
> >
> > From: TeX-Music
> > [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On Behalf
> Of
> > Andre Van Ryckeghem
> > Sent: Thursday, September 06, 2018 5:28 AM
> > To: Werner Icking Music Archive  > <mailto:tex-music@tug.org> >
> > Subject: [Tex-music] more staff crossing beams
> >
> >
> >
> > Hi all,
> >
> >
> >
> > I know, we already discussed this, but perhaps this problem can be solved?
> >
> > In each bar in the example, the last note of the staaf crossing beam should
> be an 8th. It happen only in the 1st bar.
> >
> >
> >
> > Andre
> >
> > ===
> >
> > 2 2 3 8 3 8 0 0
> >
> > 1 1 20 0
> >
> >
> >
> >
> >
> > bt
> >
> > .\
> >
> > Abpe
> >
> > w5i
> >
> > [l+14 g1- cs ]j rb4 | [ d1 d+ ]j  rb4 | [u a1 za- ]j rb rb4 /
> >
> > rb8 [ju g1+ g zb g8 ] | rb8 [ju d8 zf ] rb |  rb1 [ju e c8 ze ] rb //
> >
> > r4d r4d r4d /
> >
> > ===
> >
> >
> 
> --
> Jean-Pierre
> 
> ---
> TeX-music@tug.org mailing list
> If you want to unsubscribe or look at the archives, go to
> http://tug.org/mailman/listinfo/tex-music


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

Re: [Tex-music] more staff crossing beams

[Don Simons]

Andre, thanks very much for the report. I’ve compiled this with PMX 2.87 and 
see that only minor corrections are needed to make it come out OK (see 
attachment). I’ll definitely put this on my PMX to-do list but I won’t be able 
to get serious about it until next week…I’m working on transcribing a Soler 
quintet for strings+harpsichord into a 2-harpsichord version, and I have 
another harpsichordist coming over on Saturday to play thru the first draft.

 

--Don

 

From: TeX-Music [mailto:tex-music-bounces+dsimons=roadrunner@tug.org] On 
Behalf Of Andre Van Ryckeghem
Sent: Thursday, September 06, 2018 5:28 AM
To: Werner Icking Music Archive 
Subject: [Tex-music] more staff crossing beams

 

Hi all,

 

I know, we already discussed this, but perhaps this problem can be solved?

In each bar in the example, the last note of the staaf crossing beam should be 
an 8th. It happen only in the 1st bar.

 

Andre

===

2 2 3 8 3 8 0 0

1 1 20 0

 

 

bt

.\

Abpe

w5i

[l+14 g1- cs ]j rb4 | [ d1 d+ ]j  rb4 | [u a1 za- ]j rb rb4 /

rb8 [ju g1+ g zb g8 ] | rb8 [ju d8 zf ] rb |  rb1 [ju e c8 ze ] rb //

r4d r4d r4d /

===



avr5.tex
Description: Binary data
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

Re: [Tex-music] Tie end without begin?

[Don Simons]

Rudolfo--

You could get what you want by both starting and ending a new tie on the
first note in the 2nd ending, with the start shifted to the left. 

Out of curiosity, given that you input pmx.tex, why didn't you use PMX for
the whole job?

--Don Simons

> -Original Message-
> From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Rodolfo
> Medina
> Sent: Monday, May 28, 2018 8:45 AM
> To: tex-music@tug.org
> Subject: [Tex-music] Tie end without begin?
> 
> Hi all.
> 
> In the attached example, to be processed simply with:
> 
>  $ tex test
>  $ musixfl test
>  $ tex test
> 
> I would need, in the last bar, to terminate upon the `g' pitch the tie
that
> started in bar 3: just its termination: but that doesn't seem possible
because
> MusiXTeX obviously complains about `missing \islur0'.  Please, any
possible
> solution about that?
> 
> Thanks for any help,
> 
> Rodolfo
> 
> \input musixtex
> \input pmx
> %%
> %% New York New York
> %%
> Musica di John Kander.
> 
> \transpose0
> \parindent2cm%
> \setclef1\bass
> \instrumentnumber{2}%
> \setname1{Pianof.}%
> \setname2{Canto}%
> \setstaffs12%
> \relativeaccid%
> \generalsignature{2}%
> \generalmeter{\meterfrac44}%
> %\interstaff{11}%
> \startpiece
> \Notes
> \hu{``d!}\sk\sk\sk\hu{``a!}%
> |\lpz a\zq a\ql d\sk\lpz d\ql d\sk\ibl0c0\qb0c\tbl0\zqb0a%
> \qb0d\sk\lpz b\ql b%
> \nextvoice\itieu0f\wh f%
> &\Uptext{\metronequiv{\noteskip=3\elemskip\smallnotesize%
> \ibu010\qb01\tbu0\qb0}{\kern1em\uptrio o{1.3}0\qu1\cu}}%
> \sk\sk\sk\pause% \en \bar %2 \Notes \hu{``d!}\sk\sk\sk\hu{``a!}%
> |\zq a\ql d\sk\ql d\sk\ibl0c0\qb0c\tbl0\zqb0a\qb0d\sk\ql b%
> \nextvoice\ttie0\wh f%
> \en
> \bar %3
> \Notes
> \hu{``e!}\sk\sk\sk\hu{``a!}%
> |\zq b\ql d\sk\ql d\sk\ibl0c0\qb0c\tbl0%
> \zqb0b\qb0d\sk\ql b%
> \nextvoice\itieu0g\wh g%
> \en
> \setvolta{1}%
> \bar %4
> \Notes
> \hu{``e!}\sk\sk\sk\hu{``a!}%
> |\zq b\ql d\sk\ql d\sk\ibl0c0\qb0c\tbl0\zqb0b\qb0d\sk\ql b%
> \nextvoice\ttie0\wh g%
> \en
> \setrightrepeat%
> \setvolta{2}%
> \bar %5
> \Notes
> \qu{``e!}\sk\qp\sk\hp%
> |\zq{`g!b}\ql d\sk\qp\sk\hp\sk\sk%
> \nextvoice\qu g%
> \en
> \Endpiece
> 
> \bye
> ---
> TeX-music@tug.org mailing list
> If you want to unsubscribe or look at the archives, go to
> http://tug.org/mailman/listinfo/tex-music

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

Re: [Tex-music] Octave treble clef

[Don Simons]

Dirk Laurie wrote
> 
> 2018-05-20 21:33 GMT+02:00 Don Simons <dsim...@roadrunner.com>:
> > I’m working on PMX, trying to get it to handle (low) octave treble
> > clefs predictably in all possible scenarios. One such situation would
> > be where there is a single instrument with multiple staves, once of
> > which has a normal treble clef and another an octave treble clef. I
> > cannot see how to get MusiXTeX to do this, because in the clef
> > substitution command \settrebleclefsymbol[n]\treblelowoct the argument
> > n is instrument number, not staff number. It seems like within a given
> > instrument, you’re stuck with all of the treble clefs being the same. Am I
> right?
> 
> Do you have a typesetter's attitude or a musician's attitude to this issue?
> 
> As a musician, I would absolutely hate to play a piece with one treble clef 
> and
> one octave-treble clef. I would strongly prefer two treble clefs with one of
> them having an appropriate 8va annotation.
> 
None of the above. It's a computer programmer's attitude, trying to make the 
program robust enough to cover all the bases. I don't really expect anyone ever 
to want this feature, but then I didn't expect anyone to want to change to and 
from octave treble clef within a single voice, and someone did. I suspect the 
result is going to be that it can only be done with some devilishly complex, 
original TeX programming beyond my capabilities, and that the ultimate outcome 
will just be "sorry you can't do that with PMX".

BTW, NONE of this would ever have come up if the octave treble clefs were 
handled in MusiXTeX the same as normal clefs. Just sayin'.

--Don


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

[Tex-music] Octave treble clef

[Don Simons]

I'm working on PMX, trying to get it to handle (low) octave treble clefs
predictably in all possible scenarios. One such situation would be where
there is a single instrument with multiple staves, once of which has a
normal treble clef and another an octave treble clef. I cannot see how to
get MusiXTeX to do this, because in the clef substitution command
\settrebleclefsymbol[n]\treblelowoct the argument n is instrument number,
not staff number. It seems like within a given instrument, you're stuck with
all of the treble clefs being the same. Am I right?

 

--Don

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

Re: [Tex-music] staff crossing beams

[Don Simons]

Just as an example of how complicated this general problem can get, can anyone 
(Andre?) figure out any way at all (even using inline TeX) to get the doubled 
beam in the second part of this to come out above the main beam rather than 
below?

 

==

2 2 4 4 4 4 0 0

1 1 20 0

 

 

bt

.\

w3i

[u c83 e g1 a b8 ]j rb2 /

rb2 [j c84 e g1 b c8 ] /

==

 

--Don

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Monday, May 07, 2018 11:43 PM
To: Werner Icking Music Archive <tex-music@tug.org>
Subject: Re: [Tex-music] staff crossing beams

 

Ok Don,

 

Thanks

 

Andre

 

From: Don Simons 

Sent: Tuesday, May 8, 2018 7:41 AM

To: 'Werner Icking Music Archive' 

Subject: Re: [Tex-music] staff crossing beams

 

Andre, I haven’t forgotten about this; in fact I’ve spent some time trying to 
work out the coding. But I’m about ready to give up on trying to get PMX to do 
the right stuff on the staff-jumper with 3 sixteenths down and 1 sixteenth + 1 
eighth up. I’ve gotten part way there but I’m very worried that things I do 
would mess up other combinations … when you start changing the multiplicity AND 
the direction of the jump AND the exact location of the multiplicity change 
relative to the jump AND the number of jumps AND the number of multiplicity 
changes, there are so many possibilities I’d have a hard time sorting them all 
out and then testing them all. So I’m afraid for now you’ll just have to work 
out some inline TeX to replace the bad TeX commands with the right ones.

 

--Don

 

From: Don Simons [mailto:dsim...@roadrunner.com] 
Sent: Saturday, April 28, 2018 12:48 PM
To: 'Werner Icking Music Archive' <tex-music@tug.org <mailto:tex-music@tug.org> 
>
Subject: RE: [Tex-music] staff crossing beams

 

Andre, I think you know PMX better than I do! So it looks like all I have to do 
to fix the first problem is to get PMX to enter \tbbu1 rather than \rbbu2 
before the last note of the first staff-jumper, and rely on the user to start 
it with [l+14 .

I still haven’t sorted out the other problem.

 

--Don

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, April 28, 2018 10:45 AM
To: Werner Icking Music Archive <tex-music@tug.org <mailto:tex-music@tug.org> >
Subject: Re: [Tex-music] staff crossing beams

 

Thanks Don,

 

using  [l+14 g1- cs ]j rb4 / changes the order of the beams

 

Andre

 

From: Don Simons 

Sent: Saturday, April 28, 2018 6:09 PM

To: 'Werner Icking Music Archive' 

Subject: Re: [Tex-music] staff crossing beams

 

Very challenging. Even if I were to fix PMX to generate the “proper” code, 
there’s a basic problem with the order of the multiple beams. Here’s a related 
example that does go through, but obviously you’d prefer to have the lower beam 
continue and the upper one stop at the last 1/16 note. I haven’t tried to work 
out the TeX code for that but I suspect it’ll be very tricky.

 

--Don



==

2 2 3 8 3 8 0 0

1 1 20 0

 

 

bt

.\

Abpe

w5i

[u g1- cs ]j rb4 /

rb8 [ju g1+ g zb g8 ] //

r4d /

=

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, April 28, 2018 6:57 AM
To: Werner Icking Music Archive <tex-music@tug.org <mailto:tex-music@tug.org> >
Subject: [Tex-music] staff crossing beams

 

Dear Don, dear all

 

I still have a problem with staff crossing beams.

 

In the 1st bar: [ju g1+ g8 zb ]  does not show an 8th note for the ‘g8’ but a 
16th.

the 2nd bar seems  ok if i remove the’g8’,

but if i want a beam for [ e+ sf b s ]  and then it goes wrong, see 3rd bar.

 

Thanks for helping

 

Andre

 

=

3 2 6 8 6 8 0 0

1 2 20 0

 

 

btt

.\

Abpe

w5i

[u g1- cs d ]j rb rb2  /

rb8 rb1 [ju g1+ g8 zb ] rb rb4 //

r4d a1s b d zb  g+ zb-  f8+ zb- /

b8 fa ga e+ sf b s  .cas /

%

[u g1- cs d ]j rb rb2  [u g1- cs d ]j rb rb2 /

rb8 rb1 [ju g t ] g2 t zb  rb8 rb1 [ju g t ] g2 t zb //

r4d a1s b tl d zb t tl g+ zb- t tl f8+ zb- t  r4d f1 g tl b zg t tl e+ zg- t tl 
d8+ zg- t /

b8 fa ga e+ sf b s  .cas | b8 fa ga [ e+ sf b s ]  .cas /

%

===

  _  

---
TeX-music@tug.org <mailto:TeX-music@tug.org>  mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

  _  

---
TeX-music@tug.org <mailto:TeX-music@tug.org>  mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

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

Re: [Tex-music] staff crossing beams

[Don Simons]

Andre, I haven’t forgotten about this; in fact I’ve spent some time trying to 
work out the coding. But I’m about ready to give up on trying to get PMX to do 
the right stuff on the staff-jumper with 3 sixteenths down and 1 sixteenth + 1 
eighth up. I’ve gotten part way there but I’m very worried that things I do 
would mess up other combinations … when you start changing the multiplicity AND 
the direction of the jump AND the exact location of the multiplicity change 
relative to the jump AND the number of jumps AND the number of multiplicity 
changes, there are so many possibilities I’d have a hard time sorting them all 
out and then testing them all. So I’m afraid for now you’ll just have to work 
out some inline TeX to replace the bad TeX commands with the right ones.

 

--Don

 

From: Don Simons [mailto:dsim...@roadrunner.com] 
Sent: Saturday, April 28, 2018 12:48 PM
To: 'Werner Icking Music Archive' <tex-music@tug.org>
Subject: RE: [Tex-music] staff crossing beams

 

Andre, I think you know PMX better than I do! So it looks like all I have to do 
to fix the first problem is to get PMX to enter \tbbu1 rather than \rbbu2 
before the last note of the first staff-jumper, and rely on the user to start 
it with [l+14 .

I still haven’t sorted out the other problem.

 

--Don

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, April 28, 2018 10:45 AM
To: Werner Icking Music Archive <tex-music@tug.org <mailto:tex-music@tug.org> >
Subject: Re: [Tex-music] staff crossing beams

 

Thanks Don,

 

using  [l+14 g1- cs ]j rb4 / changes the order of the beams

 

Andre

 

From: Don Simons 

Sent: Saturday, April 28, 2018 6:09 PM

To: 'Werner Icking Music Archive' 

Subject: Re: [Tex-music] staff crossing beams

 

Very challenging. Even if I were to fix PMX to generate the “proper” code, 
there’s a basic problem with the order of the multiple beams. Here’s a related 
example that does go through, but obviously you’d prefer to have the lower beam 
continue and the upper one stop at the last 1/16 note. I haven’t tried to work 
out the TeX code for that but I suspect it’ll be very tricky.

 

--Don



==

2 2 3 8 3 8 0 0

1 1 20 0

 

 

bt

.\

Abpe

w5i

[u g1- cs ]j rb4 /

rb8 [ju g1+ g zb g8 ] //

r4d /

=

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, April 28, 2018 6:57 AM
To: Werner Icking Music Archive <tex-music@tug.org <mailto:tex-music@tug.org> >
Subject: [Tex-music] staff crossing beams

 

Dear Don, dear all

 

I still have a problem with staff crossing beams.

 

In the 1st bar: [ju g1+ g8 zb ]  does not show an 8th note for the ‘g8’ but a 
16th.

the 2nd bar seems  ok if i remove the’g8’,

but if i want a beam for [ e+ sf b s ]  and then it goes wrong, see 3rd bar.

 

Thanks for helping

 

Andre

 

=

3 2 6 8 6 8 0 0

1 2 20 0

 

 

btt

.\

Abpe

w5i

[u g1- cs d ]j rb rb2  /

rb8 rb1 [ju g1+ g8 zb ] rb rb4 //

r4d a1s b d zb  g+ zb-  f8+ zb- /

b8 fa ga e+ sf b s  .cas /

%

[u g1- cs d ]j rb rb2  [u g1- cs d ]j rb rb2 /

rb8 rb1 [ju g t ] g2 t zb  rb8 rb1 [ju g t ] g2 t zb //

r4d a1s b tl d zb t tl g+ zb- t tl f8+ zb- t  r4d f1 g tl b zg t tl e+ zg- t tl 
d8+ zg- t /

b8 fa ga e+ sf b s  .cas | b8 fa ga [ e+ sf b s ]  .cas /

%

===

  _  

---
TeX-music@tug.org <mailto:TeX-music@tug.org>  mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

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

Re: [Tex-music] Varying the vertical inter-system space globally

[Don Simons]

Hi, Matthias--

You wrote

>...
> So do I get you right that Ae does not only make the space between the
> systems equal, but also tries to spread the systems equally over the page,
> i.e. tries to fill the whole page (if some threshold, how full the page
has to
> be, is passed)?

No, not exactly. Ae itself doesn't TRY to spread the systems over the full
page height. But (evidently) when I designed it, I assumed there were enough
staves on the page to put you in "category two", i.e., where the DEFAULT is
to spread the systems roughly equally over the full page height. I don't
think I even considered the effect of Ae on "category one" pages where by
default the systems would be grouped toward the top. If you have few enough
systems to put you in category one by default, but  you would rather have
those systems spread (more-or-less) equally over the full height, use Av,
whose purpose is to cancel out the grouping of systems toward the top of the
page, and essentially to put you in category two.

Since we've gotten so far into this, let me repeat a paragraph from the PMX
manual, which explains why I really concocted Ae, and also why the default
in category two does not necessarily give EXACTLY equal vertical spacing
between systems:

"MusiXTEX normally draws a virtual box around each system and inserts equal
vertical space between boxes. When objects protrude above the top staff in a
system or below the bottom one, this can lead to unequal spacing between the
top staff line in one system and the next. If you prefer that the vertical
spacing between the staves of consecutive systems be constant for the whole
page, use the e option of the A command. One side benefit of Ae is that it
will prevent systems from spilling over onto extra pages, regardless of how
many systems are put on the page. 
When using this option, you may occasionally want to force more vertical
space between certain systems. There is a TEX macro \spread that can be
inserted anywhere in the system before the desired wider gap. It has one
argument, the desired extra space in \internotes."

Now to review what I earlier tried to explain, if you're in category one and
want to continue to group systems near the top of the page, then (1) Ae is
not recommended, (2) \spread still works to change inter-system spacing, but
(3) AI does not work (to change inter-staff spacing). I had said I may look
into (3), and I may do that. But in the meantime, I just discovered a
roundabout PMX-only way to control both the inter-system and inter-staff
spacing in category one. It uses a recent new command (PMX 2.84) AV, which
inserts hard vertical space before and after the next page eject. So you
could (1) use Av (which puts you in category 2), (2) use AV+20+0 (for
example) to insert 20 \Internote vertical space before the page eject, (3)
use AI.7 for example to reduce the inter-staff spacing.  By adjusting the
arguments of AV and AI, you could get any combination of inter-staff and
inter-system spacing you want. And you can also use Ae to force exactly
equal inter-system spaces.

--Don

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

Re: [Tex-music] Varying the vertical inter-system space globally

[Don Simons]

 "Matthias Holländer" wrote
>
> Dear Don,
> 
> I really didn't mean to offend you or get you upset, if that was the case I
> firmly beg your pardon. 

Absolutely no offense taken. It ALWAYS makes me happy to see new evidence of 
anyone using PMX.

> I only wanted to make clear what I mean. And you're
> right, I got the code confused a bit there (I will point out how and correct 
> it in
> a moment). To avoid further confusion I want to furthermore take into
> account only the example with two staves per system ("Der Tag, mein Gott,
> ist nun vergangen"), since the other one was focused on the "two pieces of
> music in one document" problem, which is solved.
> 
> In the two staves per system example, which I wanted to use to
> demonstrate the vertical spacing thing, because the change I aimed for is
> more impressive (compare the pdf-files in the attachment), there is three
> systems (six staves) on the page. 

Vertical spacing in PMX and in MusixTeX is really a bitch. I've spent countless 
hours trying to get it right both in PMX, and if PMX messes up, then by using 
inline TeX in my own typesets.  I keep hoping the problems will go away, but 
new ones keep popping up.
 
I think our wires got crossed. You seem to be referring to your 2nd posting on 
4/29, which did have an example with 3 systems, and which seems to correspond 
to one of the two pdf's you just posted . However, I had not analyzed that one 
at all, but rather was only looking at and commenting on the 3rd example file 
in your 3rd posting on 4/29, which had 5 systems and 3 \spread's. There's a 
fundamental, very important distinction between these two cases: if there are 
too few staves in total on a page, PMX by default will group them near the top 
and leave a wider space at the bottom, but otherwise spread them out more or 
less equally vertically. Your two recent PDFs were both in in the first 
category, but my earlier comments were entirely about files in the 2nd 
category. There are some major subtleties I won't go into detail here about 
what counts as "too few staves" in the first category, and also why in the 
second category they would not in general be exactly equally spaced by default. 
But suffice it to say the two categories pose radically different challenges in 
setting vertical spacing, and PMX handles them very differently. 

Historically I've spent much more effort making PMX deal with the 2nd category, 
simply because most scores use full pages. That may explain in part why, as 
I've just realized, when in the first category, AI seems to have no effect at 
all, and Ae doesn't do what you'd expect. As you probably noticed, when you 
used Ae in the code you posted for the 3-system example, curiously it did 
spread the systems a bit but not equally over the whole page height. However, 
I'd regard Ae's failure to spread the systems over the full height in the first 
category as a non-issue, because if one really wanted to spread a small number 
of systems roughly equally over the full height, he could make it happen with 
Av, together with Ae if you wanted them exactly equally spaced, and with AI to 
further adjust the spacing between staves in each system. And if you had a 
small number of systems grouped toward the top of the page and simply wanted to 
tweak the inter-system space, \spread would still work.

On the other hand, at some point I may look into why AI doesn't seem to work to 
alter inter-staff spacing in the first category.  But please don't hold your 
breath.

I am curious how you managed to adjust the inter-system spacing in the two 
first-category examples you most recently posted. DerTag_wide seems to 
correspond with the 3-system code you posted on 4/29, but as I tried to explain 
above, that behavior of Ae is not as expected and not something I ever planned 
for. However, when I remove Ae, the spacing comes out narrower than in 
DerTag_close, so the only way I can think of offhand to get your spacing there 
is to remove Ae and use \spread. Could you post the PMX files?
 
>... 
> "Don Simons" wrote:
> >I assume you're aware that in your sample you did NOT apply the
> >inter-system reduction to all the inter-system spaces, but only to 3 of the 
> >4.
>> Therefore the 3rd space got larger.
> May it be that this refers to the example of how to print 2 pieces of music 
> in a
> single document, given by Andre van Ryckeghem? 

No. See my previous comment about which of your samples I was referring to.

--Don



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

Re: [Tex-music] Varying the vertical inter-system space globally

[Don Simons]

"Matthias Holländer" wrote
> So here comes the "two pieces of music in one document" thing. 
>...
> With the help of Andres code -- thank you for that -- I can, in my view,
> significantly improve the procedure to:
> 
> ==
>... 
> ==
> There are basically two questions that remain on this code:
> 1.) I hardly get any clue of what I do there. If I'm not mistaken these 
> in-line
> TeX comands are MusiXTeX commands, but since most of them are not
> documented I guess they are from the "implementation of MusiXTeX itself"
> level, as one could maybe call it. Is there a tutorial or other way to slowly 
> get
> behind these things? I would straight away need it to understand what the
> commented out lines after the title definition can be used for and to

There is no single, simple tutorial about the inline TeX commands. Their 
definitions could be in TeX itself, musixtex.tex, or pmx.tex. You have access 
to the latter two files on your own computer, and can look in them to search 
for the definitions of the macros. Beyond that, you'd need to learn about the 
basics of TeX. None of it is at all easy. The standard reference for TeX is 
"The TeXbook" by Donald Knuth (the creator of TeX). For MusiXTeX the manual is 
available from WIMA. There is no reference explaining most of the macros 
defined in pmx.tex. 

> 2.) Change the font size of the second "Saabund on jälle öö" title from
> \bigfont to the fontsize that is used in the first title (or shrink the first 
> title's
> font size as compensational solution).
> 
That one is easy, but I had to go through several steps to refresh my memory: 
(1) look in the TeX file generated by PMX for the example, to see where and how 
the two titles were printed out. (2) when I saw that the top title was the 4th 
argument of the macro \titles, look in pmx.tex for the definition of \titles. 
The 4th argument is preceded with a font designation \BIgtype. 

So what you need to do is simply add \BIgtype right before the 2nd title entry 
in the PMX file, i.e.,

\\\def\titel{\BIgtype Saabund on j\"{a}lle \"{o}\"{o}}

--Don


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

Re: [Tex-music] Varying the vertical inter-system space globally

[Don Simons]

"Matthias Holländer" wrote
 
>...
> Quoting Don:
> >I can help you most effectively if you could provide a .pmx file that is as
> close to as possible to what you finally want, and then clearly explain what
> you’d >like to change from that.
> I will try to explain myself better. I wanted to know, if there is an
> automatized and thus globally working, and in my view nicer, way to reduce/
> increase equal inter-system space (leaving it still equal), i.e. to achieve:
> 
> ===
> 2 2 6 4 6 4 1 +1
> 1 5 20 0
> 
> tt
> ./
> 
> Tc
> Clement Cotterill Scholefield, 1874
> Tt
> Der Tag, mein Gott, ist nun vergangen\\
> Ac4e
> Ki1+14+1
> \\nobarnumbers\
> 
> % Bar 1
> \spread{-20}\
> d43 | g22 g43 d23 d4 /
> d44 D"c.f." | ( b44 c4 ) b4 ( d4 b4 ) a4 /
> 
> % Bar 2
> e43 a42 c4 d4 d4 oc e4 /
> ( g44 a4 ) e44 g4 f4 oc e4 /
> 
> % Bar 3
> \spread{-20}\
> f43 g4 f4 e2 e4 /
> d24 d4 ( g4 a4 ) b4 /
> 
> % Bar 4
> a22 a4 d23 oc f4 /
> a24 g4 f2 oc d4 /
> 
> % Bar 5
> g23 g4 d2 d4 /
> ( b44 c4 ) b4 ( d4 b4 ) a4 /
> 
> % Bar 6
> \spread{-20}\
> e43 a42 c4 d4 d4 oc c4 /
> ( g44 a4 ) e44 g4 f4 oc e4 /
> 
> % Bar 7
> b22 d4 e4 b42 c4 /
> ( d44 e4 ) f4 ( g4 b4 ) a4 /
> 
> % Ending bar
> m5400
> c43 a4 d4 g22 /
> ( e44 g4 ) f4 g2 /
> 
> 
> in contrast to the same document without any \spread command. Be aware
> that I always used the same amount of \interlines for reduction and used it
> for each inter-system space and therefore achieved the same as if Ae.8 or
> Ae1.2 would be a command to use the originally by PMX determined inter-
> system space and multiply it by e.g. 0.8. That was what I meant in my first
> email.

In this message I'm just going to address only the above example, and will 
comment on your other items later. I assume you're aware that in your sample 
you did NOT apply the inter-system reduction to all the inter-system spaces, 
but only to 3 of the 4. Therefore the 3rd space got larger. This still leaves 
me somewhat unclear about exactly what your objective is. But I'll provide the 
following comments on the general topic of vertical spacing.

1. There is no way I can think of to generate your example using pure PMX. But 
as you've demonstrated, you can do it using inline TeX. I've done hundreds of 
typesets and occasionally encountered unusual situations which, without 
rewriting PMX, could only be solved with inline TeX. Unless it's something I 
think will come up routinely, I've just bitten the bullet and used the 
necessary inline TeX. Furthermore, it's hard to think of any real music 
typesetting task that would require an isolated single inter-system gap like 
the one in your example, so I'm not inclined to spend the effort to make it 
possible with pure PMX.

2. When you use Ae, there's a law of conservation of vertical space. On each 
page, a fixed amount of vertical space must be taken up by inter-system spaces 
on one hand, and inter-staff spaces within the systems on the other hand. 
Assuming the top and bottom margins stay the same, and that there are more than 
one staff per system, then if you want to UNIFORMLY narrow the inter-system 
space, the space between staves within each system will have to get bigger, and 
vice versa.

3. If you use Ae and only have a single staff per system, it's physically 
impossible to change the inter-system spacing (without changing the page height 
or number of systems per page).

4. AI directly alters the inter-staff spacing within each system. If Ae is 
used, AI therefore indirectly affects the inter-system space, and does so 
uniformly.

5. \spread selectively alters the inter-system spacing, but has no effect of 
inter-staff spacing within a system. So if you change only one such space, then 
(with Ae) all the others will change to compensate. And if you try to \spread 
ALL of the inter-system spaces on a page by the same amount, nothing will 
change.

6. You could get the same vertical spacing in your sample file by using only a 
single \spread{20}\  command before the 4th system. Please don't ask me to 
explain why the number is 20 and not 60. Whenever I want to adjust vertical 
spacing, I get the numbers for \spread, AI, or the movement break commands by 
trial and error, not by calculation.

7. If you have a score with multiple staves per system, and if all systems are 
to be spaced equally, and if you want to uniformly change the inter-system 
spacing, (which may be what you are asking for, despite the fact it's 
inconsistent with your example file), you cannot do it without also changing 
the inter-staff spacing within each system. Therefore AI  can be used to get 
that effect. Because of this fact, at this time I'm not motivated to make any 
changes in PMX to globally (and directly) change inter-system spacing. 

8. If the unequal system spacing in your example file is REALLY what you want, 
and if you really hate using even a single instance of \spread, you could 
consider 

Re: [Tex-music] staff crossing beams

[Don Simons]

Andre, I think you know PMX better than I do! So it looks like all I have to do 
to fix the first problem is to get PMX to enter \tbbu1 rather than \rbbu2 
before the last note of the first staff-jumper, and rely on the user to start 
it with [l+14 .

I still haven’t sorted out the other problem.

 

--Don

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, April 28, 2018 10:45 AM
To: Werner Icking Music Archive <tex-music@tug.org>
Subject: Re: [Tex-music] staff crossing beams

 

Thanks Don,

 

using  [l+14 g1- cs ]j rb4 / changes the order of the beams

 

Andre

 

From: Don Simons 

Sent: Saturday, April 28, 2018 6:09 PM

To: 'Werner Icking Music Archive' 

Subject: Re: [Tex-music] staff crossing beams

 

Very challenging. Even if I were to fix PMX to generate the “proper” code, 
there’s a basic problem with the order of the multiple beams. Here’s a related 
example that does go through, but obviously you’d prefer to have the lower beam 
continue and the upper one stop at the last 1/16 note. I haven’t tried to work 
out the TeX code for that but I suspect it’ll be very tricky.

 

--Don



==

2 2 3 8 3 8 0 0

1 1 20 0

 

 

bt

.\

Abpe

w5i

[u g1- cs ]j rb4 /

rb8 [ju g1+ g zb g8 ] //

r4d /

=

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, April 28, 2018 6:57 AM
To: Werner Icking Music Archive <tex-music@tug.org <mailto:tex-music@tug.org> >
Subject: [Tex-music] staff crossing beams

 

Dear Don, dear all

 

I still have a problem with staff crossing beams.

 

In the 1st bar: [ju g1+ g8 zb ]  does not show an 8th note for the ‘g8’ but a 
16th.

the 2nd bar seems  ok if i remove the’g8’,

but if i want a beam for [ e+ sf b s ]  and then it goes wrong, see 3rd bar.

 

Thanks for helping

 

Andre

 

=

3 2 6 8 6 8 0 0

1 2 20 0

 

 

btt

.\

Abpe

w5i

[u g1- cs d ]j rb rb2  /

rb8 rb1 [ju g1+ g8 zb ] rb rb4 //

r4d a1s b d zb  g+ zb-  f8+ zb- /

b8 fa ga e+ sf b s  .cas /

%

[u g1- cs d ]j rb rb2  [u g1- cs d ]j rb rb2 /

rb8 rb1 [ju g t ] g2 t zb  rb8 rb1 [ju g t ] g2 t zb //

r4d a1s b tl d zb t tl g+ zb- t tl f8+ zb- t  r4d f1 g tl b zg t tl e+ zg- t tl 
d8+ zg- t /

b8 fa ga e+ sf b s  .cas | b8 fa ga [ e+ sf b s ]  .cas /

%

===

  _  

---
TeX-music@tug.org <mailto:TeX-music@tug.org>  mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

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

Re: [Tex-music] staff crossing beams

[Don Simons]

Very challenging. Even if I were to fix PMX to generate the “proper” code, 
there’s a basic problem with the order of the multiple beams. Here’s a related 
example that does go through, but obviously you’d prefer to have the lower beam 
continue and the upper one stop at the last 1/16 note. I haven’t tried to work 
out the TeX code for that but I suspect it’ll be very tricky.

 

--Don



==

2 2 3 8 3 8 0 0

1 1 20 0

 

bt

.\

Abpe

w5i

[u g1- cs ]j rb4 /

rb8 [ju g1+ g zb g8 ] //

r4d /

=

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, April 28, 2018 6:57 AM
To: Werner Icking Music Archive 
Subject: [Tex-music] staff crossing beams

 

Dear Don, dear all

 

I still have a problem with staff crossing beams.

 

In the 1st bar: [ju g1+ g8 zb ]  does not show an 8th note for the ‘g8’ but a 
16th.

the 2nd bar seems  ok if i remove the’g8’,

but if i want a beam for [ e+ sf b s ]  and then it goes wrong, see 3rd bar.

 

Thanks for helping

 

Andre

 

=

3 2 6 8 6 8 0 0

1 2 20 0

 

 

btt

.\

Abpe

w5i

[u g1- cs d ]j rb rb2  /

rb8 rb1 [ju g1+ g8 zb ] rb rb4 //

r4d a1s b d zb  g+ zb-  f8+ zb- /

b8 fa ga e+ sf b s  .cas /

%

[u g1- cs d ]j rb rb2  [u g1- cs d ]j rb rb2 /

rb8 rb1 [ju g t ] g2 t zb  rb8 rb1 [ju g t ] g2 t zb //

r4d a1s b tl d zb t tl g+ zb- t tl f8+ zb- t  r4d f1 g tl b zg t tl e+ zg- t tl 
d8+ zg- t /

b8 fa ga e+ sf b s  .cas | b8 fa ga [ e+ sf b s ]  .cas /

%

===

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

[Tex-music] New PMX version available

[Don Simons]

There’s a new complete distribution of PMX, Version 2.84, on the Icking 
Archive, at

 

http://icking-music-archive.org/software/htdocs/index.html

 

--Don Simons

 

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

Re: [Tex-music] PMX : moving dots

[Don Simons]

Just to show how ugly this dot-moving problem is, here an example produced by 
the code in its current state. 3 out of 4 isn’t bad, right?

 

--Don

 

=

1 1 2 4 2 4 0 0

0 3 20 0

 

t

.\

w4i

Ab

r8 b43ld+0+1 zc  

b43ld+0+1 zc r8 / 

r8 b43ld+0+1 zc /  

b43ld+0+1 zc r8 /

=



 

 

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Don Simons
Sent: Saturday, January 20, 2018 12:18 PM
To: 'Werner Icking Music Archive' <tex-music@tug.org>
Subject: Re: [Tex-music] PMX : moving dots

 

I’m still working to correct this bug. It’s proving to be insanely complicated, 
due in part to the complex and different ways I had originally set up PMX to 
store information about shifted dots on main notes and chord notes. I have so 
far managed to fix Dieter’s case (the last chord in his example below). But in 
a closely related, very specific case, my fix breaks down, namely if you don’t 
move the dot on the B but do move the one on the C. My question for the group 
is this: Can you think of any real situation where you ever would want to do 
that? I.e., a case where you have a dotted 2-note chord with an interval of a 
second, and you want to move the dot on the right-most note from its default 
position, but leave the dot on the left-most note in its default position 
(where the dot will probably crash into the other note head)? It would save me 
some more hair-pulling if I didn’t have to worry about this very particular and 
very unlikely case.

 

--Don

 

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

Re: [Tex-music] PMX : moving dots

[Don Simons]

I’m still working to correct this bug. It’s proving to be insanely complicated, 
due in part to the complex and different ways I had originally set up PMX to 
store information about shifted dots on main notes and chord notes. I have so 
far managed to fix Dieter’s case (the last chord in his example below). But in 
a closely related, very specific case, my fix breaks down, namely if you don’t 
move the dot on the B but do move the one on the C. My question for the group 
is this: Can you think of any real situation where you ever would want to do 
that? I.e., a case where you have a dotted 2-note chord with an interval of a 
second, and you want to move the dot on the right-most note from its default 
position, but leave the dot on the left-most note in its default position 
(where the dot will probably crash into the other note head)? It would save me 
some more hair-pulling if I didn’t have to worry about this very particular and 
very unlikely case.

 

--Don

 

 

From: Don Simons [mailto:dsim...@roadrunner.com] 
Sent: Thursday, January 11, 2018 3:08 PM
To: 'Werner Icking Music Archive' <tex-music@tug.org>
Subject: RE: [Tex-music] PMX : moving dots

 

Hi, Dieter, and happy new year!

 

Yes, it is a bug or a feature :) For now, it looks like you could get the dots 
where you want them by moving the dot on the opposite note. I will look into 
the coding…I’ve already located some comments about switching notes in chords 
when there are 2nds. It’s not surprising this has never come up before, since 
it depends on the 2nd, the dots, and the down stem. I assume you noticed that 
the horizontal location of the notes is a little flaky too…you’d think they 
should be the same distance from the rest in both cases. More as it develops.

 

--Don

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Dieter
Sent: Thursday, January 11, 2018 2:01 AM
To: Werner Icking Music Archive <tex-music@tug.org <mailto:tex-music@tug.org> >
Subject: [Tex-music] PMX : moving dots

 

Hi Don,

please have a look at this example.

==

114 4 4 4  0 0  0 2  20  0
  
t
./
w200
 r8   b43d+0+1   zcr8   b43ld+0+1   zc  /





The 2nd dotted note with a low stem moves the wrong dot.

Is this a bug or a feature?

Regards,

Dieter

 

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

Re: [Tex-music] Produce midi file from MusiXTeX code

[Don Simons]

Bob Tennent wrote
>  >|I use a software called "SharpEye" for scanning and  >|translating to
> MusicXML.
> 
> SharpEye requires an image as input (rather than reading PDF scores). It
can
> generate midi directly, but MusicXML -> PMX
> -> midi is likely the better choice because SharpEye doesn't
> provide an editing capabilty to correct the inevitable scanning errors.
So
> you'll have to edit the PMX and hope the edited output will be scanned
> correctly.
> 
> Free demo versions of SharpEye and PhotoScore are available.
> There's also a "lite" version of PhotoScore at half price.
> 
I'm getting older and losing neurons, and maybe that's why I can't see the
role of scanning after creating a PMX file. The original question was how to
create midi from MusiXTeX. The proposal was MusiXTeX => image => scan =>
MusixXML => XML2PMX and then I assumed PMX => midi directly. Why would you
need to scan anything AFTER editing the PMX?

--Don


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

Re: [Tex-music] PMX : moving dots

[Don Simons]

Dieter wrote

>Is there a simple way (I guess there is always some TeX-way, which I 
>do not understand) to control the position of the dot in a chord note 
>like "zc" in the example below?

Uh-oh! It's another RTFM. In the section of the PMX manual on chords, in the 
very first paragraph, it says "The only time a d is required in a chordal note 
command is if the dot’s position is to be adjusted; in this case the d is 
required, followed by one or two decimal numbers, each preceded by + or -."

I still don't have the fix for the interchanged dot adjustments on the 2nds, 
but I have located some very specific comments in the code about interchanging 
the notes in the exact case where you found the problem: Interval of a 2nd, 
down stem, and main chord note is the lower of the two. Overall the coding in 
PMX that deals with chords is very complex, scattered all around, and mostly 
written at least 15 years ago, so it's taking time to reconstruct the logic. 

--Don


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

Re: [Tex-music] Upcoming PMX

[Don Simons]

Andre, your suggestion certainly does put the b4 more to the right, aligning it 
with the other staff as if it were the last note of a simultaneous sextuplet. 
If you wanted the b to be half as long as one of the triplet notes, you would 
probably want to use that notation. 



But let’s be clear that that was never the objective of the F-tuplet 
applications that Christian brought up and that I addressed in the previous two 
posts. He wanted to typeset Bach’s dotted notation for a long and short note 
that align with the first and third notes in a triplet in the other staff. And 
then he simply wanted to replace the first note of the two with a rest. When he 
tried that as an F-tuplet with PMX 2.82, it went through OK and lined up as 
desired, but the dot on the rest was missing. 2 posts ago I pointed out that as 
it now stands, PMX 2.83 will add the dot, but will not let you adjust the 
height of the dotted rest. Then the last post showed a work-around if you DO 
want to change the height of the dotted rest, all the while keeping the same 
horizontal spacing.

 

--Don

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van 
Ryckeghem
Sent: Saturday, December 16, 2017 8:46 PM
To: Werner Icking Music Archive <tex-music@tug.org>
Subject: Re: [Tex-music] Upcoming PMX

 

Perhaps, the ‘b4’ in  r4Fx3nf+3 b4 c4 / should be more to the right.

 

This could also be an solution for the rare cases:

 

r4+2Dx6n r+5D r-2 b4 c4 /

 

Andre

 

 

 

From: Don Simons 

Sent: Saturday, December 16, 2017 8:03 PM

To: 'Werner Icking Music Archive' 

Subject: Re: [Tex-music] Upcoming PMX

 

I’d like to point out that the notes in the F-tuplet I discussed earlier could 
be typeset without using the F-option at all, but with a horizontal shift 
instead. Then if you wanted to raise the rest you could use the standard 
command.

 

--Don

 



--

2 1 2 4 2 4 0 0

0 3 20 0

 

bt

.\

AbeK

w6i

g43x3n-1 f g  a /

r4Fx3nf+3 b4 c4 /

g43x3n-1 f g  a /

rd8 X:-1 b14 X: c4 /

g43x3n-1 f g  a /

rd8+4 X:-1 b14 X: c4 /

--

 

 

 

From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Don Simons
Sent: Saturday, December 16, 2017 10:09 AM
To: 'Werner Icking Music Archive' <tex-music@tug.org <mailto:tex-music@tug.org> 
>
Subject: [Tex-music] Upcoming PMX

 

I’m very close to releasing a new version of PMX reflecting various fixes 
requested by Andre and Christian over the last several weeks. Before 
finalizing, I’d like some opinions about how far to go with one of them. 
Christian has used some constructions like r4Fx3 b. With notes, this gives a 
dotted eighth followed by a sixteenth, horizontally spaced as if they were the 
first and third notes in a triplet. (It’s a very, very rare notation used by 
Bach, and no one else I know of). Christian pointed out that when starting with 
a rest, for consistency the rest should be dotted. I’ve worked out a way to get 
PMX to do that. The problem is that my band-aid coding is guaranteed to fail if 
you try to raise or lower the (now dotted) rest from the default, midstaff 
position. The problem occurs either if you try to raise it manually, or if PMX 
tries to do it internally as a result of the global AK option for keyboard rest 
positioning in 2-voice staves. 

 

The question is whether I should expend the considerable additional programming 
effort needed to make this extremely rare construction work in the doubly rare 
case where the dotted rest would need to be raised or lowered.

 

--Don

 



  _  

---
TeX-music@tug.org <mailto:TeX-music@tug.org>  mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

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