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 Maps</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The KMid Handbook"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Deleting a collection"
HREF="deletingacollection.html"><LINK
REL="NEXT"
TITLE="Do I need a midi map ?"
HREF="doineedamidimap.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 KMid Handbook</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="deletingacollection.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="doineedamidimap.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="MIDIMAPS"
>Chapter 4. Midi Maps</A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="WHATISAMIDIMAP"
>4.1. What is a midi map ?</A
></H1
><P
>A Midi Map is something that maps midi events in other midi events .</P
><P
>This is totally needed if a synthesizer doesn't understand the standard events (that is, if a synthesizer is not General Midi compliant), in this case, a midi map will translate General Midi events in the events that that synthesizer understands.</P
><P
>For example you can make a midi map that converts all the <TT
CLASS="LITERAL"
>Change patch to
Bright Piano</TT
> events, to <TT
CLASS="LITERAL"
>Change patch to Trumpet</TT
> events, and so when a song tries to play a piano, it will play a trumpet instead.</P
><P
>This may sound odd, (why playing a trumpet when the song is made to play
a piano ?), but it is very useful. The GM standard specifies that when a
midi keyboard receives an event to change patch to <TT
CLASS="LITERAL"
>0</TT
>, it will change the
current patch to <TT
CLASS="LITERAL"
>Grand Piano</TT
>, but older synthesizer will change for example to a <TT
CLASS="LITERAL"
>Electric Guitar</TT
> when it receives a <TT
CLASS="LITERAL"
>0</TT
>. This old keyboard,
needed to receive a <TT
CLASS="LITERAL"
>3</TT
> (for example) to change to a <TT
CLASS="LITERAL"
>Piano</TT
>. And here comes
the midi map in action, changing all <TT
CLASS="LITERAL"
>change patch to 0</TT
> to <TT
CLASS="LITERAL"
>change patch to 3</TT
> and thus really playing the correct instrument when it has to.</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="deletingacollection.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="doineedamidimap.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Deleting a collection</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Do I need a midi map ?</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>