t; without
reprogramming PMX. But I guess that's not possible, since (as Bob implicitly
suggests) if single, up-beamed notes appeared above the staff, there would
be ledger lines to be avoided.
> -Original Message-
> From: Bob Tennent [mailto:rdtenn...@gmail.com]
> Sent: Sunday, August 20, 201
It's been interesting and a little frustrating looking into the 4 "features"
Andre identified. Most of the frustration is from a combination of my fading
memory and insufficient commenting in the PMX code, making it very difficult
to reconstruct PMX's internal logic. But here's where I stand on
K-0+4
e44 f g a b c d e /
===
The transposition is handled internally in PMX and does not use \transpose,
regardless of how far you are transposing.
--Don Simons
> -Original Message-
> From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of R
; ./
> d24x3 zd+ c- zc+ b- zb+ d-x3 zd+ c-d zc+ b- zb+ /
> f4 f rb rb //
> b2Dx3 a b2Dx3 a /
> =======
>
> Andre
> -Oorspronkelijk bericht-
> From: Don Simons
> Sent: Saturday, April 29, 2017 8:04 AM
> To: 'Werner Icking Music Archi
Hi, Andre—
Regarding changing a beam’s multiplicity where it jumps staves: Thanks for
pointing this out…I had never even thought of it. Unlike the issue with dots, I
don’t think this one can be fixed with PMX commands alone. As you probably
realized, it can be fixed with in-line TeX; below
Based on recent list postings, I'm considering implementing staff gaps in
PMX. (Since the need is so rare, this is mainly an intellectual challenge).
It would use psframe from pstricks, to paint a white box from one barline to
the next, covering the full height of the system. The psframe construct
out how to shorten the stem that way? I'll probably also want to do
this for beamed notes.
--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
The image below is from a PDF. When I print it out, the "#" symbol looks
normal !?
From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Don Simons
Sent: Sunday, August 27, 2017 11:38 AM
To: 'Werner Icking Music Archive' <tex-music@tug.org>
Subject: Re: [Tex-musi
the "#" symbol in the
subtitle looks weird? I got the same result both with ghostview and with
acrobat distiller.
--Don
> -Original Message-
> From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Don
> Simons
> Sent: Saturday, Au
Andre Van Ryckeghem wrote
> 1. In the first bar, the hidden accidentals reserve space. This is
corrected in
> the second bar by using 'zcf<0 '
...
> ===
> 1 1 6 8 6 8 0 0 1 3 20 0
>
> t
> ./
> Apb
> r8+6 a8n+ o.+5 o_ zff zefi ffi zefi zcf efi zcfi zaf cfi zafi zff afi
> r8+zffi
> ze
alls above the staff (or below, for \upz,
\ust)?
--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
c-boun...@tug.org] On Behalf Of Jean-
> Pierre Coulon
> Sent: Monday, August 28, 2017 11:09 PM
> To: Werner Icking Music Archive <tex-music@tug.org>
> Subject: Re: [Tex-music] Strange "#" symbol
>
> On Mon, 28 Aug 2017, Don Simons wrote:
>
> > I don't k
Tough question. I haven't worked out any details. But there's a clue in the
MusiXTeX manual about how you might proceed. See version 1.24PRE, p.96, in the
example for ossia. You could treat the coda as an ossia. You'd also have to
figure out how to shorten the main line of music. You could get
I think you need to activate postscript slurs … insert the command Ap .
--Don
From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Andre Van
Ryckeghem
Sent: Tuesday, October 10, 2017 9:51 PM
To: Werner Icking Music Archive
Subject: [Tex-music] staff jumpng
Christian Mondrup wrote
> On 2017-12-16 22:17, Dirk Laurie wrote:
> > 2017-12-16 21:03 GMT+02:00 Don Simons <dsim...@roadrunner.com>:
> >
> >> I’d like to point out that the notes in the F-tuplet I discussed
> >> earlier could be ty
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
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
Dirk wrote
>...
>
> The following PMX file produces the attached output. I can't play it on my
> recorder.
>
> ---
> 1 -1 1 4 4 0 6 0.0 0 1 1 20 0
>
> 0
> ./
> w60m
> c44x3 d r e44x3 f r c2 /
> ---
Thanks for the report! Maybe you need a sopranininino recorder :-)
Meanwhile, I believe
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
There's a new beta distribution of PMX version 2.82 on WIMA, at
http://icking-music-archive.org/software/pmx/pmx282PRE.zip
The only new feature here is allowing xtuplets to end with a rest. It had
been sitting around waiting for an excuse to go public, and that excuse came
out of the blue
/
==
Andre
From: Don Simons
Sent: Friday, December 8, 2017 1:57 AM
To: tex-music@tug.org <mailto:tex-music@tug.org>
Subject: [Tex-music] New PMX beta
There’s a new beta distribution of PMX version 2.82 on WIMA, at
http://icking-music-archive.org/software/pmx/pmx282P
I'll be interested to see if anyone comes up with a solution. I've faced
this question in the past but the best I could do was to end the system with
a long blank rest and remove the final barline.
--Don Simons
> -Original Message-
> From: TeX-Music [mailto:tex-music-boun...@t
something, because the 4-tuplet test file did not run
with the most recent version pmx282.
For triplets with two rests, stay tuned.
--Don
From: Don Simons [mailto:dsim...@roadrunner.com]
Sent: Friday, December 08, 2017 8:40 AM
To: 'Werner Icking Music Archive' <tex-music@tug.org>
Subje
Just a few months ago I had worked out how to make an arbitrary gap in a
staff, using pstricks. It's a sign of old age that I had forgotten about it,
but I did recently stumble across it and adapted it to the end of a final
staff. You may have to fiddle a bit with the height and width tweaks
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
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
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
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.
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
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 i
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-
> Fro
mething 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 assum
"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:
>
> ==
>...
>
"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,
hanges 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
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
>
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
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
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
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
+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 c
sb.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
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
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
: 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
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
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
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
e 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
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
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
hat 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
>
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 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 an
ay 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
-
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
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
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-
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
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\s
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
ally 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 num
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
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:
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
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
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
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
>
> 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...! Wai
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
> >>
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
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
> g
ize=.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 enab
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?
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
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,
er 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 l
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
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
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
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
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
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
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
mail.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
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
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
(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: "
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
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
t;+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
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
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
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
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,
f\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 S
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
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
>
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.
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
501 - 600 of 623 matches
Mail list logo