Notice that if any gain automation has been set and the automation state is set on "Play" (see below), then the Gain fader is driven by - the automation, and not by the user. The Gain fader will turn grey to show it's + the automation, and not by the user. The Gain fader will turn grey to show it is inactive.
diff --git a/include/backup-and-sharing-of-sessions.html b/include/backup-and-sharing-of-sessions.html index bed790c..da89ee9 100644 --- a/include/backup-and-sharing-of-sessions.html +++ b/include/backup-and-sharing-of-sessions.html @@ -81,7 +81,7 @@Encoding the audio sources to FLAC allows for a good size reduction of the session. It should be noted though that FLAC is a fixed-point format, meaning that if the - audio in the session is in a floating-point format, this conversion will loose + audio in the session is in a floating-point format, this conversion will lose some information on the samples values that are rounded, though usually, this lost information cannot be perceived. Choosing "None" for Audio Compression does not compress the audio to FLAC, hence preserving the floating-point diff --git a/include/behringer-devices-in-mackielogic-control-mode.html b/include/behringer-devices-in-mackielogic-control-mode.html index 2451459..80b4669 100644 --- a/include/behringer-devices-in-mackielogic-control-mode.html +++ b/include/behringer-devices-in-mackielogic-control-mode.html @@ -192,7 +192,7 @@ The surface can be broken into 8 groups of controls:
Use name highlight bars in region display When enabled the - region name is displayed, in the editor, in it's own bar at the bottom of + region name is displayed, in the editor, in its own bar at the bottom of the region. When disabled, the region name is display at the top of the region, possibly over audio waveforms or MIDI notes.
diff --git a/include/latency-and-latency-compensation.html b/include/latency-and-latency-compensation.html index c688393..62009f2 100644 --- a/include/latency-and-latency-compensation.html +++ b/include/latency-and-latency-compensation.html @@ -83,7 +83,7 @@ Low latency is not always a feature you want to have. It comes with a couple of drawbacks: the most prominent is increased power consumption because the CPU needs to process many small chunks of audio data, - it is constantly active and can not enter power-saving mode (think fan-noise). + it is constantly active and can not enter power-saving mode (think fan noise). Since each application that is part of the signal chain must run in every audio cycle, low-latency systems will undergocontext switches between applications more often, which incur a significant overhead. @@ -95,7 +95,7 @@A large delay between the pressing of the keys and the sound the instrument - produces will throw-off the timing of most instrumentalists (save church + produces will throw off the timing of most instrumentalists (save church organists, whom we believe to be awesome latency-compensation organic systems.)
- This is where latency-compensation comes into play. There are two ways to + This is where latency compensation comes into play. There are two ways to compensate for latency in a DAW, read-ahead and write-behind. The DAW starts playing a bit early (relative to the playhead), so that when the sound arrives at the speakers a short time later, it is exactly aligned with the material that is being recorded. - Since we know that play-back has latency, the incoming audio can be delayed + Since we know that playback has latency, the incoming audio can be delayed by the same amount to line things up again.
As you may see, the second approach is prone to various implementation issues regarding timecode and transport synchronization. Ardour uses read-ahead to compensate for latency. The time displayed in the Ardour clock corresponds - to the audio-signal that you hear on the speakers (and is not where Ardour + to the audio signal that you hear on the speakers (and is not where Ardour reads files from disk).
diff --git a/include/osc58-automation.html b/include/osc58-automation.html index 6515f08..3e82c20 100644 --- a/include/osc58-automation.html +++ b/include/osc58-automation.html @@ -1,6 +1,6 @@
- Ardour has automation modes for many of it's controls. As of version + Ardour has automation modes for many of its controls. As of version 5.9, OSC can control what automation mode a fader uses. (See Automation.)
diff --git a/include/osc58-controlling-ardour-with-osc.html b/include/osc58-controlling-ardour-with-osc.html index 3543e98..e6ba85f 100644 --- a/include/osc58-controlling-ardour-with-osc.html +++ b/include/osc58-controlling-ardour-with-osc.html @@ -53,9 +53,9 @@ here"/>- Control surface set up allows the controller to tell Ardour about it's + Control surface set up allows the controller to tell Ardour about its capabilities. The surface can tell Ardour how many control strips it - has for banking, if it is capable of setting it's faders or buttons + has for banking, if it is capable of setting its faders or buttons to values set by Ardour's GUI or automation, What kind of math the faders use and more.
@@ -600,7 +600,7 @@ Any of these actions that can be moved to session->action calls may reapear.Ardour does feedback by sending the same path back that is used to control the same function. As such any controls that have feedback - have a parameter that is the value of the control or it's state + have a parameter that is the value of the control or its state (on or off). In the case of OSC paths listed on the main OSC page as having no parameter, if they have feedback, they will also work with a 1 for button press and 0 for button release. This is because diff --git a/include/osc58-personal-monitoring-control.html b/include/osc58-personal-monitoring-control.html index 65239de..5412328 100644 --- a/include/osc58-personal-monitoring-control.html +++ b/include/osc58-personal-monitoring-control.html @@ -18,8 +18,8 @@
Ardour is not limited to talking to one personal monitor controller at a time, but is able to deal with many simultaneously, each controlling - it's own Aux bus. + its own Aux bus.
The send controls and feedback all have the send id (1 to n) in line
diff --git a/include/osc58-querying-ardour.html b/include/osc58-querying-ardour.html
index 7e59c24..018ded0 100644
--- a/include/osc58-querying-ardour.html
+++ b/include/osc58-querying-ardour.html
@@ -70,7 +70,7 @@
if the strips have changed. This would be true if a strip gets moved, created or
deleted. When this happens Ardour sends /strip/list to the surfaces
that have previously requested a /strip/list. This lets the
- surface know that it's list of strips is no longer valid.
+ surface know that its list of strips is no longer valid.
A bus will not have a record enable and so a bus message will have one less parameter than a track. It is the controllers diff --git a/include/osc58-using-the-setup-dialog.html b/include/osc58-using-the-setup-dialog.html index c498b42..5c440d2 100644 --- a/include/osc58-using-the-setup-dialog.html +++ b/include/osc58-using-the-setup-dialog.html @@ -32,7 +32,7 @@
This field is informational only. It shows where Ardour will receive OSC messages. The system Name and the Port are the most important parts. - Normally, Ardour will use 3819 as it's server port. However, if some + Normally, Ardour will use 3819 as its server port. However, if some other server is already using this port, Ardour will try to use the next port up and will keep trying up to 10 ports up.
diff --git a/include/patch-change.html b/include/patch-change.html index a692a45..005bafc 100644 --- a/include/patch-change.html +++ b/include/patch-change.html @@ -73,7 +73,7 @@ each model once (i.e. it will skip files, if there are clashes).- After you have done modifications to a file, it's a good idea to validate it. This can + After you have done modifications to a file, it is a good idea to validate it. This can be done using the tool xmllint as shown below:
diff --git a/include/the-transport-menu.html b/include/the-transport-menu.html
index a995400..e6a462f 100644
--- a/include/the-transport-menu.html
+++ b/include/the-transport-menu.html
@@ -4,7 +4,7 @@
- Start/Stop Starts or stops the playhead, and recording if it's armed Start/Stop Starts or stops the playhead, and recording if it is armed Play
Play Selection Only plays the selected part of the session, be it a range or selected regions Play Selection w/Preroll As the previous menu, except it starts the playback 1/2 bar before the beginning of the selection
- Palette Hover over a color to display it's name. Click
+ Palette Hover over a color to display its name. Click
on a color to open a color chooser dialog.
diff --git a/include/transport-tab.html b/include/transport-tab.html
index 89172e8..682e450 100644
--- a/include/transport-tab.html
+++ b/include/transport-tab.html
@@ -150,7 +150,7 @@ transport tab"/>
Enable LTC generator, when enabled Ardour will
- output an LTC timecode signal on it's LTC-out port.
+ output an LTC timecode signal on its LTC-out port.
diff --git a/include/zoom-controls.html b/include/zoom-controls.html
index a408ac9..86dd756 100644
--- a/include/zoom-controls.html
+++ b/include/zoom-controls.html
@@ -16,7 +16,7 @@
The two leftmost zoom buttons (− and +) use this zoom focus to zoom out and in respectively.
-
The Zoom to session button is a handy shortcut to zoom out or in until all the session (as defined by it's start/end markers) fits horizontally.
+The Zoom to session button is a handy shortcut to zoom out or in until all the session (as defined by its start/end markers) fits horizontally.
Changing the Number of visible tracks dropdown menu
allows to fit this number of tracks vertically in the screen.