[musicians-guide] fixed bug 670540; various revisions to FluidSynth and Rosegarden
crantila
crantila at fedoraproject.org
Wed Jun 15 20:41:47 UTC 2011
commit 6158823a420e764c6ab32c028302242809e6b8bc
Author: Christopher Antila <crantila at fedoraproject.org>
Date: Wed Jun 15 16:41:30 2011 -0400
fixed bug 670540; various revisions to FluidSynth and Rosegarden
en-US/Book_Info.xml | 4 +-
en-US/FluidSynth.xml | 74 ++++++++++++++++++++++----------------------
en-US/Revision_History.xml | 21 ++++++++++++-
en-US/Rosegarden.xml | 68 +++++++++++++++++++++-------------------
4 files changed, 94 insertions(+), 73 deletions(-)
---
diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml
index 35f7af9..bd6f3be 100644
--- a/en-US/Book_Info.xml
+++ b/en-US/Book_Info.xml
@@ -5,11 +5,11 @@
]>
<bookinfo id="book-Musicians_Guide-Musicians_Guide">
<title>Musicians' Guide</title>
- <subtitle>Audio creation and music software in Fedora Linux.</subtitle>
+ <subtitle>Audio creation and music software in Fedora Linux</subtitle>
<!-- Haydn: <subtitle>A guide to Fedora Linux's audio creation and music capabilities, written in a new and special way.</subtitle> -->
<productname>Fedora Draft Documentation</productname>
<pubsnumber>0</pubsnumber> <!-- N.B.: I have no idea why this is here, but the book doesn't work without it -CRA -->
- <edition>14.9.5</edition>
+ <edition>15.9.1</edition>
<abstract>
<para>
diff --git a/en-US/FluidSynth.xml b/en-US/FluidSynth.xml
index 044dca9..901e6c4 100644
--- a/en-US/FluidSynth.xml
+++ b/en-US/FluidSynth.xml
@@ -26,6 +26,7 @@
<para>
There is a large selection of SoundFonts available for free on the internet, and some are also available for purchase, including a few very high quality SoundFonts. The following three websites have links to SoundFont resources, and some SoundFonts available for paid or free download. No guarantee is made of the quality of the material provided, or of the quality and security of the websites.
<itemizedlist>
+ <!-- I verified these on 15 June 2011 (crantila) -->
<listitem><para><citetitle>S. Christian Collins' "General User" SoundFont</citetitle>, available from <ulink url="http://www.schristiancollins.com/generaluser.php" />.</para></listitem>
<listitem><para><citetitle>HammerSound SoundFont Library</citetitle>, available at <ulink url="http://www.hammersound.net/cgi-bin/soundlink.pl" />.</para></listitem>
<listitem><para><citetitle>homemusician.net SoundFont Library</citetitle>, available at <ulink url="http://soundfonts.homemusician.net/" />.</para></listitem>
@@ -33,7 +34,7 @@
</itemizedlist>
</para>
<para>
- See the "Optional Installation: SoundFont ..." below for installation instructions.
+ See <xref linkend="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Install_SoundFont_Files" /> below for instructions to install a SoundFont.
</para>
</section>
<section id="sect-Musicians_Guide-FluidSynth-MIDI_Terms">
@@ -72,7 +73,7 @@
</para>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Installation">
- <title>Thare Are Two Ways to Install <application>FluidSynth</application></title>
+ <title>Install <application>FluidSynth</application></title>
<para>
There are two ways to install <application>FluidSynth</application>. The first, to install <application>FluidSynth</application> with <application>Qsynth</application>, allows <application>FluidSynth</application> to be used with the <application>Qsynth</application> graphical interface. It also installs a default SoundFont, which can be used by any SoundFont-aware application (like <application>timidity++</application>). This installation method does not - by default - allow <application>FluidSynth</application> to be used from a terminal, although this ability can be easily added later. This is the installation method recommended for most users.
</para>
@@ -81,36 +82,31 @@
</para>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Installation_with_Qsynth">
- <title>Installation with <application>Qsynth</application></title>
+ <title>Install with <application>Qsynth</application></title>
<para>
- This installation method is recommended for most users, and will install everything you need to start using <application>FluidSynth</application>.
+ We recommend this installation method for most users. Follow these instructions to install everything you need for <application>FluidSynth</application>.
</para>
<procedure>
- <step><para>Use "PackageKit" or "KPackageKit" to install the "qsynth" package.</para></step>
- <step><para>Review and approve the proposed installation:
- <itemizedlist>
- <listitem><para><!-- this was another warning to install <application>JACK</application> but I don't want it any more --></para></listitem>
- <listitem><para>The installation may include the "fluid-soundfont-gm" package, which is quite large.</para></listitem>
- </itemizedlist>
- </para></step>
+ <step><para>Use <application>PackageKit</application> or <application>KPackageKit</application> to install the <package>qsynth</package> package.</para></step>
+ <step><para>Review and approve the proposed installation. If you did not previously install the <package>fluid-soundfont-gm</package> packge, <application>PackageKit</application> will install it now. The <package>fluid-soundfont-gm</package> package is approximately 142 MB.</para></step>
</procedure>
<para>
- If you wish to use <application>FluidSynth</application> from a terminal, without the <application>Qsynth</application> graphical interface, you can enable this capability by installing the <package>fluidsynth</package> package. This package is not needed if you only intend to run <application>FluidSynth</application> with <application>Qsynth</application>, because <application>Qsynth</application> only uses files in the <package>fluidsynth-libs</package> package, which is automatically installed with <application>Qsynth</application>. If you are unsure of whether you should install the <package>fluidsynth</package> package, you can safely install it, even if you never use it. It only uses a small amount of hard drive space.
+ If you wish to use <application>FluidSynth</application> from a terminal emulator, without the <application>Qsynth</application> graphical interface, you can enable this capability by installing the <package>fluidsynth</package> package. You do not need <package>fluidsynth</package> if you will use the <application>Qsynth</application> graphical interface. If you are unsure whether you want the <package>fluidsynth</package> package, you can safely install it, even if you never use it. It only uses a small amount of hard drive space.
</para>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Installation_without_Qsynth">
- <title>Installation without <application>Qsynth</application></title>
+ <title>Install without <application>Qsynth</application></title>
<para>
- This installation method is recommended only for advanced users. You will have to use <application>FluidSynth</application> from a terminal. You will also have to install a SoundFont file before using <application>FluidSynth</application>.
+ We only recommend this installation method for advanced users. Follow these instructions to install <application>FluidSynth</application> without a graphical interface or SoundFont file. You must install a SoundFont file before you can use <application>FluidSynth</application> (see <xref linkend="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Install_SoundFont_Files" />).
</para>
<para>
Use <application>PackageKit</application> or <application>KPackageKit</application> to install the <package>fluidsynth</package> package.
</para>
</section>
- <section id="sect-Musicians_Guide-FluidSynth-Req_and_Inst">
- <title>Installation of SoundFont Files</title>
+ <section id="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Install_SoundFont_Files">
+ <title>Install SoundFont Files</title>
<para>
- <application>Qsynth</application> automatically installs a SoundFont for use with <application>FluidSynth</application>, but if you did not install <application>Qsynth</application>, or if you want to add additional SoundFont files with additional programs, you will need to install them separately. The Fedora package repositories offer a small selection of SoundFont files, which you can find by searching for "soundfont" with PackageKit, KPackageKit, or yum. These files will automatically be installed correctly. If you wish to install additional SoundFont files, it is recommended that you install them in the same location - and with the same security settings - as the ones available from the Fedora repositories. If you do this, then you enable all users of the computer system to access the files, you will not "lose" them if you forget where they are stored, and you help to minimize the potential security risk of using software downloaded from the internet.
+ <application>Qsynth</application> automatically installs a SoundFont for use with <application>FluidSynth</application>, but if you did not install <application>Qsynth</application>, or if you want to add additional SoundFont files with additional programs, you will need to install them separately. The Fedora package repositories offer a small selection of SoundFont files, which you can find by searching for "soundfont" with <application>PackageKit</application>, <application>KPackageKit</application>, or <application>yum</application>. These files will automatically be installed correctly. If you wish to install additional SoundFont files, it is recommended that you install them in the same location - and with the same security settings - as the ones available from the Fedora repositories. If you do this, then you enable all users of the computer system to access the files, you will not "lose" them if you forget where they are stored, and you help to minimize the po
tential security risk of using software downloaded from the internet.
</para>
<para>
The following steps move a SoundFont file called <filename>myFont.sf2</filename> to the default folder (<filename>/usr/share/soundfonts</filename>), and correctly set the security settings. Note that you will need the system administrator's password (belonging to the "root" account) to complete this operation. If you do not have this password, it is best to ask the system administrator to install the files for you. Alternately, you may simply use the SoundFont file from your a sub-folder in your home folder.
@@ -139,7 +135,7 @@
</section> <!-- Ends "Requirements and Installation" Section --> <!-- <application>FluidSynth</application>-Req_and_Inst- -->
<section id="sect-Musicians_Guide-FluidSynth-In_a_Terminal">
- <title>Using <application>FluidSynth</application> in a Terminal</title>
+ <title>Use <application>FluidSynth</application> in a Terminal Emulator</title>
<para>
This is not the recommended way to use <application>FluidSynth</application>, because the <application>Qsynth</application> graphical interface is much easier to use. <application>Qsynth</application> automatically configures most of <application>FluidSynth</application>'s settings by default, allowing you to avoid focus on how you want to use <application>FluidSynth</application>, rather than on how to use <application>FluidSynth</application>.
</para>
@@ -152,12 +148,12 @@
</section>
<section id="sect-Musicians_Guide-FluidSynth-Configuring">
- <title>Configuring <application>Qsynth</application></title>
+ <title>Configure <application>Qsynth</application></title>
<para>
When you quit <application>Qsynth</application>, all settings are preserved, and re-used when <application>Qsynth</application> is re-started. This includes settings for additional instances of <application>Qsynth</application> (described below), which are also re-created when <application>Qsynth</application> is re-started.
</para>
<section id="sect-Musicians_Guide-FluidSynth-Configuring-Starting_FluidSynth">
- <title>Starting <application>FluidSynth</application></title>
+ <title>Start <application>FluidSynth</application></title>
<procedure>
<step><para>Start <application>Qsynth</application> from the Applications menu, or the K Menu</para></step>
<step><para>The <application>FluidSynth</application> engine will be started automatically.</para></step>
@@ -166,7 +162,7 @@
</procedure>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Configuring-SoundFont">
- <title>SoundFont Configuration</title>
+ <title>Configure the SoundFont</title>
<para>
The default "FluidR3" SoundFont, installed with <application>Qsynth</application>, is automatically configured.
</para>
@@ -174,13 +170,13 @@
To configure an additional Soundfount:
</para>
<procedure>
- <step><para>Click on the 'Open' button, and navigate to the path of the SoundFont you wish to add. This should be <filename>/usr/share/soundfonts</filename>, if installed to the standard location specified in <xref linkend="sect-Musicians_Guide-FluidSynth-Req_and_Inst" />.</para></step>
+ <step><para>Click on the 'Open' button, and navigate to the path of the SoundFont you wish to add. This should be <filename>/usr/share/soundfonts</filename>, if installed to the standard location specified in <xref linkend="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Install_SoundFont_Files" />.</para></step>
<step><para>Select the additional SoundFont, then click the 'Open' button.</para></step>
<step><para>To change the SoundFont ID (SFID), use the 'Up' and 'Down' buttons to change the position of the SoundFonts, as desired. This does not directly change the function of <application>FluidSynth</application> - any SoundFont should work with any SoundFont ID number.</para></step>
</procedure>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Configuring-JACK_Output">
- <title><application>JACK</application> Output Configuration</title>
+ <title>Configure <application>JACK</application> Output</title>
<para>
It is possible to configure <application>FluidSynth</application> to output synthesized audio either to <application>JACK</application> or to ALSA. The default, and recommended, method is to output synthesized audio to <application>JACK</application>. This allows the greatest control over audio quality, and the greatest flexibility in terms of routing and multiplexing (for definition see <xref linkend="sect-Musicians_Guide-Vocabulary-Routing_and_Multiplexing" />), which allows you to simultaneously record the synthesized audio signal and listen to it.
</para>
@@ -206,24 +202,28 @@
</para>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Configuring-MIDI_Input">
- <title>MIDI Input Configuration</title>
+ <title>Configure MIDI Input</title>
<para>
- <application>FluidSynth</application> will only produce sound as instructed by a connected (software- or hardware-based) MIDI device. If you are having problems configuring <application>FluidSynth</application> to accept MIDI input, verify the following options.
+ <application>FluidSynth</application> generates sound as instructed by a connected (software- or hardware-based) MIDI device. Verify the following settings so <application>FluidSynth</application> connects to the devices you want.
</para>
<procedure>
- <step><para>Open <application>Qsynth</application>'s "Setup" window.</para></step>
- <step><para>The "Enable MIDI Input" setting must be enabled.</para></step>
- <step><para>There are two settings for "MIDI Driver" that you would likely want.
+ <step><para>Open the <application>Qsynth</application> "Setup" window.</para></step>
+ <step><para>The "Enable MIDI Input" check-box must be checked.</para></step>
+ <step><para>Choose the correct "MIDI Driver" setting:
<itemizedlist>
- <listitem><para>When set to "alsa_seq", the input will appear on <application>QjackCtl</application>'s "ALSA" tab in the "Connect" window. This is useful if the MIDI generator device that you are using, such as a MIDI-enabled keyboard, is connected directly to ALSA.</para></listitem>
- <listitem><para>When set to "jack", the input will appear on <application>QjackCtl</application>'s "MIDI" tab in the "Connect" window. This is useful if the MIDI generator device that you are using, such as <application>Rosegarden</application>, is connected directly to <application>JACK</application>.</para></listitem>
+ <listitem>
+ <para>Use the "alsa_seq" setting if you want to connect <application>FluidSynth</application> with a source on the "ALSA" tab of the <application>QjackCtl</application> "Connect" window. Use this setting for <application>Rosegarden</application> and <application>Qtractor</application> in most cases.</para>
+ </listitem>
+ <listitem>
+ <para>Use the "jack" setting if you want to connect <application>FluidSynth</application> with a sources on the "MIDI" tab of the <application>QjackCtl</application> "Connect" window.</para>
+ </listitem>
</itemizedlist>
- </para></step>
- <step><para>You can set the number of MIDI input channels provided by <application>FluidSynth</application>. Refer to <xref linkend="sect-Musicians_Guide-FluidSynth-Changing_Number_of_Input_Channels" /> below.</para></step>
+ </para></step>
+ <step><para>If you want to change the number of MIDI input channels in <application>FluidSynth</application>, refer to <xref linkend="sect-Musicians_Guide-FluidSynth-Changing_Number_of_Input_Channels" /> below.</para></step>
</procedure>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Configuring-Viewing_all_Settings">
- <title>Viewing all <application>FluidSynth</application> Settings</title>
+ <title>View all <application>FluidSynth</application> Settings</title>
<procedure>
<step><para>Open the "Setup" window</para></step>
<step><para>Select the "Settings" tab</para></step>
@@ -234,7 +234,7 @@
</section>
<section id="sect-Musicians_Guide-FluidSynth-Assigning_Programs_to_Channels">
- <title>Assigning Programs to Channels with <application>Qsynth</application></title>
+ <title>Assign Programs to Channels with <application>Qsynth</application></title>
<para>
The best way to do this is through your MIDI sequencer, like <application>Qtractor</application> or <application>Rosegarden</application>. If you are using an application which doesn't allow you to send program-change messages, or if you need to configure programs for another reason, you can follow these instructions.
</para>
@@ -248,7 +248,7 @@
<step><para>Remember that channel 10 is reserved for percussion instruments, and should not be changed from a General MIDI percussion program.</para></step>
</procedure>
<section id="sect-Musicians_Guide-FluidSynth-Changing_Number_of_Input_Channels">
- <title>Changing the Number of MIDI Input Channels</title>
+ <title>Change the Number of MIDI Input Channels</title>
<para>
You can increase the number of MIDI input channels offered by <application>FluidSynth</application>. Although <application>QSynth</application> will let you set any number between 1 and 256, channels will be added and removed only in sets of 16. <application>Qsynth</application> will automatically create the lowest number of channels that will allow as many channels as you need. Each set of 16 channels will be indicated in <application>JACK</application> with an additional MIDI input device. The name of the device indicates which channels are listening: channels 1 through 16 listen to the device ending in 0; channels 17 through 32 listen to the device ending in 1; channels 33 through 58 listen to the device ending in 2; and so on.
</para>
@@ -262,7 +262,7 @@
</procedure>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Saving_and_Reusing_Channel_Assignments">
- <title>Saving and Reusing Channel Assignments</title>
+ <title>Save and Reuse Channel Assignments</title>
<para>
QSynth allows you to save multiple sets of program assignments, which you can restore later. This means that you will not have to re-configure all of the channels every time you want to change them.
</para>
@@ -286,7 +286,7 @@
</section>
<section id="sect-Musicians_Guide-FluidSynth-Reverb_and_Chorus">
- <title>Using Reverb and Chorus with <application>Qsynth</application></title>
+ <title>Use Reverb and Chorus with <application>Qsynth</application></title>
<para>
While "reverb" (meaning "reverberation") and "chorus" effects are not part of the General MIDI standard, they are offered by most MIDI synthesizers. <application>FluidSynth</application> is no exception, and the <application>Qsynth</application> interface provides a convenient and easy way to adjust settings of the reverb and chorus effect-generators. Experimentation is the only way to know whether you have chosen the right settings, and they will probably change depending on the music you are working on, and even during a piece. Most MIDI sequencers and players (including Qtractor and Rosegarden) allow you to send MIDI messages changing the reverb and chorus settings while a session is playing.
</para>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index b7fd469..285c3b6 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -297,10 +297,28 @@
</revdescription>
</revision>
+ <revision>
+ <revnumber>15.9.1</revnumber>
+ <date>15 June 2011</date>
+ <author>
+ <firstname>Christopher</firstname>
+ <surname>Antila</surname>
+ <email>crantila at fedoraproject.org</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Fixed Bug 670540.</member>
+ <member>Revised several other aspects of Chapters 9 (Rosegarden) and 10 (FluidSynth).</member>
+ <member>Removed period from end of subtitle.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
<!-- NOTE: When adding a revision above, be sure to update the <edition> tag in "Book_Info.xml" -->
<!-- Fedora 16 (General) -->
<!-- TODO: standardize the paragraph about installing JACK -->
+ <!-- TODO: ensure correct permissions for JACK; I think I have the user group wrong -->
<!-- TODO: finish the "TODO" in Ardour.xml at line 178 -->
<!-- TODO: Bug 673519 ("Where is 'Percussion' check-box?") -->
<!-- TODO: Bug 710330 ("Section 11.5.1 Broken Link to Local Help File") -->
@@ -312,7 +330,7 @@
<!-- TODO: Bug 665664 ("LilyPond Example Scores Are Incomplete") -->
<!-- Fedora 16 (Qthings) -->
- <!-- TODO: Bug 670540 ("Qsynth's MIDI driver... ") -->
+ <!-- QA: Bug 670540 ("Qsynth's MIDI driver... ") -->
<!-- TODO: Bug 670533 ("Qtractor chapter needs step-by-step... ") -->
<!-- Low-Priority -->
@@ -324,6 +342,7 @@
<!-- TODO: convert SuperCollider examples to <xi:include ... /> -->
<!-- TODO: convert LilyPond examples to <xi:include ... /> -->
<!-- TODO: see whether SELinux can be configured to determine who/what has access to real-time stuff for JACK -->
+ <!-- TODO: fix up the SELinux portion of "Install SoundFont Files" in FluidSynth (ch. 10.2.5 in f15) -->
<!-- Ongoing Tasks -->
<!-- TODO: ensure that everything is formatted correctly -->
diff --git a/en-US/Rosegarden.xml b/en-US/Rosegarden.xml
index 235a6fe..38c9245 100644
--- a/en-US/Rosegarden.xml
+++ b/en-US/Rosegarden.xml
@@ -47,50 +47,52 @@
<section id="sect-Musicians_Guide-Rosegarden-Configuration-JACK_and_Qsynth">
<title>Setup <application>JACK</application> and <application>Qsynth</application></title>
- <para>
- <orderedlist>
- <listitem><para>Start <application>QjackCtl</application> to control <application>JACK</application>.</para></listitem>
- <listitem><para>Start <application>Qsynth</application> to control FluidSynth.</para></listitem>
- <listitem><para>In order to receive MIDI input from <application>Rosegarden</application>, <application>Qsynth</application> will need to be configured to use the "alsa_seq" MIDI Driver. Instructions for doing this can be found in <xref linkend="sect-Musicians_Guide-FluidSynth-Configuring-MIDI_Input" />.</para></listitem>
- <listitem><para>You may want to disconnect all <application>JACK</application> connections except for those that you want to use with <application>Rosegarden</application>. Open <application>QjackCtl</application>'s "Connect" window, and verify the following:
+ <procedure>
+ <step><para>Start <application>QjackCtl</application> to control <application>JACK</application>.</para></step>
+ <step><para>Start <application>Qsynth</application> to control <application>FluidSynth</application>. <application>FluidSynth</application> starts automatically.</para></step>
+ <step><para>Start <application>Rosegarden</application>.</para></step>
+ <step><para>Configure <application>Qsynth</application> to use the "alsa_seq" MIDI driver. Refer to <xref linkend="sect-Musicians_Guide-FluidSynth-Configuring-MIDI_Input" />.</para></step>
+ <step><para>You may want to disconnect all <application>JACK</application> connections except the connections you will use with <application>Rosegarden</application>. Use the <application>QjackCtl</application> "Connect" window to make these connections:
<itemizedlist>
- <listitem><para>On the "Audio" tab:
- <itemizedlist>
- <listitem><para>Qsynth's output ports are connected to the "system" input ports.</para></listitem>
- <listitem><para>If you plan to use audio in <application>Rosegarden</application> (in addition to MIDI), then you will need to connect its output ports to the "system" input ports, too. The ports labeled "record monitor" are to be used to monitor audio while it is being recorded. The ports labeled "master out" will be used during regular file playback. <application>Rosegarden</application> does not need to be connected directly to the system output ports if you are only using MIDI.</para></listitem>
- <listitem><para>If you plan to record audio in <application>Rosegarden</application>, then you will need to connect an output port (probably from "system") to <application>Rosegarden</application>'s input port. Be aware that <application>Rosegarden</application> can record from two independent sources ("1" and "2"), with two channels ("L" for left and "R" for right) from each, to produce a stereo recording.</para></listitem>
- </itemizedlist>
- </para></listitem>
- <listitem><para>On the "MIDI" tab:
- <itemizedlist><listitem><para>Nothing.</para></listitem></itemizedlist>
- </para></listitem>
- <listitem><para>On the "ALSA" tab:
- <orderedlist>
- <listitem><para>Rosegarden's output ports must be connected to the "FLUID synth" input port:
+ <listitem><para>On the "Audio" tab:
<itemizedlist>
- <listitem><para>1:sync out (sends MIDI control messages)</para></listitem>
- <listitem><para>2:external controller (for the first set of MIDI instruments in the session)</para></listitem>
- <listitem><para>3:out 2 - General MIDI Device (for the second set of MIDI instruments in the session)</para></listitem>
+ <listitem><para>The <application>Qsynth</application> output ports connect to the "system" input ports. If you only use MIDI in <application>Rossegarden</application>, and you do not use audio in <application>Rosegarden</application>, you do not need further connections on the "Audio" tab.</para></listitem>
+ <listitem><para>If you use audio in <application>Rosegarden</application>, ensure the "master out" ports connect to the "system" input ports.</para></listitem>
+ <listitem><para>If you use audio in <application>Rosegarden</application>, ensure the "record monitor" ports connect to the "system" input ports.</para></listitem>
+ <listitem><para>If you use audio in <application>Rosegarden</application>, ensure the input ports connect to the "system" outputput ports. Note that <application>Rosegarden</application> can record from two independent sources ("1" and "2"), with two channels ("L" for left and "R" for right) from each, to produce a stereo recording.</para></listitem>
</itemizedlist>
</para></listitem>
- <listitem><para>To make <application>Rosegarden</application> take commands from another MIDI device, you'll need to connect its output ports to <application>Rosegarden</application>'s input ports. I don't know what they are for yet:
- <itemizedlist>
- <listitem><para>0:record in</para></listitem>
- <listitem><para>2:external controller</para></listitem>
- </itemizedlist>
+ <listitem><para>On the "MIDI" tab:
+ <itemizedlist><listitem><para>Nothing.</para></listitem></itemizedlist>
+ </para></listitem>
+ <listitem><para>On the "ALSA" tab:
+ <orderedlist>
+ <listitem><para>Connect the <application>Rosegarden</application> output ports to the "FLUID synth" input ports:
+ <itemizedlist>
+ <listitem><para>1:sync out (sends MIDI control messages)</para></listitem>
+ <listitem><para>2:external controller (for the first set of MIDI instruments in the session)</para></listitem>
+ <listitem><para>3:out 2 - General MIDI Device (for the second set of MIDI instruments in the session)</para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>If you want <application>Rosegarden</application> to accept commands from other MIDI devices, connect these <application>Rosegarden</application> input ports to the other devices output ports:
+ <itemizedlist>
+ <listitem><para>0:record in</para></listitem>
+ <listitem><para>2:external controller</para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ </orderedlist>
</para></listitem>
- </orderedlist>
- </para></listitem>
</itemizedlist>
- </para></listitem>
- </orderedlist>
- </para>
+ </para></step>
+ </procedure>
<para>
- If a connection is not being used, it is better to leave it disconnected, to avoid making mistakes.
+ We recommend that you disconnect all ports unless you need to connect them. If you have an extra connection, you may accidentally send a signal, and produce undesirable results.
</para>
</section>
+
<section id="sect-Musicians_Guide-Rosegarden-Configuration-Rosegarden">
<title>Setup <application>Rosegarden</application></title>
+
<para>
<orderedlist>
<listitem><para>'Edit > Preferences'</para></listitem>
More information about the docs-commits
mailing list