Werner Icking wrote:
> > Date: Tue, 14 Mar 2000 16:27:26 -0600
> > From: "Eric Petersen [Aero]" <[EMAIL PROTECTED]>
>
> > On Tue, 14 Mar 2000, Werner Icking wrote:
> >
> > > It would be interesting to convince PMX to do that using inline-TeX :-)
> >
> > And what is wrong with
> >
> > \\setsign1{2}\
> >
> > in the first music paragraph of PMX? (I've tried it; it works! But, alas,
> > the MIDI output is not-so-good sounding.)
>
> That's the hint, what I ment.
>
> I thought about coding as it sounds (as it is e.g. missing for \trebleoct or
> \treblelowoct, ...) and then making the transposition with inline TeX.
> One could e.g. redefine & and | to make the transposition local. But this
> requires in addition to change stems and beams. So I think it could be done
> well only within PMX; something like "K7+4-1" for "Corni in Fa" if these
> have the 7th voice for a composition is in C.
What \setsign does is solely to change signs; no transposition is made. What I
would like a pmx feature for transposing instruments to do is to read pitches
entered as they should sound, i.e. in C, and transpose the printing of the
corresponding voices to the keys used by the player of the instruments in
question. For example in a composition in C major a Bb clarinet part should be
written in D major. That is the way editors like Finale behave. If pmx were
programmed that way you will be able to enter your score in actual sounding
pitches, do proof listening from the MIDI output, and then first when you're
confident with your typesetting add directives for the transposing instruments.
--
Christian Mondrup, Computer Programmer
Scandiatransplant, Skejby Hospital, University Hospital of Aarhus
Brendstrupgaardsvej, DK 8200 Aarhus N, Denmark
Phone: +45 89 49 53 01
