[xiph-cvs] cvs commit: speex/doc manual.lyx
Jean-Marc Valin
jm at xiph.org
Sat Mar 22 12:59:47 PST 2003
jm 03/03/22 15:59:47
Modified: doc manual.lyx
Log:
spelling fixes
Revision Changes Path
1.63 +22 -29 speex/doc/manual.lyx
Index: manual.lyx
===================================================================
RCS file: /usr/local/cvsroot/speex/doc/manual.lyx,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- manual.lyx 22 Mar 2003 19:19:48 -0000 1.62
+++ manual.lyx 22 Mar 2003 20:59:47 -0000 1.63
@@ -2791,8 +2791,8 @@
\begin_inset Formula $A(z/\gamma)$
\end_inset
- filter will have its poles at
-\begin_inset Formula $p_{i}^{'}=\gamma p_{i}$
+ will have its poles at
+\begin_inset Formula $p'_{i}=\gamma p_{i}$
\end_inset
, making it a flatter version of
@@ -2875,7 +2875,7 @@
\layout Standard
An LPC analysis is first performed on a (asymetric Hamming) window that
- spans all the current frame and half a frame in advance.
+ spans all of the current frame and half a frame in advance.
The LPC coefficients are then converted to Line Spectral Pair
\begin_inset LatexCommand \index{line spectral pair}
@@ -2998,7 +2998,7 @@
That means that the innovation signal is divided in sub-vectors (of size
5 to 20) and quantized using a codebook that represents both the shape
and the gain at the same time.
- This save many bits that would otherwise be allocated for a separate gain
+ This saves many bits that would otherwise be allocated for a separate gain
at the price of a slight increase in complexity.
\layout Subsection
@@ -4173,7 +4173,7 @@
Last thing, it should be noted that for most codecs (including Speex) encoding
quality sometimes varies depending on the input.
Note that the complexity is only approximate (within 0.5 mflops and using
- the lowers complexity setting).
+ the lowest complexity setting).
Decoding requires approximately 0.5 mflops
\begin_inset LatexCommand \index{complexity}
@@ -4816,7 +4816,7 @@
without affecting inter-operability.
For that reason, the implementation provided and described here should
only be considered as a reference implementation.
- The enhancement system is devided in two parts.
+ The enhancement system is divided into two parts.
First, the synthesis filter
\begin_inset Formula $S(z)=1/A(z)$
\end_inset
@@ -4896,7 +4896,7 @@
\end_inset
can also be decoded with the narrowband decoder.
- Since the low band encoding has already been described only the high band
+ Since the low band encoding has already been described, only the high band
encoding is described in this section.
\layout Subsection
@@ -4908,7 +4908,7 @@
The only difference is that we use only 12 bits to encode the high-band
LSP's using a multi-stage vector quantizer (MSVQ).
The first level quantizes the 10 coefficients with 6 bits and the error
- is then quantized using 6 bits too.
+ is then quantized using 6 bits, too.
\layout Subsection
Pitch Prediction
@@ -4920,7 +4920,7 @@
kHz).
Second, it would be very hard to implement since the QMF folds the 4-8
kHz band into 4-0 kHz (reversing the frequency axis), which means that
- the location of the harmonics are no longer at multiples of the fundamental
+ the location of the harmonics is no longer at multiples of the fundamental
(pitch).
\layout Subsection
@@ -4934,8 +4934,8 @@
Bit allocation
\layout Standard
-For the wideband mode, all the narrowband frame is packed before the high-band
- is encoded.
+For the wideband mode, the entire narrowband frame is packed before the
+ high-band is encoded.
The narrowband part of the bit-stream is as defined in table
\begin_inset LatexCommand \ref{cap:bits-narrowband}
@@ -5449,7 +5449,7 @@
Isn't there a GPL implementation of the GSM-FR codec? Why is Speex necessary?
\layout Standard
-First of all, it's not clear whether or not GSM-FR is covered by a phillips
+First of all, it's not clear whether or not GSM-FR is covered by a Phillips
patent (see http://kbs.cs.tu-berlin.de/~jutta/toast.html).
Also, GSM-FR offers mediocre quality at a relatively high bit-rate, while
Speex can offer equivalent quality at almost half the bit-rate.
@@ -5460,7 +5460,7 @@
Under what license is Speex released?
\layout Standard
-As of version 1.0 beta 1, Speex in released under Xiph's BSD-like license.
+As of version 1.0 beta 1, Speex is released under Xiph's BSD-like license.
This license is the most permissive of the open-source licenses.
\layout Subsection*
@@ -5477,15 +5477,7 @@
, what's the difference?
\layout Standard
-Ogg is a
-\begin_inset Quotes eld
-\end_inset
-
-container format
-\begin_inset Quotes erd
-\end_inset
-
- for holding multimedia data.
+Ogg is a container format for holding multimedia data.
Vorbis is an audio codec that uses Ogg to store its bit-streams as files,
hence the name Ogg Vorbis.
Speex also uses the Ogg format to store its bit-streams as files, so technicall
@@ -5506,8 +5498,8 @@
\layout Standard
Speex files have the .spx extension.
- Note, however that all the Speex tools (speexenc, speexdec) do not rely
- on the extension at all so any extension will work.
+ Note, however that the Speex tools (speexenc, speexdec) do not rely on
+ the extension at all, so any extension will work.
\layout Subsection*
Can I use Speex for compressing music
@@ -5549,7 +5541,7 @@
In the case of Speex, encoding consists of finding, for each vector of
5 to 10 samples, the entry that matches the best within a codebook consisting
of 16 to 256 entries.
- On the other hand, at decoding all that needs to be done is lookup the
+ On the other hand, at decoding all that needs to be done is look up the
right entry in the codebook using the encoded index.
Since a lookup is much faster than a search, the decoder works much faster
than the encoder.
@@ -5558,7 +5550,7 @@
Why is Speex so slow on my iPaq (or insert any platform without an FPU)?
\layout Standard
-Well the parenthesis provides the answer: no FPU (floating-point unit).
+Well, the parenthesis provides the answer: no FPU (floating-point unit).
The Speex code makes heavy use of floating-point operations.
On devices with no FPU, all floating-point instructions need to be emulated.
This is a very time consuming operation.
@@ -5569,7 +5561,7 @@
How do I fix that?
\layout Standard
-One of the cause could be scaling of the input speech.
+One of the causes could be scaling of the input speech.
Speex expects signals to have a
\begin_inset Formula $\pm2^{15}$
\end_inset
@@ -5612,7 +5604,8 @@
It's hard to give precise figures since no formal listening tests have been
performed yet.
All I can say is that in terms of quality, Speex competes on the same ground
- as other proprietary (not necessarily the best, but not the worst either).
+ as other proprietary codecs (not necessarily the best, but not the worst
+ either).
Speex also has many features that are not present in most other codecs.
These include variable bit-rate (VBR), integration of narrowband and wideband,
as well as stereo support.
@@ -5635,7 +5628,7 @@
the 15 kbps mode if you want DTMF to be transmitted correctly.
DTMF at 8 kbps may work but your mileage may vary.
Also, make sure you don't use the lowest complexity (see SPEEX_SET_COMPLEXITY
- or --comp option), as it causes important noise.
+ or --comp option), as it causes significant noise.
\layout Subsection*
Can Speex pass V.9x modem signals correctly?
<p><p>--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'cvs-request at xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.
More information about the commits
mailing list