# The &noteedit; Handbook

Jörg
Anders
Professur Rechnernetz u. verteilte Systeme , TU-Chemnitz

    j.anders@informatik.tu-chemnitz.de

Christian
Fasshauer

    mseacf@gmx.net

Erik
Sigra

    sigra@home.se

David
Faure

    david@mandrakesoft.com

Matt
Gerassimoff

    mgeras@telocity.com

Leon
Vinken

    leon.vinken@hetnet.nl

Pete
Goodliffe
TSE3 sequencer library

    pete.goodliffe@pace.co.uk

2001
Jörg Anders

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

2002-04-08
2.5.0

&noteedit; is a score editor for &kde;

KDE
&noteedit;
Qt
music
editor
notes
MuxiXTeX
LilyPond
PMX
MUP
keyboard
score
MIDI
libkmidi
TSE3

## Using &noteedit;

### Starting &noteedit;

This chapter describes the use of &noteedit; for editing notes.

&noteedit; may be started by one of several ways as described below.

- You may start &noteedit; by selecting it from the Music submenu of the panel.

- You may start &noteedit; by entering the following at the command prompt:

  % `noteedit` &

- The mini command line (invoked with Alt F2) may also be used to start &noteedit;

Once &noteedit; starts, you will see a window like the following: &noteedit; Mainwindow

### Insertion

#### Inserting notes

Choose a note length on tool bar ()! Choose dotted (), double dot () tied () staccato () sforzato (), portato (), strong pizzicato (), sforzando () fermata (), arpeggio (), pedal on (), or pedal off () as needed.

`Only if you want to create a visible accidental:` Choose sharp (), flat (), double sharp (), double flat () or natural ()!

Press &LMB; at note position!

Alternatively you can activate the keyboard insertion mode by pressing the keyboard insert button (). In this case you can choose the pitch by cursor Up/Down keys and the insertion position by cursor Left/Right keys. To insert a note press Enter!

`only with TSE3` Alternatively you can specify the pitch by a MIDI keyboard connected to your sound card. If you press the black keyboard button () you can hear the notes played on MIDI keyboard. If you press the red keyboard button () the pitch is determined by the MIDI keyboard.

Another possibility is to use the computer keyboard instead of a MIDI keyboard:

- `C` means pitch C

- `D` means pitch D

- `E` means pitch E

- ...

You can redefine the case because all keys are configurable

If you insert notes at the end &noteedit; will insert bars according the current time signature. (configurable)

Normally &noteedit; chooses the stem direction automatically. You can force a certain stem direction by pressing the stem Up/Down buttons ().

MUP users! See also the mixed beam problem!

Normally the dot and accidental buttons turn off after insertion. Use the glue button() to change this behaviour.

#### Problems with double whole notes

Although the double whole note is called ``breve`` in (almost) all music typesetters (except PMX, here it is called '9') the representation differs:

- In MUP, LilyPond and ABC music it looks like a whole note with 2 additional lines:

- In MusiXTeX and PMX it is a small rectangle: and

- MusiXTeX offers the whole note with 2 additional lines, too.

To unify the representation I decided for the whole note with 2 additional lines: . This can be exported to MusiXTeX, MUP, LilyPond and ABC music. Thus, only PMX shows the small rectangle: .

#### Grace notes

&noteedit; offers 3 types of graces notes:

- 8th grace:

- 16th grace

- stroken grace:

All graces are stem up.

During playback there is no difference between these 3 types. `Please note!` Grace notes are conflicting things: They do not contribute to measure length. On the other hand a certain amount of time is needed to play them. This time must be taken from other notes. Thus, if you insert - say - 20 grace notes between two 8th you cannot expect the playback really works! Problems also occur if you place some graces without a main note.

Please avoid leading graces! Leading graces have a negative start time. You'll never hear them. Insert an empty measure instead!

#### Problems exporting graces notes

`MusiXTeX` MusiXTeX accepts the graces so as written on score: with/without beam, with/without slur, even beamed stroken graces.

`LilyPond` LilyPond changes the beam status reasonably. Version 1.4.x cannot deal with slurs in grace notes. &noteedit; will warn you.

`ABC music` changes the beam status reasonably.

`PMX` PMX changes the slur and beam status reasonably.

`MUP` MUP hates beam statements in grace notes. It sets the beams reasonably. So, if you are a MUP user never produce grace notes with beams! Furthermore, MUP cannot deal with graces after. &noteedit; will warn you. Furthermore: MUP has no means to describe more than one slurred grace note. &noteedit; "extends" the MUP syntax in this case. Of course, the result is not MUP-able. &noteedit; will warn you!

#### Drum notes

&noteedit; offers 5 different types of drum notes. Choose one of them on drum toolbar (). If you can't see this toolbar then select it on ``View`` menu. `Note!` &noteedit; supports 2 different kinds of drum clefs. (see Insert Clef)

To produce audible drum notes during playback set the staff channel to drum channel (channel 10 on most sound cards).

Problems with exportation of drum notes

`MusiXTeX`: All 5 drum notes are supported in MusiXTeX.

`LilyPond`: First of all: I was told my drum exportation doesn't use all LilyPond features. Perhaps a LilyPond guru can review the &noteedit; LilyPond output and send me a mail what to to.

The drum notes export works but with some side effects. All notes in a chord appear with the same drum note type. Only 3 of the 5 types are supported. &noteedit; will warn you.

`ABC music` cannot deal with drum notes. &noteedit; will warn you.

`PMX`: Drum notes are not supported in PMX. &noteedit; will warn you.

`MUP`: The MUP compatibility ends here. MUP doesn't support drum notes. &noteedit; "extends" the MUP syntax to correctly restore the score. &noteedit; will warn you, because (of course) the result isn't MUP-able.

#### Inserting rests

Choose a rest length on tool bar ()! Choose dotted () or hidden ( / see multiple voices) if you wish.

Press &RMB; at rest position!

Alternatively you can activate the keyboard insertion mode by pressing the keyboard insert button (). In this case you can determine the insertion position by cursor Left/Right keys. To insert a rest press Space!

#### Multi rests

``Insert --> multirest ...`` ... choose the length of multi rest

`Note!` Some restrictions apply to multi rests in MUP and PMX:

- MUP: a multi rest must appear in every staff and it must be of the same length. If this isn't the case &noteedit; divides the multi rest in a sequence of "normal" rests. `That means:` If &noteedit; restores such a score the multi rest is changed against a series of "normal" rests. &noteedit; will warn you in this case.

- PMX: PMX doesn't accept multi rests if the score has more than one line.

#### Insert Clef

Insert Clef ... choose Clef with or without octave shift

If you are not sure which octave shift choose a clef without octave shift.

Press &LMB; at insertion position.

Likewise you can choose one of the 2 drum clefs. I introduced a 2nd drum clef with an arrow downward to determine MIDI mapping. The drum clef with arrow downward maps the notes like the bass clef. Of course, this 2nd drum clef is exported to MusiXTeX and LilyPond as "normal" drum clef.

The drum clef is not exported to PMX, MUP and ABC music.

MUP cannot deal with clefs in the middle of a bar. (i.e. there is a trick but this is too complicated for &noteedit;).

#### Inserting key signatures, time signatures

Insert Key signature... ... choose key !

Insert Time signature... ... choose signature !

Press &LMB; at insertion position.

The time signature (except the first time signature) must occur immediately after a bar. Maybe the playback works if you don't follow this restriction. But (re-)storing such files can give indefinite results.

`MUP users!` If you place a key signature (except the first key signature) not immediately after a bar MUP won't work! &noteedit; will warn you!. MUP cannot deal with key signatures in the middle of a bar. (i.e. there is a trick but this is too complicated for &noteedit;).

#### Volume Change

To change the volume during playback place a volume change at the appropriate position:

Insert Volume signature... (Choose a volume and a volume sign)

Press &LMB; at insertion position. The name of the volume sign has no influence during playback.

#### Tempo Signature

To change the playback tempo place a tempo signature at the appropriate position:

Insert Tempo signature... (Choose a tempo)

Press &LMB; at insertion position. If you want to give the whole part an unique tempo place the tempo signature before the first note.

`Remark:` Although the tempo signature can be attached to a certain staff the tempo signature influences all other staves.

#### Program (instrument) Change

The change of the staff's voice is called a "MIDI program change". You can achieve this by placing a program change marker at the appropriate position:

Insert Voice change... (Choose a program (instrument))

Press &LMB; at insertion position.

#### Insert a note to a chord

Choose tied () if needed. Activate one of the note buttons. Press &LMB; near the chord. The length is the same as the length of the other notes of the chord.

Alternatively you can activate the keyboard insertion mode by pressing the keyboard insert button (). In this case you can add a note to a chord by pressing Crtl+Enter.

#### Insert a bar

Usually &noteedit; inserts bars automatically if you append a note (configurable).

If you want to insert bars "by hand" then select a music element with &LMB;! Press Tab! The bar appears behind the element.

Or press | The bar will be inserted at mouse position.

#### Insert a double bar

To insert a double bar choose:

Insert DoubleBar

Press &LMB; at insertion position

#### Repeat

You can define a part to be repeated by setting a repeat open () and repeat close bar () or repeat both ():

Insert RepeatOpen.

Insert RepeatClose

Insert RepeatOpenClose

To define alternative parts during repeat use special ending 1 () and special ending 2 ():

Insert SpecialEnding1

Insert SpecialEnding2

Press &LMB; at insertion position.

Set the repeat and special ending signs in every staff! Otherwise the replay behaviour is undefined.

#### Multi repeats

Normally the part is repeated 2 times. If you whish more repeats you can specify the repeat count: Select a repeat close symbol and choose:

Edit Set N time repeat

A menu pops up. Choose a repeat count and press `Ok`!

The current version exports the signature only to MUP!

Set the repeat and special ending signs in every staff! In particular specify the identical repeat count in every staff! Otherwise the replay behaviour is undefined.

#### Lyrics

You can attach up to 5 lines of lyrics to each staff.

Staff Lyrics... You can either use the lyrics editor or import the lyrics from a file. In either case the lyrics should look like:(see: `lyrics/whiskey[1-5].txt` or `lyrics/water[12].txt`):

            The water is wide, I can- not cross o'er
            and nei- ther have I wings to fly.
            Build me a boat that can car- ry two
            a- and both shall row my love and I.
            O down in the mea- dows the o- ther day
            a- gath'- ring flow'rs both fine and gay,  -
            a- gath'- ring flow'rs bo- oth red and blue,
            I lit- tle thought wha- at love could do.
            2.)I leaned my

&noteedit; interprets all blanks as hyphenation symbol. Select the appropriate staff and choose:

Staff Lyrics... Import choose a line number and a text file

You can repeat this as many times as you want till the lyrics are correct. Likewise you can change the staff geometry to get enough place for the lyrics. You can remove the lyrics from current staff by clearing the board.

See `example4.not` for a lyrics example with 5 lines!

Please note:

- The '-' sign behind gay,! If you want a note without lyrics choose a non-blank character.

- Instead of the '-' sign you can use the asterix ('*'). In contrast to '-' sign the asterix isn't printed on score. Thus, it only appears in lyrics dialog.

- &noteedit; assumes a isolatin-1 coding. So you can use German umlauts (ä, ö, ü, ...). They are correctly translated into MusiXTeX. But be warned: MUP will fail if you use non-ascii characters!

- The lyrics are exported into MusiXTeX, MIDI file, PMX file (and implicitly to MUP). The PMX lyrics export has some drawbacks. Please read the PMX export discussion page! There are some MIDI players which show the lyrics during playback (the AWE MIDI player tkmidi by Takashi Iwai, kmid from KDE «but unfortunately the whole text in one line», timidity «but unfortunately the whole text at the beginning»)

- If there are repeat signs and more than 1 lyrics line &noteedit; attaches the second lyrics line to the repeated part in MIDI file.

- Avoid empty lyrics lines. Fill them from 1 ... 5!

- If you want assign several syllables to one note use `<...>` parenthesis: `Byl jsem <v le-> su.`(Czech)

#### Working with guitar chord diagrams and chords

> Many thanks to Mikhail Yakshin GreyCat@users.sourceforge.net. I used about 2000 lines from his kguitar project (). Note! kguitar is still under development. So excuse some small problems. For instance: If you can't find your preferred chord diagram for a certain chord please set the fingers by hand!

To insert a chord popup the chord dialog:

Insert Chord...

Choose a base, a mode, and a modification. (The bass field doesn't work, yet!). The chord window shows some guitar diagrams to play this chord. If you can't find your preferred guitar chord diagram you can:

- change from ``Root`` to ``Inv1 #1``, ``Inv #2`` ...

- change from ``Usual`` to ``Rare`` or ``All``.

If nothing helps then select a guitar chord diagram closest to your intentions and set the fingers in finger window by hand!

The ``show diagram`` checkbox determins whether only the chord name or the whole diagram is printed.

Select a chord name and press ``Ok``.

Select a note or rest with &LMB;. The chord name and the guitar chord diagram (if selected) is attached.

To change the chord activate the edit mode () and select the appropriate note or rest with &LMB;. The chord dialog pops up. Change the chord and press ``Ok``!

To remove the chord activate the edit mode () and select the appropriate note or rest with &LMB;. The chord dialog pops up. Press ``Remove Chord``!

If you expect a different set of chord names and/or modification symbols configure the chord section with configuration dialog.

##### Problems exporting chord diagrams

- `MUP` can deal with chord names and chord diagrams. But it expects a chord diagram dictionary at top of file. Actually this is no problem. But if you attach 2 different chord diagrams for the same chord name there is no possibility to to distinguish the 2 forms. To give every chord diagram an unique name &noteedit; adds some underscores to the chord name. So be not surprised if you named a chord C7 and _C7 is printed. MUP cannot deal with a mix of some chords with chord diagram and some chords without chord diagram. MUP cannot deal with barre.

- `MusiXTeX` has an additional package called MusiXGui. This allows to annotate guitar chord diagrams and chord names. It works but unfortunately there is no possibility to add a fret information. So, if the fret is not equal 1 NoteEdit appends the fret information to the chord name. MusiXTeX/MusiXGui can only deal with full barre.

- `LilyPond` cannot deal with guitar chord diagrams. Actually it has a special feature for chord name annotation. But this is unusable for &noteedit; export because it tries reverse mapping from pitch combination to chord name. Thus, &noteedit; exports the chord names as ordinary uptext.

- `ABC music` cannot deal with guitar chord diagrams. Thus, &noteedit; only exports the chord names.

- `PMX` can neither deal with chord names nor with guitar cord diagrams. Thus, &noteedit; omits the information.

#### Insert a new staff

Staff New

#### Trills

Insert Line... choose a trill symbol

Select a note with &LMB;. The trill is attached.

To remove a trill activate the edit mode () and select the chord. Use the `enable` checkbox!

Use the slider to control the length of the trill. `Note!` &noteedit; plays the trill and exports the trill to MIDI file. But it uses the post Mozart method (dcdcdcdcdcdc...)

#### (De-)Crescendo

Insert Line... choose the dynamic symbol

Select a note with &LMB;. The dynamic is attached.

Use the slider to control the length of the (de-)crescendo. To switch between crescendo and decrescendo use the turn checkbox.

To remove a (de-)crescendo activate the edit mode () and select the appropriate note or rest with &LMB;. Use the enable checkbox!

To produce a audible (de-)crescendo place two Volume Changes with different volume to the left and to the right of the (de-)crescendo symbol.

Some soundcards do not support fade-in/fade-out. So if you get unexpected results during (de-)crescendo playback use the `--without-fadein` configure option! The (de-)crescendo is further audible if you use relatively short notes. But the volume of a series of tied and/or relatively long notes (halfs/wholes) will remain at start volume value.

`Note further!` The (de-)crescendo will cause some problems in MusiXTeX and PMX if the (de-)crescendo crosses the line break :-(

#### Octaviation (va lines)

Insert Line... choose the octaviation symbol

Select a note with &LMB;. The octaviation is attached.

Use the slider to control the length of the octaviation line.

To remove a octaviation activate the edit mode () and select the appropriate note or rest with &LMB;. Use the enable checkbox!

The octaviation is not supported by ABC music. &noteedit; will warn you!

#### Segno, dal Segno ...

To insert Segno items choose:

Insert Segno... ... choose Segno, dal Segno, dal Segno al Fine, dal Segno al Coda, Fine or Coda

Press &LMB; at insertion position

Set the signs in every staff! Otherwise the replay behaviour is undefined. Furthermore, it is your responsibiltity to place the signs in a reasonable manner.

#### Ritardando, Accelerando

To insert ritardando choose:

Insert Ritardando

To insert accelerando choose:

Insert Accelerando

Press &LMB; at insertion position

To produce a audible ritardando(accelerando) place two tempo signatures with different value to the left and to the right of the ritardando(accelerando) symbol. &noteedit; assumes the begin of the ritardando(accelerando) at the left tempo signature and the end of the ritardando(accelerando) at the right tempo signature

### Modification

#### Selection

- Activate the selector () or the edit mode () and click element with &LMB;!

- If there is a selected element: User back/forward cursor keys.

Use scroll bar if needed!

#### Goto Measure

Edit Goto (Choose a measure number)

Alternatively, you can use the horizontal scroll bar or the wheel mouse (if correctly configured in X11)

#### Change pitch

Select a note! Press up/down cursor keys!

This does not work in keyboard insertion mode!

#### Change length, dotted, tied, flat, beamed, sharp, natural

Change into edit mode by pressing edit button ()! In edit mode there is a special selection policy. If you select a note or rest the buttons reflect the state of the note/rest. If you change the button state the note/rest is changed according to the state of the buttons.

#### Change staff position

Staff Move ... choose a position

#### Deleting elements

Select an element! Press backspace! The element will be deleted.

Likewise you can use the Del key. In this case the next note is selected after deletion.

#### Deleting a note from a chord

Select the chord! Press ctrl and the &LMB; near the note to be deleted!

Alternatively you can activate the keyboard insertion mode by pressing the keyboard insert button (). In this mode you can delete a note from a chord by selecting a chord, placing the cursor at the line of the note to be deleted and pressing Ctrl+Backspace!

#### Modification of clefs, time signatures, key signatures

You can't modify these elements in current version. The only possibility is: deleting and re-insertion.

#### Block instructions

Make sure the selector () is activated! You can mark a part of a staff as block by clicking and holding &LMB; and moving the mouse. The marked part is highlighted.

You can mark the whole staff by double click on staff

If a block is selected you can:

- delete the block with backspace key;

- insert the block at some other position by clicking &MMB; at this position.

`Note!` There are some complicated situations which &noteedit; cannot solve. For instance: If you mark a part from a staff with treble clef and insert this part into another staff with bass clef the result is indefinable.

If you work with multiple voices per staff the meaning of the block instruction depends on voice counter. If it displays A a block instruction influences all voices on staff. Otherwise only the current voice is processed.

`Note!` If the voice counter displays A and the destination staff has less voices than the source staff the block copy fails.

A first voice can only be copied to a first voice.

#### Beamed Notes

Mark a block of notes to be beamed! Press the beam button ()!

#### Triplets

Mark a block of notes and/or rest which shall built the triplet! Press the triplet button ()!

`Note:` &noteedit; cannot make a triplet from arbitrary notes! The sum must be divisible by 3.

#### N-tuplets

With &noteedit; you can build N-tuplets, whereby N in {2,3,4,5,6,7,8,9,10}. Mark a block of notes and/or rest which shall built the N-tuplet! Select Insert Tuplet... and define the number of notes and their playtime! The playtime must be expressed in number of notes of slider above. For instance: If you want 7 8th shall be as long as a half note then define:

`Note:` &noteedit; cannot make a N-tuplet from arbitrary notes! The sum of 128ths must be divisible by N.

##### Problems with N-tuplet exportation

- LilyPond is best prepared for all kind of N-tuplets

- ABC music is best prepared for all kind of N-tuplets if N < 10

- MusiXTeX is prepared for triplets. It uses the `uptrio` statement which produces a bracket with a small "3" in the middle. For N-tuplets it uses the `xtuplet` statement which produces the number without a bracket. If the N-tuplet is beamed it looks like an N-Tuplet. If not it looks like some notes with a number above. It is your resposibility to mark the N-tuplet for instance with a slur (or so ...)

- PMX cannot deal with N-tuplets ending with a rest. Actually all N-tuplet members must be of the same length, besides some notes are as half as long as the others. PMX cannot deal with an N-tuplet who's real playtime cannot be expressed with one (eventually dotted) note.

- MUP cannot deal with an N-tuplet who's real playtime cannot be expressed with one (eventually dotted) note.

#### Slurs

To connect some notes with a slur mark a block of notes and press the slur button (). `Note!` The slur has no influence during replay! To break a slur change into edit mode, select the first note of a slur and de-activate the slur button ().

MUP - users! The length of a slur is no longer restricted. &noteedit; now uses a MUP conform description of slurs over more than 1 note. This holds for 1st and 2nd voice. In other voices slurs over more than 1 note cannot be expressed. So if you plan to MUP the file do note create such slurs in 3rd, 4th ... voice!

#### Multistaff block instruction

Sometimes it is necessary to copy or delete a block of one staff and the parts of some other staves which sound at the same time. Therefore &noteedit; offers multistaff block instructions. To initiate a multistaff block instruction:

1. Mark a block as described in Block instructions;

2. Activate the multistaff block mode: Edit MultiStaff (choose the staves ...);

3. Do a block instruction like block delete or block copy;

The order is important! Note: The multistaff behavior rests valid as long as the block selection is valid. So you can do the multistaff block copy as many times as you want.

In principle you can copy/paste between different windows/scores. But this can cause unexpected results if the count of staves differs.

The block instructions can be undone. But it is undone staff by staff. So if you deleted notes on 6 staves you need 6 undos to undo the multistaff block instruction.

#### Autobar

Edit AutoBar

If the staff has an anacrusis then set the first bar. &noteedit; begins placing the bars at this first bar.

Choose the staves to be influenced!

This should produce the bar lines.

#### Autobeam

Edit Autobeam

(choose the count of notes to be beamed and if rests be should included and the staves which should be influenced!)

&noteedit; doesn't care about rests inside/not inside beams. But MUP cannot deal with rests inside beams. So if you plan to use the file as MUP input always interdict rests inside beams!

#### Cleanup rests

Imagine after MIDI import you got a drum track like this: This is nonsense! The drummer played quarters. But because he hit the drums very short the MIDI exporter seems to hear these complicated rests. The cleanup rests feature allows you to delete a group of rests whose length is shorter than a certain amount. Of course, the rests are not really deleted. Instead of this their time is added to the note before.

For instance: If you choose quarter in the above situation the result looks like: If there is a selected region the function influences only the selected region.

#### Merge MIDI tracks

There are some cases where it is advantageous to have the possibilty to merge some MIDI tracks before the TSE3 TSE3 --> Score operation. For instance: There are some piano MIDI files which have up to 5(!) tracks. &noteedit; in turn possibly splits them further into a bass and a treble clef staff. The result is not playable. Thus, it is a good idea to merge all piano tracks into one track.

To assist this &noteedit; offers an Information feature:

TSE3 Information

To merge some tracks do:

TSE3 TSE3 --> Merge select the staves to be merged ...

#### Undo

You can undo your last operations by pressing the undo button ()

`Note!` You cannot undo operations which deal with the staves itself (delete staff, insert staff, NEW). These operations invalidate the whole undo history.

#### Redo

You can undo your last undo by pressing the redo button ()

#### Deleting a staff

Select the staff to be deleted! Staff Delete

#### Set staff properties

To set the staff properties choose:

Staff Staff properties...

#### Staff name

You can give each staff a name. The name is exported into MusiXTeX, LilyPond, PMX and ABC music. Furthermore it is shown at the left side of the note page. You can turn off this by View Show staff names

#### Setting staff geometry

You can change the overlength and underlength of a staff. Furthermore you can determine the position of a possible lyrics line.

#### Set a channel

You should give every staff a different channel. `Attention!` On most sound cards channel 10 is reserved for drum track!

#### Select staff volume

You can set the volume in a range of 0...127. (see also: Volume Change)

#### Select a voice

`Attention!` &noteedit; assumes the general MIDI table. This is the case for most sound cards. (see also: Program Change)

#### Set stereo position

You can set the stereo position of the staff in a range of 0...127

#### Set reverberation

You can set the reverberation of the staff in a range of 0...127 Whether you can hear this effect depends on your soundcard. Hear the beginning of `example2.not` on AWE 64/ 24 MB RAM and soundfont `8mbgmsfx.sf2`: example2.mp3 (625 Kbyte)

#### Set chorus

You can set the chorus of the staff in a range of 0...127. The chorus is an effect which produces a group of instruments instead of one single instrument.

Whether you can hear this effect depends on your soundcard. Hear the beginning of `example2.not` on AWE 64/ 24 MB RAM and soundfont `8mbgmsfx.sf2`: example2.mp3 (625 Kbyte)

#### Play transposed

If you place an instrument on score which isn't in C tuning you have a problem during replay. Therefore &noteedit; offers the possibility to specify a staff should be played with an offset. Use the play transposed slider to determine the offset in semitones

### Tools

#### Score layout

&noteedit; offers a board to determine the score layout: braces (piano staff), brackets (staff groups) and continued/discontinued bar rules.

&noteedit; does its best to export the score layout. But depending on your typesetting system the score layout possibly changes (see below).

File Scrore layout...

This pops up the following menu:

By dragging and holding the &LMB; you can select a group of staffs. If you click on one of the 6 function buttons you can create/remove brackets (staff groups) or a braces (piano scores). The `continue bar` and `discontinue bar` buttons determine the bar rule policy.

#### Problems exporting staff layout

`MusiXTeX` MusiXTeX actually accepts either completely continued or completely discontinued bar rules. If you specify a mix of partial continued and partial discontinued bar rules &noteedit; produces some statements of the `musixdbr.tex` package by Rainer Dunker. &noteedit; produces a warning and gives advice to install this package. Otherwise MusiXTeX will fail.

`PMX` PMX is a preprocessor to MusiXTeX and therefore the same problems apply.

`ABC music` ABC music cannot deal with nested braces in brackets. &noteedit; will warn you.

`LilyPond` LilyPond can deal with braces and brackets. It changes the staff rules according to some LilyPond inherent rules. I was told it is possible to break these rules. But I assume they are there for good reasons. &noteedit; will warn you if a LilyPond rule will change the staff rule policy.

`MUP` MUP has no limitations.

#### Transpose

To transpose the selected staff choose:

Tools Transpose... select the count of semitones

It is your responsibility to set a new key signature! Use the reduce accidentals tool to change sharps against flats if necessary.

If you want to transpose only a part of the staff then mark the appropriate part before!

If you want to transpose a group of staffs then select them before:

Edit MultiStaff

The chords names are transposed if there is no chord diagram attached.

#### Change clef

Especially after MIDI import it is sometimes necessary to change the clef which is chosen by &noteedit;. To do this choose:

Tools Change clef... Choose the new clef!

If you want to change the clef of only a part of the staff then mark the appropriate part before!

`Note!` The marked range should begin with a clef! &noteedit; stops changing the chords/notes if a new clef appears.

#### Reduce Accidentals

Imagine the following situation:

This can happen especially after transpose or recording from MIDI keyboard. You wanted to play in A flat Major but &noteedit; used sharp notes. To solve this &noteedit; offers an appropriate tool:

Tools Reduce accidentals...

This changes the lines and accidentals so that the number of accidentals decreases. In case above the this would result in:

#### Combine chords

Imagine the following situation: This can happen especially after autobar function. In this case the `Combine chords` tool is useful:

Tools Collect Notes ...

#### Change Accidentals

Independent of the key signature you can change all accidentals of the current staff to sharp:

Tools Set all to sharp

or to flat:

Tools Set all to flat

If there is a selected region the operation only effects this region.

### View

#### Creating Windows

You can open up as many windows you want ( Window New ). This allows you to copy/paste elements between different scores.

`Attention!` In principle you can use the multistaff copy. But this can cause unexpected results if the count of staves differs.

#### Zoom

You can choose the zoom factor by the zoom selection (). Furthermore you can set your preferred zoom value in config file.

Alternatively you can zoom using the `Zoom in/out` buttons. ()

#### Show/Hide bar numbers staff names and auxiliary insert lines

You can choose whether &noteedit; shall show the bar numbers or not by using the checkboxes on: View menu. The same holds for the auxiliary insert lines and staff names.

#### Show/Hide staff context

You can decide whether &noteedit; shall show the context (actual clef and key signature) during replay at the left hand side: View Show staff context

### Working with multiple voices per staff (polyphony)

#### Creating multiple voices

To work with voices pop up the voices dialog:

Staff Voices...

To create a voice press `Create voice` button. Then you should choose the Y-position of the rests in voice to make it possible to associate the rests to voices:

After that you should choose the preferred stem direction of that voice:

- stem up: All notes have stems upward if no otherwise stated;

- stem auto: &noteedit; determines the stem direction depending on line if no otherwise stated;

- stem down: All notes have stems downward if no otherwise stated;

`Note!` You can always overwrite the stem direction using the stem Up/Down buttons ().

#### How to work with multiple voices per staff

First of all: There is a first voice which has priority over all other voices. That means:

- You cannot delete the first voice.

- The only elements which can occur in other voices are notes (chords) and rests.

Before inserting something in other voices you should finish insertion in first voice (at least till measure of insertion):

`Note!` There is always a current voice. You can change the current voice by left/right clicking the voice counter:

- --> all voices (the current voice is the first voice)

- --> the current voice is the first voice

- --> the current voice is the 2nd voice

- ...

The current voice is the first voice if the voice counter displays A and if the voice counter displays 1 What's the difference? If the voice counter displays 1 all elements which do not belong to voice 1 are gray. If the voice counter displays A all elements in all voices are shown in black or red. So you can get a better impression of the score. Other differences follow (see below).

Now if you select voice 2 as current voice all elements of voice 1 are in gray:

If you now insert 4 8th somewhere in measure 2 &noteedit; assumes this is the first element in measure and fills the measures before with hidden rests:

You can insert more hidden rests by pressing the hidden rest button (). For instance: If in current example the first 8th shall be one 8th away from bar line, insert a hidden rest of one 8th:

Of course, you could also insert a "normal rest" if you wish. The hidden rests don't appear on Postscript file and they are not shown if the voice counter displays A

You can manipulate only elements in current voice. This holds also for selection.

#### Block instructions with multiples voices per staff

The meaning of block instructions depends on voice counter. If it displays ``A`` a block instruction influences all voices on staff. Otherwise only the current voice is processed.

- If the voice counter displays ``A``: You cannot copy a block to a staff with less voices.

- A block in first voice can only be copied to a first voice.

#### Aspects of exportation of multiple voices per staff

##### LilyPond

LilyPond is best prepared for multiple voices per staff.

##### ABC music

ABC music is best prepared for multiple voices per staff. Sometimes the stem direction isn't optimal.

##### MusiXTeX

Paradox: Although MusiXTeX has no 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 staves.

##### PMX

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

##### MUP

MUP can process up to 3 voices per staff. But it hates 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.

### Playing

#### Set the MIDI device

Settings Configure &noteedit;... ... select a device

#### Play/Muting

If some staves need muting:

Staff Mute staffs... choose staves

Press play button ()! If there is a selected note &noteedit; begins playing at this note. Otherwise it plays from beginning. &noteedit; will highlight the played notes and scroll if necessary.

It is possible to determine the page turn over point

`Attention!` During play some other functions will not work!

#### Stop playing

Press play button () again.

#### Using the aRts MIDI scheduler

From version 0.1.3 on Pete Goodliffe's <pete.goodliffe@pace.co.uk> TSE3 library has an aRts MIDI scheduler. As a result &noteedit; can act as MIDI source for aRts.

If you want to use &noteedit; with aRts MIDI scheduler then make sure the aRts headers (`artsmidi.h`) are installed before you compile TSE3.

Start &noteedit; with:

`noteedit -arts`

Start:

`artscontrol`

View View Midi Manager... On Midi Inputs you should already see the source "TSE3". From Add aRts Synthesis Midi Output menu select some instruments. Connect "TSE3" with one of these instruments and &noteedit; will play this instrument.

The interesting thing here is: With the program artsbuilder you can create your own instruments. Start:

`artsbuilder`

and read the online help. There is a very instructive tutorial which declares how to define a MIDI instrument.

### Configuration

To set general properties choose:

Settings Configure &noteedit; -> Editing

- `allow mixed beams`: &noteedit; produces such beams under circumstances: This is no problem in MusiXTeX and &noteedit; itself. But MUP cannot deal with such kind of beams. Therefore: If you plan to MUP the result disallow such beams!

- `move according key` The value determines what happens if you move a note upward or downward. If checked the semitone is chosen according to the key signature. If not, the semitone is kept.

- With the slider `page turn over` you can determine how many pixels before page end &noteedit; performs page turn over.

- If you insert notes or rests at the end &noteedit; will insert bars according the current time signature. To toggle this feature use the "autom. bar insertion" checkbox.

- Inserting notes or move them up or causes a MIDI echo. To toggle this feature use the "insert echo" checkbox.

- Using the chords dialog you can determine the set of chord names and/or modification symbols

#### Key configuration

With Settings Key configuration you pop up a key configuration dialog. Note! This is made by means of the KDE widget `KKeyDialog`. Unfortunately, the `KKeyDialog` has no knowledge about the keyboard layout. For instance: On German keyboard the '=' sign is in 2nd keyboard layer. Therefore `Shift+Equal` is configured. If the '=' sign isn't in 2nd keyboard layer on your keyboard, please change this to `Equal`.

#### Colors

The colors can be changed under Settings Configure &noteedit; -> Colors

#### MIDI PEDAL COMMANDS

You can enable/disable the usage of MIDI PEDAL COMMANDS during replay: Settings Configure &noteedit; -> General -> useMidiPedal

#### Autosave

You can enable an autosave policy on: Settings Configure &noteedit; -> General

Choose an autosave time interval. &noteedit; makes a backup of the current score in a file whose name is built by appending `.sav` to current filename.

#### Score information

You can attach overall score information (author, title, ...) to the current score:

File Score information

The score information is exported as far as the destination format allows this.

#### Save parameters

Choose:

File Output params...

The selected values are exported into MUP format if the enable box is checked.

#### Configuration file

According to `KDE developer guide` your personal configurations are saved in:

`<KDEHOME>/share/config/noteeditrc`

### (Re-)Storing

#### Saving

If the file has a name try:

CtrlS File Save

otherwise try:

File Save As... ( choose a file name)

As mentioned above the file format is similarly to that of music publication program (MUP). So you if you are MUP user you have the possibility to convert the files into MIDI and Postscript. But MUP is a shareware. So the direct export into MusiXTeX, PMX, LilyPond or ABC music and MIDI is recommended.

#### Restoring/Autoload

CtrlO File Open... ... choose a file name

If AutoLoad is enabled ( Settings Configure &noteedit; --> General) the last processed file is loaded at program start.

### Export MIDI

File Export MIDI... ... choose MIDI file name

See also: working with TSE3

### Export MusiXTeX

File Export MIDI... ... choose parameters and TeX file name

To produce a printable output `please read the` MusiXTeX export discussion page. `It is `not``: `latex` `file`.tex

### Export LilyPond

File Export LilyPond... ... choose parameters and TeX file name

To produce a printable output please read the LilyPond export discussion page.

### Export ABC music

&noteedit; produces code for abcm2ps version 3.x.y

File Export ABC... ... choose parameters and ABC music file name

To produce a printable output `please read the` ABC music export discussion page.

### Export MusicXML

&noteedit; can export MusicXML.

File Export MusicXML... ... choose the MusicXML file name

For an overview of the current MusicXML exporter's limitations please read the MusicXML export discussion page.

### Import MusicXML

&noteedit; can import MusicXML.

File Import MusicXML... ... choose the MusicXML file name

For an overview of the current MusicXML importer's limitations please read the MusicXML import discussion page.

### Export PMX

File Export PMX... ... choose parameters and PMX file name

To produce a printable output `please read the` PMX export discussion page.

### MIDI import

#### Import MIDI

`only with TSE3`

The MIDI import is performed by means of the TSE3 library. During MIDI export a lot of score information gets lost. Therefore the MIDI import generally needs some human intervention. Please read the MIDI import discussion page for more information!

The current version of &noteedit; doesn't recognize triplets. So do not try to import swing music or so. But some classical examples work well. I tried from classical midi archive and Rimsky-Korsakov's Flight of the Bumblebee (looks very lazy). The result looks as if a musician could play this.

See also: working with TSE3

To import do:

TSE3 TSE3 MIDI in. ( ... choose a MIDI file)

This creates an internal TSE3 structure.

Before creating the score from TSE3 Song structure you should apply a MidiEventFilter:

TSE3 Filter dialog...

This window rests on screen until the Dismiss button is pressed. The filter values apply to next ``MIDI --> Score`` action. Estimate the shortest note at the selected staves and choose this as the snap distance. A good idea is also to limit the min/max volume.

If there are a lot of obviously bad ties you should de-activate the Exact Length button. See the MIDI import discussion page for a detailed explanation!

By de-activating the Exact Volume button you can cause &noteedit; compute an average volume of the track. The ``dynamic`` slider determines variance. If the variance is 0 all notes have the average volume. The greater the variance the greater is the divergence of the note's volume depending on their real volume.

If you don't want any volume signature on score either:

- choose Exact Volume and set min and for max volume equally or:

- de-activate Exact Volume and set dynamic to 0

For further information read the MIDI import discussion page!

To create the score from internal TSE3 structure do:

TSE3 TSE3 -->Score

or press the TSE3-->Score button on filter dialog!

Choose the staves which should be imported. If the import is not as expected choose other filter values and import again!

After some seconds you should see the score but without bar lines. If the music has an anacrusis set the first bar line at the selected staves! (If you aren't sure do nothing)

`Tip!` Because the TSE3 Song structure is kept you can repeat the last 2 steps as many times as you want.This way you can import the staves step by step.

Use AutoBar

Use Autobeam

Use Cleanup rests

Use Merge MIDI tracks

##### Record MIDI

`only with TSE3`

First of all: To avoid excessive expectations I strongly recommend reading of the MIDI import discussion page

If you have a MIDI keyboard connected to your soundcard you can play and record the music. To to this:

1. Create a TSE3 Song from score (If you have an empty score then produce an empty Song!)

   TSE3 Create TSE3 song

   This song is played during record!

2. Select a staff!

   &noteedit; ignores all channel information given by your keyboard. The MIDI echo will be on the MIDI channel of the currently selected staff!

3. Press the record button ()! A metronome menu and a filter menu appear. They rest on screen until you press the Dismiss button. On metronome menu choose:

   - the recording tempo;

   - the device the metronome shall play on;

   - a bar and a beat note.

   If you are not sure leave all values unchanged.

   The record tempo doesn't influence the playback tempo!

4. On metronome dialog press Start recording! You should hear a metronome. If not try a different device! The metronome plays an upbeat of 4 quarters. So begin playing on the keyboard with the beginning of the 5th quarter! If the score wasn't empty you should also hear the notes of the other staves.

5. At the end of recording press the record button () again! A warning appears that this overrides the current staff. If you accept the MIDI --> Score transformation begins.

If the import is not as expected choose other filter and select: Staff Import recording or press the Import recording button on filterdialog. This imports the recorded track again.

After that choose autobeamand autobar.

##### Problems with MIDI import

- The current version does not recognize triplets.

### Working with TSE3

`only with TSE3`

Versions >= 0.0.22 of the TSE3 library now support the ALSA sound system (Advanced Linux Sound Architecture project) (Thanks to Pete Goodliffe <pete.goodliffe@pace.co.uk>). &noteedit; uses the TSE3 ALSA MIDI scheduler as favored sound basis. If this doesn't work it tries to create an OSS (Open Sound System) scheduler (the traditional system). In some special cases this can cause problems. You can avoid ALSA by :

Settings Configure &noteedit; -> Sound

Note:

- If you have an ALSA system possibly both MIDI schedulers work. That's because the ALSA system has an OSSemulation. But the emulation doesn't support the read direction. So if you want to read/record from MIDI keyboard and you have an ALSA system, please use the TSE3 ALSA scheduler.

- The TiMidity++ v2.10.2 server works only in ALSA system.

The TSE3 library defines an internal Song structure (see: The TSE3 Song class) and a file format (see: TSE3 Music Description Language (TSE3MDL)). In the future some new TSE3 based projects are expected. Because &noteedit; can produce and read the TSE3 data the data will be interchangeable with these programs.

Use TSE3 TSE3 -->Score to produce the the TSE3 Song structure from score. If you have a TSE3 Song structure you can:

- create a TSE3 file: TSE3 Write TSE3 Song (choose a file name).

- create a MIDI file: TSE3 TSE3 MIDI out (choose a file name). &noteedit; has its own MIDI exporter. But the files produced by TSE3 are smaller because it creates compressed data (for details see: The TSE3 Midi export class).

- play the song for checking the correctness: TSE3 Play TSE3 Song . Note: There is no note highlighting and you can't stop playback in current version.

- reconstruct the score from TSE3 Song: TSE3 TSE3 -->Score . Because the TSE3 Song structure only stores the MIDI relevant data a lot of score information gets lost during TSE3 Song creation. See Import MIDI about how to reconstruct the score.

You have 2 possibilities to create a TSE3 Song structure from file:

- From MIDI file: TSE3 TSE3 MIDI in (See also: Import MIDI)

- From TSE3 file: TSE3 Read TSE3 song

### Quit the program

File Quit

### Shortcuts

Note! All keys are configurable

key | operation
Delete | delete element, new actual is next element
Backspace | delete element, new actual is previous element
Insert | toggle edit mode
1 | whole note
2 | half note
3 | toggle triplet
4 | quarter note
5 | 8th note
6 | 16th note
7 | 32nd note
8 | 64th note
9 | 128th note
. | toggle dotted
~, ` | toggle tied
#, + | sharp
n, = | natural
b, - | flat
Alt + cursor left | Goto start
Alt + cursor right | Goto end
K | toggle keyboard insert mode
C | pitch C
D | pitch D
E | pitch E
F | pitch F
G | pitch G
A | pitch A
B | pitch B

## Credits and License

&noteedit; Copyright 2001 Jörg Anders

This documentation is licensed under the terms of the GNU Free Documentation License.

This program is licensed under the terms of the GNU General Public License.

## Frequently Asked Questions (FAQ)

I wrote a MUP file but &noteedit; cannot read it.

I said &noteedit; uses a `similary` file format as MUP. The files produced by &noteedit; should be readable by MUP. But the contrary way failes in most cases.

Can &noteedit; print the score ?

Not directly! But with the help of some music typesetting programs you can print the score. Read:

- ExportMusixTeX

- MusiXTeX export discussion page

- Export LilyPond

- LilyPond export discussion page

- Export ABC music

- ABC music export discussion page

- Export PMX

- PMX export discussion page

Furthermore the &noteedit; storage format is close to the MUP format. Thus, most &noteedit; files are directly MUP-able

I can't hear any sound! I see the running red notes but there is no sound! What's wrong?

First of all: Try to play a MIDI file with kmid (not (!!!) kmidi). As long as kmid does not produce any sound, &noteedit; (and any other MIDI device based software) will not produce any sound, too! The reason is: Either your soundcard has no hardware MIDI synthesizer or it has a hardware MIDI synthesizer but it is not supported by Linux.

Be not confused if you can play MIDI files on Windows. If your soundcard has no hardware MIDI synthesizer Windows automatically starts a software which converts the MIDI data into WAV (PCM) data in real time. This works if your computer has enough performance.

Such software exists for Linux, too. But it is more complicated because:

- It works only if you have an ALSA system. This is always the case with SuSE Linux. (Other Linuxes I don't know). In any case: You can always change from OSS System to ALSA by compiling the ALSA modules "by hand".

- You have to start this software "by hand".

- These software MIDI sythesizers need a so-called soundfont, a collection of sample tones of every instrument of a virtual orchestra. These soundfonts are copyrighted, i.e. actually nothing for a free system like Linux

But there is a (relatively bulky) way! See The TiMidity server detailed instructions!

If I close &noteedit; I hear a terrible loud sound. What does it mean and how can I avoid it?

Actually this sound shall be played during MusiXTeX export and remember the users with dramatic effort that ``latex` file.`tex`` is incorrect (see next question). Unfortunatly you block the sound device with some other application. Note, this application can be timidity in server mode. In this case the aRts sound server which is responsible for playing this sound playes the sound as soon as the sound device becomes free. And this is the case if you close noteedit.

To avoid the sound dectivate the checkbox at: Settings Configure &noteedit; -> MusixWarn

Why is there such a terrible warning during MuxiXTeX export ?

I tried to clarify that ``latex` file.`tex`` does not suffice. You'll find such a hint on WEB page in this documentation in tips of the day. I implored the users: "Please read the MusiXTeX export discussion page!". Nothing helps! If I search the WEB I get a lot of &noteedit; descriptions claiming ``latex` file.`tex`` is correct. And I see examples. Some users proudly present the MusiXTeX ouput and do not remark the unaligned right margin.

Even worse: I get some mails: "&noteedit; is ok but it produces MusiXTeX pages with non-aligned right margin!"

So I decided for this drastic feature.

How can I avoid the terrible warning during MusiXTeX export ?

Dectivate the checkbox at: Settings Configure &noteedit; -> MusixWarn

During configure I get an error: Cannot find >= Qt-2.2.2

This can be because of many problems. If you are sure you have an appropriate Qt then most often this has to do with your compiler version. Many users install g++-3.x and expect that programs can be linked with QTs/KDEs which are compiled with g++-2.x. But as experiances show: This is not possible! You have to re-compile the whole Qt and the whole KDE (takes 3 days).

I get an error concerning apps/noteedit/resources.

`"Can't find apps/noteedit/resources. Check your installation and $KDEDIR if set"`

You didn't install &noteedit; (make install) ! The local installation is very complicated. There is a shell script that should place the files and links correctly in &noteedit; top directory:

`cd` path`/noteedit-2.5.0`

`./admin/locinst.sh`

Then set environment variable `KDEDIRS` to noteedit top directory:

Shell | command
(t)csh | `setenv KDEDIRS path_to_noteedit-2.5.0_direcory`
other shell | `export KDEDIRS=path_to_noteedit-2.5.0_direcory`

`cd noteedit`

`./noteedit [`file`.not`]

During file load an error concerning klauncher occurs:

`"... Could not read network connection list.`

`Please check that the 'dcopserver' program is running!"`

and:

`"can't talk to klauncher"`

You use &noteedit; outside KDE and the KDE binaries are not in your PATH. Add the KDE binaries to your PATH! If this doesn't help try:

`rm /tmp/.ICE-unix/*`

`rm $HOME/.DCOPserver_*`

I loaded a .not file made with a previous &noteedit; version. It seems the the first tempo signature appears in last instead of first staff. What shall I do?

Yes, there is a slight version incompatibility concerning .not files before < --- > after 1.18.2. Please correct this and store the file. Now the tempo signature should be at correct place.

I wrote a score with leading graces. But I can't hear them!

Please avoid leading graces! Leading graces have a negative start time. You'll never hear them. Insert an empty measure instead!

Something is wrong with lyrics spacing. The words overlap!

I don't know what's wrong! It has to do with font management of your X11 system. Try to change in noteedit/chord.cpp near line 97:

    #if QT_VERSION >= 300
    #define LYRICSWIDTH_FAC(x) ((int) (1.5 * x))
    #else
    #define LYRICSWIDTH_FAC(x) (x)
    #endif

against:

    #define LYRICSWIDTH_FAC(x) ((int) (1.5 * x))

If this doesn't help increase the value 1.5

Something is wrong with lyrics spacing. The spacing between the words is too large!

I don't know what's wrong! It has to do with font management of your X11 system. Try to change in noteedit/chord.cpp near line 97:

    #if QT_VERSION >= 300
    #define LYRICSWIDTH_FAC(x) ((int) (1.5 * x))
    #else
    #define LYRICSWIDTH_FAC(x) (x)
    #endif

against:

    #define LYRICSWIDTH_FAC(x) (x)

I loaded a .not file made with a previous &noteedit; version. But the staff and lyrics distances are wrong.

The meaning of the `overlength`, `underlength` and `lyricsdist` parameters has changed in version 1.11.0:-( Please edit the ".not" files and multiply the distance values with 3. Or load every ".not" file and correct the values using the staff properties dialog.

The replay works but it hangs during page turn over. What can I do ?

If you use a software midi synthesizer like TiMidity server please start them as root and icrease its priority. This way the priority ot the TiMidity process increases.

Use the following command in this case:

`timidity --realtime-priority=100 -iA -B2,8 -Os1l -s 44100`

This can lead to operating system problems if your CPU performance is too small! If so, then try to decrease the priority and/or the frequency:

`timidity --realtime-priority=60 -iA -B2,8 -Os1l -s 22050`

If this doesn't help then turn off the context view. Unfortunately, the context view is a very time consuming issue.

I cannot hear the sound although Kmidi works without any problem! What's wrong?

This is no surprise! If Kmid worked and &noteedit; not, this were surprising. Kmidi first converts the MIDI data into PCM (WAV) data. Then it plays the sound via PCM (not MIDI) device. You can check this by playing the sound with Kmidi and handle the PCM ruler and then the MIDI ruler on your sound mixer. The MIDI ruler (if any) has no influence.

Important: Try to play a MIDI file with kmid (not (!!!) kmidi). As long as kmid does not produce any sound, &noteedit; (and any other MIDI device based software) will not produce any sound, too! The reason is: Either your soundcard has no hardware MIDI synthesizer or it has a hardware MIDI synthesizer but it is not supported by Linux.

Be not confused if you can play MIDI files on Windows. If your soundcard has no hardware MIDI synthesizer Windows automatically starts a software which converts the MIDI data into WAV (PCM) data in real time. This works if your computer has enough performance.

Such software exists for Linux, too. But it is more complicated because:

- It works only if you have an ALSA system. This is always the case with SuSE Linux. (Other Linuxes I don't know). In any case: You can always change from OSS System to ALSA by compiling the ALSA modules "by hand".

- You have to start this software "by hand".

- These software MIDI sythesizers need a so-called soundfont, a collection of sample tones of every instrument of a virtual orchestra. These soundfonts are copyrighted, i.e. actually nothing for a free system like Linux

But there is a (relatively bulky) way! See The TiMidity server detailed instructions!

&noteedit; crashes after the output `TSE3 ALSA MIDI scheduler created`

In most cases it has not to do with &noteedit; itself. It has to do with your ALSA system or more precise with your ALSA module parameters in `/etc/modules.conf`. To clarify this try the TSE3 test program `tse3play`. First determine the available ports:

`tse3play -list`

Or it this doen't work:

`tse3play -list` file`.mid`

The on every available MIDI port try to play the MIDI file:

`tse3play -port` port file`.mid`

till you hear the music or it crashes. If it crashes it is clear your ALSA system is the reason why.

Actually I can't help here because I'm not an ALSA guru. Please contact the ALSA developers! Time ago I had a similar problem with a laptop with Yamaha YMF7xx sound card. Even worse: My whole Linux crashed. At this time I adapted the OSS (Open Sound System) hints in Linux source documentation (`/usr/src/linux/Documentation/sound/README.ymfsb`) to the ALSA system and it worked. But I'm afraid this is no general solution. Note: This was ALSA-0.5.

As an interim solution you can start &noteedit; without creating an ALSA MIDI scheduler:

`noteedit --noalsa`

&noteedit; uses the so-called ALSA-OSS emulation in this case. The ALSA-OSS emulation doesn't permit the read direction. Thus, read and record from MIDI keyboard isn't possible.

Another option would be: Remove ALSA and use the pre-ALSA sound modules!

Another possibility is: You don't have any sound device and &noteedit; is badly compiled. This can also be detected by:

`tse3play -list`

Or it this doen't work:

`tse3play -list` file`.mid`

If this doesn't report any device a bad &noteedit; compilation could be the reason why. Try to re-compile &noteedit; and make sure the `-fexecptions` option is set during compilation of `midimapper.cpp` and `tse3handler.cpp`.

My whole Linux hangs if I try to start &noteedit;. I have to restart the system.

Note! It is impossible that a program which runs in user space stops Linux (except swap overflow). Even if the program has tons of bugs. It has to to with you ALSA module parameters. Unfortunately, I can't help you in this case. Please contact the ALSA developers! As an interim solution you can start &noteedit; without creating an ALSA MIDI scheduler:

`noteedit --noalsa`

&noteedit; uses the so-called ALSA-OSS emulation in this case. The ALSA-OSS emulation doesn't permit the read direction. Thus, read and record from MIDI keyboard isn't possible.

Another option would be: Remove ALSA and use the pre-ALSA sound modules!

## The MIDI import discussion page

The following text is a overview of the essence of MIDI data. It shall give non-information engineers the possibility to use the MIDI event filter and tell them about the problems of importing MIDI data. A detailed MIDI description can be found at (for instance) http://TSE3.sourceforge.net/docs.html.

Imagine a pump which presses air through 8 parallel tubes. The tubes have a small slot with an endless paper in it. At the end of each of these tubes is an organ-pipe. Each of the 8 organ-pipes plays a different note. As long as there is paper in the slot you can't hear anything. But the paper has elongated holes and it is moved upward with a certain tempo. So if one of these elongated holes is in the slot the appropriate note sounds. The volume can be determined by the width of the elongated holes.

Nothing more is necessary to determine music! And MIDI data are of this kind! A MIDI file can be regarded as a long paper with holes:

At the border is a scale of ticks and the tempo is given in ticks per second.

Now regard the following situation:

In `C`-line is a hole of 12 ticks and in `D`-line a hole of 6 ticks. &noteedit; shall build a score from this information. But it is impossible because ticks is a MIDI term. But &noteedit; needs half note, quarter note and so on.

Fortunately the MIDI file contains a hint. The MIDI header chunk has a field called delta-time ticks per quarter. And if this field determines 24 ticks per quarter the score is (almost) clear:

Is it really clear? Here are some other possibilities:

That's the first reason for the necessity of human intervention. The MIDI file doesn't contain any hint about beams or ties or so. Furthermore in some cases the clef in unclear. &noteedit; tries to choose the most suitable clef. But sometimes the clef is not as expected. In this case you can change the clef.

Fortunately MIDI files (can) contain a hint about the time signature and the key signature. If present &noteedit; uses this information.

But really difficult problems occur in MIDI files generated by a human playing. Regard the following example:

Assume a quarter note has 16 ticks! There is a `C` of 11 ticks and a `E` of 8 ticks. The exact computation is:

11 ticks = 8 ticks + 2 ticks + 1 tick --> 8th + 32nd + 64th followed by a 64th rest followed by a 8th:

But presumably the musician wanted to play: . But he released the `C`-key a bit early. And &noteedit; can "hear" with a precision of a 128th note! Therefore it recognizes a 64th rest.

These are the situations where MIDI event filters should be applied. &noteedit; uses the one of the MIDI event filters offered by Pete Goodliffe's TSE3 library. The SimpleMidiEventFilter offers the possibility to determine the shortest note. If you specify an 16th as shortest note all events are snapped to the next tick which is divisible by 4 (The length of a 16th in ticks):

`Note!` This happens to the beginning an to the end of the note.

Instead of this you can also determine the smallest rest. If you specify a quarter as shortest rest &noteedit; "knows" a 64th rest cannot occur. This deletes the 64th rest.

### The Exact Length button

To explain the meaning of the `Exact Length` button look at the following "MIDI file". The delta-time ticks per quarter value is 4:

Actually the score is clear: But sometimes this is nonsense! For instance, there are a lot of MIDI files with drum tracks of this kind, but a drummer would be very surprised because nobody is able to make a tom-tom sound a whole note or so. On MIDI files this is no problem, because the synthesizer on your soundcard creates waves of this kind:

So the sound ends independent of the length of the MIDI note. To create a reasonable score all notes should be stopped if the next MIDI note begins. I tested some commercial MIDI --> score programs. They always stop the current note if the next note begins. But I think this is an dangerous implication for instance in case of string tracks. Therefore &noteedit; has an `Exact Length` button. If you de-activate this button all notes are stopped if the next note begins. Only notes with the same MIDI start time are combined to a chord. If you activate this button &noteedit; tries to build the exact chords by means of ties. Note! In some complicated cases this can cause "open" ties with no tie partner. If this occurs either correct this by hand or de-activate the `Exact Length` button!

## The LilyPond export discussion page

### "old" LilyPond

`Attention!` If you use LilyPond-1.2 (or less) use the configure option:

`--with-oldlily`

Otherwise the output is incorrect.

LilyPond is a new music typesetter. It produces beautiful sheet music from a high level description file. The home page is at http://lilypond.org. Furthermore LilyPond is part of most Linux distributions.

The LilyPond input is easy to understand. Thus, you have the possibility to post-edit the &noteedit; output.

### Quick Start

I assume you produced a file named `mus1.ly`. Accept all parameters on the "File export" form. Or choose `landscape` format if you wish. If you want to limit the count of measures per line press the appropriate button ( ) and choose a number.

### Generating DVI file

If you compiled LilyPond by your own, you ordinarily have to set some environment variables. There are some scripts for your LilyPond installation in buildscripts/out subdirectory of the LilyPond source tree. Apply the script (especially if the LilyPond output isn't as expected):

(t)csh | source `path/buildscripts/out/lilypond-login`
other shell | `. path/buildscripts/out/lilypond-profile`

Type:

`ly2dvi mus1.ly`

This produces `mus1.dvi`

You can preview the result with:

`xdvi mus1.dvi`

Or if you exported in landscape mode:

`xdvi -paper 30x21 mus1.dvi`

### Generating Postscript file

To get a printable Postscript output do:

`dvips mus1.dvi -o mus1.ps`

Or if you decided for `landscape` format:

`dvips mus1.dvi -t landscape -o mus1.ps`

Or (better):

`ly2dvi -P mus1.ly`

This produces a printable output `mus1.ps`

If you have a PostScript printer the printing is produced by:

`lpr mus1.ps`

### LilyPond installation tips

Besides the TeX base package you need for installation and usage:

- The MetaPost package;

- The kpathsea headers;

These packages are not necessarily installed together with the TeX base package.

For the LilyPond, ly2dvi, xdviand dvips programs possibly some environment variables must be set. Please read the LilyPond install instruction and have a look at the buildscripts/out subdirectory!

If you get some strange symbols on PostScript/DVI file apply the clean-fonts script in buildscripts/out subdirectory.

### Font sizes

LilyPond supports different font sizes. You can choose one with font size button ( )

### Beams

Do not expect the same beams as on &noteedit; score, because LilyPond has its own very intelligent beam algorithm. It is recommended to use it. But if you want the same beams as in &noteedit; select the keep beams checkbox.

### Stem direction

Do not expect the same stem direction as on &noteedit; score, because LilyPond has its own stem algorithm. But if you want the same stem direction as in &noteedit; select the keep stem dir. checkbox.

Another possibility is the keep stem dir. if multiple voices checkbox. In this case only those staffs keep the stem direction which have more than 1 voice.

### Ties

To reduce the number of ties select the sparse ties checkbox.

The following cannot be expressed in LilyPond: . &noteedit; warns you in this case and the result will be: .

### Volume signs

You can choose 3 different policies of exporting the volume signs:

- Omit all volume signs;

- Volume signs above the staff;

- Volume signs below the staff;

### Problems exporting the score Layout

LilyPond can deal with braces and brackets. It changes the staff rules according to some LilyPond inherent rules. I was told it is possible to break these rules. But I assume they are there for good reasons. &noteedit; will warn you if a LilyPond rule will change the staff rule policy.

### Omit the score generation

Advanced LilyPond users who want to produce their own score layout possibly find the only voices checkbox useful. In this case &noteedit; produces a file with only the voice (staff) definitions. The LilyPond user should supply a file with the score definition and an appropriate include:

    \include "paper16.ly"

    \include "theFromNoteeditProducedFile.ly"

    \score {
            ...

            \paper {
                    ...
            }
    }

### Measures

&noteedit; produces bar lines in LilyPond input file. This causes LilyPond to check the correct adjustment of the measures and warns you if it isn't correct. The output is produced in any case. But because of this warnings you get a also a warning from &noteedit;.

### Drum notes

First of all: I was told my drum exportation doesn't use all LilyPond featurs. Perhaps a LilyPond guru can review the &noteedit; LilyPond output and send me a mail what to to.

You can try to export drum notes by checking the appropriate checkbox. But be warned! LilyPond will fail in most cases!

### Problems with grace notes

LilyPond changes the the beam status reasonably. Version 1.4.x cannot deal with slurs in grace notes. &noteedit; will warn you.

### international lyrics

There is a choise to select output charachter coding. You can choose between ascii, utf8, iso-latin1, and unicode. Perhaps this helps to create more interantional LilyPond output.

### Problems with guitar chord diagrams

LilyPond cannot deal with guitar chord diagrams. Actually it has a special feature for chord name annotation. But this is unusable for &noteedit; export because it tries reverse mapping from pitch combination to chord name. Thus, &noteedit; exports the chord names as ordinary uptext.

## MusicXML export discussion page

### About MusicXML

MusicXML is a new music interchange format for music software programs. MusicXML is currently supported by many companies and music software developers in their products, such as Finale, KGuitar, Rosegarden, SharpEye, Tabazar and XEMO. Furthermore, converters to and from various other formats exist.

See http://www.musicxml.org/xml for more information about MusicXML.

### Limitations

The current MusicXML exporter does not support:

- Drum clefs and notes

- Guitar chord diagrams

- More than two voices in one staff

- Multistaff parts (e.g. for piano music one part with two staves should be generated)

- Note shapes (cross, alternative cross, cross with circle, rectangle and triangle)

- Score info (subject, last author and comment)

- Score layout (braces, brackets etc.)

- Staff properties (the options)

- Voice changes

### Export to KGuitar

Due to KGuitar's design as a guitarist tabulature environment, many classical score related features are not supported. As of KGuitar version 0.4.9, no specific bugs are found when importing MusicXML files generated by &noteedit;.

## MusicXML import discussion page

### Limitations

Just like the MusicXML exporter, the current importer does not support:

- Drum clefs and notes

- Guitar chord diagrams

- Note shapes (cross, alternative cross, cross with circle, rectangle and triangle)

- Score info (subject, last author and comment)

- Score layout (braces, brackets etc.)

- Staff properties (the options)

- Voice changes

Multistaff parts (e.g. piano music) are imported as several separate staves.

The importer generates a fatal error for any event that prevents importing in a useful way. Warnings are generated for everything recognized and supported, but containing (recoverable) errors.

`Note:` to prevent too many warnings, MusicXML features that are recognized by the importer, but not handled, do not generate a warning. Unrecognized MusicXML features do generate warnings.

Due to bugs in Qt version 2.x, importing UTF-16 encoded MusicXML files is not possible when &noteedit; uses that Qt version. This is typically the case when running on &kde; version 2.x.

### Import from KGuitar

As of KGuitar version 0.4.9, the following problems are found:

- For each track, KGuitar exports two staves (classical notation and tabulature). In &noteedit; this results in one staff with notes and one empty staff.

- Many "Repositioning voice" errors may be reported

### Import from Rosegarden

Rosegarden's MusicXML exporter is still in a very early development phase. Version 0.9.1, generated a syntactically incorrect XML file, resulting in fatal errors on import, because:

- Not every <part> has a corresponding </part>

- Note types crotchet and minim should be quarter, half etc.

- MIDI channel numbers in MusicXML range from 1 to 16, Rosegarden starts at 0

- MIDI program numbers range from 1 to 128, Rosegarden starts at 0

- The part-name is empty

- The score-part is empty

The previous Rosegarden version 0.9.5 does generate syntactically correct XML. The set of supported MusicXML features, however, is still very limited. Besides general staff information only clef, key signature, time signature, note and rest are written. Especially the lack of beam and stem direction information is very noticable. Time signatures are sometimes missing, sometimes too many are found.

Rosegarden 0.9.5 does not write any accidental information. &noteedit; tries to add the missing information, but does not always succeed. This may lead to missing accidentals.

The current Rosegarden version 0.9.6 adds support for accidentals and ties. The time signature problem is fixed, but beam and stem direction information are still missing. Nevertheless, the overall result is quite workable.

You can use &noteedit;'s Autobeam feature to create the missing beams.

## PMX export discussion page

### PMX

Before reading this you should be familar with MusiXTeX. Read - for instance - the MusiXTeX export discussion page

PMX is a preprocessor for MusiXTeX. &noteedit; produces this output because some users find it a better readable than MusiXTeX.

Generally, PMX isn't a part of the usual Linux distributions. A good WEB page on how to get PMX and its relation to MusiXTeX can be found at: http://icking-music-archive.sunsite.dk.

PMX produces TeX `not` LaTeX! Because it is a preprocessor it causes a 4th pass.

### Quick Guide

Make sure the PMX, TeX (te_tex) and the MusiXTeX packages are installed!

PMX introduces a new term: system: A system is a vertical group of staffs including all the instruments. &noteedit; asks you for the number of systems per page.

Furthermore you are asked for the count of pages. Note: If you specify some bad values here PMX and/or MusiXTeX fail. Make your own experiences what is possible and what not! You need not repeat the export. You can find these parameters at the beginning of the PMX file. Because &noteedit; comments these lines it should be easy to find the appropriate numbers.

The field `Measures per system` does not influence the PMX output but the PMX source. For better readability you can choose how many measures are collected to a system.

Choose `landscape` format if needed.

I assume you produced a file named `mus1.pmx`.

1. type

   `pmxab mus1.pmx`

   This produces `mus1.tex`

2. remove all files named `mus1.mx1` or `mus.mx2` from a possible former TeX generation (that is the first thing you yould check if you get a funny result):

   `rm mus1.mx[12]`

3. type:

   `tex mus1.tex`

   his produces `mus1.mx1`.

4. type:

   `musixflx mus1.mx1`

   This produces `mus1.mx2`.

5. type:

   `tex mus1.tex`

   again. This produces `mus1.dvi`.

You can preview the result with:

`xdvi mus1.dvi`

If you exported in landscape mode:

`xdvi -paper 30x21 mus1.dvi`

You can convert the `dvi` file into a printable PostScript file by typing:

`dvips mus1.dvi -o mus1.ps`

If you decided for `landscape` format:

`dvips mus1.dvi -t landscape -o mus1.ps`

To preview the PostScript file use gv:

`gv mus1.ps`

If you have a PostScript printer the printing is produced by:

`lpr mus1.ps`

### Limitations

Because PMX is a MusiXTeX preprocessor it has simlilary limitations as MusiXTeX:

- PMX doesn't support more than 12 staffs.

- PMX doesn't support more than 10 parallel (over all staffs) ties.

- PMX doesn't support 128ths notes.

- Because MusiXTeX has problems with (de-)crescendo symbols crossing the line break, PMX has the same problems, too.

PMX has its own beam and stem up/down decision algorithm. So do not expect the same beams and stems as shown on score. Sometimes these algorithms fail :-(

PMX can only deal with this sort of triplets: . It fails in case of these triplets.

PMX-Version 2.30 can deal with these triplets.

So &noteedit; exports triplets with 2 members with length ratio 1:2.

PMX cannot deal with triplets ending with a rest:

Similary problems occur with N-tuplets:

PMX cannot deal with N-tuplets ending with a rest. Actually all N-tuplet members must be of the same length, besides some notes are as half as long as the others. PMX cannot deal with an N-tuplet who's real playtime cannot be expressed with one (eventually dotted) note.

`Note!` PMX expects the sum of note/rest length matches the time signature! &noteedit; warns you if this isn't the case.

PMX has its own algorithm to compute the space for the notes. This can cause lyrics spacing problems. The reason is: Actually PMX cannot deal with lyrics. &noteedit; produces raw TeX statements which are not taken into account during space computation. Perhaps the usage of the `musixlry` package gives better results.

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. But sometimes the result isn't PMX-able.

Drum notes are not supported in PMX. &noteedit; will warn you and exports the drum notes as "normal" notes.

### Staff selection

If you want to export only a subset of staffs press "Staff selection" button and choose the appropriate staffs

### Keep beams

The PMX generation causes the following contradiction in case of beamed chords:

To ensure correct placement of beams the note with lowest distance from beam must appear first in text.

On the other hand: PMX determins the direction of the beam: up or down.

So, &noteedit; has no idea what is the note in chord with lowest distance from beam. If this causes beam problems (beams crossing stems) the `keep beams` button could be helpful. In this case &noteedit; places beam direction statements into PMX source and thus, it has enough information to determine the suitable order of notes.

### Problems with grace notes

PMX changes the slur and beam status of grace notes reasonably.

### Problems with guitar chord diagrams

PMX can neither deal with chord names nor with guitar cord diagrams. Thus, &noteedit; omits the information.

### Using musixlyr

If you prefer a compact text block in MusiXTeX file you can select the `with musixlyr` checkbox. Note! In this case you need the `musixlyr.tex` package by Rainer Dunker either installed or in current working directory. You can get this package from http://icking-music-archive.sunsite.dk.

### Problems exporting the score Layout

PMX is a preprocessor to MusiXTeX and therefore the same problems apply.

PMX actually accepts either completely continued or completely discontinued bar rules. If you specify a mix of partial continued and partial discontinued bar rules &noteedit; produces some statements of the `musixdbr.tex` package by Rainer Dunker. &noteedit; produces a warning and gives advice to install this package. Otherwise PMX will fail.

## The MusiXTeX export discussion page

### MusiXTeX

> I were never able to implement the MusiXTeX export without the help of Werner Icking the moderator of the mutex mailing list and excellent MusiXTeX expert. Werner Icking died on the night of February the 8th 2001 in a bicycle accident as he drove home from his workplace.

MusiXTeX is a very powerfull tool which produces unrivaled beautiful music pages. An important advantage of MusiXTeX is: It is (La-)TeX. So it is no problem to enhance the notes with music theoretical or music historical or other related texts. One problems is: The "&" symbol is redefined by MusiXTeX. Please read the MusiXTeX documention about this topic.

I implemented only a small subset of the many features offerd by MusiXTeX. But because it is (La-)TeX it is readable (and writeable) by ordinary editors. If you wish some other features you can post-edit the TeX file. To support this &noteedit; attaches the bar numbers to the `\bar` statement as a comment. If you export with bar numering you can compare the MusiXTeX file with the DVI file to find the position of the appropriate measure.

According to documentation the original ftp server of MusiXTeX shall be `hprib.lps.u-psud.fr`. But the server is empty. (???) A good WEB site with a lot of information can be found at http://icking-music-archive.sunsite.dk.

Furthermore you have a MusiXTeX documentation on your Linux system (`/usr/doc/packages/musixtex` or so.. ).

### Quick Guide

Make sure the LaTeX (te_latex) and the MusiXTeX packages are installed!

Accept all parameters on export formular. Or choose `landscape` format if you wish.

If you want to limit the count of measures per line press the appropriate button ( ) and choose a number.

I assume you produced a file named `mus1.tex`. Ignore all possible warnings and error messages which occur during export. (You get always a MusiXTeX file besides you have more than 9 staffs) and do the following 4 steps:

1. remove all files named `mus1.mx1` or `mus.mx2` from a possible former TeX generation (that is the first thing you yould check if you get a funny result):

   `rm mus1.mx[12]`

2. type:

   `latex mus1.tex`

   This produces `mus1.mx1`.

3. type:

   `musixflx mus1.mx1`

   This produces `mus1.mx2`.

4. type:

   `latex mus1.tex`

   again. This `produces mus1.dvi`.

You can preview the result with:

`xdvi mus1.dvi`

If you exported in landscape mode:

`xdvi -paper 30x21 mus1.dvi`

You can convert the `dvi` file into a printable PostScript file by typing:

`dvips mus1.dvi -o mus1.ps`

If you decided for `landscape` format:

`dvips mus1.dvi -t landscape -o mus1.ps`

To preview the PostScript file use `gv`:

`gv mus1.ps`

If you have a PostScript printer the printing is produced by:

`lpr mus1.ps`

### Script based export

To simplify the process of making a correct dvi-file, you can copy this little shellscript musix2dvi:

    #!/bin/bash

    # musix2dvi xxx.tex

    # musix2dvi removes the xxx.mx[12]-files, then:
    #   latex xxx
    #   musixflx xxx
    #   latex xxx

    # remove .tex from filename
    TEXFILE=${1%.tex}

    rm -f $TEXFILE.mx[12]
    latex $TEXFILE
    musixflx $TEXFILE
    latex $TEXFILE

When you start your MusiXTeX-export, type `/path/to/musix2dvi %f` in the MusiXTeX-Cmd-field and &noteedit; will start musix2dvi after the export.

`%f` will be substituted with the filename of your exportfile.

### Problems with MusiXTeX

Although MusiXTeX is a very powerful tool it has some limitations:

- MusiXTeX doesn't support more than 6 staffs.

- MusiXTeX doesn't support more than 6 parallel (over all staffs) ties.

- MusiXTeX doesn't support more than 6 parallel (over all staffs) beams.

- MusiXTeX doesn't support 128ths notes.

- MusiXTeX has problems with (de-)crescendo symbols crossing the line break.

### Solutions

The greatest problem is the tie restriction. Indeed, if you have not more than 6 staffs &noteedit; doesn't need more than 6 beams.

BTW: This is `one` beam:

Unfortunatly this is not true if you use multiple voices per staff. In this case the beams can run out of stock, because theoretically all available beams can be in first staff.

Too many ties may occur in chords:

In this case &noteedit; omits some ties an warns you. It is a good idea to use the bar numbering option ) to find the position of the problem.

The solution offered by &noteedit; is to build spare ties ( over chords: :

Another solution (if possible) would be to export only a subset of staffs ( ).

If you install the package `musixadd` you can increase the staff, ties, beam count up to 9. (More is not possible). Select the musixadd checkbox ) in this case.

In a similary way you can solve the 128th problem by installing the `musixbm` package. Select the `musixbm` checkbox ( ) in this case.

MusiXTeX has also some Problems with N-tuplets:

MusiXTeX is prepared for triplets. It uses the `uptrio` statement which produces a bracket with a small "3" in the middle. For N-tuplets it uses the `xtuplet` statement which produces the number without a bracket. If the N-tuplet is beamed it looks like an N-Tuplet. If not it looks like some notes with a number above. It is your resposibility to mark the N-tuplet for instance with a slur (or so ...)

&noteedit; offers export with 2 different sizes:

- normalmusicsize (default)

- smallmusicsize

With size box you can select one of 4 different sizes.

The staff geometry parameters influence the staff positions. `Please note!` Because the &noteedit; music signs differ from MusiXTeX music signs in form and dimension there is no direct coherence between the &noteedit; presentation and the MusiXTeX presentation. In difficult cases you have to play with the staff geometry parameters to get a reasonable MusiXTeX output.

### Using musixlyr

If you prefer a compact text block in MusiXTeX file you can select the `with musixlyr` checkbox. Note! In this case you need the `musixlyt.tex` package by Rainer Dunker either installed or in current working directory. You can get this package from http://icking-music-archive.sunsite.dk.

### Exporting guitar chord diagrams

MusiXTeX has an additional package called MusiXGui. This allows to annotate guitar chord diagrams and chord names. It works but unfortunately there is no possibility to add a fret information. So, if the fret is not equal 1 NoteEdit appends the fret information to the chord name. MusiXTeX/MusiXGui can only deal with full barre.

### international lyrics

There are 3 choices to control input and output conding and to add some TeX moduls. This is important for international character set handling. Don't ask me too much about this topic! All I know is : `T2A` + `cp1251` + `UTF-8` produces Russian (Cyrillic) texts. And `T2A` + `ucs` + `UTF-8` produces correct Urkrainian texts.

If you have problems with your character set and you know what to do: Let me know!

### Problems exporting the score Layout

MusiXTeX actually accepts either completely continued or completely discontinued bar rules. If you specify a mix of partial continued and partial discontinued bar rules &noteedit; produces some statements of the `musixdbr.tex` package by Rainer Dunker. &noteedit; produces a warning and gives advice to install this package. Otherwise MusiXTeX will fail.

## The ABC music export discussion page

### What is ABC music

ABC music is an ASCII based music description language. More information is available at http://www.gre.ac.uk/~c.walshaw/abc/ and http://abcplus.sourceforge.net.

The free software abcm2ps (http://moinejf.free.fr) produces a PostScript output from ABC input.

abcm2ps is a very surprising tool, because:

- it is GPL

- it consists of only 10 C files

- it compiles in less than 30 seconds

- it converts Beethoven's 5th symphony (1st mov.) in 10 seconds to PostScript

- it doesn't require any (La)TeX installation

### How to get a printable output

&noteedit; produces code for abcm2ps version 3.x.y

Accept all parameters on export formular. Or choose `expressions above` or `measure numbers in a box` format if you wish. If the staffs are too narrow you can change the vertical staff separation.

The `width` and `height` parameters should be changed if you don't use A4 paper size. Do not use these values to get landscape mode! (see below)!

I assume you produced a file named `mus1.abc`.

Type: `abcm2ps -c -O= mus1.abc`

This produces the PostScript file `mus1.ps`. To preview the PostScript file use gv:

`gv mus1.ps`

If you have a PostScript printer the printing is produced by:

`lpr mus1.ps`

If you want a landscape format type:

`abcm2ps -c -O= -l mus1.abc`

This produces the PostScript file `mus1.ps`. To preview the PostScript file use gv:

`gv mus1.ps`

If you have a PostScript printer the printing is produced by:

`lpr mus1.ps`

For more information (page/measure numbering) read the abcm2ps manual or simply type: `abcm2ps --help`

### Restrictions

ABC music has some minimal restrictions:

- it cannot deal with drum staff (notes, clef)

- there are apparently some problems with context change (key, clef, time signature, tempo change)

- ABC music cannot deal with differet long measures in a system

Therefore: If you plan to export the score to ABC make sure all measures are filled and are of the same length. This holds especially for 2nd, 3rd, ... voice!

### Problems exporting the score Layout

ABC music cannot deal with nested braces in brackets. &noteedit; will warn you.

## Installation

### How to obtain &noteedit;

&noteedit; can be found at http://rnvs.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html.

### Installing &noteedit; from RPMs

If you find an RPM for your Linux distribution, you can install &noteedit; from RPM.

You need a TSE3 package. So if you find a TSE3 RPM for your Linux distribution install TSE3 first. Otherwise compile TSE3 from source

If you want to use &noteedit; with aRts MIDI scheduler then make sure the aRts headers (`artsmidi.h`) are installed before you compile TSE3.

To install the &noteedit; package from a binary RPM you must be logged in as root. Assuming that the name of the RPM is `filename.rpm`, do the following at the command prompt:

`% rpm``-ivh` filename.rpm

### Installing from source

#### Requirements for source compilation

You need the following packages:

- g++ compiler (You can use g++-3.x, but make sure QT/KDE (others ???) is also g++-3.x-compiled/You need TSE3-0.2.5 for gcc-3.2!)

- X11 (include and libraries)

- Qt (include and libraries) Qtdevel2 (>=Qt-2.2.2)

- YACC or Bison

- LEX or flex

- KDE-2.x.y or KDE3

- gettext (only for text translation)

- extractrc(from kde developement) (only for text translation)

recommended:

- TSE3 Library Version (0.1.2, 0.1.3, 0.2.3, 0.2.5) see: http://TSE3.sourceforge.net

- A good idea is also: LaTeX (te_latex package), MusiXTeX, xdvi, dvips, gv.

- abcm2ps (version 3.x.y!!!) http://moinejf.free.fr

- and: LilyPond (for LilyPond installation MetaPost and the kpathsea headers)

- likewise: LibKMid; see http://www.arrakis.es/~rlarrosa/libkmid.html (Note: Not all features are available in this case! (MIDI import))

- If you want to use &noteedit; with aRts MIDI scheduler: aRts (include and libraries; especially `artsmidi.h`)

If you want to use &noteedit; with aRts MIDI scheduler then make sure the aRts headers (`artsmidi.h`) are installed before you compile TSE3.

You can compile the program without any MIDI-library. But in this case an

`#include /usr/src/linux/include/linux/soundcard.h`

occurs which can cause a lot of machine/sound card depencies. Therefore if your sound doesn't work and you are sure MIDI works on your machine (you use KMid successfully) then try compilation with one of the libraries! Use the TSE3 library if you want to use all features including MIDI import!

#### Building

If you have different KDE/Qt versions make sure the PATH variable only references the KDE/Qt version you wish to use for NoteEdit!

Please uninstall an older version especially all old `noteeditui.rc` files. If you don't have the source distribution to "make uninstall" remove all in

path_to_your_kde_installation`/share/apps/noteedit`

Decompress and configure the archive:

`tar -xvzf noteedit-2.5.0.tgz`

`cd noteedit-2.5.0`

(t)csh | other shell
`setenv QTDIR path_to_your_qt_installation` | `export QTDIR=path_to_your_qt_installation`
`setenv KDEDIR path_to_your_kde_installation` | `export KDEDIR=path_to_your_kde_installation`

`./configure --prefix=`path_to_your_kde_installation

whereby path_to_your_kde_installation is the path there KDE usually resides on you system. You can always find out this path my means of the following command:

`kde-config --prefix`

If you installed TSE3 library in an unusual directory:

`./configure --with-libtse3-include=`dir_to_tse3_includes `--with-libtse3-libs=`dir_to_tse3_libs

If you want to use libKMid instead of TSE3 library:

`./configure --with-libkmid`

(`Note:` Not all features are available in this case! (MIDI Import))

If you installed libKMid in an unusual directory:

`./configure --with-libkmid-include=`dir_to_libkmid/libkmid.h `--with-libkmid-libs=`dir_to_libkmid.so

If you won't use any library (not recommended; see above!)

`./configure --without-libs`

If you use LilyPond 1.2.x

`./configure --with-oldlily`

In priciple you can use the parameter `--enable-final` But this is not recommended, because the resulting code is 30% greater. This is because of the -fexecption compiler option which is applied to tho whole source. Without `--enable-final` the -fexecption compiler option is only applied to the necessary C modules.

Type:

`make`

This should create &noteedit;

Type (as root):

`make install`

This should install &noteedit;

If you don't like &noteedit; type (as root):

`make uninstall`

This should remove &noteedit;

Then start the program: It is recommended to start &noteedit; in KDE environment. If not then make sure the kde binaries are in your PATH.

Type:

`noteedit`

or:

`noteedit` file`.not`

This should start the note editor. If there is an error `"error opening sequencer"` a soundcard depency (as mentioned above) avoids the access to the MIDI device. The editor works but you can't play the music :-((.

If you have an AWE-64 (or - 32 (???)) don't forget to load your orchestra (sfxload) before starting noteedit!

### First test

File Open `examples/example1.not`

or:

File Open `examples/example2.not`

or: ...

or:

File Open `examples/example12.not`

Press the play button( ). If you hear the music the program works :-))

If not then try to change the MIDI device ( Settings Configure &noteedit; -> Sound --> MIDI Devices).

Or (`only with TSE3`) change the TSE3 MIDI scheduler by unchecking the ALSA option:

Settings Configure &noteedit; --> Sound --> Sequencers

and restart &noteedit;.

(see also: Working with TSE3)

BTW: The quality depends on soundcard. Hear the beginning of `example2.not` on AWE 64/ 24 MB RAM and soundfont `8mbgmsfx.sf2`: example2.mp3 (625 Kbyte)

### The TiMidity server

(`only with TSE3`) You can use the MIDI to WAVE converter and player TiMidity++ ( http://timidity.sourceforge.net) in server mode. This approach is interesting for all those who can't bring the MIDI device to work.

Please load the newest version via CVS (as explained on that page)

This requires an ALSA sound system!

A presupposition is that TiMidity++ is compiled with (at least) the `configure` options:

`--enable-audio=alsa --enable-server --enable-alsaseq`

You sould also try to change "the orchestra" by installing a different soundfont. Please have a look at http://www.hammersound.net and search for `FluidR3` soundfont!

Unfortunately, this soundfont is in `sfArk` compression format. There is no Linux program to de-compress this. But you can do do it with the help of the Windows-Emulator wine. A step-by-step instruction follows (see below)!

If you've got the soundfont file store it somewhere as (for instance) `FluidR3.sf2` Then in `/usr/share/timidity/timidity.cfg` (or `/usr/local/share/timidity/timidity.cfg`) change:

`dir` <path_to_the_directory_there_the_FluidR3.sf2_file_is_situated>

and:

`soundfont FluidR3.sf2`

Comment all other lines! If all is ok, you can start TiMidity++ with:

`timidity -iA -B2,8 -Os1l -s 44100`

Select on &noteedit; sound configure dialog ( Settings Configure &noteedit; --> Sound). You should see 4 new MIDI devices:

- Timidity port 0 128:0

- Timidity port 1 128:1

- Timidity port 2 128:2

- Timidity port 3 128:3

Choose one of them and the replay should work!

Tip: If the replay interrupts during turn over then start TiMidity++ as `root`. This increases the priority of the TiMidity++ process. Use the following command in this case:

`timidity --realtime-priority=100 -iA -B2,8 -Os1l -s 44100`

This can lead to operating system problems if your CPU performance is too small! If so, then try to decrease the priority and/or the frequency:

`timidity --realtime-priority=60 -iA -B2,8 -Os1l -s 22050`

### Installation of FluidR3 soundfont

First create a directory (for instance) `/tmp/SOUNDFONT`:

`cd /tmp`

`mkdir SOUNDFONT`

Store the file `FluidR3122501.zip` there an un-"zip" the file:

`unzip FluidR3122501.zip`

The result is `FluidR3 GM.sfArk`. Download the de-compressor from http://www.melodymachine.com. Choose there `sfArk v2.15` and store the `.exe` at `/tmp/SOUNDFONT`! Start the setup:

`wine sfark_setup.exe`

If this doesn't work please attach a virtual drive to `/tmp`. Edit the file `$HOME/.wine/config` and register `/tmp` as new drive:

    [Drive E]
    "Path" = "/tmp"
    "Type" = "hd"
    "Label" = "Tmp Drive"
    "Filesystem" = "win95"

Make sure the letter is really new and not already in use!

After launching `setup.exe` choose `E:\tmp\SFARK` (i.e `/tmp`) as install direcory! To avoid problems please use the command line version of sfArk (because of the spaces in file name the apostrophs are necessary):

`wine sfArkXTc.exe "FluidR3 GM.sfArk"`

`wine "FluidR3 GM.sfArk.exe"`

It is recommended the rename the resulting file`FluidR3 GM.SF2` because the Linux shell has problem dealing with spaces in file names:

`mv "FluidR3 GM.SF2" FluidR3.sf2`

Use `FluidR3.sf2` as described above!

### How to obtain KDE

KDE can be found on The KDE FTP site or one of it's mirrors.

### Compilation and Installation of KDE

&ksnapshot; may be installed from the kdegraphics package either by installing a binary RPM or by compiling the source package.