Re: [Tex-music] PMX news: Instrument-wise transposition

2011-06-02 Thread Dirk Laurie
On Thu, Jun 02, 2011 at 02:54:22AM +0200, Don Simons wrote:
 
 I've been avoiding facing up to the possibility of entering info in the
 transposed key, let alone working out how to get MIDI to deal with it. I have
 vague notions of somehow internally doing a reverse transposition. This will
 take longer to work out.
 
At the syntax level it's easy to dream up something logical:

K[+/-][trans amt.][+/-][new key]
applies to the whole score
Ki[instrument #][+/-][trans amt.][+/-][new key]
applies to this instrument, overriding whole score
KIi[instrument #][+/-][trans amt.]
applies to this instrument's MIDI output (default: no transposition)
KSi[instrument #][+/-][sharps/flats]
instrument-specific key signature, overriding isig
needed at start of score since transposing 0 semitones will print the
old and new key signatures.

Those terrible piano pieces (Scriabin? Rachmaninov? I forget) that notate
the two hands in different keys will have to be notated as one instrument
per hand :-)  Didn't the formidable Serge occasionally write piano music
on three staves, or is that only the poor editor's attempt at making it
playable for people with normal hands?

Dirk
Dirk
---
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 news: Instrument-wise transposition

2011-06-02 Thread Cornelius C. Noack

On Wed, 1 Jun 2011, Don Simons wrote:


Date: Wed, 1 Jun 2011 17:54:22 -0700
From: Don Simons dsim...@roadrunner.com
Reply-To: Werner Icking Music Archive tex-music@tug.org
To: 'Werner Icking Music Archive' tex-music@tug.org
Subject: Re: [Tex-music] PMX news: Instrument-wise transposition

Dirk Laurie wrote


Comment: MIDI transposition should be independent of the printout.


There are three different pitch levels to worry about (relative to concert 
pitch):

1. PMX input
2. Printed output
3. MIDI output


Here are my 2 bits to the `common usage' regarding printed
output:
  1) it's completely nonstandardized, even among
 `professional' editors,
  2) to my experience, in the full scores used by
 (professional) conductors, the notation of transposing
 instruments is usually NOT concert pitch, but the
 notation as read by the instrumentalists (C for a B
 clarinet in a concert pitch B), whereas in pocket scores
 and scores for amateur use, you often find concert pitch
 only, troughout.

 In tonal music, one can usually find out which is the case
 by looking at the key signatures, a clue unfortunately
 missing in most contemporary works,

  3) an absolutely stupefying example is in a wind quartet
 (flute, oboe, clarinet in B, bassoon) by Boris Blacher,
 editor Bote  Bock: in the (pocket) score, you find the
 clarinet denoted in its own B pitch (i.e. NOT concert pitch),
 but in the flute part, the clue notes of the clarinet are
 denoted in concert pitch!! With keys absent, it takes
 some detective sleuthing to find out what's going on
 (apparently the editor considers the reader of the score
 a professional, whereas a flutist is considered a
 non-wood-instrumentalist  ... well  ... ).


Summing all this up, my conclusion for PMX is:

  a) with a score fully in concert pitch, there is no issue,
  b) if the PMX writer aims for practical use, she should take
 advantage of the new K feature BOTH in the score and the
 parts (for the transposing instruments). Although it's of
 course possible to arrange things differently in the
 score and the (transposing) parts, it's NOT advisable,
 for reason c),
  c) in all cases, the MIDI output should give everything as
 it sounds. That, IMHO, is an absolute MUST! How easy that
 is to implement depends on the MIDI implementation from
 the PMX source or the resulting TeX source -- Don !!??

 But in any case, again IMHO, implementing concert pitch in
 the score and the transposing pitch(es) in the part(s) is
 a luxury that isn't worth Dons time.

Don: I shall describe the rules in my tutorial according to
 PMX 2.610, i.e. as is, hoping that nobody will in the
 meantime find a bug in that version!

ccn.
--
..

  Prof.Dr. Cornelius C. Noack
  Inst. f. Theor. Physik FB 1
  Universitat Bremen   Phone: +49 (421) 218-62031
  Otto-Hahn-Allee   Fax  :  -4869
  D - 28334  Bremen home : +49 (421)  34 22 36
Fax:  346 7872
  E-mail: noack at itp.uni-bremen.de   or   ccnoack at mailaps.org
  WWW-page: www.itp.uni-bremen.de/~noack
..
---
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 news: Instrument-wise transposition

2011-06-02 Thread Luigi Cataldi

Don Simons wrote:

There's a new beta version 2.610 of PMX that has the ability to transpose
one or several selected instruments.
  
A very important improvement! I'm very glad to you, Don. I've tested it 
with wine and it works well, but I cannot compile the sources for linux 
with f2c.


I've changed to the getarg lines and compiled with the command 'f2c 
pmxab.f -Nx400 -Nn802' but it doesn't works.


I need some help!

Luigi

My informations:

s.o.: debian lenny 5.0.8 on kernel linux 2.6.26-2-amd64
compiler: f2c (Fortran to C Translator) version 20061008

Here is my output.

f2c pmxab.f -Nx400 -Nn802

pmxab.f:
  MAIN pmxab:
  accsym:
  addask:
  addblank:
  addfb:
  addmidi:
  addstr:
  adjusteskz:
  askfig:
  backfill:
  beamend:
  beamid:
  beamn1:
  beamstrt:
  BLOCK DATA:
  catspace:
  chax:
  checkdyn:
  chkarp:
  chkimidi:
  chklit:
  chkpm4ac:
  clefsym:
  crdacc:
  crdaccs:
  doacc:
  docrd:
  dodyn:
  dograce:
Warning on line 5219 of pmxab.f: local variable lshft never used
  dopsslur:
  doslur:
  dotmov:
  dotrill:
  endslur:
  errmsg:
  eskb4:
  f1eon:
  feon:
  findbeam:
  findeonk:
  fnote:
  g1etchar:
  g1etnote:
  g1etset:
  g1etx:
  getbuf:
  getchar:
  getdyn:
  getfig:
  getgrace:
  getitransinfo:
  getmidi:
  getnote:
  getorn:
  getpmxmod:
  getset:
  getsquez:
  getx:
  i1fnodur:
  iashft:
  ifnodur:
  ifnolev:
  igetbits:
  igetvarlen:
  isdotted:
  isetvarlen:
  istring:
  lenstr:
  levrn:
  lfmt1:
  linebreakties:
  littex:
  llen:
  log2:
  logbeam:
  m1rec1:
  make1bar:
  make2bar:
  makeabar:
  midievent:
  moveln:
  mrec1:
  ncmid:
  ncmidf:
  newvoice:
  notefq:
  notex:
  ntindex:
  ntrbbb:
  numclef:
  outbar:
  pmxa:
  pmxb:
Warning on line 19094 of pmxab.f: incompatible lengths for common block 
comtrans

  poestats:
  precrd:
  printl:
  putarp:
  putast:
  putcb:
  putfig:
  putorn:
  putshft:
  puttitle:
  putxtn:
  read10:
  readin:
  readmeter:
  readnum:
  setbits:
  setbm2:
  setmac:
  setmeter:
  setupb:
  sortpoe:
  spsslur:
  sslur:
  stop1:
  topfile:
  udfq:
  udqq:
  ulfq:
  upcaseq:
  wgmeter:
  writemidi:
  writesetsign:
Warning on line 23336 of pmxab.f: ignoring text after end.
Error on line 23337 of pmxab.f: Declaration error for  MAIN: external 
name already used

  MAIN:
Warning on line 23348 of pmxab.f: RETURN statement in main or block data
  wsclef:


---
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 news: Instrument-wise transposition

2011-06-02 Thread Don Simons
Hey, Luigi--

Thanks for the report! You wrote

A very important improvement! I'm very glad to you, Don. I've tested it
with wine and it works well, 

So you enjoyed the wine? Maybe a good Chianti?

but I cannot compile the sources for linux
with f2c.
...

One of those inexplicable Windows batch script things happened when I
consolidated all my separate FORTRAN sources into one. (It did the same
thing OK about 200 times and screwed up the 201st). I should consult with
Andre the DOS whiz about it :-) I've manually fixed the source file,
replaced the one in the zip at

http://www.icking-music-archive.org/software/pmx/pmx2610.zip

and confirmed at least that I can compile the single source file with
gfortran.

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