commit 4bb8ff0b541c3cdfb081d09c5f84772385e2e4b3
Author: Christopher Antila <crantila(a)fedoraproject.org>
Date: Sun Feb 27 23:24:32 2011 -0500
Fixed bugs 677362 and 674335
en-US/Book_Info.xml | 4 ++--
en-US/Digital_Audio_Workstations.xml | 4 ++--
en-US/FluidSynth.xml | 2 +-
en-US/Real_Time_and_Low_Latency.xml | 2 +-
en-US/Revision_History.xml | 22 ++++++++++++++++++++--
5 files changed, 26 insertions(+), 8 deletions(-)
---
diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml
index 0bddec9..a24c7b4 100644
--- a/en-US/Book_Info.xml
+++ b/en-US/Book_Info.xml
@@ -8,8 +8,8 @@
<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> <!-- NB: I have no idea why this is here, but the book doesn't work without it -CRA -->
- <edition>14.9.3</edition>
+ <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.4</edition>
<abstract>
<para>
diff --git a/en-US/Digital_Audio_Workstations.xml b/en-US/Digital_Audio_Workstations.xml
index ec3d075..64ed512 100644
--- a/en-US/Digital_Audio_Workstations.xml
+++ b/en-US/Digital_Audio_Workstations.xml
@@ -139,7 +139,7 @@
<section id="sect-Musicians_Guide-Region_Clip_Segment">
<title>Region, Clip, or Segment</title>
<para>
- Region, clip, and segment are synonyms: different software uses a different word to refer to the same thing. A x<firstterm>multitrack</firstterm> (or <firstterm>clip</firstterm> or <firstterm>segment</firstterm>) is the portion of audio recorded into one track during one take. Regions are represented in the main DAW interface window as a rectangle, usually coloured, and always contained in only one track. Regions containing audio signal data usually display a spectrographic representation of that data. Regions containing MIDI signal data usually displayed as matrix-based representation of that data.
+ Region, clip, and segment are synonyms: different software uses a different word to refer to the same thing. A <firstterm>region</firstterm> (or <firstterm>clip</firstterm> or <firstterm>segment</firstterm>) is the portion of audio recorded into one track during one take. Regions are represented in the main DAW interface window as a rectangle, usually coloured, and always contained in only one track. Regions containing audio signal data usually display a spectrographic representation of that data. Regions containing MIDI signal data usually displayed as matrix-based representation of that data.
</para>
<para>
For the three DAW applications in the Musicians' Guide:
@@ -166,7 +166,7 @@
<section id="sect-Musicians_Guide-Transport_and_Playhead">
<title>Transport and Playhead</title>
<para>
- The <firstterm>transport</firstterm> is responsible for managing the current time in a session, and with it the playhead. The <firstterm>playhead</firstterm> marks the point on the timeline from where audio audio would be played, or to where audio would be recorded. The transport controls the playhead, and whether it is set for recording or only playback. The transport can move the playhead forward or backward, in slow motion, fast motion, or real time. In most computer-based DAWs, the playhead can also be moved with the cursor. The playhead is represented on the DAW interface as a vertical line through all tracks. The transport's buttons and displays are usually located in a toolbar at the top of the DAW window, but some people prefer to have the transport controls detached from the main interface, and this is how they appear by default in Rosegarden.
+ The <firstterm>transport</firstterm> is responsible for managing the current time in a session, and with it the playhead. The <firstterm>playhead</firstterm> marks the point on the timeline from where audio would be played, or to where audio would be recorded. The transport controls the playhead, and whether it is set for recording or only playback. The transport can move the playhead forward or backward, in slow motion, fast motion, or real time. In most computer-based DAWs, the playhead can also be moved with the cursor. The playhead is represented on the DAW interface as a vertical line through all tracks. The transport's buttons and displays are usually located in a toolbar at the top of the DAW window, but some people prefer to have the transport controls detached from the main interface, and this is how they appear by default in Rosegarden.
</para>
</section>
diff --git a/en-US/FluidSynth.xml b/en-US/FluidSynth.xml
index 41e1c16..044dca9 100644
--- a/en-US/FluidSynth.xml
+++ b/en-US/FluidSynth.xml
@@ -68,7 +68,7 @@
<section id="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Software_Requirements">
<title>Software Requirements</title>
<para>
- <application>FluidSynth</application> requires the <systemitem><application>JACK</application> Audio Connection Kit</systemitem>. If you have not already installed the <application>JACK</application> packages from the Planet CCRMA at Home repository, then it is recommended that you do so <emphasis>before</emphasis> installing <application>FluidSynth</application>. See <xref linkend="sect-Musicians_Guide-Install_and_Configure_JACK" /> for instructions.
+ <application>FluidSynth</application> requires the <systemitem><application>JACK</application> Audio Connection Kit</systemitem>. If you have not already installed the <application>JACK</application> packages, we recommend that you do so <emphasis>before</emphasis> you install <application>FluidSynth</application>. See <xref linkend="sect-Musicians_Guide-Install_and_Configure_JACK" /> for instructions.
</para>
</section>
<section id="sect-Musicians_Guide-FluidSynth-Req_and_Inst-Installation">
diff --git a/en-US/Real_Time_and_Low_Latency.xml b/en-US/Real_Time_and_Low_Latency.xml
index 05924e6..c9e1c27 100644
--- a/en-US/Real_Time_and_Low_Latency.xml
+++ b/en-US/Real_Time_and_Low_Latency.xml
@@ -65,7 +65,7 @@
<section id="sect-Musicians_Guide-Getting_Real_Time_Kernel_in_Fedora">
<title>Getting a Real-Time Kernel in Fedora Linux</title>
<para>
- In Fedora Linux, the real-time kernel is provided by the Planet CCRMA at Home software repositories. Along with the warnings in the Planet CCRMA at Home chapter (see <xref linkend="sect-Musicians_Guide-CCRMA_Security_and_Stability" />), here is one more to consider: the real-time kernel is used by fewer people than the standard kernel, so it is less well-tested. The changes of something going wrong are relatively low, but be aware that using a real-time kernel increases the level of risk. Always leave a non-real-time option available, in case the real-time kernel stops working.
+ In Fedora Linux, the real-time kernel is provided by the Planet CCRMA at Home software repositories. Along with the warnings in the Planet CCRMA at Home chapter (see <xref linkend="sect-Musicians_Guide-CCRMA_Security_and_Stability" />), here is one more to consider: the real-time kernel is used by fewer people than the standard kernel, so it is less well-tested. The chances of something going wrong are relatively low, but be aware that using a real-time kernel increases the level of risk. Always leave a non-real-time option available, in case the real-time kernel stops working.
</para>
<para>
You can install the real-time kernel, along with other system optimizations, by following these instructions:
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index bac35b3..9bf6702 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -237,14 +237,31 @@
</revdescription>
</revision>
+ <revision>
+ <revnumber>14.9.4</revnumber>
+ <date>27 February 2011</date>
+ <author>
+ <firstname>Christopher</firstname>
+ <surname>Antila</surname>
+ <email>crantila(a)fedoraproject.org</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Added fixes for Bugs 677362 and 674335.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
<!-- NOTE: When adding a revision above, be sure to update the <edition> tag in "Book_Info.xml" -->
<!-- Finite Tasks -->
- <!-- TODO: Bug 673519 ("Where is 'Percussion' check-box?") -->
+ <!-- TODO: (QA) Bug 674335 ("JACK need not be from Planet CCRMA repo") -->
+ <!-- TODO: (QA) Bug 677362 ("simple typos") -->
+ <!-- TODO: (QA) Bug 654187 ("Errors in Musicians' Guide LilyPond section") -->
<!-- TODO: (QA) Bug 670520 ("ALSA sound server should be JACK") -->
<!-- TODO: Bug 670540 ("Qsynth's MIDI driver... ") -->
<!-- TODO: Bug 670533 ("Qtractor chapter needs step-by-step... ") -->
- <!-- TODO: (QA) Bug 654187 ("Errors in Musicians' Guide LilyPond section") -->
+ <!-- TODO: Bug 673519 ("Where is 'Percussion' check-box?") -->
<!-- TODO: Bug 665660 ("External Files for Ardour Tutorial Are Missing") -->
<!-- TODO: Bug 665662 ("SuperCollider Chapters Are in First Person") -->
<!-- TODO: Bug 665664 ("LilyPond Example Scores Are Incomplete") -->
@@ -255,6 +272,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: standardize the paragraph about installing JACK -->
<!-- Ongoing Tasks -->
<!-- TODO: ensure that everything is formatted correctly -->