Sophie: kdemultimedia-1:2.1.1-5mdk i586

kdemultimedia-2.1.1-5mdk.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>MIDI</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The aRts Handbook"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="GUI Elements"
HREF="detail-gui-elements.html"><LINK
REL="NEXT"
TITLE="The Midi Manager"
HREF="midi-manager.html"><META
HTTP-EQUIV="Content-Style-Type"
CONTENT="text/css"><LINK
REL="stylesheet"
HREF="common/kde-common.css"
TYPE="text/css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=iso-8859-1"><META
HTTP-EQUIV="Content-Language"
CONTENT="en"><LINK
REL="stylesheet"
HREF="common/kde-localised.css"
TYPE="text/css"
TITLE="KDE-English"><LINK
REL="stylesheet"
HREF="common/kde-default.css"
TYPE="text/css"
TITLE="KDE-Default"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#AA0000"
VLINK="#AA0055"
ALINK="#AA0000"
STYLE="font-family: sans-serif;"
><DIV
CLASS="logoheader"
><A
HREF="http://www.kde.org/"
><IMG
SRC="common/logotp3.png"
BORDER="0"
ALT="The K Desktop Environment"
HEIGHT="62"
WIDTH="229"></A
></DIV
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The <SPAN
CLASS="APPLICATION"
>aRts</SPAN
> Handbook</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="detail-gui-elements.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="midi-manager.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="MIDI"
>Chapter 5. <SPAN
CLASS="ACRONYM"
>MIDI</SPAN
></A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="MIDI-OVERVIEW"
>5.1. Overview</A
></H1
><P
>The midi support in aRts can do a number of things. First of all, it allows
<I
CLASS="EMPHASIS"
>communication</I
> between different pieces of software that
produce or consume MIDI events. If you for instance have a sequencer and a
sampler that are both aRts aware, aRts can send the MIDI events from the
sequencer to the sampler.</P
><P
>On the other hand, aRts can also help applications to <I
CLASS="EMPHASIS"
>interact with
the hardware</I
>. If a piece of software (for instance the sampler)
works together with aRts, it will be able to receive the MIDI events from an
external MIDI keyboard as well.</P
><P
>Finally, aRts makes a great <I
CLASS="EMPHASIS"
>modular synthesizer</I
>. It is
designed to do exactly this. So you can build instruments out of small modules
using artsbuilder, and then use these instruments to compose or play music.
Synthesis does not necessarily mean pure synthesis, there are modules you can
use to play samples. So aRts can be a sampler, synthesizer, and so on, and
being fully modular, it is very easy to extend, very easy to experiment with,
powerful and flexible.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="detail-gui-elements.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="midi-manager.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><SPAN
CLASS="ACRONYM"
>GUI</SPAN
> Elements</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Midi Manager</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>