1
<html><head><title>Managing banks and programs for MIDI devices</title><link rel="stylesheet" href="kde-default.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.67.2"><meta name="keywords" content="Rosegarden, sequencer, MIDI, audio, music, notation, score, KDE"><link rel="start" href="index.html" title="The Rosegarden Handbook"><link rel="up" href="studio.html" title="Chapter�5.�The Studio"><link rel="prev" href="studio-device-editor.html" title="Managing MIDI devices"><link rel="next" href="studio-audio-routing.html" title="Audio Routing"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.13 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div style="background-image: url(top-middle.png); width: 100%; height: 131px;"><div style="position: absolute; right: 0px;"><img src="top-right-konqueror.png" style="margin: 0px" alt=""></div><div style="position: absolute; top: 25px; right: 100px; text-align: right; font-size: xx-large; font-weight: bold; text-shadow: #fff 0px 0px 5px; color: #444">Managing banks and programs for MIDI devices</div></div><div style="margin-top: 20px; background-color: #white; color: black; margin-left: 20px; margin-right: 20px;"><div style="position: absolute; left: 20px;"><a accesskey="p" href="studio-device-editor.html">Prev</a></div><div style="position: absolute; right: 20px;"><a accesskey="n" href="studio-audio-routing.html">Next</a></div><div class="navCenter">The Studio</div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="studio-bank-editor"></a>Managing banks and programs for MIDI devices</h2></div></div></div><p>
2
<div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="rg-bankeditor.png" alt="The MIDI bank and program editor"><hr></div></div>
4
Remember that each MIDI device contains a number of
5
instruments, and that you can assign tracks to those
6
instruments. In MIDI terms, each instrument corresponds to
7
a single channel on your MIDI synth. You can choose which
8
of the available voices (sounds) on your synth each
9
instrument uses, but in order to do this, you need to let
10
Rosegarden know the names for all of the available voices.
12
This dialog allows you to attach banks of programs (names for
13
voices) to your MIDI devices, thus permitting each
14
instrument on a device to be set to use one of those voices
15
in the <a href="segment-view-instrumentparameterbox.html" title="The Instrument Parameter Box">Instrument
18
The usual way to set up the program names for a device is
19
simply to import them from one of the supplied device
20
(".rgd") files. To do this, select a device in the list on
21
the left of the dialog, then click the Import button below
22
the list and choose the .rgd file corresponding to your
25
If there is no current .rgd file available for your synth,
26
then you can use this dialog to create a new bank. To do this
27
you will have to find the program map in your synth's MIDI
28
Implementation Chart and enter all the names by hand: you can
29
then Export them to a .rgd file to share with other Rosegarden
30
users. Contact the rosegarden-user mailing list if you have
31
made a new .rgd file and would like to share it. (This is how
32
all of the existing .rgd files have come to be included with
33
Rosegarden: other users have contributed them.)
34
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="studio-keymappings"></a>Percussion Key Mappings</h3></div></div></div><p>
35
Many MIDI synthesizers have at least one percussion program,
36
in which each "pitch" plays a different type of sound.
37
Rosegarden contains a dedicated percussion matrix editor to
38
view and edit notes against a scale consisting of the
39
correct names for the pitches, instead of against the
40
conventional piano keyboard pitch scale.
42
The key mappings available for a particular MIDI device are
43
also defined in the Rosegarden device (".rgd") file. Each
44
MIDI program that is defined as a percussion program can
45
have a key mapping associated with it; if there is one, then
46
it will be used by default in any track that is assigned to
47
this program. Like program and bank definitions, key
48
mappings can be imported from and exported to .rgd files.
49
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="studio-soundfonts"></a>SoundFonts</h3></div></div></div><p>
50
If you happen to be using a soft-synth or soundcard synth
51
that uses SoundFont (.sf2) files, you can simply load the
52
correct program names directly from your .sf2 file into this
53
dialog. Just ask to Import as normal, and then choose the
54
.sf2 file that you are using instead of a .rgd file.
55
</p><p>Note that the Studio only manages information about
56
existing MIDI devices for Rosegarden, it does not actually
57
handle tasks such as loading a SoundFont to your soundcard in
58
the first place. If you want to make sure a SoundFont is
59
loaded to your soundcard when Rosegarden starts up, you should
60
use the special "Load SoundFont to SoundBlaster card at
61
startup" option in the sequencer configuration in
62
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenu">Settings</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Configure Rosegarden...</span></span>.
63
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="studio-variations"></a>Variations</h3></div></div></div><p>
64
Some MIDI devices (for example, those from Roland)
65
organise their program names using a scheme known as
66
"variations". For these devices, you generally want to
67
select a program by first selecting the basic program name
68
— such as a piano — and then selecting one
69
of a set of variations on that program — such as an
70
electric piano. This is in contrast to General MIDI-based
71
synths, which organise their programs into banks and
72
expect you to choose a bank first and then a program from
75
Rosegarden can support devices that use variations, but
76
you still have to enter the program names in a bank
77
format. Internally, devices that use variations still use
78
MIDI bank select controllers to choose between the
79
variations; you need to find out from your synth's
80
documentation whether your device uses the LSB or MSB bank
81
select to choose variations, and which bank number
82
corresponds to which variation. You can then enter the
83
banks as normal, and use the "Show Variation list based on
84
MSB/LSB" option on the bank dialog to tell Rosegarden to
85
show variations instead of banks when displaying that
86
device in an instrument parameter box.
87
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="studio-midi-import"></a>Program mapping on <span class="acronym">MIDI</span> import</h3></div></div></div><p>
89
When you import a <span class="acronym">MIDI</span> file into a composition, <span class="application">Rosegarden</span>
90
uses the existing studio setup to determine how to map the
91
<span class="acronym">MIDI</span> programs onto <span class="application">Rosegarden</span> instruments. The aim is to
92
ensure that every <span class="acronym">MIDI</span> program gets mapped to an instrument
93
that really exists in your studio (and thus is actually
94
attached to your computer), so that all the <span class="acronym">MIDI</span> tracks
99
The <span class="acronym">MIDI</span> program-change and bank-select events found in the
100
imported file are used when importing, but only as an aid to
101
help find the appropriate instrument for each <span class="acronym">MIDI</span> track
102
from the set of instruments in your studio. So, for
103
example, if your studio is currently set up to contain only
104
<span class="acronym">GM</span> instruments, and you import a <span class="acronym">MIDI</span> file with <span class="acronym">GS</span> program
105
changes onto it, <span class="application">Rosegarden</span> will remap the <span class="acronym">GS</span> banks back
106
onto <span class="acronym">GM</span> because they're all it knows that you have at the
107
time you import the file. It doesn't remember the original
108
<span class="acronym">GS</span> program numbers.
112
This means that you should always ensure that your studio is
113
correctly configured for the devices you actually have,
114
before you import the <span class="acronym">MIDI</span> file. Otherwise the program data
115
in the <span class="acronym">MIDI</span> file may be lost.
117
</p></div></div><div style="background-color: #white; color: black; margin-top: 20px; margin-left: 20px; margin-right: 20px;"><div style="position: absolute; left: 20px;"><a accesskey="p" href="studio-device-editor.html">Prev</a></div><div style="position: absolute; right: 20px;"><a accesskey="n" href="studio-audio-routing.html">Next</a></div><div align="center"><a accesskey="h" href="index.html">Home</a></div></div><div style="background-color: #white; color: black; margin-left: 20px; margin-right: 20px;"><div class="navLeft">Managing MIDI devices�</div><div class="navRight">�Audio Routing</div><div class="navCenter"><a accesskey="u" href="studio.html">Up</a></div></div><br><br><div class="bannerBottom" style="background-image: url(bottom-middle.png); background-repeat: x-repeat; width: 100%; height: 100px; bottom:0px;"><div class="BannerBottomRight"><img src="bottom-right.png" style="margin: 0px" alt=""></div><div class="bannerBottomLeft"><img src="bottom-left.png" style="margin: 0px;" alt=""></div><div id="comments" style="position:relative; top: 5px; left: 1em; height:85px; width: 50%; color: #cfe1f6"><p>Would you like to make a comment or contribute an update to this page?<br>
118
Send feedback to the <a href="mailto:kde-docs@kdemail.net" style="background:transparent; color:#cfe1f6; text-decoration: underline;">KDE Docs Team</a></p></div></div></body></html>
b'\\ No newline at end of file'