lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

noteedit:multiple voices per staff


From: Joerg Anders
Subject: noteedit:multiple voices per staff
Date: Mon, 17 Sep 2001 18:42:02 +0200 (CEST)

noteedit-1.14.3 is available:

  http://rnvs.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html

New features:
=============

  - multiple voices per staff (see/hear: example10.not); 
  - export of variable length trills to LilyPond
       (requires LilyPond > 1.5.1); 
  - export of triplets with length ratio 2:1 to PMX 
  - score information (author, title, ...) 
  - transpose of ranges/groups of staff 
  - change clef 
  - multilingual (see below) 
  - compilation with some wrong installed LEXs on some Linux distributions 
possible

Thanks to Erik Sigra <address@hidden >
------------------------------------

He made some changes which make noteedit more KDE conform. Among them: 
  - multilingual features. Thus, noteedit now has a: 
     o Swedish version (translation by Erik Sigra, please contact 
address@hidden for comments) 
     o German version (translation by Erik Sigra/J.Anders, please contact 
address@hidden for comments) 
  - The configuration is saved in $HOME/.kde2/share/config/noteeditrc. This 
obsoletes noteedit.cfg 
  - configuration of general appearance (background color, staff color, ...); 
  - autosave with configurable autosave interval; 
  - load last processed file (configurable) 

Aspects of exportation/working of multiple voices per staff
--------------------------------------------------

      First of all: Please read the documentation:
      
        
http://rnvs.informatik.tu-chemnitz.de/~jan/noteedit/doc/docu.html#mulvoices
      
      The multiple voice interface is a logical problem because it means to 
insert
      a note/or rest somewhere where already a note sounds. The trick is: How 
can the
      user determine the start time?


LilyPond
-------

LilyPond is best prepared for multiple voices per staff. But do not
forget the keep stem dir. checkbox! Otherwise LilyPond applies the
default stem rules which gives bad results.

MusiXTeX
-------

Paradox: Although MusiXTeX has now special syntax constructs for multiple
voices per staff you can export as many voices as you want
to MusiXTeX because many MusiXTeX commands rather describe a (turtle) graphic 
than music.

But the multiple voices per staff cause a new export error: Too many beams!
MusiXTeX allows as many beams as staffs. So, if you
have only one voice per staff there are always enough beams.
But with multiple voices per staff theoretically all available beams can be in
first staff. Thus, no beam rests for the other staffs.

PMX
---

PMX allows 2 voices per staff (There are some tricks to achieve more.
But no systematical syntax constructions which are successfull in
all cases.). Noteedit warns you and omits the supernumerary voices.

MUP
---

MUP can process up to 3 voices per staff. But it hats stem statements if a staff
has multiples voices. But Noteedit always produces stem
statements to correctly restore the score. This causes tons of warnings during
MUP processing. Ignore them all! MUP in turn will ignore all
stem statements.

If a staff has more than 3 voices Noteedit "extends" the MUP syntax.
Of course, the result is not MUP-able. Noteedit warns you in this case. 

other features:
==============

   - insertion/deletion/modification of notes, rests, dotted notes/rests,
     tied notes, slured notes, clefs with/without shift, time signatures,
     key signatures, volume signatures, tempo signatures, triplets, repeat
     groups with/without special ending and instrument changes on different
     staffs;
   - stem up/down
   - zoom
   - building chords;
   - trills;
   - (de-)crescendo
   - fermata;
   - forzato, portato, strong pizzicato, sforzando;
   - building groups of beamed notes;
   - playing on /dev/sequencer (if correctly configured) whereby:
        o giving each staff a different voice;
        o giving each staff a different channel;
        o giving each staff a different reverbation and chorus;
        o highlighting the played notes;
        o muting staffs;
   - lyrics
   - export MusiXTeX;
   - export PMX;
   - export MIDI;
   - import MIDI;
   - read from MIDI keyboard;
   - Application of MIDI event filters to eliminate
     some dirty effects (especially on human played MIDI files);
   - record from MIDI keyboard;
   - saving an restoring the files. The fileformat is similarily to the
     format of the music publication program (MUP). So you if you are a MUP
     user you have the possibility to convert the files into MIDI and
     Postscript. But this is no longer necessary because noteedit can export
     MusiXTeX, PMX and MIDI.

-- 
J.Anders, Chemnitz, GERMANY (address@hidden)
-- 
J.Anders, Chemnitz, GERMANY (address@hidden)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]