This is Info file rosehelp.info, produced by Makeinfo-1.55 from the
input file rosehelp.x.


File: rosehelp.info,  Node: The Rosegarden Top Box,  Next: File Boxes,  Up: Rosegarden

   The Rosegarden Top Box                Introduction

   The Rosegarden program suite comprises three parts: the Top Box,
Sequencer (see [*note The Rosegarden Sequencer::.]) and Editor (see
[*note The Rosegarden Editor::.]).  The Top Box is a small program
whose task is to coordinate the activities of the other two.  You
should normally run the Rosegarden suite by starting up just the Top
Box; this is usually carried out by running a program called
"rosegarden".  Once the Top Box has been started, the Sequencer and
Editor can be started from it.

   The Top Box appears as a small window containing a single row of
buttons.  These are labelled `Notate', `Sequence', `Exit' and `Help'.
There is also an `About' button, the square to the left of the window
containing the Rosegarden logo, which, when pressed, yields a short but
flashy enumeration of the Top Box's authors.  (Most of the Rosegarden
programs' larger windows are equipped with `About' buttons.)

   The other buttons behave as follows:

   -- The `Notate' button invokes [*note The Rosegarden Editor::.].
This is a tool for transcription, display and editing of music in a
traditional musical notation.

   -- The `Sequence' button invokes [*note The Rosegarden Sequencer::.].
This is for recording, displaying, manipulating and playing music in
MIDI format.

   -- The `Exit' button exits the Top Box, and also exits the Editor
and Sequencer if they have been started up.

   -- The `Help' button calls up the interactive hypertext help system
(see [*note The Rosegarden Help System::.]).  The Help system contains
the entire Rosegarden reference manual, with cross-references; if
you're reading this on your computer screen rather than on paper, you
may well be using it.  Help may also be called up from the `Help'
buttons on the Editor and Sequencer, so long as the Top Box is there to
provide it.

   The Editor and Sequencer can also invoke and use each other, so long
as the Top Box is running; details of how to start the Sequencer from
the Editor are in [*note Playing a piece of music::.] and [*note
Sequencing a piece of music::.], and of how to start the Editor from
the Sequencer are in [*note Preparing a MIDI file for the Editor::.].


File: rosehelp.info,  Node: File Boxes,  Next: The Rosegarden Help System,  Prev: The Rosegarden Top Box,  Up: Rosegarden

   File Boxes                Concept

   Using many of the major functions within the Rosegarden editor and
sequencer involves understanding the File Box.  File Boxes are smallish
windows which are popped up whenever a Rosegarden program requires you
to select a file or enter a filename for opening or saving.  Their
purpose is to list the files in a given directory, allowing you select
files, move to different directories and other simple operations.

   A File Box is divided up into five areas:

   -- The top label.  This shows the name of the directory being
inspected; if you click-and-hold upon it you get a menu of directories
higher up in the file tree; selecting one of these moves to and
displays that directory.

   -- The main file list.  This shows the names of the files and
subdirectories in the current directory, with subdirectories first.
The list may not be complete, because by default (although you can
change this using the filter button, below) the File Box filters out
all files with names beginning with a dot or ending with certain
special characters.  If the list is long, it can be scrolled through
with the scrollbar to its left.  The entries in the file list can be
clicked and selected, as explained below.

   -- The filter button.  This starts out labelled `Normal files'; by
clicking on it you can choose which sorts of files to display in the
file list.  The choices are `Normal files', which shows only those
files with names which suggest that they are not backup or hidden
files; `Dot files', which shows hidden dot files as well as normal
ones; and `All files', which shows hidden dot files and backup files as
well as normal ones.

   -- The current-file label.  This is initially empty, but when the
name of a file (as opposed to a subdirectory) is selected in the main
file list, it is copied down to this label.  If you're using the File
Box to choose a file to save into, you can also click on this label and
type a new filename into it.  (File Boxes for loading files don't allow
you to do this.)

   -- The action buttons: `Load' or `Save', `Cancel' and `Help'.
Clicking on the button labelled `Load' or `Save' (depending on what the
file box is being used for) causes the file whose name is displayed in
the current-file label to be used.  The `Cancel' button cancels the
function that this File Box is being used for, and the `Help' button
calls up help on this function.

   Files in the file list can be selected by clicking on them; selecting
a file just copies its name to the current-file label, where, if this
File Box is for a Save operation, it can be edited.  Double-clicking
(clicking twice in quick succession) on the name of a file selects and
activates it, in the same way as selecting it and then using the `Load'
or `Save' button.  Clicking on the name of a subdirectory moves into
that directory, and displays its contents in the main file list.


File: rosehelp.info,  Node: The Rosegarden Help System,  Next: Help organisation,  Prev: File Boxes,  Up: Rosegarden

   The Rosegarden Help System                Introduction

   Rosegarden is equipped with a powerful online hypertext help system,
containing the whole of the Rosegarden Reference Manual in a
hierarchical cross-referenced format.

   The Help is a generic browser based upon the GNU Info format, with a
structure similar to that used in several other packages such as GNU
Emacs.

   The structure of help pages is described in the next page.  If you
are using the online Help to read this, you can reach the next page by
clicking on these words: [*note Help organisation::.]; a reference
guide to the features and buttons of the Help window can be found under
[*note Using help::.].


File: rosehelp.info,  Node: Help organisation,  Next: Using help,  Prev: The Rosegarden Help System,  Up: Rosegarden

   Help organisation                Concept

   Help documentation is organised into a set of pages, structured in a
tree hierarchy.  There is one page (or `node') at the top of the tree:
this is called `Top'.  This has a menu of subpages, each of which has
its own menu; finally, the pages containing actual information, like
this one, are at the bottom (the `leaves') of the tree.  You can get
from a page to any of the subpages on its menu simply by clicking the
first mouse button on the name of the page you want to go to.

   The subpages accessible from a page's menu are stored in order; each,
in addition to being a `child' of its `parent' menu page, has up to two
`sibling' pages, `previous' and `next'.  The previous, next and parent
pages are always available through the arrow buttons immediately above
the help text window.  From the current page, for instance, the
previous page is available through the button labelled `The Rosegarden
Help System', the next through `Using help', and the parent page
through `Rosegarden'.

   The Help system also provides some hypertext support, in the form of
cross-references.  These are words or phrases which appear in the text
emboldened or in an italic face, and which may be clicked upon in order
to transport the user directly to their page.  For instance, when using
the Help system you can click on the words [*note The Rosegarden Help
System::.] in this sentence to transport you to the page of that name,
which happens to be the one before this, and on [*note Help
organisation::.] to redisplay this very


File: rosehelp.info,  Node: Using help,  Next: The Rosegarden Editor,  Prev: Help organisation,  Up: Rosegarden

   Using help                Procedure

   The Help window is split into three rough areas: the button bars, at
the top; the help text window, next down; and the help menu window, at
the bottom.  Normally only one of the text and menu windows is in use:
if there is text in the current page, there will be no menu, and if
there is a menu, the only text will be the page's title.

   The buttons used for motion -- those which take you to the previous,
next and parent pages, plus the buttons which operate cross-reference
links and menu selection -- are described in the previous page, [*note
Help organisation::.].  The other buttons are:

   -- the About button.  This is the one with a picture of a pot of
roses on it.  If you click on it, it'll tell you some particularly
uninteresting things about the author.

   -- the Search button.  The Help system has a search system which,
given one or more keywords, can supply a list of all the help pages
which might be connected in some way with those keywords.  It does this
just by scanning the text of the help pages to see if it can find your
keywords in them anywhere.  (This doesn't mean that it can also search
for parts of words.  It can't.)  To use it, click on `Search', station
the mouse pointer just in front of the words `Search string:', type in
one or more words, and without pressing + return, hit the `Execute
Search' button at the top of the window.

   After searching, if you haven't found a more interesting page as a
result of the search, you can return to the help page you were
previously looking at with the `Return to Help Page' button at the top
of the Search display.

   -- the History button.  This, when pressed, switches to the History
display, which shows you which pages you've read since Help was
started.  You can click on these to return to them, or on the `Show
Current Page' button to return to the page you were on when you pressed
History.

   -- the Exit button.  This closes down the Help window until next time
it's called for.


File: rosehelp.info,  Node: Rosegarden,  Next: Editor,  Up: Top

   Rosegarden section

* Menu:

* The Rosegarden Top Box:: introduction
* File Boxes:: concept
* The Rosegarden Help System:: introduction
* Help organisation:: concept
* Using help:: procedure


File: rosehelp.info,  Node: The Rosegarden Editor,  Next: Starting a new piece of music,  Prev: Using help,  Up: Editor

   The Rosegarden Editor                Introduction

   The Rosegarden Editor module allows the user to display and edit
music in a traditional musical notation, transcribing from MIDI sources,
saving and loading in MIDI or the editor's own internal format, or
printing using

   the MusicTeX music typesetting system.  The editor can be run
independently or as part of the Rosegarden suite; this help is only
available when it is run as part of the suite.


File: rosehelp.info,  Node: Starting a new piece of music,  Next: Opening an editor file,  Prev: The Rosegarden Editor,  Up: Editor

   Starting a new piece of music                Procedure

   To begin work on a new piece, call up the [*note Editor File::.]
menu and select the [*note Editor File - New::.] function.  A small
window will then pop up asking you how many staffs you want in the
piece.  The default number is 1; if you only want one, just click on
the Apply button in the window.  Otherwise, use the keyboard to delete
the 1 and type in the number of staffs you need.  Then click on Apply,
or Cancel to abandon the new piece.

   The main editing window will then clear and the opening stubs of a
new set of staffs will appear.  The editor chooses a likely set of clef,
key and time markings (C major, 4/4 time, and each staff in either
treble, alto or bass clef depending upon its position), and gives the
staffs some default (uninformative) names.  All of these things can be
changed: see [*note Changing bar properties::.] and [*note Bar - Time
Signature::.] to change the time, [*note Editing and using the
clipboard::.], [*note Using the Palette::.] and [*note Inserting notes
and signs::.] to delete the clef and insert a new clef, and [*note
Operations on staffs::.] and [*note Stave - Rename Staff::.] to change
the names of the staffs.


File: rosehelp.info,  Node: Opening an editor file,  Next: Saving an editor file,  Prev: Starting a new piece of music,  Up: Editor

   Opening an editor file                Procedure

   Files which have previously been saved from the editor (see [*note
Saving an editor file::.]) can be reopened for further editing using
the [*note Editor File - Open::.] function on the [*note Editor
File::.] menu.  To do this, select the [*note Editor File - Open::.]
menu entry, select the file to be opened on the file box (see [*note
File Boxes::.]), and click on the Load button.  Provided the file is a
properly formed Rosegarden editor file, it will be opened and its
contents displayed on the main editing window.

   Opening a new file does not affect the buffer which was previously
being edited: its contents, and those of every other buffer which has
been opened since the editor was started and has not been closed, are
available by selecting the buffer's name on the list on the [*note
Editor File::.] menu.  If you do want to finish editing the current
buffer for good when loading a new one, select [*note Editor File -
Close::.] before opening the new file.


File: rosehelp.info,  Node: Saving an editor file,  Next: Printing a piece of music,  Prev: Opening an editor file,  Up: Editor

   Saving an editor file                Procedure

   To save a buffer into its associated disc file, choose the [*note
Editor File - Save::.] function from the [*note Editor File::.] menu.

   To save a buffer into a new file, without affecting the contents of
any file(s) which may previously have been associated with it, use the
[*note Editor File - Save As::.] function instead.  This pops up a file
box (see [*note File Boxes::.]) to prompt for a file into which to save
the buffer, and saves it in there.  The new file will subsequently be
that associated with the buffer, replacing any old one (so subsequent
uses of [*note Editor File - Save::.] will save into this new file).
The name of the buffer (displayed in the title bar and in the [*note
Editor File::.] menu) is also changed accordingly.

   If there is no disc file associated with the current buffer, for
example if the buffer is being used to display a MIDI file opened
straight from the sequencer, the [*note Editor File - Save::.] function
will not be available.  To save such files you must tell the editor
where they should go, using [*note Editor File - Save As::.].


File: rosehelp.info,  Node: Printing a piece of music,  Next: Moving around,  Prev: Saving an editor file,  Up: Editor

   Printing a piece of music                Procedure

   Although we would like to include support for printing directly from
the Rosegarden editor (via PostScript, for instance), this is not yet
available.  Printing music requires use of, and familiarity with, the
MusicTeX music typesetting language (see [*note Exporting MusicTeX
files::.]).


File: rosehelp.info,  Node: Moving around,  Next: Using the Palette,  Prev: Printing a piece of music,  Up: Editor

   Moving around                Procedure

   When a buffer is first opened, the main window displays its contents,
starting with the first bar (or `measure,' for the more
transatlantically or transcontinentally inclined) shown at the left of
the display.  When a piece of music becomes taller or wider than the
window size, it becomes necessary to move the view around within it.

   The main editing window is equipped with two scrollbars, a horizontal
one at the bottom and a vertical one to the left, and with five motion
buttons at the bottom.

   The scrollbars work in the same way as on many other X applications,
such as `xterm'.  While the pointer is over a scrollbar, the first
mouse button scrolls towards the end or bottom of the piece by an
amount proportional to the distance along the scrollbar the pointer is
placed; the third button scrolls in the other direction by a similar
amount; and the second button causes the displayed section to jump to
the point in the piece corresponding to the distance along the
scrollbar the pointer is placed.

   The motion buttons move the display (respectively) left by a whole
screenful, left by a single bar, to any bar of your choosing (upon
clicking on the bar number display you are asked for a bar number to
which to jump), right by a single bar and right by a while screenful.

   You can also use the cursor keys on the keyboard to move around a
piece.  Left and right will always move by one bar left or right, but
the up and down buttons will only work in edit mode (see [*note Using
the editing cursor::.]) -- when inserting notes, they are instead used
to change the length of note to be inserted.


File: rosehelp.info,  Node: Using the Palette,  Next: Inserting notes and signs,  Prev: Moving around,  Up: Editor

   Using the Palette                Procedure

   The Palette is the smaller window which appears to the right of the
editor's main window when the editor is started up.  It is used to
select items to be inserted in the music in the main window.

   The Palette window contains a set of buttons for selecting note or
rest lengths, clefs, and accidental modifiers.

   If you click on a note on the palette, it will be highlighted and
that length of note will be selected for insertion into the music on the
main window.  The cursor in the main window will change to a cross to
show that insertion mode is enabled, and then clicking with the left
mouse button over the main stave of music will insert notes.  (See
[*note Inserting notes and signs::.].)

   The selection can be cleared, to return to editing mode (see [*note
Using the editing cursor::.]), by clicking again on the selected note
in the Palette.  (Clicking with the right mouse button on the main
window will also return you to editing mode.)  To select a different
length of note or rest, or a clef, for insertion, just click on it.

   At the top of the Palette there are four `modifier' buttons.  These
show the sharp, flat and natural signs, and a dot.  If any of these are
selected, they will be used to modify inserted notes (and rests, in the
case of the dot).  So for example, to obtain a dotted-quaver rest,
select the quaver rest and the dot modifier; to obtain a sharpened
crotchet note, select the crotchet, ensure that the dot modifier is not
selected, and select the sharp modifier.

   Double-sharps and double-flats are not available.

   Finally, at the very top of the Palette is a toggle button labelled
"Follow Key".  If this is ticked, notes inserted into the musical stave
will be transposed into the right key signature, so you will only need
to use the sharp, flat and natural buttons for accidental notes not
conforming to the signature.  (Accidentals that you explicitly select
from the buttons on the Palette will still be used in preference,
however.)  If the "Follow Key" button is not ticked, all notes will be
entered as naturals unless you have explicitly requested an accidental.


File: rosehelp.info,  Node: Inserting notes and signs,  Next: Considerations in inserting notes,  Prev: Using the Palette,  Up: Editor

   Inserting notes and signs                Procedure

   The editor has two modes of operation: insert and edit mode.  The two
can be distinguished, because in insert mode, the mouse pointer becomes
crosshair-shaped when it enters the main edit window; in edit mode, an
approximately I-shaped cursor is used instead.  To enter insert mode,
one of the insertable items on the Palette must be selected (see [*note
Using the Palette::.]); if none are selected, the editor is in edit
mode, in which various editing operations can be carried out (see
[*note Using the editing cursor::.] and [*note Editing and using the
clipboard::.]).

   To insert an item into the music, select it on one of the Palette's
item buttons, then click the left mouse button when the mouse pointer
is somewhere within the main window.  If the pointer is over a staff
when the button is pressed, the item will be inserted under the
pointer.  If the item is a note, the position of the pointer vertically
on the staff will be used to determine the pitch of the note.  You can
use the Palette's sharp, flat, natural and dot buttons (see [*note
Using the Palette::.] and [*note Considerations in inserting notes::.])
to apply accidentals and dots to the note you want to insert; you can
also hold the left Control or Alt key on the keyboard for a sharp or
flat respectively, the right Alt key for a natural, or the left Shift
for a dotted note; and the up and down cursor keys, when used in insert
mode, change the selected note length.

   When you've inserted enough notes or rests into a bar to fill the bar
according to the time signature in force at that point of the staff,
the notes will spill over into a new bar.  If necessary, some notes or
rests may be split and tied over the bar line in order to maintain a
bar length as close as possible to the `correct' length.  If you then
insert more notes before a tied note so as to push it entirely over
into the next bar, it will be rejoined into a single note.

   See also [*note Considerations in inserting notes::.].


File: rosehelp.info,  Node: Considerations in inserting notes,  Next: Using the editing cursor,  Prev: Inserting notes and signs,  Up: Editor

   Considerations in inserting notes                Procedure

   After a note or other item has been inserted, the stave will be
reformatted and redisplayed with the new item in place.  This could
cause a considerable change in the layout of the stave: for instance,
inserting a very short note into a bar previously containing only
fairly long ones will cause the bar to become vastly wider.

   Inserting an item can have an effect on other items after it in its
staff.  For instance, inserting a clef will change the pitch of any
notes following it, and inserting a key signature may alter any
accidentals displayed on subsequent notes.

   In any case, the display of notes depends to some extent upon the key
signature.  For example: a flattened note entered into a piece whose
key signature already lists a flat for a note of that pitch will be
displayed without the flat; a note entered into a piece with a sharp in
the key signature for a note of that pitch will be displayed with an
explicit natural sign, unless the "Follow Key" option on the Palette is
ticked; and so on.  Similarly, display of notes can be affected by the
presence of accidentals on notes earlier in the same bar.


File: rosehelp.info,  Node: Using the editing cursor,  Next: Editing and using the clipboard,  Prev: Considerations in inserting notes,  Up: Editor

   Using the editing cursor                Procedure

   Editing music in any other way than simply inserting notes and signs
requires that the program be in edit mode.  This mode is enabled
whenever insert mode isn't: i.e., when no insertable items are selected
on the Palette window (see [*note Inserting notes and signs::.] and
[*note Using the Palette::.] for further explanations).  You can enter
edit mode by clicking again on the selected item on the palette to
clear its selection, or by clicking with the right mouse button over
the main window.  When the editor is in edit mode, the mouse pointer
turns into an I-shaped bar upon entering the main edit window.

   There are two fundamental editing selection techniques: placing the
cursor, and sweeping out an area.  Almost every editing function
requires that one or the other of these be carried out to select which
bit of music the editing should affect.

   To place the cursor, simply click with the first mouse button when
the mouse pointer is over some area of musical staff on the main edit
window.  A tall, narrow cursor sigil will be drawn beneath the cursor.
Subsequent clicks elsewhere will move the cursor, and scrolling the
stave (see [*note Moving around::.]) or entering insert mode (see
[*note Inserting notes and signs::.]) will cause the cursor to be
removed.  For examples of functions which can be executed when the
cursor has been placed, see [*note Editing and using the clipboard::.],
[*note Operations on staffs::.], [*note Changing bar properties::.],
[*note Tempos and times::.] and [*note Adding text::.].

   To sweep out an area, first click with the first mouse button over an
area on a staff; and then,  without releasing the mouse button, drag
the mouse left or right along the staff.  A rectangular area will be
swept out to follow the pointer as you move the mouse; its edges will
always `snap' to enclose the nearest musical item on the staff.  Once
an area has been swept, there are various functions available which
affect only the contents of that area: for examples, see [*note Editing
and using the clipboard::.], [*note Grouping::.] and [*note Marking
chords::.].


File: rosehelp.info,  Node: Editing and using the clipboard,  Next: Grouping,  Prev: Using the editing cursor,  Up: Editor

   Editing and using the clipboard                Procedure

   The [*note Editor Edit::.] menu provides several general functions
for editing music.  Several of these require that an area has been
swept out or that the editing cursor is placed (see [*note Using the
editing cursor::.]).

   There is one general editing function, [*note Editor Edit -
Delete::.], which deletes all items enclosed in the area swept out on
the main window.

   There are four functions for manipulating the editor's clipboard.
The clipboard is a tool for temporarily storing sections of music: they
can be taken from the main window and stored in the clipboard until (or
in case) they are needed later.  The clipboard can only store one clip
of music at a time, and it can only be from one staff, although there
is no limit on its length.  To store something in the clipboard, sweep
out an area on the main window and then use [*note Editor Edit -
Cut::.], if you want it also to be removed from the main window, or
[*note Editor Edit - Copy::.] if you want a new copy to be made for the
clipboard and the swept section of music also to stay in place in the
main window.  Either way you will lose anything which may previously
have been held in the clipboard.

   The contents of the clipboard can then be inserted into the music at
a different point: to do so, position the cursor on a staff somewhere,
and use [*note Editor Edit - Paste::.].  The clipboard's contents will
then be inserted into the music at the cursor position.  You can view
the clipboard's contents at any time without using [*note Editor Edit -
Paste::.] by using the [*note Editor Edit - Show Clipboard::.] function.

   The [*note Editor Edit::.] menu also contains the function [*note
Editor Edit - Edit Chord::.].  This requires exactly one chord to be
swept out on the main window.  It allows you to change various aspects
of the chord without deleting and replacing it.


File: rosehelp.info,  Node: Grouping,  Next: Chords,  Prev: Editing and using the clipboard,  Up: Editor

   Grouping                Procedure

   The Rosegarden editor will support

   two kinds of groups: beamed groups

   and triplet (and similar time-domain-perverted)

   groups.

   To group together a series of notes, contain them in a swept area
(see [*note Using the editing cursor::.]) and then select the [*note
Group - Beam::.],

   [*note Group - Simple Tuplet::.] or [*note Group - Tuplet::.]
function from the [*note Group::.] menu.  To ungroup a series of notes
which contains some grouped notes, enclose them in a swept area and
select the [*note Group - Break Group::.] function.  A swept-out series
of items can be grouped even if they are not all chords, although in
order for the [*note Group - Beam::.] function to have any effect, the
series must contain at least two chords.

   If you have a long series of notes which you would like divided into
beamed groups without having them all beamed together into one group,
you can use the [*note Group - Auto Beam::.] function.  This finds
likely-looking sequences of notes within the selected area, and forms
them into beamed groups.  See also [*note Importing MIDI files::.]
(where the same technique is used) for some discussion of how this
process can go wrong.

   The [*note Group::.] menu also provides access to some other
functions for expressing relations between notes.

   Dynamic markings can be added across groups of items, using the
[*note Group - Slur::.], [*note Group - Crescendo::.] and [*note Group
- Decrescendo::.] functions, which decorate a selected series of items
with a slur (or tie, or phrase) marking, or with opening or closing
hairpin dynamic markings respectively.  The latter three functions have
yet to be implemented.


File: rosehelp.info,  Node: Chords,  Next: Operations on staffs,  Prev: Grouping,  Up: Editor

   Chords                Procedure

   Chords can be combined and broken: the [*note Editor Edit - Chord::.]
function takes all the chords within a swept area and replaces them
with one big chord containing notes of every pitch found in any of the
original chords, and the [*note Editor Edit - Unchord::.] function
breaks a chord down into its constituent notes.

   You can also specify complete chords using guitar chord notation with
the [*note Editor Edit - Create Chord::.] function.  This asks for a
chord name, and inserts that chord at the current position of the
editing cursor.


File: rosehelp.info,  Node: Operations on staffs,  Next: Changing bar properties,  Prev: Chords,  Up: Editor

   Operations on staffs                Procedure

   The [*note Stave::.] menu provides several functions for manipulating
the display and content of the staffs in a piece, and how they relate
to each other.

   To add staffs to the score or remove existing staffs, use the [*note
Stave - Add Staff::.] and [*note Stave - Delete Staff::.] functions.

   Adding a staff requires that you choose where the new staff is to go
in the piece: a box is popped up to offer you a choice of at top
(first), at bottom (last), or, if a staff is selected by having the
cursor positioned in it, after the selected staff.  The empty stub of
the new staff will be placed where requested, with default clef and
time signature markings already in place.

   Deleting a staff requires that there is a staff selected with the
cursor.  As deleting a whole staff causes its entire contents to be
lost, a box will be popped up to ask you to confirm the deletion before
it is carried out.

   You can also delete the contents of a staff without removing the
staff from the stave, by using the [*note Stave - Empty Staff::.]
function, which also asks you for confirmation; and you can change the
displayed name of a staff with the [*note Stave - Rename Staff::.]
function.

   Often one staff within a piece of music may end before the others.
If you object to having a gaping hole in the latter part of the score
where a staff has ended, you can use the [*note Stave - Fill To End::.]
function, which fills in the selected staff with rests until it is the
same length as the longest staff in the piece.

   The [*note Stave::.] menu also offers three functions for changing
the relationship between staffs: [*note Stave - Connect Above::.] and
[*note Stave - Connect Below::.] declare that the selected stave
belongs to the same instrument as that above or below it, and that it
should be connected to it.  This is carried out by continuing the bar
lines along to the given staff with solid lines instead of the default
dotted ones.  [*note Stave - Disconnect::.] reverses this by
disconnecting the selected staff from those both above and below it.


File: rosehelp.info,  Node: Changing bar properties,  Next: Tempos and times,  Prev: Operations on staffs,  Up: Editor

   Changing bar properties                Procedure

   The [*note Bar::.] menu contains several functions for changing the
meaning of bar lines, and any instructional indications within the bar
(for which see [*note Tempos and times::.]).  To use any of these
functions, there must be a bar selected by having the cursor placed
within it.

   The [*note Bar - Plain::.], [*note Bar - Double Bar::.], [*note Bar
- Repeat at Start::.] and [*note Bar - Repeat at End::.] functions are
used to change the type of bar line the selected bar has.  [*note Bar -
Plain::.] resets it to having single bar lines at both beginning and
end; the others give it a double bar line at the end, a dotted double
bar line at the beginning and a dotted double bar line at the end,
respectively.

   Normally, the Rosegarden editor reformats the music it contains as it
is entered; it is free to move bar line about as it wishes to ensure
that all the bars are of the same length.  It will however usually
leave double-bars and repeat bars alone (see [*note Bar - Double
Bar::.] for details of exactly how it handles them), so if you want to
make sure later sections of music aren't moved around all over the
place just because you're editing an earlier bit, try putting a double
bar line in somewhere.


File: rosehelp.info,  Node: Tempos and times,  Next: Adding text,  Prev: Changing bar properties,  Up: Editor

   Tempos and times                Procedure

   The [*note Bar::.] menu provides some functions for adding, removing
and changing meta musical indications such as tempo and time markings.

   The [*note Bar - Label::.], [*note Bar - Metronome::.] and [*note
Bar - Time Signature::.] functions change the label, metronome marking
for the bar and time signature.  [*note Bar - Label::.] prompts you for
a textual label, and then if there is no label already present on the
bar, it adds the new label above the opening bar line; otherwise it
replaces the old label with the new one.  Similarly, [*note Bar -
Metronome::.] allows you to enter a new tempo marking and replaces any
existing metronome marking with the it -- there can only be one tempo
marking in a given bar, in whichever staff of the piece --, and [*note
Bar - Time Signature::.] allows you to replace any existing time
signature marking in this bar, or if you wish in the bar at this point
in every staff, with a new one.

   To remove a label or metronome marking from a bar, use the [*note
Bar - Remove Label::.] and [*note Bar - Remove Metronome::.] functions.

   See [*note Changing bar properties::.] for other uses of the [*note
Bar::.] menu.


File: rosehelp.info,  Node: Adding text,  Next: Marking chords,  Prev: Tempos and times,  Up: Editor

   Adding text                Procedure

   The Rosegarden editor allows descriptive and decorative text to be
added to the music in four different styles (in addition to bar labels,
for which see [*note Tempos and times::.]).  To add text, place the
cursor on a staff and then use the [*note Text::.] menu.

   The four functions at the top of the [*note Text::.] menu, the
[*note Text - Add Text options::.], all work in the same way: by
prompting you for some text and then adding it to the music above or
below the position of the cursor.  The difference is in the placement
and style of the text, and the menu entries contain small icons to try
to remind you of the purpose of each one.

   The text styles are as follows:

   -- above the staff, in a smallish font;

   -- a considerable distance above the staff, in a larger font;

   -- below the staff, in a smallish font; and

   -- below the staff, in a smallish font and in italics.

   Text can also be removed using the [*note Text::.] menu; the [*note
Text - Clear Group::.], [*note Text - Clear Bar::.] and [*note Text -
Clear Staff::.] functions remove all text found within a swept-out
area, a bar selected by cursor placement or a staff selected by cursor
placement, respectively.


File: rosehelp.info,  Node: Marking chords,  Next: Importing MIDI files,  Prev: Adding text,  Up: Editor

   Marking chords                Procedure

   The Rosegarden editor supports several types of dynamic markings and
decorations for chords.  Some of these, such as slurs and (de)crescendo
marks, may extend over series of musical items; these are described in
[*note Grouping::.].  Others, such as accents, affect only single
chords (although they can be added to several chords at one go).  This
sort of marking is found on the [*note Marks::.] menu.

   To add marks to chords, first sweep out an area on the stave (see
[*note Using the editing cursor::.]).  (A mark-adding operation will
affect every chord in the swept area, but won't affect any non-chord
items found in the area.)  Then call the [*note Marks::.] menu and
select the relevant function for the type of mark you need, and that
mark will be placed over your selected chords.

   To remove marks, sweep out an area and then use the `Unmark' function
on the [*note Marks::.] menu.  Any marks present on any chords within
the swept area will be deleted.


File: rosehelp.info,  Node: Importing MIDI files,  Next: Exporting MIDI files,  Prev: Marking chords,  Up: Editor

   Importing MIDI files                Procedure

   The Rosegarden editor includes powerful (but by no means infallible)
facilities for reading and generating MIDI files.  These are available
from the [*note Editor Tools::.] menu.

   To read in a MIDI file and display it in musical notation for
subsequent editing, use the [*note Editor Tools - Import MIDI::.]
function.  This prompts you for the name of a MIDI file to open (see
[*note File Boxes::.]), prompts for quantization levels in the same way
as the Sequencer's [*note Track - Quantize::.] function, and reads it
in as a new buffer.  There is no disc file associated with the new
buffer, so in order to save it as a new editor file you must use the
[*note Editor File - Save As::.] function, not [*note Editor File -
Save::.].

   The [*note Editor Tools - Import MIDI::.] function can only deal
with MIDI Type 0 (single track) and Type 1 (simultaneous track) files;
if you have a Type 2 (sequential track) file, use [*note The Rosegarden
Sequencer::.] to divide it into separate files before editing.  (See
[*note Organising recorded data::.] for help in managing different
types of files in the sequencer.)  MIDI Type 1 files often reserve the
first track for file meta-events such as key and tempo events; the
editor checks for this, and if it finds no actual notes in the first
track, that track will not be displayed (although it will still be
processed to obtain meta-event information for the other tracks).

   The editor attempts to maintain the correct clef, key and tempo
markings for the MIDI file, to arrange its note pitches and lengths
sensibly and to beam together groups of quavers and shorter notes in a
likely way.  When it gets something wrong, it is likely to be for one
of these two reasons:

   -- The MIDI file is quantized to too short a note length.  In this
case, a note which should fill a certain length (say for example a
quaver) may be interpreted a a shorter note plus a rest (such as a
dotted semiquaver and a demisemiquaver rest) because it has been
released too soon.  This can ruin the layout of the piece more
effectively than you might imagine.  Quantizing can be a tricky
process: if the file does actually contain some genuinely short notes,
quantizing may lose them; and forms such as triplets may be lost.

   Whilst the Rosegarden Editor can quantize MIDI files on import, there
are more possibilities available if you use [*note The Rosegarden
Sequencer::.] to inspect and quantize files before trying to import
them into the editor: see [*note Organising recorded data::.] and
[*note Preparing a MIDI file for the Editor::.] for help on quantizing
in the sequencer and transferring files directly from the sequencer to
the editor.

   -- The MIDI file contains the wrong time signature for the piece.  As
compound times (6/8, 9/16 and so on) are normally beamed in groups of
multiples of three notes, and simple times in groups of multiples of
two, a file which gives the wrong time signature can be wrongly beamed.
This often happens where the file has the default signature of 4/4,
but should in fact be in 6/8 or some other such time.

   -- The MIDI file contains triplets or other stretched or squashed
series of notes.  There is no portable way to represent such forms in
MIDI, and the editor isn't clever enough to know when the note lengths
should suggest that triplets were intended.

   -- The beaming algorithm employed by the editor has failed.  This can
often happen in conjunction with quantizing problems, or when the piece
is in an unusual time signature; usually it means that the beamer has
become out of phase with the beat of the music, and can no longer find
any likely-looking groups to beam.  There is very little that you can
do about this, except ensure that the file is properly quantized and be
prepared to do some editing after it has been imported.


File: rosehelp.info,  Node: Exporting MIDI files,  Next: Playing a piece of music,  Prev: Importing MIDI files,  Up: Editor

   Exporting MIDI files                Procedure

   The editor is capable of producing MIDI Type 1 (simultaneous track)
files from the music in its buffers.  MIDI files can be used as a
standard musical interchange format for sequencers and synthesisers;
they are also accepted by some other notation programs.  Using MIDI
files to store music intended for further editing using the Rosegarden
editor later is not recommended because, although they take
considerably less disc space than Rosegarden editor files, they cannot
store all the necessary information on grouping, marking, dynamics,
text and so on.

   To write the current buffer out to a file in MIDI format, use the
[*note Editor Tools - Export MIDI::.] function on the [*note Editor
Tools::.] menu.  You will be prompted for a file in which to put the
MIDI output (see [*note File Boxes::.]), and the buffer will be
immediately written out to that file as MIDI.  The contents of the
buffer in the editor will be unaffected.

   For details of how to send MIDI data directly to [*note The
Rosegarden Sequencer::.] without having to write them to a file in
between, see [*note Playing a piece of music::.] and [*note Sequencing
a piece of music::.].


File: rosehelp.info,  Node: Playing a piece of music,  Next: Sequencing a piece of music,  Prev: Exporting MIDI files,  Up: Editor

   Playing a piece of music                Procedure

   To hear the music in the current buffer, you can use the [*note
Editor Tools - Play MIDI::.] function on the [*note Editor Tools::.]
menu to invoke [*note The Rosegarden Sequencer::.] and request it to
play the music through its default MIDI output device.  See [*note
Playing a MIDI file::.] for comments on how the sequencer will
interpret this request.

   This function requires that the complete Rosegarden suite is running:
the editor must have been started up from [*note The Rosegarden Top
Box::.], and the sequencer must be available for execution (although it
need not have been started up yet).


File: rosehelp.info,  Node: Sequencing a piece of music,  Next: Exporting MusicTeX files,  Prev: Playing a piece of music,  Up: Editor

   Sequencing a piece of music                Procedure

   The [*note Editor Tools - Sequence MIDI::.] function on the [*note
Editor Tools::.] menu allows you to sequence the MIDI representation of
a musical buffer immediately, without having to export it to a file and
load it into a sequencer later.  Selecting the function causes the
contents of the current buffer to be sent to [*note The Rosegarden
Sequencer::.] in MIDI Type 1 format.  If the sequencer is already
running, it will be sent the data and will raise its window to the
front of the display when ready; otherwise, it will be started up
automatically.

   This function requires that the complete Rosegarden suite is running:
the editor must have been started up from [*note The Rosegarden Top
Box::.], and the sequencer must be either already running, or available
for execution.


File: rosehelp.info,  Node: Exporting MusicTeX files,  Next: Customising the editor,  Prev: Sequencing a piece of music,  Up: Editor

   Exporting MusicTeX files                Procedure

   MusicTeX is a music typesetting language which consists of a set of
macros working on top of the TeX typesetting language.  In order to
make use of MusicTeX files such as those produced by the Rosegarden
editor, your system must be equipped with the TeX program, the MusicTeX
package and a suitable set of fonts for printing music and drivers for
sending the output to your printer.

   To produce MusicTeX output, select the [*note Editor Tools - Export
MusicTeX::.] function and choose a file in which to save the output
(see [*note File Boxes::.]).  The current buffer will be processed and
a MusicTeX transcription of it placed in the selected file.


File: rosehelp.info,  Node: Customising the editor,  Next: Editor File,  Prev: Exporting MusicTeX files,  Up: Editor

   Customising the editor                Procedure

   Run-time customisation is intended to be available through the
[*note Editor Tools - Preferences::.] function on the [*note Editor
Tools::.] menu.  This has not yet been implemented.


File: rosehelp.info,  Node: Editor File,  Next: Editor File - New,  Prev: Customising the editor,  Up: Editor

   Editor File                Menu

   The File menu on the Rosegarden Editor contains functions for editing
new buffers, loading, saving and printing buffers and exiting the
application.  It doesn't contain functions for less basic file
operations such as manipulating MIDI or MusicTeX files: these are found
on the [*note Editor Tools::.] menu.

   The File menu also lists the names of all buffers which have been
opened since the editor was started and which have not been closed
since.  Selecting one of these names switches to editing that buffer.
Notice that the entire contents of every file you open in the editor
are held in memory until its closure (see [*note Editor File -
Close::.]); opening many large files may affect the performance of the
editor or of the computer.


File: rosehelp.info,  Node: Editor File - New,  Next: Editor File - Open,  Prev: Editor File,  Up: Editor

   Editor File - New                Function

   This function is part of the [*note Editor File::.] menu.

   Creates an empty piece of music for editing, first asking you how
many staffs you need in the score.  Initialises the staff names, clefs
and time signatures to a default set, all of which may be changed
afterwards.

   See [*note Starting a new piece of music::.].


File: rosehelp.info,  Node: Editor File - Open,  Next: Editor File - Close,  Prev: Editor File - New,  Up: Editor

   Editor File - Open                Function

   This function is part of the [*note Editor File::.] menu.

   Opens a previously saved file for editing.  See also [*note Opening
an editor file::.].

   For a description of how the file selection box works, see [*note
File Boxes::.].

   The file format used by Rosegarden has changed since the last
release (v2.0 beta 1); if you try to open an `old' Rosegarden file
using this function, it will fail but will offer to import the file as
an old-format file instead (in the same way as if you had asked to load
it using the [*note Editor Tools - Import Old Rosegarden File::.]
function).


File: rosehelp.info,  Node: Editor File - Close,  Next: Editor File - Include,  Prev: Editor File - Open,  Up: Editor

   Editor File - Close                Function

   This function is part of the [*note Editor File::.] menu.

   Closes and removes the buffer currently being edited, first giving
you the option of saving any changes you may have made to it.


File: rosehelp.info,  Node: Editor File - Include,  Next: Editor File - Save,  Prev: Editor File - Close,  Up: Editor

   Editor File - Include                Function

   This function is part of the [*note Editor File::.] menu.

   Opens a previously saved file and inserts its contents at the current
cursor position.  Either the current buffer or the newly inserted
section of music may be altered in cases where they don't match: for
instance, if they have differing numbers of staffs.

   This function has not yet been implemented.


File: rosehelp.info,  Node: Editor File - Save,  Next: Editor File - Save As,  Prev: Editor File - Include,  Up: Editor

   Editor File - Save                Function

   This function is part of the [*note Editor File::.] menu.

   Saves the buffer currently being edited into its associated disc
file.  This is only possible if it was originally loaded using [*note
Editor File - Open::.], or if it has previously been saved by use of
[*note Editor File - Save As::.]).  See also [*note Saving an editor
file::.].


File: rosehelp.info,  Node: Editor File - Save As,  Next: Editor File - Print,  Prev: Editor File - Save,  Up: Editor

   Editor File - Save As                Function

   This function is part of the [*note Editor File::.] menu.

   Saves the buffer currently being edited into a new file, prompting
you for a file name.  See [*note Saving an editor file::.].

   For a description of how the file selection box works, see [*note
File Boxes::.].


File: rosehelp.info,  Node: Editor File - Print,  Next: Editor File - Exit,  Prev: Editor File - Save As,  Up: Editor

   Editor File - Print                Function

   This function is part of the [*note Editor File::.] menu.

   Sends the current buffer to a PostScript (tm) printer or to a file in
PostScript format.

   This function has not yet been implemented.


File: rosehelp.info,  Node: Editor File - Exit,  Next: Editor Edit,  Prev: Editor File - Print,  Up: Editor

   Editor File - Exit                Function

   This function is part of the [*note Editor File::.] menu.

   Exits the application, offering the option of saving any changed
buffers first.


File: rosehelp.info,  Node: Editor Edit,  Next: Editor Edit - Undo,  Prev: Editor File - Exit,  Up: Editor

   Editor Edit                Menu

   The Edit menu yields functions for manipulating the clipboard (cut,
copy and paste), plus a couple of other general editing functions.  See
[*note Editing and using the clipboard::.] for an overview of the Edit
menu.


File: rosehelp.info,  Node: Editor Edit - Undo,  Next: Editor Edit - Delete,  Prev: Editor Edit,  Up: Editor

   Editor Edit - Undo                Function

   This function is part of the [*note Editor Edit::.] menu.

   Undoes the effect of the last change to the buffer.

   This function has not yet been implemented.


File: rosehelp.info,  Node: Editor Edit - Delete,  Next: Editor Edit - Cut,  Prev: Editor Edit - Undo,  Up: Editor

   Editor Edit - Delete                Function

   This function is part of the [*note Editor Edit::.] menu.

   Deletes the contents of the selected area.


File: rosehelp.info,  Node: Editor Edit - Cut,  Next: Editor Edit - Copy,  Prev: Editor Edit - Delete,  Up: Editor

   Editor Edit - Cut                Function

   This function is part of the [*note Editor Edit::.] menu.

   Deletes the contents of the selected area, moving them into the
clipboard.  The previous contents of the clipboard, if any, are lost.


File: rosehelp.info,  Node: Editor Edit - Copy,  Next: Editor Edit - Paste,  Prev: Editor Edit - Cut,  Up: Editor

   Editor Edit - Copy                Function

   This function is part of the [*note Editor Edit::.] menu.

   Copies the contents of the selected area to the clipboard.  The
previous contents of the clipboard, if any, are lost.


File: rosehelp.info,  Node: Editor Edit - Paste,  Next: Editor Edit - Show Clipboard,  Prev: Editor Edit - Copy,  Up: Editor

   Editor Edit - Paste                Function

   This function is part of the [*note Editor Edit::.] menu.

   Inserts the contents of the clipboard into the current buffer at the
cursor position.  The clipboard itself is not changed.


File: rosehelp.info,  Node: Editor Edit - Show Clipboard,  Next: Editor Edit - Chord,  Prev: Editor Edit - Paste,  Up: Editor

   Editor Edit - Show Clipboard                Function

   This function is part of the [*note Editor Edit::.] menu.

   Pops up a small window showing the contents of the clipboard.


File: rosehelp.info,  Node: Editor Edit - Chord,  Next: Editor Edit - Unchord,  Prev: Editor Edit - Show Clipboard,  Up: Editor

   Editor Edit - Chord                Function

   This function is part of the [*note Editor Edit::.] menu.

   Transforms the chords within the selected area into a single chord.
This chord will contain a note of every pitch found in the selected
area, and its length will be that of the last chord in the area.


File: rosehelp.info,  Node: Editor Edit - Unchord,  Next: Editor Edit - Create Chord,  Prev: Editor Edit - Chord,  Up: Editor

   Editor Edit - Unchord                Function

   This function is part of the [*note Editor Edit::.] menu.

   Transforms the single chord within the selected area into a sequence
of one-note chords.  One chord will be created for every pitch found in
the original chord.  No guarantee is made about the order in which the
new chords will appear.


File: rosehelp.info,  Node: Editor Edit - Create Chord,  Next: Editor Edit - Edit Chord,  Prev: Editor Edit - Unchord,  Up: Editor

   Editor Edit - Create Chord                Function

   This function is part of the [*note Editor Edit::.] menu.  It allows
you to make chords by describing them in guitar chord notation.

   The Create Chord dialog will accept one or several comma-separated
chord names in standard "Jazz" notation (e.g. C, Gm, Amaj7, E\#9) and
insert them on the staff at the point of the current editing cursor.

   Rosegarden is pretty tolerant on the "syntax" used to name the chord
you wish to insert, and should recognize most of the chord names you
can find in common music scores.

   Here are a few rules and examples for the sake of clarity, which you
should recognize as those you're already familiar with, give or take a
few restrictions inherent to the ASCII nature of the thing:

   -- The root and the altered bass (if any) should always be specified
with a capital letter.

   -- The altered bass should be specified with a leading slash
character (`/'), e.g. C/G (C major with a G bass).

   -- Minor chords should be named with an lower case `m', not a minus
sign: Cm.

   -- Power chords (root, 5th, octave) should be noted with a trailing
5: C5

   -- Chord complexity can go up to the 13th: C7, C9, C11, C13.

   -- Suspended, diminished and augmented chords should be noted as
follows, respectively: Csus (i.e. Csus4), Csus2, Cdim (Cdim7 should
work), Caug (i.e. C+).

   -- Major seventh chord should be named as Cmaj7.

   -- Added 9th, 11th and 13th should be noted as Cadd9, Cadd11 and so
on.

   -- Altered notes should be specified with leading `-' (`b') or `+'
(`\#') signs: C-5, C7-5, C7\#9, C6b11, C13+9.  Only the 5th, 9th, 11th
and 13th can be specified as being altered this way.

   Note that a `\#' or `b' right after the root will always be treated
as altering the root itself and not the following note.  So Ab5 is an Ab
power chord, not an A major with a flattened fifth.  Use `+' or `-' to
express this: A-5.

   The Create Chord module, and this help text, were written and
contributed by Guillaume Laurent.


File: rosehelp.info,  Node: Editor Edit - Edit Chord,  Next: Stave,  Prev: Editor Edit - Create Chord,  Up: Editor

   Editor Edit - Edit Chord                Function

   This function is part of the [*note Editor Edit::.] menu.

   Invokes a window containing functions for making changes to various
properties of the selected chord.

   The chord edit window is split into three parts:

   -- The chord display, plus four directional buttons.  The display
itself shows the chord and the clef it's in on the stave.  One of the
note heads of the chord (if it has more than one head) is indicated
with an arrow.  Clicking the up and down buttons, above and below the
chord display, moves the pitch of the indicated note head up or down by
one semitone respectively.  Clicking the left and right buttons
decreases or increases the length of the chord.

   -- A label showing which head of the chord is indicated; if the chord
has more than one head, this can be changed by clicking the arrow
buttons on the left and right of this label.  Changing the indicated
head will move the indicating arrow on the chord display up or down
accordingly, and subsequent pitch changes will act upon the newly
indicated note-head.

   -- A set of `OK', `Cancel' and `Help' buttons.


File: rosehelp.info,  Node: Stave,  Next: Stave - Add Staff,  Prev: Editor Edit - Edit Chord,  Up: Editor

   Stave                Menu

   The Stave menu contains functions for manipulating the stave by
adding or removing staffs, performing staff-wide changes or altering the
properties of each staff.  Most of these are only available when a
staff has been "selected", by positioning the cursor in it.  More local
changes, such as changing the time signature, are found on the [*note
Bar::.] menu.

   See [*note Operations on staffs::.] for an overview of the functions
on the Stave menu.


File: rosehelp.info,  Node: Stave - Add Staff,  Next: Stave - Delete Staff,  Prev: Stave,  Up: Editor

   Stave - Add Staff                Function

   This function is part of the [*note Stave::.] menu.

   Adds a blank staff to the piece, first asking you where to place it.
Staffs can be added first or last; if you've already placed the cursor
on a particular staff, you can also choose to insert the new staff
after than one on the score.


File: rosehelp.info,  Node: Stave - Delete Staff,  Next: Stave - Empty Staff,  Prev: Stave - Add Staff,  Up: Editor

   Stave - Delete Staff                Function

   This function is part of the [*note Stave::.] menu.

   Deletes the staff containing the cursor, and its entire contents.


File: rosehelp.info,  Node: Stave - Empty Staff,  Next: Stave - Rename Staff,  Prev: Stave - Delete Staff,  Up: Editor

   Stave - Empty Staff                Function

   This function is part of the [*note Stave::.] menu.

   Deletes the entire contents of the staff containing the cursor.


File: rosehelp.info,  Node: Stave - Rename Staff,  Next: Stave - Connect Above,  Prev: Stave - Empty Staff,  Up: Editor

   Stave - Rename Staff                Function

   This function is part of the [*note Stave::.] menu.

   Allows you to enter a new name for the staff containing the cursor.
This name is displayed to the left of the staff, and is used as the
track name when that staff is exported in a MIDI file (see [*note
Editor Tools - Export MIDI::.]).


File: rosehelp.info,  Node: Stave - Connect Above,  Next: Stave - Connect Below,  Prev: Stave - Rename Staff,  Up: Editor

   Stave - Connect Above                Function

   This function is part of the [*note Stave::.] menu.

   Declares that the staff containing the cursor is to be connected to
that immediately above it; for example, if they belong to the same
instrument.  Bar lines are drawn in solid lines (as opposed to the
usual dotted lines) between connected staffs.

   This function has not yet been implemented.


File: rosehelp.info,  Node: Stave - Connect Below,  Next: Stave - Disconnect,  Prev: Stave - Connect Above,  Up: Editor

   Stave - Connect Below                Function

   This function is part of the [*note Stave::.] menu.

   Declares that the staff containing the cursor is to be connected to
that immediately below it; for example, if they belong to the same
instrument.  Bar lines are drawn in solid lines (as opposed to the
usual dotted lines) between connected staffs.

   This function has not yet been implemented.


File: rosehelp.info,  Node: Stave - Disconnect,  Next: Stave - Fill To End,  Prev: Stave - Connect Below,  Up: Editor

   Stave - Disconnect                Function

   This function is part of the [*note Stave::.] menu.

   Declares that the staff containing the cursor is not to be connected
to any other above or below it.  This is the default state for staffs,
and this function is normally used to negate the effect of [*note Stave
- Connect Above::.] or [*note Stave - Connect Below::.].

   This function has not yet been implemented.


File: rosehelp.info,  Node: Stave - Fill To End,  Next: Group,  Prev: Stave - Disconnect,  Up: Editor

   Stave - Fill To End                Function

   This function is part of the [*note Stave::.] menu.

   Ensures that the staff containing the cursor is of the same length as
the longest staff in the current buffer.  This is effected by filling
up the staff with rests, from the end of the last note or rest in it up
to the end of the piece.

   This function has not yet been implemented.


File: rosehelp.info,  Node: Group,  Next: Group - Tie,  Prev: Stave - Fill To End,  Up: Editor

   Group                Menu

   The Group menu contains functions which act on selected areas of
music.  These are only available when an area has been swept out with
the pointer.  There are functions to carry out actions such as beaming
groups, adding or removing slurs, forming triplets and such like.

   See also [*note Grouping::.], which contains an overview of these
functions.


File: rosehelp.info,  Node: Group - Tie,  Next: Group - Slur,  Prev: Group,  Up: Editor

   Group - Tie                Function

   This function is part of the [*note Group::.] menu.

   Ties together two adjacent chords so as to play them as one long
chord. You can only tie together two chords at a time, and they must be
adjacent and have identical sets of pitches. To remove a tie, drag out
the same two chords and use the [*note Group - Remove Indication::.]
function.

   Tie information is used in producing MIDI output.


File: rosehelp.info,  Node: Group - Slur,  Next: Group - Crescendo,  Prev: Group - Tie,  Up: Editor

   Group - Slur                Function

   This function is part of the [*note Group::.] menu.

   Places a slur (or phrase) mark over the selected group of items.  To
remove a slur, drag out the same area and use the [*note Group - Remove
Indication::.] function.

   Slur marks are not currently considered when producing MIDI from a
score.


File: rosehelp.info,  Node: Group - Crescendo,  Next: Group - Decrescendo,  Prev: Group - Slur,  Up: Editor

   Group - Crescendo                Function

   This function is part of the [*note Group::.] menu.

   Places a crescendo mark (opening hairpin) below the selected items.
To remove a crescendo mark, drag out the same area and use the [*note
Group - Remove Indication::.] function.

   Crescendo marks are not currently considered when producing MIDI from
a score.


File: rosehelp.info,  Node: Group - Decrescendo,  Next: Group - Remove Indication,  Prev: Group - Crescendo,  Up: Editor

   Group - Decrescendo                Function

   This function is part of the [*note Group::.] menu.

   Places a decrescendo mark (closing hairpin) below the selected items.
To remove a decrescendo mark, drag out the same area and use the [*note
Group - Remove Indication::.] function.

   Decrescendo marks are not currently considered when producing MIDI
from a score.


File: rosehelp.info,  Node: Group - Remove Indication,  Next: Group - Beam,  Prev: Group - Decrescendo,  Up: Editor

   Group - Remove Indication                Function

   This function is part of the [*note Group::.] menu.

   Removes any slurs, ties or crescendo or decrescendo marks which start
and end completely within the selected area.


File: rosehelp.info,  Node: Group - Beam,  Next: Group - Simple Tuplet,  Prev: Group - Remove Indication,  Up: Editor

   Group - Beam                Function

   This function is part of the [*note Group::.] menu.

   Beams together the selected chords.  The angle and placement of the
beam are entirely at the editor program's own discretion.


File: rosehelp.info,  Node: Group - Simple Tuplet,  Next: Group - Tuplet,  Prev: Group - Beam,  Up: Editor

   Group - Simple Tuplet                Function

   This function is part of the [*note Group::.] menu.

   Forms the selected chords into a triplet group, or similarly
structured group (containing however many notes you have selected).

   The Simple Tuplet function will form a group of three notes into a
triplet group, four notes into a group which plays in the time of
three, five notes into a group playing in the time of four, and so on.
(As a special case, a group of two notes will be made to play in the
time of three, rather than one.)

   Using the Simple Tuplet function always has the same effect as using
the [*note Group - Tuplet::.] function and then accepting the default
tuplet setup from its dialogue box.


File: rosehelp.info,  Node: Group - Tuplet,  Next: Group - Break Group,  Prev: Group - Simple Tuplet,  Up: Editor

   Group - Tuplet                Function

   This function is part of the [*note Group::.] menu.

   Forms the selected chords into a triplet or other tuplet group.

   This function allows you to re-express a group of any number of beats
so as to play in the time of any other number.  This allows you to make
triplet groups, but also a lot of other madly stretched or squashed
groups.

   When this function is activated, it will first show a dialogue box
for you to select the particular kind of tuplet you want for the group
of notes.  This gives you two things to change:

   -- a menu offering all the possible expressions of the current length
of the selected group in terms of basic notes of various lengths.  For
instance, if you have selected a group containing a crotchet and a
quaver, you will be offered the choice of considering it as three
quavers, six semiquavers, twelve demisemiquavers, four dotted
semiquavers or various other possibilities.

   -- a field in which you can enter the number of your selected basic
notes in which you want the group re-expressed.

   Thus to play a crotchet and quaver group in triplet time, you'd
select "3 quavers" as the original time of the group and "2" as the
number of quavers to squash it into.  For a more ambitious tuplet
group, you might draw say 14 semiquavers and then ask to squash them
into the time of say 8.  Anything is possible (and most of it turns up
in real music, somewhere).

   The Tuplet dialogue box will normally attempt to give you a sensible
default choice -- for instance, if you have selected a group three
quavers long, you will be offered default selections corresponding to
quaver triplets.

   Tuplet groups are always displayed with beams, if the constituent
notes are short enough, and if you make tuplets of notes already
grouped, the containing group will be broken.

   Note that Rosegarden will not normally split tuplet groups across bar
lines.  It is possible to split up tuplet groups in certain situations
(for instance by making a beamed group from part of an existing tuplet
group); the results may be unexpected.

   Notice also that it isn't possible to see, by looking at a tuplet
group out of context, what time it's supposed to be played in.  For
instance, a group of three quavers marked with a 3 may be intended to
play in the time of four, rather than the usual two.  The only way to
work out the intention is to look at the time signature and do some
arithmetic.  (This is a restriction of the musical notation, not of
Rosegarden.)


File: rosehelp.info,  Node: Group - Break Group,  Next: Group - Auto Beam,  Prev: Group - Tuplet,  Up: Editor

   Group - Break Group                Function

   This function is part of the [*note Group::.] menu.

   Breaks up any groups which have been formed on the items within the
selected area.  This undoes the effect of any uses of [*note Group -
Beam::.] and [*note Group - Tuplet::.] on any of the selected items.


File: rosehelp.info,  Node: Group - Auto Beam,  Next: Group - Transpose,  Prev: Group - Break Group,  Up: Editor

   Group - Auto Beam                Function

   This function is part of the [*note Group::.] menu.

   Searches for sequences of notes within the selected area which could
be beamed together but aren't, and beams them.  The beaming algorithm
is the same as that used when importing MIDI (see [*note Importing MIDI
files::.]); it is not guaranteed to make a good job of it.

   Using this function will (probably) not disturb any beamed groups
already present in the selected area.  If you want to unbeam the area
first, use [*note Group - Break Group::.] on it first.

   This function has not yet fully implemented.


File: rosehelp.info,  Node: Group - Transpose,  Next: Group - Invert,  Prev: Group - Auto Beam,  Up: Editor

   Group - Transpose                Function

   This function is part of the [*note Group::.] menu.

   Transposes a section of music, first prompting you to enter the
number of semitones by which to transpose the music up or down.

   If an area is selected, its contents are transposed; if the cursor is
placed but no area is swept out, the contents of the staff containing
the cursor are transposed, from the cursor position to the end of the
staff; if no area is swept and the cursor is not placed, the whole
piece is transposed.

   Note that transposition is in terms of semitones and not the current
key or harmony.


File: rosehelp.info,  Node: Group - Invert,  Next: Group - Retrograde,  Prev: Group - Transpose,  Up: Editor

   Group - Invert                Function

   This function is part of the [*note Group::.] menu.

   Inverts a section of music, first prompting you to enter the number
of semitones by which the first note of the group differs from the
central (fixed) point of the inversion.

   If an area is selected, its contents are inverted; if the cursor is
placed but no area is swept out, the contents of the staff containing
the cursor are inverted, from the cursor position to the end of the
staff; if no area is swept and the cursor is not placed, the whole
piece is inverted.

   Note that inversion is in terms of semitones and not the current key
or harmony.


File: rosehelp.info,  Node: Group - Retrograde,  Next: Bar,  Prev: Group - Invert,  Up: Editor

   Group - Retrograde                Function

   This function is part of the [*note Group::.] menu.

   If an area is selected, its contents are reversed in retrograde
motion; if the cursor is placed but no area is swept out, the contents
of the staff containing the cursor are reversed, from the cursor
position to the end of the staff; if no area is swept and the cursor is
not placed, the whole piece is reversed.


File: rosehelp.info,  Node: Bar,  Next: Bar - Plain,  Prev: Group - Retrograde,  Up: Editor

   Bar                Menu

   The Bar menu contains functions which affect one or more bars.  For
these to be available, a bar must be "selected", by positioning the
cursor in it.  There are functions to change the properties of the
selected bar (such as [*note Bar - Repeat at Start::.]), and also to
effect changes upon the whole of the music from the selected bar
onwards (such as [*note Bar - Time Signature::.]).

   See [*note Changing bar properties::.] and [*note Tempos and
times::.] for an introduction to the Bar menu.


File: rosehelp.info,  Node: Bar - Plain,  Next: Bar - Double Bar,  Prev: Bar,  Up: Editor

   Bar - Plain                Function

   This function is part of the [*note Bar::.] menu.

   Makes the bar containing the cursor into a plain bar, with single bar
lines at both ends.


File: rosehelp.info,  Node: Bar - Double Bar,  Next: Bar - Repeat at Start,  Prev: Bar - Plain,  Up: Editor

   Bar - Double Bar                Function

   This function is part of the [*note Bar::.] menu.

   Places a double bar line at the end of the bar containing the cursor.

   You can only place double bar lines at points where there is already
some music present on every staff in the score; the staffs will then
all acquire the double bar and will also all be connected with a dotted
line.

   Rosegarden always tries to keep double bar lines in the same place as
you originally placed them.  In practice this means they always remain
immediately before the item (note, rest or whatever) that was at the
start of the bar following the one you asked to place the double bar
after.  In keeping the double bar line associated with that item,
Rosegarden will happily ignore the fact that there may at some
subsequent point be the wrong number of beats in the bar before it.

   If you remove the item immediately after a double bar line, the bar
line might also disappear, to be replaced by a simple single bar.  This
is a side-effect of Rosegarden's attempts to keep the double bar
associated with the same item (and is a known bug).

   The editor may also show strange side-effects if you try to place a
double bar line at a point where there are tied notes on one or more
staffs - those staffs will not acquire the double bar, even when the
tied notes are rejoined.  (See [*note Inserting notes and signs::.] for
an explanation of automatically-tied notes.)


File: rosehelp.info,  Node: Bar - Repeat at Start,  Next: Bar - Repeat at End,  Prev: Bar - Double Bar,  Up: Editor

   Bar - Repeat at Start                Function

   This function is part of the [*note Bar::.] menu.

   Places a double bar line with repeat dots at the start of the bar
containing the cursor.  Repeat information is currently ignored when
playing and sequencing music.


File: rosehelp.info,  Node: Bar - Repeat at End,  Next: Bar - Label,  Prev: Bar - Repeat at Start,  Up: Editor

   Bar - Repeat at End                Function

   This function is part of the [*note Bar::.] menu.

   Places a double bar line with repeat dots at the end of the bar
containing the cursor.  Repeat information is currently ignored when
playing and sequencing music.


File: rosehelp.info,  Node: Bar - Label,  Next: Bar - Remove Label,  Prev: Bar - Repeat at End,  Up: Editor

   Bar - Label                Function

   This function is part of the [*note Bar::.] menu.

   Prompts for a textual label for the bar containing the cursor.  The
label is displayed above the bar line at the start of the bar, and
replaces any label previously marking that bar.

   Labels are actually associated with sections of notes, rather than
bar lines; therefore, if the music in the current bar is moved left or
right as a result of editing something before it, the label will travel
with it.


File: rosehelp.info,  Node: Bar - Remove Label,  Next: Bar - Metronome,  Prev: Bar - Label,  Up: Editor

   Bar - Remove Label                Function

   This function is part of the [*note Bar::.] menu.

   Removes any label currently marking the bar containing the cursor.


File: rosehelp.info,  Node: Bar - Metronome,  Next: Bar - Remove Metronome,  Prev: Bar - Remove Label,  Up: Editor

   Bar - Metronome                Function

   This function is part of the [*note Bar::.] menu.

   Prompts for a pairing of a note length and a tempo indication, to be
placed above the bar containing the cursor.  The tempo indication is
assumed to express the number of notes of the given length whose
lengths together amount to one minute, and is preserved in any MIDI
output generated from this buffer (see [*note Editor Tools - Export
MIDI::.]).

   In which staff the cursor is currently placed is not important.


File: rosehelp.info,  Node: Bar - Remove Metronome,  Next: Bar - Time Signature,  Prev: Bar - Metronome,  Up: Editor

   Bar - Remove Metronome                Function

   This function is part of the [*note Bar::.] menu.

   Removes any metronome marking found above the bar containing the
cursor.  In which staff the cursor is currently placed is not important.


File: rosehelp.info,  Node: Bar - Time Signature,  Next: Bar - Key Signature,  Prev: Bar - Remove Metronome,  Up: Editor

   Bar - Time Signature                Function

   This function is part of the [*note Bar::.] menu.

   Prompts for a new time signature to be placed at the start of the
current bar.  The time signature may be placed in the current staff
only, or in all staffs in the piece, and affects the formatting of the
music in this and all subsequent bars (or until another contradictory
time signature is met).

   Time signatures are preserved in MIDI output (see [*note Editor
Tools - Export MIDI::.]).


File: rosehelp.info,  Node: Bar - Key Signature,  Next: Text,  Prev: Bar - Time Signature,  Up: Editor

   Bar - Key Signature                Function

   This function is part of the [*note Bar::.] menu.

   Inserts a new key signature at the point where the cursor is placed.
If a key signature is already in force, it will be cancelled
appropriately in combination with introducing the new one.

   To choose the new key signature, you will be given a dialogue box
showing part of a staff with a treble clef, with the selected signature
shown on the staff.  The box has up and down arrow buttons which add or
remove sharps, or remove or add flats, to the signature, plus an option
menu which you can use to select a particular signature by name.

   There is also an option to transpose the rest of the staff into the
new key. If selected, this will simply cause any notes affected by the
new key signature to be sharpened or flattened accordingly.  Otherwise,
the note pitches will be left as they were and accidentals will be
introduced as necessary.  (This sense of "transposition" is thus
different from that invoked through the [*note Group - Transpose::.]
function.)

   Once a key signature has been inserted into a piece of music, it
works like any other musical item.  In particular you can select it
with the selection cursor and (for example) delete it as normal.  See
[*note Inserting notes and signs::.] for comments on the semantics of
key signatures.

   Key signatures are preserved as meta-events in MIDI output (see
[*note Editor Tools - Export MIDI::.]), although their effects are also
carried out explicitly on the note pitches.


File: rosehelp.info,  Node: Text,  Next: Text - Add Text options,  Prev: Bar - Key Signature,  Up: Editor

   Text                Menu

   The Text menu contains functions for adding and removing textual
labels to or from the musical score.  These labels are saved with the
music (see [*note Saving an editor file::.]), but are not properly
preserved in MIDI files (see [*note Exporting MIDI files::.]).  Most of
these functions require that the cursor is placed, in order to position
the text above or below the cursor position.

   Functions for handling labels above the bar line are in the [*note
Bar::.] menu.

   See also [*note Adding text::.] for further descriptions of these
functions.


File: rosehelp.info,  Node: Text - Add Text options,  Next: Text - Clear Group,  Prev: Text,  Up: Editor

   Text - Add Text options                Function

   These functions are part of the [*note Text::.] menu.

   The Text menu contains four functions dedicated to adding text to the
staff at the cursor position.  The menu list simply shows `Text' four
times, each time accompanied by a small icon indicating the position
and style which will be used by that function.

   The four possible styles are: immediately above the staff, in a
medium font; considerably above the staff, in a larger font; and below
the staff, in medium and italic fonts respectively.

   Each function prompts for the text you would like to display.


File: rosehelp.info,  Node: Text - Clear Group,  Next: Text - Clear Bar,  Prev: Text - Add Text options,  Up: Editor

   Text - Clear Group                Function

   This function is part of the [*note Text::.] menu.

   Removes all text above or below any items in the selected area.


File: rosehelp.info,  Node: Text - Clear Bar,  Next: Text - Clear Staff,  Prev: Text - Clear Group,  Up: Editor

   Text - Clear Bar                Function

   This function is part of the [*note Text::.] menu.

   Removes all text above or below any items in the bar containing the
cursor.  This includes the bar label, if one is present.


File: rosehelp.info,  Node: Text - Clear Staff,  Next: Marks,  Prev: Text - Clear Bar,  Up: Editor

   Text - Clear Staff                Function

   This function is part of the [*note Text::.] menu.

   Removes all text above or below any items in the staff containing the
cursor.  First checks to make sure of your intentions.


File: rosehelp.info,  Node: Marks,  Next: Editor Tools,  Prev: Text - Clear Staff,  Up: Editor

   Marks                Menu

   The Marks menu lists several kinds of markings.  Sweeping out an area
of music and selecting one of these marking functions will cause every
chord within the area to be decorated with the given mark, whilst the
Unmark function removes any decorations from any chords within the
selected area.

   There is currently no way to place marks on items other than chords
(for instance, you cannot place a pause mark over a rest).

   See also [*note Marking chords::.], which describes further the use
of the Marks menu.


File: rosehelp.info,  Node: Editor Tools,  Next: Editor Tools - Import MIDI,  Prev: Marks,  Up: Editor

   Editor Tools                Menu

   The Tools menu contains functions for high-level manipulation of the
musical data: converting to and from MIDI format, invoking a sequencer
or producing typesetting output.  There is also a function ([*note
Editor Tools - Preferences::.]) for changing some details of the
behaviour of the editor.

   See also [*note Importing MIDI files::.], [*note Exporting MIDI
files::.], [*note Playing a piece of music::.], [*note Sequencing a
piece of music::.] and [*note The Rosegarden Sequencer::.] for more
description of the MIDI-handling functions on the Tools menu, and
[*note Exporting MusicTeX files::.] and [*note Customising the
editor::.] for an introduction to its other capabilities.


File: rosehelp.info,  Node: Editor Tools - Import MIDI,  Next: Editor Tools - Export MIDI,  Prev: Editor Tools,  Up: Editor

   Editor Tools - Import MIDI                Function

   This function is part of the [*note Editor Tools::.] menu.

   Prompts for a MIDI file to be imported.  The editor will read the
file, check whether you'd like it to be quantized, convert it to
Rosegarden Editor format with one staff for each MIDI track (excepting
track zero in the case where it contains no actual notes), beam chords
into groups automatically, choose apparently suitable clefs for each
staff and display the music including any textual, key or tempo
information found in the file.

   Once imported, the buffer acts as a normal editor buffer: it can be
edited as usual, and saved, exported or sequenced.  As the editor has
no filename for the converted file, it cannot be saved using the [*note
Editor File - Save::.] option, but only using [*note Editor File - Save
As::.].

   See also [*note Importing MIDI files::.].


File: rosehelp.info,  Node: Editor Tools - Export MIDI,  Next: Editor Tools - Play MIDI,  Prev: Editor Tools - Import MIDI,  Up: Editor

   Editor Tools - Export MIDI                Function

   This function is part of the [*note Editor Tools::.] menu.

   Prompts for a filename and saves the current buffer into that file in
MIDI format.  MIDI files thus produced should be compatible with any
reputable sequencing software, including [*note The Rosegarden
Sequencer::.].

   MIDI files are exported including all information pertinent to their
playback, except for dynamic information.  However, they should not be
used when storing score files which you have created using the
Rosegarden editor, because the MIDI format cannot record much of the
information present in a Rosegarden editor file; use [*note Editor File
- Save::.] to create suitable files instead.

   See also [*note Exporting MIDI files::.].


File: rosehelp.info,  Node: Editor Tools - Play MIDI,  Next: Editor Tools - Sequence MIDI,  Prev: Editor Tools - Export MIDI,  Up: Editor

   Editor Tools - Play MIDI                Function

   This function is part of the [*note Editor Tools::.] menu.

   Plays the music in the current buffer by creating an intermediate
MIDI format file and using [*note The Rosegarden Sequencer::.] to play
it.  This function is only available when the full Rosegarden Suite is
in operation, including [*note The Rosegarden Top Box::.].

   This function has been partly implemented, but does not yet work.

   See also [*note Playing a piece of music::.].


File: rosehelp.info,  Node: Editor Tools - Sequence MIDI,  Next: Editor Tools - Import Old Rosegarden File,  Prev: Editor Tools - Play MIDI,  Up: Editor

   Editor Tools - Sequence MIDI                Function

   This function is part of the [*note Editor Tools::.] menu.

   Sends a MIDI representation of the music in the current buffer to
[*note The Rosegarden Sequencer::.] for sequencing.  If the sequencer
is not yet running, it will be started.  This function is only
available when the full Rosegarden Suite is in operation, including
[*note The Rosegarden Top Box::.].

   See also [*note Sequencing a piece of music::.].


File: rosehelp.info,  Node: Editor Tools - Import Old Rosegarden File,  Next: Editor Tools - Export MusicTeX,  Prev: Editor Tools - Sequence MIDI,  Up: Editor

   Editor Tools - Import Old Rosegarden File                Function

   This function is part of the [*note Editor Tools::.] menu.

   Prompts for a filename and tries to load that file as a Rosegarden
notation file saved from version 1 or 2.0a of the Rosegarden editor.
Use this to convert files saved from old versions of the editor into
the file format used by this version.

   Double-bar and repeat-bar indications in the saved file will not be
preserved when the file is loaded; you'll have to add them in again
afterwards.

   It isn't possible to save files from this version of the editor in
the format used by previous versions.  (The onward march of technology
will sweep us all with it in the end.)


File: rosehelp.info,  Node: Editor Tools - Export MusicTeX,  Next: Editor Tools - Preferences,  Prev: Editor Tools - Import Old Rosegarden File,  Up: Editor

   Editor Tools - Export MusicTeX                Function

   This function is part of the [*note Editor Tools::.] menu.

   Prompts for a filename and saves the current buffer into that file in
MusicTeX format.  Files thus produced can be processed using the TeX
typesetting language with the MusicTeX music typesetting macro package
to produce high-quality printed output.

   If you intend to make use of this function, you should make sure
you're familiar with TeX and MusicTeX first.  The output Rosegarden
produces is likely to be incomplete and imperfect and will probably
need editing by hand before it will process and print well.  MusicTeX
can be very challenging to use, and documenting it is considerably
outside the scope of this help file.

   (A brief note, however: Rosegarden includes an "autolines"
declaration in the file, but with arbitrary values, and by default it
leaves the declaration commented out.  No other attempt is made to fix
correct line breaks, so you will probably want to uncomment this
declaration and insert some better values.  If you find that TeX runs
out of memory or gets gradually slower and slower, you'll probably need
to uncomment the autolines declaration.)

   See also [*note Exporting MusicTeX files::.].


File: rosehelp.info,  Node: Editor Tools - Preferences,  Next: The Rosegarden Sequencer,  Prev: Editor Tools - Export MusicTeX,  Up: Editor

   Editor Tools - Preferences                Function

   This function is part of the [*note Editor Tools::.] menu.

   Pops up a customisation settings box using which you can change some
of the properties of the program's behaviour.

   This function has not yet been implemented.

   See also [*note Customising the editor::.].


File: rosehelp.info,  Node: Editor,  Next: Sequencer,  Prev: Rosegarden,  Up: Top

   Editor section

* Menu:

* The Rosegarden Editor:: introduction
* Starting a new piece of music:: procedure
* Opening an editor file:: procedure
* Saving an editor file:: procedure
* Printing a piece of music:: procedure
* Moving around:: procedure
* Using the Palette:: procedure
* Inserting notes and signs:: procedure
* Considerations in inserting notes:: procedure
* Using the editing cursor:: procedure
* Editing and using the clipboard:: procedure
* Grouping:: procedure
* Chords:: procedure
* Operations on staffs:: procedure
* Changing bar properties:: procedure
* Tempos and times:: procedure
* Adding text:: procedure
* Marking chords:: procedure
* Importing MIDI files:: procedure
* Exporting MIDI files:: procedure
* Playing a piece of music:: procedure
* Sequencing a piece of music:: procedure
* Exporting MusicTeX files:: procedure
* Customising the editor:: procedure
* Editor File:: menu
* Editor File - New:: function
* Editor File - Open:: function
* Editor File - Close:: function
* Editor File - Include:: function
* Editor File - Save:: function
* Editor File - Save As:: function
* Editor File - Print:: function
* Editor File - Exit:: function
* Editor Edit:: menu
* Editor Edit - Undo:: function
* Editor Edit - Delete:: function
* Editor Edit - Cut:: function
* Editor Edit - Copy:: function
* Editor Edit - Paste:: function
* Editor Edit - Show Clipboard:: function
* Editor Edit - Chord:: function
* Editor Edit - Unchord:: function
* Editor Edit - Create Chord:: function
* Editor Edit - Edit Chord:: function
* Stave:: menu
* Stave - Add Staff:: function
* Stave - Delete Staff:: function
* Stave - Empty Staff:: function
* Stave - Rename Staff:: function
* Stave - Connect Above:: function
* Stave - Connect Below:: function
* Stave - Disconnect:: function
* Stave - Fill To End:: function
* Group:: menu
* Group - Tie:: function
* Group - Slur:: function
* Group - Crescendo:: function
* Group - Decrescendo:: function
* Group - Remove Indication:: function
* Group - Beam:: function
* Group - Simple Tuplet:: function
* Group - Tuplet:: function
* Group - Break Group:: function
* Group - Auto Beam:: function
* Group - Transpose:: function
* Group - Invert:: function
* Group - Retrograde:: function
* Bar:: menu
* Bar - Plain:: function
* Bar - Double Bar:: function
* Bar - Repeat at Start:: function
* Bar - Repeat at End:: function
* Bar - Label:: function
* Bar - Remove Label:: function
* Bar - Metronome:: function
* Bar - Remove Metronome:: function
* Bar - Time Signature:: function
* Bar - Key Signature:: function
* Text:: menu
* Text - Add Text options:: function
* Text - Clear Group:: function
* Text - Clear Bar:: function
* Text - Clear Staff:: function
* Marks:: menu
* Editor Tools:: menu
* Editor Tools - Import MIDI:: function
* Editor Tools - Export MIDI:: function
* Editor Tools - Play MIDI:: function
* Editor Tools - Sequence MIDI:: function
* Editor Tools - Import Old Rosegarden File:: function
* Editor Tools - Export MusicTeX:: function
* Editor Tools - Preferences:: function


File: rosehelp.info,  Node: The Rosegarden Sequencer,  Next: Loading a MIDI file,  Prev: Editor Tools - Preferences,  Up: Sequencer

   The Rosegarden Sequencer                Introduction

   The Rosegarden Sequencer module allows the user to manipulate MIDI
files and data in a variety of ways, as well as providing facilities
for MIDI recording and playback. The sequencer can be run either
independently or as an integrated part of the Rosegarden suite. When
the sequencer is run independently this help information will not be
available.


File: rosehelp.info,  Node: Loading a MIDI file,  Next: Saving a MIDI file,  Prev: The Rosegarden Sequencer,  Up: Sequencer

   Loading a MIDI file                Procedure

   To load a new MIDI file select [*note Sequencer File - Open::.]. You
will then be  presented with a file dialogue box. Select the required
file from the  list presented and press the + Load button. The file
will now load.


File: rosehelp.info,  Node: Saving a MIDI file,  Next: Recording MIDI data,  Prev: Loading a MIDI file,  Up: Sequencer

   Saving a MIDI file                Procedure

   To save the current MIDI file, select [*note Sequencer File -
Save::.]. If the file has not yet been saved you will be prompted to
supply a name for the new file. If the file has been saved before (or
was loaded in via the [*note Sequencer File - Open::.] option) then the
new file will simply be saved over the top of the old file. To save the
file under a different name, use the [*note Sequencer File - Save
As::.] option.


File: rosehelp.info,  Node: Recording MIDI data,  Next: Organising recorded data,  Prev: Saving a MIDI file,  Up: Sequencer

   Recording MIDI data                Procedure

   [*note The Rosegarden Sequencer::.] allows you to record data from
attached MIDI devices in real-time. To record data select the [*note
Sequencer File - Record::.] option. This will set the sequencer into a
listening state. Any MIDI events received over the MIDI link will now
be stored in memory and returned to you as a new un-named track
appended to the list of tracks in the main window after you have
stopped recording by clicking on the + STOP button that is displayed
while recording. This data can then be manipulated and viewed using the
standard track editing functions. Note that the sequencer will record
ALL the MIDI data it receives regardless of the source device. Any
unwanted events can be filtered out using the [*note Track - Filter By
Channel::.] and [*note Track - Filter By Event::.] options. See [*note
Organising recorded data::.] for more details on the editing facilities
that are available.

   When recording the sequencer using a temporary buffer to store
incoming events. The size of this buffer is by default 10,000 events,
but can be set by you to be larger if necessary using the [*note Midi -
MIDI Setup::.] option. See [*note Configuring your MIDI setup::.] for
further information.


File: rosehelp.info,  Node: Organising recorded data,  Next: Displaying a track,  Prev: Recording MIDI data,  Up: Sequencer

   Organising recorded data                Procedure

   One of the main functions of the sequencer is to allow the user to
reformat MIDI data in a more organised manner than its raw recorded
form. The sequencer allows MIDI data to be separated into tracks, each
of which contains information for a sub-section of the music. Tracks in
the sequencer are played back simultaneously, and can be viewed as
equivalent to the tracks on a multi-track recording device. Although
the MIDI file format defines a form for sequential track files this
format is not currently supported by the sequencer.

   Usually tracks contain data for a single instrument, (although when
transcribing music for an instrument such as the piano it may be
desirable to separate the events into left- and right-hand parts).
Also the MIDI file specification states that in multi-track files,
Track 0 should contain the tempo map and key and time signature events,
and that these events should not appear in other tracks in the file.
The Rosegarden sequencer does not enforce this organisation, but in
order to ensure that MIDI files produced by Rosegarden are readable by
other applications the user should attempt to conform to this format.

   To enable the user to re-organise data in a MIDI file the Rosegarden
sequencer provides a number of track editing functions. The principle
concept is the use of + filters to strip out unwanted events in the
MIDI track, along with + cloning, which is used to create an exact copy
of a track, and + merging, which can be used to combine two separate
tracks.

   Filter functions are available from the + Track menus on the main
windows and piano roll and event list sub-windows. The filter are as
follows:

   [*note Track - Filter By Channel::.]. This filter allows you to strip
out all the events from a MIDI track, retaining only those events on
the specified channel. This filter is particularly useful for
separating tracks by instrument.

   [*note Track - Filter By Event::.]. This filter strips out all the
events in a track which are not of the type or types specified. Use this
filter to help with creating Track 0, or to remove unwanted events,
such as text meta-events which are no longer meaningful in the edited
track.

   [*note Track - Filter By Pitch::.]. This allows you to strip out any
events from a track which fall above or below a specified pitch. This
filter can be used (for instance) to crudely split keyboard lines into
left- and right-hand parts before passing to the Notation editor to be
turned into music score.

   In addition to the event filter tracks can be transposed to a
different key using the [*note Track - Transpose::.] function, and
quantized to make the playing more regular, using the [*note Track -
Quantize::.] option. Events may also be moved from one channel to
another for a given track by use of the [*note Track - Change
Channel::.] facility.


File: rosehelp.info,  Node: Displaying a track,  Next: Editing with the Event List,  Prev: Organising recorded data,  Up: Sequencer

   Displaying a track                Procedure

   Tracks can be displayed in two formats. The simplest form is the
event list. This is simply a list of all the MIDI events in the selected
track, with some textual description of their parameters, and is useful
for obtained detailed information about the events in a MIDI track. All
the events in the track are displayed in the list. To display a track
as an event list select the track from the track list in the main
window and the select the [*note Track - Event List::.] menu option.

   Alternatively tracks may be displayed using the `Piano Roll' format.
This provides a graphical representation of the MIDI track, displaying
note events as rectangular boxes over a traditional musical staff. Only
note events are displayed on the piano roll. To display a track as a
piano roll select the track from the track list in the main window and
then select the [*note Track - Piano Roll::.] menu option.

   Both piano roll and event list windows have menu options to call up
the complementary format for displaying the track in the window. To
call up the piano roll window from an event list window simply select
[*note Track - Piano Roll::.], and similarly to call up an event list
window from a piano roll, select [*note Track - Event List::.].

   The Rosegarden sequencer provides full click and drag editing
facilities on both the piano roll and event list displays. See [*note
Editing with the Piano Roll::.] and [*note Editing with the Event
List::.] respectively for more details.


File: rosehelp.info,  Node: Editing with the Event List,  Next: Editing with the Piano Roll,  Prev: Displaying a track,  Up: Sequencer

   Editing with the Event List                Procedure

   The event list sub-windows provide you with a detailed list of all
the events present on a MIDI track. For a description of the display
format for event list windows, see [*note Track - Event List::.].

   From an event list window you have access to all the track
manipulation functions, plus the ability to use the clipboard to cut
and paste events. To cut, copy or delete events outline the area to be
edited by clicking at the start event and dragging the cursor down to
the end event. The event list can be scrolled while doing this by
moving the cursor outside of the window bounds. Once you have selected
the required events select the + Cut, + Copy or + Delete options from
the + Edit menu as required.

   To paste events into a track using the event list window click on the
event in the event list before which you wish to have the events
inserted and select + Paste. If more than one event is selected then
the events from the clipboard will be pasted before the start event in
the selection.

   See [*note Sequencer Edit - Cut::.], [*note Sequencer Edit -
Copy::.], [*note Sequencer Edit - Paste::.] and [*note Sequencer Edit -
Delete::.] for further information on the clipboard functions.

   To modify an event in the event list by changing one or more of its
parameters select [*note Event - Modify Event::.]. A dialogue box will
be called up containing the parameters for the chosen event and
allowing you to alter them. If a number of events are selected then a
dialogue box will only be produced for the first event in the selection.

   In addition to manipulating existing functions new events can be
created using the options on the [*note Event::.] menu. If you have
selected an event in the event list before selecting one of these
options then the dialogue box that is called up will contain the time
of the selected event in the time field, and the event will be inserted
just before the selected event after you have clicked on + OK. You are
still free to change this time value if you wish.  For more information
on the specific dialogue boxes for each event type see the following
sections,


File: rosehelp.info,  Node: Editing with the Piano Roll,  Next: Preparing a MIDI file for the Editor,  Prev: Editing with the Event List,  Up: Sequencer

   Editing with the Piano Roll                Procedure

   The + Piano Roll windows provide a graphical display of the note
events present in a MIDI track (see [*note Track - Piano Roll::.] for
an overview).

   The + Piano Roll windows support all the track manipulation
functions as well as click and drag editing in a manner similar to the
+ Event List windows. To select an area click at the start and drag the
pointer to outline the required events. Unlike the event list, however,
it is not possible to scroll beyond the current contents of the window
when selecting. Once you have selected the required events select the +
Cut, + Copy or + Delete options from the + Edit menu as required.

   To paste events into a track select the required insertion point by
clicking on the piano roll display and then select the + Paste option.
The events will be pasted in with the appropriate time values.

   See [*note Sequencer Edit - Cut::.], [*note Sequencer Edit -
Copy::.], [*note Sequencer Edit - Paste::.] and [*note Sequencer Edit -
Delete::.] for further information on the clipboard functions.

   The event creation and modification functions that are available from
event list windows are also available from piano roll windows.


File: rosehelp.info,  Node: Preparing a MIDI file for the Editor,  Next: Playing a MIDI file,  Prev: Editing with the Piano Roll,  Up: Sequencer

   Preparing a MIDI file for the Editor                Procedure

   In order to get the best results when using the Rosegarden Editor to
produce a transcription of a MIDI file it is necessary to first tidy up
the MIDI data in a number of ways.

   Firstly the file should be quantized to a reasonable resolution with
respect to both note timing and duration.In general a fairly coarse
granularity should be used to produce a tidy transcription, however the
coarser the resolution the more information is lost when transcribing.
Optimum values will of course vary from piece to piece, but as a rough
guide most pieces of music transcribe fairly well using semi-quaver
resolution for both note position and duration. See [*note Track -
Quantize::.] for details on how to quantize MIDI data.

   Secondly each track in the MIDI file is mapped to a separate staff
when transcribing. It should be ensured that the MIDI file only
contains a single instrument in each track. Since each MIDI instrument
must reside on a separate MIDI channel this can be achieved by using
the [*note Track - Filter By Channel::.] function.

   Although splitting the file into tracks solely by instrument works
fine for some pieces, often music for keyboard instruments is best
transcribed as separate staves for the left hand and right hand parts
of the music. Splitting MIDI files in this manner is a more difficult
task. The basic procedure that can be used is to first split the track
at some designated pitch by cloning it using [*note Track - Clone::.]
and then filtering the two resulting tracks using [*note Track - Filter
By Pitch::.], so that one track contains notes above the designated
pitch and the other contains the notes below this value. This provides
a rough first approximation of the left and right hand parts, which can
then be hand edited by using the cut and paste options to transfer
anomalous notes between the two tracks.

   Finally a number of useful meta-events can be inserted into Track 0
of the file, which will then be used by the Rosegarden Editor to aid
with the transcription process. Tempo events and time and key signature
events will all be interpreted correctly and placed at the relevant
point in the transcription, and will affect the format of the
transcribed music. If these events are not inserted into the MIDI file
they can always be added in using the editor after transcription, but
the resulting beaming may differ.

   See the Rosegarden Editor page for [*note Importing MIDI files::.]
for a discussion on the Editor's approach to automatic beaming. See
[*note Organising recorded data::.] for more detailed descriptions of
how to set about re-organising raw MIDI data.


File: rosehelp.info,  Node: Playing a MIDI file,  Next: Configuring your MIDI setup,  Prev: Preparing a MIDI file for the Editor,  Up: Sequencer

   Playing a MIDI file                Procedure

   To play back a MIDI file in real-time over a MIDI link select the
[*note Sequencer File - Play::.] menu option (although you should
probably first check that the sequencer is correctly configured for
your system, see [*note Configuring your MIDI setup::.].

   Playback will commence immediately and may be stopped by clicking on
the displayed + STOP button. If playback sounds garbled then check that
your MIDI devices are configured correctly. If necessary you can modify
the events in the MIDI file to enable correct playback - most commonly
this involves using [*note Track - Change Channel::.] to alter the
channel that these events are transmitted on.

   Playback can also become garbled if the system you are using is
heavily loaded. The sequencer provides a number of facilities to help
alleviate this problem, see [*note Midi - MIDI Setup::.] for more
details.


File: rosehelp.info,  Node: Configuring your MIDI setup,  Next: Generating C-Sound,  Prev: Playing a MIDI file,  Up: Sequencer

   Configuring your MIDI setup                Procedure

   It is most important to correctly configure the sequencer to
correspond to your MIDI setup before attempting real-time recording or
playback. Most importantly you should ensure that the port name is
correct. If the port name is incorrect then strange things may occur
(probably involving other people on your network who may not be too
happy). The most common port names for MIDI ports on the Silicon
Graphics are "/dev/ttyd1" and "/dev/ttyd2" which correspond to the two
serial ports on the rear of the machine.

   To configure or check your MIDI setup choose the [*note Midi - MIDI
Setup::.] option.


File: rosehelp.info,  Node: Generating C-Sound,  Next: Sequencer File,  Prev: Configuring your MIDI setup,  Up: Sequencer

   Generating C-Sound                Procedure

   Rosegarden can translate MIDI files to part of a C-Sound score file.
The format is straightforward, with each staff treated as a separate
instrument, and MIDI notes translated into the standard equal-tempered
C-Sound pitches, and the MIDI velocity given as the fifth parameter.

   The translation if achieved via the [*note Sequencer Tools - Export
CSound::.] option.


File: rosehelp.info,  Node: Sequencer File,  Next: Sequencer File - Record,  Prev: Generating C-Sound,  Up: Sequencer

   Sequencer File                Menu

   The File menu in the Rosegarden Sequencer provides functions for
loading, saving, recording and playing MIDI files.


File: rosehelp.info,  Node: Sequencer File - Record,  Next: Sequencer File - Open,  Prev: Sequencer File,  Up: Sequencer

   Sequencer File - Record                Function

   Start recording MIDI data being broadcast by an external MIDI
device. The incoming data is recorded until the + Stop button on the +
Record dialogue box is pressed. The recorded information will appear as
a new track on the track list.


File: rosehelp.info,  Node: Sequencer File - Open,  Next: Sequencer File - Close,  Prev: Sequencer File - Record,  Up: Sequencer

   Sequencer File - Open                Function

   This option allows you to read in a previously saved MIDI file. See
[*note Loading a MIDI file::.].


File: rosehelp.info,  Node: Sequencer File - Close,  Next: Sequencer File - Save,  Prev: Sequencer File - Open,  Up: Sequencer

   Sequencer File - Close                Function

   This option closes the current MIDI file. If the file has been
altered since it was read in then you will be asked whether you wish to
save it before it is discarded.


File: rosehelp.info,  Node: Sequencer File - Save,  Next: Sequencer File - Save As,  Prev: Sequencer File - Close,  Up: Sequencer

   Sequencer File - Save                Function

   Saves the current MIDI file. If the file has not been previously
saved then you will be prompted to supply a file name. See [*note
Saving a MIDI file::.].


File: rosehelp.info,  Node: Sequencer File - Save As,  Next: Sequencer File - File Info,  Prev: Sequencer File - Save,  Up: Sequencer

   Sequencer File - Save As                Function

   Saves the current MIDI file under a new name. You will be prompted to
supply the new file name. See [*note Saving a MIDI file::.].


File: rosehelp.info,  Node: Sequencer File - File Info,  Next: Sequencer File - Set Timebase,  Prev: Sequencer File - Save As,  Up: Sequencer

   Sequencer File - File Info                Function

   Report useful information about the current MIDI file, including its
full pathname, the number of tracks and events, and the file format
type.


File: rosehelp.info,  Node: Sequencer File - Set Timebase,  Next: Sequencer File - Play,  Prev: Sequencer File - File Info,  Up: Sequencer

   Sequencer File - Set Timebase                Function

   Alters the timebase for the current file. The timebase corresponds to
the number of time divisions per MIDI quarter note. Changing this value
will result in tempo settings and note lengths being incorrect, and may
cause playback to become garbled.


File: rosehelp.info,  Node: Sequencer File - Play,  Next: Sequencer File - Exit,  Prev: Sequencer File - Set Timebase,  Up: Sequencer

   Sequencer File - Play                Function

   Plays the MIDI file out via the MIDI port. See [*note Playing a MIDI
file::.].


File: rosehelp.info,  Node: Sequencer File - Exit,  Next: Sequencer Edit,  Prev: Sequencer File - Play,  Up: Sequencer

   Sequencer File - Exit                Function

   Use this option to leave the sequencer. If the current MIDI file has
been altered but has not been saved then you will be asked whether you
wish to save it before leaving the sequencer.


File: rosehelp.info,  Node: Sequencer Edit,  Next: Sequencer Edit - Undo,  Prev: Sequencer File - Exit,  Up: Sequencer

   Sequencer Edit                Menu

   The sequencer + Edit menu provides access to the clipboard functions
(cut, copy, and paste) and related general editing functions.


File: rosehelp.info,  Node: Sequencer Edit - Undo,  Next: Sequencer Edit - Delete,  Prev: Sequencer Edit,  Up: Sequencer

   Sequencer Edit - Undo                Function

   This function allows you to undo the last operation you performed on
a MIDI track. Only operations that affect a single track can be undone
in this manner.


File: rosehelp.info,  Node: Sequencer Edit - Delete,  Next: Sequencer Edit - Cut,  Prev: Sequencer Edit - Undo,  Up: Sequencer

   Sequencer Edit - Delete                Function

   This function deletes the selected area. The area to be deleted may
be specified from either the main window track list or from areas
selected in the + Piano Roll or + Event List sub-windows.


File: rosehelp.info,  Node: Sequencer Edit - Cut,  Next: Sequencer Edit - Copy,  Prev: Sequencer Edit - Delete,  Up: Sequencer

   Sequencer Edit - Cut                Function

   This function removes the contents of the selected area, moving them
into the clipboard. The previous contents of the clipboard, if any, are
lost. The area to be cut may be specified from either the main window
track list or from areas selected in the + Piano Roll or + Event List
sub-windows.


File: rosehelp.info,  Node: Sequencer Edit - Copy,  Next: Sequencer Edit - Paste,  Prev: Sequencer Edit - Cut,  Up: Sequencer

   Sequencer Edit - Copy                Function

   This function copies the contents of the selected area to the
clipboard. The selected area is left unaltered by this operation. The
previous contents of the clipboard, if any, are lost. The area to be
copied may be specified from either the main window track list or from
areas selected in the + Piano Roll or + Event List sub-windows.


File: rosehelp.info,  Node: Sequencer Edit - Paste,  Next: Sequencer Edit - Show Clipboard,  Prev: Sequencer Edit - Copy,  Up: Sequencer

   Sequencer Edit - Paste                Function

   This function inserts the contents of the clipboard at the point
specified by the selection cursor. The insertion point may be specified
from either the main window track list or selections made in the +
Piano Roll or + Event List sub-windows.


File: rosehelp.info,  Node: Sequencer Edit - Show Clipboard,  Next: Track,  Prev: Sequencer Edit - Paste,  Up: Sequencer

   Sequencer Edit - Show Clipboard                Function

   Displays a small window showing the contents of the clipboard in
event list format.


File: rosehelp.info,  Node: Track,  Next: Track - Event List,  Prev: Sequencer Edit - Show Clipboard,  Up: Sequencer

   Track                Menu

   The track menu provides a number of functions that operate over whole
tracks. The menu is accessible from the sequencer main window and from
piano roll and event list windows.


File: rosehelp.info,  Node: Track - Event List,  Next: Track - Piano Roll,  Prev: Track,  Up: Sequencer

   Track - Event List                Function

   Pulls up a window displaying a list of the MIDI events in the
selected track. From this new window you have access to the + Track, +
Edit and + Event menus, which you can use to manipulate events in this
track. You may have as many event list windows as you like open
simultaneously, with a limit of one window per track.

   The event list gives a textual representation of the MIDI events in
the order they appear in the track. The basic format for each event
description is:

     _______________________________________
             <Event Time> <Event Name> [<Event Data>]
     
     _______________________________________

   The event time is given as the number of beats from the start of the
track.  The events can be of the following types:

     _______________________________________
       Note On               <Chnl> <Note> <Octave> <Velocity> <Duration>
       Controller Change     <Chnl> <Controller Number> <Value>
       Program Change        <Chnl> <Program Number>
       Polyphonic Aftertouch <Chnl> <Note> <Octave> <Velocity>
       Monophonic Aftertouch <Chnl>
       Pitch Bend            <Chnl> <Pitch Change>
       Set Tempo             <Tempo> bpm
       Set SMPTE Offset      <SMPTE Values>
       Time Signature        <Time Sig>
       Key Signature         <Key Sig>
       Text Event            <Text String>
     
     _______________________________________

   Any events which are encountered which the sequencer cannot support
will be displayed as,

     _______________________________________
       Unsupported Event     <Hex dump of event arguments.>
     
     _______________________________________


File: rosehelp.info,  Node: Track - Piano Roll,  Next: Track - Rename,  Prev: Track - Event List,  Up: Sequencer

   Track - Piano Roll                Function

   The Piano Roll window displays the contents of a track using a
graphical notation similar to the roll of paper controlling a
traditional pianola. Notes are displayed positioned on a musical stave
and are represented as boxes. The length of the note is thus
proportional to the size of the box, and its position denotes the pitch
of the note and its place in the piece. Natural notes are shown as dark
boxes, sharps/flats are shown as light boxes. MIDI events other than
note events are not shown on the piano roll.

   From the Piano Roll window you have access to the + Track, + Edit
and + Event menus, which you can use to manipulate the track.


File: rosehelp.info,  Node: Track - Rename,  Next: Track - Track Info,  Prev: Track - Piano Roll,  Up: Sequencer

   Track - Rename                Function

   Renames the selected track. Any previous Track Name events for that
track will be deleted.


File: rosehelp.info,  Node: Track - Track Info,  Next: Track - Clone,  Prev: Track - Rename,  Up: Sequencer

   Track - Track Info                Function

   Displays useful information about the track, including its length in
beats and the total number of events contained in the track.


File: rosehelp.info,  Node: Track - Clone,  Next: Track - Merge,  Prev: Track - Track Info,  Up: Sequencer

   Track - Clone                Function

   Produces an identical copy of the selected track. This new track is
added to the end of the track list in the main window.


File: rosehelp.info,  Node: Track - Merge,  Next: Track - Filter By Channel,  Prev: Track - Clone,  Up: Sequencer

   Track - Merge                Function

   Merges the selected track with another track. After selecting this
option you will be prompted for the number of the track you wish to
merge with the selected track. Tracks are merged in a zip fastener
fashion.


File: rosehelp.info,  Node: Track - Filter By Channel,  Next: Track - Filter By Event,  Prev: Track - Merge,  Up: Sequencer

   Track - Filter By Channel                Function

   Removes all events from the selected track except for those on the
specified channel. After selecting this option you will be prompted for
the channel that is to be retained.


File: rosehelp.info,  Node: Track - Filter By Event,  Next: Track - Filter By Pitch,  Prev: Track - Filter By Channel,  Up: Sequencer

   Track - Filter By Event                Function

   Removes all the events from the selected track that are not of the
types specified by the user. After selecting this option you will be
presented with a dialogue box showing the possible MIDI event types.
Any event types that are ticked in this dialogue box will be retained
in the track.


File: rosehelp.info,  Node: Track - Filter By Pitch,  Next: Track - Change Channel,  Prev: Track - Filter By Event,  Up: Sequencer

   Track - Filter By Pitch                Function

   Removes all events from the selected track except those above (or
below) the pitch specified by the user. On selecting this option you
will be presented with a dialogue box in which you must enter the pitch
from which to filter and the direction in which notes should be
retained (i.e. above or below the specified pitch). The pitch is given
in a note and octave format. Note C in octave 5 is middle C.


File: rosehelp.info,  Node: Track - Change Channel,  Next: Track - Quantize,  Prev: Track - Filter By Pitch,  Up: Sequencer

   Track - Change Channel                Function

   Moves all events in the selected track that are on one channel to a
different channel. After selecting this option you must enter the
channel to change from and the channel to change to into the waiting
dialogue box. Channels are specified by a number in the range 0 to 15.


File: rosehelp.info,  Node: Track - Quantize,  Next: Track - Transpose,  Prev: Track - Change Channel,  Up: Sequencer

   Track - Quantize                Function

   This function allows you to regularize the duration and position of
the notes in the selected MIDI track. If this option is selected from
the main window Track menu, and no track is selected on the track list,
then quantization will be carried out on all the tracks in the file.

   After selecting this option you will be presented with a dialogue box
containing two buttons and two menus. Pressing the `Quantize Note
Positions' or `Quantize Note Durations' buttons enables or disables the
specified type of quantization. When either of the quantization modes
are enabled the associated menu will become sensitive, allowing you to
select the granularity to quantize to (i.e. the smallest note duration
or position permissible in the piece). Selecting OK will then perform
the quantization.

   Note that the `Quantize All Tracks' operation cannot be undone.


File: rosehelp.info,  Node: Track - Transpose,  Next: Midi,  Prev: Track - Quantize,  Up: Sequencer

   Track - Transpose                Function

   Allows the user to transpose the selected track up or down by a
number of semitones. If the option is selected from the main window and
no track has been selected from the track list then the operation will
be carried out across all the tracks in the file.


File: rosehelp.info,  Node: Midi,  Next: Midi - MIDI Setup,  Prev: Track - Transpose,  Up: Sequencer

   Midi                Menu

   This menu contains options used for configuring the MIDI setup to
suit your equipment. It is only available from the sequencer main
window.


File: rosehelp.info,  Node: Midi - MIDI Setup,  Next: Midi - Set Initial Patches,  Prev: Midi,  Up: Sequencer

   Midi - MIDI Setup                Function

   This function allows you to configure the MIDI setup of your machine
for playback and recording. Currently the only supported platform for
real-time recording and playback is Silicon Graphics machines.

   Upon selecting this option you are presented with a dialogue box from
which you can change a number of sequencer MIDI-related parameters.
These are:

   + Port Mode. This indicates whether the port should be configured to
be synchronous or asynchronous. Altering this value can improve
playback on heavily loaded systems.

   + Maintain Tempo. With this option selected the sequencer will
attempt to maintain the tempo of a piece even if it is not being given
enough processing time to do the job properly. This option can be
switched on or off according to taste. With the option enabled a
heavily loaded machine will produce jerky output, but maintain the
correct overall tempo. With the option disabled a heavily loaded
machine will produce slower but slightly less jerky playback. (Of
course the ideal solution is to use a lightly loaded machine when
playback quality will be much higher).

   + Port Name. This allows you to specify the name of the port you are
using as a MIDI port. On a Silicon Graphics workstation this will
usually be one of the two serial ports at the back of the machine
("/dev/ttyd1" or "/dev/ttyd2").

   + Event Buffer Size. This value specifies the size of the storage
buffer used when recording real-time MIDI data. The default size of
10,000 events should be large enough for most pieces.


File: rosehelp.info,  Node: Midi - Set Initial Patches,  Next: Midi - Reset,  Prev: Midi - MIDI Setup,  Up: Sequencer

   Midi - Set Initial Patches                Function

   This function has not yet been implemented.


File: rosehelp.info,  Node: Midi - Reset,  Next: Midi - System Reset,  Prev: Midi - Set Initial Patches,  Up: Sequencer

   Midi - Reset                Function

   This function has not yet been implemented.


File: rosehelp.info,  Node: Midi - System Reset,  Next: Midi - System Exclusive,  Prev: Midi - Reset,  Up: Sequencer

   Midi - System Reset                Function

   This function has not yet been implemented.


File: rosehelp.info,  Node: Midi - System Exclusive,  Next: Sequencer Tools,  Prev: Midi - System Reset,  Up: Sequencer

   Midi - System Exclusive                Function

   This function has not yet been implemented.


File: rosehelp.info,  Node: Sequencer Tools,  Next: Sequencer Tools - Notate,  Prev: Midi - System Exclusive,  Up: Sequencer

   Sequencer Tools                Menu

   This menu provides functions that communicate with other
applications. The available options are [*note Sequencer Tools -
Notate::.], [*note Sequencer Tools - Export CSound::.] and [*note
Sequencer Tools - External MIDI Player::.].


File: rosehelp.info,  Node: Sequencer Tools - Notate,  Next: Sequencer Tools - Export CSound,  Prev: Sequencer Tools,  Up: Sequencer

   Sequencer Tools - Notate                Function

   Passes the MIDI file to [*note The Rosegarden Editor::.] to be used
as the basis for a new musical score. If the editor is not active at
the time of the request then it is started automatically.


File: rosehelp.info,  Node: Sequencer Tools - Export CSound,  Next: Sequencer Tools - External MIDI Player,  Prev: Sequencer Tools - Notate,  Up: Sequencer

   Sequencer Tools - Export CSound                Function

   Converts the current MIDI file to Csound score format in a fairly
simple format.  It does translate tempo and notes; other MIDI events
get translated as comments.  There is no attempt to generate f
statements or orchestra files.


File: rosehelp.info,  Node: Sequencer Tools - External MIDI Player,  Next: Event,  Prev: Sequencer Tools - Export CSound,  Up: Sequencer

   Sequencer Tools - External MIDI Player                Function

   Invokes an external program of your choosing, giving it (on the
command-line) the name of a temporary MIDI file generated from the
current file.  This is would normally be used for playing MIDI through
a supplied MIDI player on a system for which Rosegarden does not
directly support MIDI playback.


File: rosehelp.info,  Node: Event,  Next: Event - Modify Event,  Prev: Sequencer Tools - External MIDI Player,  Up: Sequencer

   Event                Menu

   The + Event menu is available from + Event List

   windows and allows the user to create or modify MIDI events for the
track displayed in that window.


File: rosehelp.info,  Node: Event - Modify Event,  Next: Event - Insert Text Event,  Prev: Event,  Up: Sequencer

   Event - Modify Event                Function

   This function calls up a dialogue box listing the properties of the
selected event, and allowing you to change each by editing its textual
representation.

   If more than one MIDI event is selected, dialogue boxes will be shown
for each selected event in turn.


File: rosehelp.info,  Node: Event - Insert Text Event,  Next: Event - Insert Tempo Event,  Prev: Event - Modify Event,  Up: Sequencer

   Event - Insert Text Event                Function

   This function allows you to insert text events into a MIDI track. You
are presented with a dialogue box with a pulldown menu and two data
fields. The menu allows you to choose the type of the text event you
are about to insert which may be one of the following,

     _______________________________________
             Text Event
             Copyright Notice
             Track Name
             Instrument Name
             Lyric
             Text Marker
             Cue Point
     
     _______________________________________

   The two data fields allow you to enter the time of the event and the
textual contents of the event.


File: rosehelp.info,  Node: Event - Insert Tempo Event,  Next: Event - Insert Note Event,  Prev: Event - Insert Text Event,  Up: Sequencer

   Event - Insert Tempo Event                Function

   This function is not yet implemented.


File: rosehelp.info,  Node: Event - Insert Note Event,  Next: Event - Insert Controller Change,  Prev: Event - Insert Tempo Event,  Up: Sequencer

   Event - Insert Note Event                Function

   This function allows you to insert note events into a MIDI track.
You are presented with a dialogue box asking you to provide values for
the time, channel, pitch, octave, velocity and duration parameters of
the event.

   The pitch should be specified as a note name.  Sharps are indicated
by appending the octothorpe (`\#') sign to the name.  Flats cannot be
described; instead, write the note below with a sharp.  The octave
value must be in the range 0 to 10; middle C is the C in octave 5.

   The channel should be any number between 0 and 15.  The velocity
should be in the range 0 to 127, although the scale over which this
operates is device-dependent.  Duration is measured in beats, and may
be a fractional value.


File: rosehelp.info,  Node: Event - Insert Controller Change,  Next: Event - Insert Channel Aftertouch,  Prev: Event - Insert Note Event,  Up: Sequencer

   Event - Insert Controller Change                Function

   This function allows you to enter controller change events at any
point in a MIDI track. You are presented with a dialogue box and must
supply data for the four fields in it. You must specify the time of the
event, the channel the event is to be transmitted on, the number of the
controller that is to be changed, and the new value for the controller.
Controller numbers and values are specific to the MIDI devices you are
using - your manuals should contain a table of appropriate values.


File: rosehelp.info,  Node: Event - Insert Channel Aftertouch,  Next: Event - Insert Polyphonic Aftertouch,  Prev: Event - Insert Controller Change,  Up: Sequencer

   Event - Insert Channel Aftertouch                Function

   This function is not yet implemented.


File: rosehelp.info,  Node: Event - Insert Polyphonic Aftertouch,  Next: Event - Insert Program Change,  Prev: Event - Insert Channel Aftertouch,  Up: Sequencer

   Event - Insert Polyphonic Aftertouch                Function

   This function is not yet implemented.


File: rosehelp.info,  Node: Event - Insert Program Change,  Next: Event - Insert Pitch Change,  Prev: Event - Insert Polyphonic Aftertouch,  Up: Sequencer

   Event - Insert Program Change                Function

   This function allows you to enter program change events at any point
in a MIDI track.  You are presented with a dialogue box and must supply
data for the three fields in it.  You must specify the time of the
event, the channel that the event is to be transmitted on, and the new
program number to be transmitted.


File: rosehelp.info,  Node: Event - Insert Pitch Change,  Next: Musical and MIDI Terms,  Prev: Event - Insert Program Change,  Up: Sequencer

   Event - Insert Pitch Change                Function

   This function is not yet implemented.


File: rosehelp.info,  Node: Sequencer,  Next: Glossary,  Prev: Editor,  Up: Top

   Sequencer section

* Menu:

* The Rosegarden Sequencer:: introduction
* Loading a MIDI file:: procedure
* Saving a MIDI file:: procedure
* Recording MIDI data:: procedure
* Organising recorded data:: procedure
* Displaying a track:: procedure
* Editing with the Event List:: procedure
* Editing with the Piano Roll:: procedure
* Preparing a MIDI file for the Editor:: procedure
* Playing a MIDI file:: procedure
* Configuring your MIDI setup:: procedure
* Generating C-Sound:: procedure
* Sequencer File:: menu
* Sequencer File - Record:: function
* Sequencer File - Open:: function
* Sequencer File - Close:: function
* Sequencer File - Save:: function
* Sequencer File - Save As:: function
* Sequencer File - File Info:: function
* Sequencer File - Set Timebase:: function
* Sequencer File - Play:: function
* Sequencer File - Exit:: function
* Sequencer Edit:: menu
* Sequencer Edit - Undo:: function
* Sequencer Edit - Delete:: function
* Sequencer Edit - Cut:: function
* Sequencer Edit - Copy:: function
* Sequencer Edit - Paste:: function
* Sequencer Edit - Show Clipboard:: function
* Track:: menu
* Track - Event List:: function
* Track - Piano Roll:: function
* Track - Rename:: function
* Track - Track Info:: function
* Track - Clone:: function
* Track - Merge:: function
* Track - Filter By Channel:: function
* Track - Filter By Event:: function
* Track - Filter By Pitch:: function
* Track - Change Channel:: function
* Track - Quantize:: function
* Track - Transpose:: function
* Midi:: menu
* Midi - MIDI Setup:: function
* Midi - Set Initial Patches:: function
* Midi - Reset:: function
* Midi - System Reset:: function
* Midi - System Exclusive:: function
* Sequencer Tools:: menu
* Sequencer Tools - Notate:: function
* Sequencer Tools - Export CSound:: function
* Sequencer Tools - External MIDI Player:: function
* Event:: menu
* Event - Modify Event:: function
* Event - Insert Text Event:: function
* Event - Insert Tempo Event:: function
* Event - Insert Note Event:: function
* Event - Insert Controller Change:: function
* Event - Insert Channel Aftertouch:: function
* Event - Insert Polyphonic Aftertouch:: function
* Event - Insert Program Change:: function
* Event - Insert Pitch Change:: function


File: rosehelp.info,  Node: Musical and MIDI Terms,  Prev: Event - Insert Pitch Change,  Up: Glossary

   Musical and MIDI Terms                Glossary

   + Aftertouch. The change in pressure on a key after the initial key
press.  Normally used to control vibrato or other characteristics.

   + Bar. Also known as a measure.  A musical time, a grouping of beats.

   + Beat. A single stroke or pulsation.

   + Buffer. A temporary storage area in memory.

   + Channel. In MIDI, channels are used to separate different sections
of a song that are going to play simultaneously.  Each channel is
assigned to a single instrument in any particular instant of time.  One
channel is usually reserved for a percussion voice.

   + Clef. The symbol at the beginning of a staff that determines the
pitch.

   + Clock. A clock is used to synchronize two devices.  In MIDI, the
term clock is used to denote a single time source, which everything
plays along with.  MIDI clocks are actually special messages that are
sent 24 times (normally) per beat, and are used to synchronize two
sequencers, or a sequencer and a drum machine. Normally, the
sequencer's clock is the important one.  Other clock sources are rarely
used. The Rosegarden sequencer does not make use of clocking signals.

   + Controller. In sequencing, refers to a setting or parameter for a
MIDI device, such as controller 7 (volume).

   + Controller Change. This event will be displayed in the Event List
window.  It refers to a change in a synthesizer setting.  There are 128
possible MIDI controllers.

   + Cut-And-Paste. In word-processing, this function means moving text
from one place in a document to another.  In MIDI, one can copy a
section of a musical passage and paste it elsewhere.

   + Data Bytes. These are the bytes which follow the status byte in a
MIDI message, e.g., what note has been struck, how hard.

   + Filter. In MIDI filters are used primarily in connection with
events (note on, program change, tempo change...) and with channel
changes.  Each event is either filtered (deleted), transformed, or
passed through.

   + General Midi Mode. A convention specifying how a sequence (a song)
should be constructed, so that it will play on a variety of MIDI
devices. Most modern pieces of MIDI kit conform to this standard.

   + Import. To bring data from one program into another.

   + Instrumentation. The selection of instruments in a MIDI
arrangement.

   + Key Signature. Musical notation shows this in terms of sharps and
flats after the clef.  Software sequencers usually show a song key as
"F Major/D Minor," and indicate the number of sharps or flats.  B-flat
Major/G Minor has two flats, for example.

   + Messages. The net effect of MIDI-computing is sound: melodies,
harmonies, rhythms...  But the MIDI message (the MIDI event) itself is
not a sound.  Notes and other information are transmitted as digital
commands over the MIDI link at a rate of about 1,000 events per second.

   + Metronome. A device to mark time by producing a repeated tick.
The older type-a triangular box with a vibrating arm-was succeeded by
an electrical unit.  In MIDI, the ticks are computer-generated.

   + MIDI.  An acronym for Musical Instrument Digital Interface.  This
is a standard protocol for communication between musical devices.

   + MIDI Thru. One of the three defined MIDI port types.  A MIDI In
port receives information from other equipment.  A MIDI Out port sends
information to other equipment.  A MIDI Thru port outputs the
information received through a MIDI In port, sending it to other
equipment.  This allows for MIDI events to be echoed to other
synthesizers. The Rosegarden sequencer does not currently support MIDI
Thru.

   + Multi-Timbral. In MIDI, a multi-timbral sound module can play
several timbres (sounds) on different channels simultaneously.  A
multi-timbral device is one that is prepared to sound like more than
one instrument at a time.

   + Music. Any sequence of sounds assembled in a pre-meditated fashion.

   + Patch. In some early keyboard synthesizers, one selected
"instruments" to play (e.g., vibraphone, clarinet...)  Later, the term
"voice" emerged, in part, because some of the sounds were beyond
instruments (police whistles, human voices, etc.).  In contemporary
MIDI-computing, the word "patch" is prominent-one reason being that a
single keyboard setting, like 99, may encompass a large range of
percussive sounds.  In any event, to a sequencer, the patch setting
will determine the nature of the sounds.

   + Piano Roll Editor. A common notation used for editing by many
sequencers.  The notes of each track are shown as horizontal bars: the
vertical position representing pitch; the horizontal length
representing duration of the note (or chord).

   + Pitch Bend Wheel. A wheel on a keyboard that allows notes to be
bent up or down.  "Pitch bend" is also a MIDI message.

   + Polyphony. From the Greek, meaning variety of tones.  In MIDI, the
question is: "How many notes can be played simultaneously?" Maximum
polyphony cannot be exceeded.

   + Program Change. A MIDI event used to select a new program or patch.

   + Quantization. To quantize is to force all notes played to fall on
the nearest time interval specified.  It shifts events to an exact
rhythmic position. Note duration can also be similarly transformed.

   + Record. In the world of sound, to register something reproducible
on a disk, like a phonograph record, or on magnetic tape.  Traditional
recording captures the amplitude (height) and frequency (number) of
wave forms.  MIDI-computing does not really "record." It encodes
messages, digitally, by means of numbers.  Because of established
usage, however, the words "record" and "recording" often appear in
MIDI-computing, along with "play," "rewind," "fast forward," etc.  In
MIDI-computing, these words are really metaphors.  A typical sequencer
will "record" all of the MIDI events received, along with the time they
were received.

   + Silence. The blissful absence of music.

   + Standard Midi File. Often identified by its extension (.MID, .MFF
or .SMF), this is a file that can store MIDI messages, such as songs.
The data in a MIDI file can be played, manipulated, edited...  A MIDI
file comprises actions performed on an instrument (keys pressed, how
hard...)  There is a standard MIDI file format.  A principal advantage
of a MIDI file is that it uses comparatively little disk space, but,
more importantly, it is a standard across platforms and sequencers.

   + Status Byte. In a MIDI message, this announces what kind of
message is being sent, e.g., "note-on."

   + Synthesizer. (Often shortened to synth.)  A device which is
capable of producing synthetic sounds.  Originally, a synthesizer was
so called because it synthesized acoustic instruments.  Nowadays the
term refers to the sound-generating circuitry of any MIDI gear.
Another term is sound module.

   + Tempo. In music, the rate of speed (like allegretto).

   + Time Base. The number of ticks per beat.

   + Time Signature. In traditional musical notation, this is expressed
as a fractional sign, like 3/4.  The denominator indicates the unit for
the beat; the numerator shows the number of notes per bar.

   + Track. In MIDI, the term "track" designates a location where one
records or plays back a musical message, usually a portion of the total
arrangement.  To illustrate, one might record an oboe melody line on
Track Two, then record a bowed bass line on Track Three.  When played,
the sounds can be simultaneous.  Most MIDI software now accommodates 64
tracks of music, enough for a rich orchestral sound.  Tracks are purely
for convenience; channels are required.

   + Transpose. To perform a musical composition in a different key.
Both synthesizers and sequencers can carry out this function.

   + Velocity. Velocity is the MIDI way of determining how hard a note
is pressed on the keyboard controller.


File: rosehelp.info,  Node: Glossary,  Prev: Sequencer,  Up: Top

   Glossary section

* Menu:

* Musical and MIDI Terms:: glossary


File: rosehelp.info,  Node: Top,  Up: (dir)



* Menu:

* Rosegarden:: section
* Editor:: section
* Sequencer:: section
* Glossary:: section



Tag Table:
Node: The Rosegarden Top Box92
Node: File Boxes2402
Node: The Rosegarden Help System5442
Node: Help organisation6246
Node: Using help7934
Node: Rosegarden10071
Node: The Rosegarden Editor10333
Node: Starting a new piece of music10915
Node: Opening an editor file12279
Node: Saving an editor file13445
Node: Printing a piece of music14720
Node: Moving around15189
Node: Using the Palette16972
Node: Inserting notes and signs19268
Node: Considerations in inserting notes21455
Node: Using the editing cursor22795
Node: Editing and using the clipboard25113
Node: Grouping27170
Node: Chords28997
Node: Operations on staffs29683
Node: Changing bar properties31922
Node: Tempos and times33327
Node: Adding text34655
Node: Marking chords36010
Node: Importing MIDI files37137
Node: Exporting MIDI files41140
Node: Playing a piece of music42481
Node: Sequencing a piece of music43279
Node: Exporting MusicTeX files44266
Node: Customising the editor45114
Node: Editor File45473
Node: Editor File - New46371
Node: Editor File - Open46857
Node: Editor File - Close47614
Node: Editor File - Include47978
Node: Editor File - Save48520
Node: Editor File - Save As49039
Node: Editor File - Print49489
Node: Editor File - Exit49861
Node: Editor Edit50165
Node: Editor Edit - Undo50532
Node: Editor Edit - Delete50857
Node: Editor Edit - Cut51133
Node: Editor Edit - Copy51497
Node: Editor Edit - Paste51845
Node: Editor Edit - Show Clipboard52211
Node: Editor Edit - Chord52525
Node: Editor Edit - Unchord52971
Node: Editor Edit - Create Chord53452
Node: Editor Edit - Edit Chord55623
Node: Stave56892
Node: Stave - Add Staff57487
Node: Stave - Delete Staff57934
Node: Stave - Empty Staff58228
Node: Stave - Rename Staff58522
Node: Stave - Connect Above58989
Node: Stave - Connect Below59520
Node: Stave - Disconnect60049
Node: Stave - Fill To End60594
Node: Group61092
Node: Group - Tie61577
Node: Group - Slur62109
Node: Group - Crescendo62557
Node: Group - Decrescendo63035
Node: Group - Remove Indication63534
Node: Group - Beam63882
Node: Group - Simple Tuplet64230
Node: Group - Tuplet65068
Node: Group - Break Group67727
Node: Group - Auto Beam68154
Node: Group - Transpose68890
Node: Group - Invert69626
Node: Group - Retrograde70397
Node: Bar70915
Node: Bar - Plain71542
Node: Bar - Double Bar71823
Node: Bar - Repeat at Start73395
Node: Bar - Repeat at End73787
Node: Bar - Label74170
Node: Bar - Remove Label74785
Node: Bar - Metronome75064
Node: Bar - Remove Metronome75702
Node: Bar - Time Signature76069
Node: Bar - Key Signature76693
Node: Text78349
Node: Text - Add Text options79048
Node: Text - Clear Group79783
Node: Text - Clear Bar80073
Node: Text - Clear Staff80417
Node: Marks80750
Node: Editor Tools81397
Node: Editor Tools - Import MIDI82232
Node: Editor Tools - Export MIDI83258
Node: Editor Tools - Play MIDI84175
Node: Editor Tools - Sequence MIDI84823
Node: Editor Tools - Import Old Rosegarden File85458
Node: Editor Tools - Export MusicTeX86333
Node: Editor Tools - Preferences87750
Node: Editor88226
Node: The Rosegarden Sequencer91355
Node: Loading a MIDI file91901
Node: Saving a MIDI file92303
Node: Recording MIDI data92903
Node: Organising recorded data94301
Node: Displaying a track97338
Node: Editing with the Event List99013
Node: Editing with the Piano Roll101334
Node: Preparing a MIDI file for the Editor102731
Node: Playing a MIDI file105578
Node: Configuring your MIDI setup106650
Node: Generating C-Sound107444
Node: Sequencer File107990
Node: Sequencer File - Record108270
Node: Sequencer File - Open108686
Node: Sequencer File - Close108972
Node: Sequencer File - Save109324
Node: Sequencer File - Save As109666
Node: Sequencer File - File Info109991
Node: Sequencer File - Set Timebase110338
Node: Sequencer File - Play110790
Node: Sequencer File - Exit111060
Node: Sequencer Edit111422
Node: Sequencer Edit - Undo111718
Node: Sequencer Edit - Delete112052
Node: Sequencer Edit - Cut112430
Node: Sequencer Edit - Copy112907
Node: Sequencer Edit - Paste113426
Node: Sequencer Edit - Show Clipboard113865
Node: Track114137
Node: Track - Event List114467
Node: Track - Piano Roll116273
Node: Track - Rename117087
Node: Track - Track Info117341
Node: Track - Clone117633
Node: Track - Merge117912
Node: Track - Filter By Channel118286
Node: Track - Filter By Event118646
Node: Track - Filter By Pitch119128
Node: Track - Change Channel119721
Node: Track - Quantize120177
Node: Track - Transpose121206
Node: Midi121616
Node: Midi - MIDI Setup121893
Node: Midi - Set Initial Patches123585
Node: Midi - Reset123809
Node: Midi - System Reset124021
Node: Midi - System Exclusive124237
Node: Sequencer Tools124460
Node: Sequencer Tools - Notate124864
Node: Sequencer Tools - Export CSound125252
Node: Sequencer Tools - External MIDI Player125704
Node: Event126214
Node: Event - Modify Event126529
Node: Event - Insert Text Event126960
Node: Event - Insert Tempo Event127792
Node: Event - Insert Note Event128031
Node: Event - Insert Controller Change128962
Node: Event - Insert Channel Aftertouch129673
Node: Event - Insert Polyphonic Aftertouch129944
Node: Event - Insert Program Change130215
Node: Event - Insert Pitch Change130748
Node: Sequencer130990
Node: Musical and MIDI Terms133306
Node: Glossary141269
Node: Top141404

End Tag Table:
