summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWerner Schweer <ws.seh.de>2006-06-28 11:48:48 +0000
committerWerner Schweer <ws.seh.de>2006-06-28 11:48:48 +0000
commitdc4a5e6b2ca87fd1ac50245aff1defa35c80b754 (patch)
treebf79af83d643185a8463fdba16887cb69578a6c4
parent277f8057e6b44fcae55aba7efc9a63d7d8087c24 (diff)
updates
-rw-r--r--muse/doc/man/en/man-en.tex2
-rw-r--r--muse/doc/man/en/miditracks.tex122
-rw-r--r--muse/doc/man/en/projects.tex37
-rw-r--r--muse/doc/man/en/structure.tex19
4 files changed, 180 insertions, 0 deletions
diff --git a/muse/doc/man/en/man-en.tex b/muse/doc/man/en/man-en.tex
index 07d7bf8f..be746129 100644
--- a/muse/doc/man/en/man-en.tex
+++ b/muse/doc/man/en/man-en.tex
@@ -297,6 +297,8 @@
can be imported\par
\component projects.tex
+\component structure.tex
+\component miditracks.tex
\startappendices
\component ../gpl.tex
diff --git a/muse/doc/man/en/miditracks.tex b/muse/doc/man/en/miditracks.tex
new file mode 100644
index 00000000..1ad172bb
--- /dev/null
+++ b/muse/doc/man/en/miditracks.tex
@@ -0,0 +1,122 @@
+\chapter{Midi}
+ \section{Midi Routing}
+ \section{Midi Setup}
+ \subsection{Simple Setup}
+
+ In a simple setup every midi connector of the computer is connected
+ to a single midi device. Every midi track corresponds to a
+ different midi channel.
+ This setup is the most flexible and should always be used if
+ possible.
+
+ \subsection{Extended Setup}
+
+ \index{several midi tracks for a midi channel}
+ In an extended setup more than one midi track is routed to the
+ same midi channel. Of course a midi controller is associated with
+ a midi channel so you cannot different controller values for
+ each individual track.
+
+ \subsection{Complex Setup}
+ \index{multiple devices connected to one midi connector}
+ We call a setup complex if there is more than one midi device
+ connected to a midi connector.
+ Every device uses one ore more of the available 16 midi channel.
+ You have to make sure the channels do not overlap. For this
+ the midi devices must be configured to only listen on their
+ assigned channels.
+ Midi messages which are not bound to a midi channel (Sysex
+ messages) can be send to inividual devices by assigning a
+ different device id for every device. This device id can be
+ configure in \M\ to adress specific devices.
+
+ Because midi connections have only a very limited
+ bandwidth \index{midi bandwidth}, the complex setup should be
+ avoided.
+
+ \section{Midi Inputs}
+ Midi Inputs are repesented as a track in the mixer and in the
+ arranger.
+
+ A midi input has the following properties:
+
+ \blank[big]
+ \Input{Alsa Port:} this is the route to an ALSA input port.
+ A ALSA port can be connected to more than one midi input.
+ \Input{Plugins:} midi events read from the ALSA port can be routed
+ through several midi plugins. Available plugins can
+ filter or modify midi events.
+ \Input{Outputs:} a midi input has 16 outputs, one for every midi
+ channel. Every midi channel can be routed to a different
+ midi track.
+ Midi events received in a midi track do not have any
+ channel information anymore.
+ In a simple setup all channel of all midi inputs are
+ routed to all midi tracks. This is the default.
+
+ \blank[big]
+
+ \section{Midi Track}
+ The midi track contains all midi note on/off events.
+ Its represented as a strip in the mixer and as a track in the
+ arranger. The mixer strip representation is not very interesting
+ because a midi track has not many mixer relevant parameters.
+ For this midi tracks are not shown in the mixer by default.
+
+ Midi track properties:
+
+ \blank[big]
+ \Input{Record:} switches the track into record mode
+
+ \Input{Monitor:} when the monitor switch is on, on record all
+ midi events are routed to the track output.
+ Attention: this can lead to a midi feed back loop.
+
+ \Input{Mute:} mutes the track
+
+ \Input{Solo:} ---not yet defined---
+
+ \Input{Input:} track inputs can be routed to midi inputs
+
+ \Input{Output:} the track output can be routed to one or more
+ midi channels. Midi channels are always connected to
+ a midi port.
+
+ \blank[big]
+
+ \section{Midi Channel}
+ Midi channel normally contain all midi controller events.
+
+ Midi channel properties:
+
+ \blank[big]
+
+ \blank[big]
+
+ \section{Midi Port}
+
+ \index{Midi Port} A midi port represents an external midi device
+ and has the following properties:
+
+ \blank[big]
+ \Input{Instrument:} \index{Midi instrument} describes the properties
+ of an external midi instrument. The instrument can be
+ selected from a list of available instrument descriptions.
+
+ \Input{Master Volume:} \index{Midi Master Volume} is a midi
+ controller to change the volume of all midi channels of a port.
+
+ \Input{Device Id:} \index{Midi Device Id} if there are more than
+ one midi devices connected to a midi connctor then every device
+ must be assigned a unique device id.
+ The configured device id selects one of the connected devices.
+
+ \Input{Alsa Port:} this is the route to an ALSA midi port.
+ A port output can be connected to more than one ALSA port.
+
+ \blank[big]
+
+ Every midi port has 16 midi channel.
+
+ \section{Midi Synthesizer}
+
diff --git a/muse/doc/man/en/projects.tex b/muse/doc/man/en/projects.tex
index 391e5c22..d08f2e7b 100644
--- a/muse/doc/man/en/projects.tex
+++ b/muse/doc/man/en/projects.tex
@@ -52,4 +52,41 @@
choose from. The template can be a complete project but
without any wave data and normally without any midi data.
+ \M\ sucht Templates an zwei Orten:
+ im globalen \M\ Installationspfad (Factory Presets) sowie im
+ \M\ Verzeichnis relativ zum {\tt HOME} Verzeichnis des
+ Anwenders (User Presets)
+ \section{Projekt backup}
+
+ There is no special build in function in \M\ to backup a project.
+ But as all project data is contained in one folder, standard system
+ tool can be used to backup.
+
+ Project are always complete in itself and do not contain any
+ references to outside files. One execption are soundfonts \index{soundfonts}
+ as used by the fluid \index{fluid} synthesizer.
+ Its recommended to manually copy these files also to the
+ project folder.
+
+ Projects can be moved in the folder hierarchy without problems
+ as they do not contain any absolute file paths.
+
+ \section{Wave files and samplerate}
+
+ \index{wave files}\index{audio projecs}\index{midi projects}
+ \index{samplerate}
+
+ \M\ differences between midi projects and audio projects.
+ Audio projects contain in addition to midi data wave files.
+
+ Audio project have a defined samplerate and can only be loaded
+ and edited if the project samplerate is identical to the
+ current samplerate.
+
+ The current sample rate is defined by the JACK audio server and
+ can not be changed within \M.
+
+ If you want to import wave files with a samplerate different from
+ the current sample rate, they must be converted
+ (resampled\index{resample})
diff --git a/muse/doc/man/en/structure.tex b/muse/doc/man/en/structure.tex
new file mode 100644
index 00000000..f50e3829
--- /dev/null
+++ b/muse/doc/man/en/structure.tex
@@ -0,0 +1,19 @@
+\chapter{Structure}
+ \section{Tracks}
+
+ A project contains tracks analog to a conventional tape machine.
+ Tracks contain midi- audio- or controller data.
+ Tracks are presented in two different ways:
+
+ \blank[big]
+ \Input{Arranger:} tracks are displayed in a vertical list
+ \Input{Mixer:} the mixer shows track in a horizontal view
+
+ \par\blank[big]
+
+ Tempo and time signature are internal tracks not shown in the
+ arranger or mixer.
+
+ \section{Parts}
+
+ Midi- and audio tracks can be divided on the time axis into parts.