mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-04 20:04:50 +00:00
Remove as much trailing whitespace as possible.
Change-Id: I873c1c6d00f447269bd841494459efccdd2c19c0
This commit is contained in:
@@ -200,13 +200,13 @@ extern struct {
|
||||
/* Error correction */
|
||||
/* Subroutine SETUP is the only place where order is assigned a value, */
|
||||
/* and that value is 10. It could increase efficiency 1% or so to */
|
||||
/* declare order as a constant (i.e., a Fortran PARAMETER) instead of as
|
||||
/* declare order as a constant (i.e., a Fortran PARAMETER) instead of as
|
||||
*/
|
||||
/* a variable in a COMMON block, since it is used in many places in the */
|
||||
/* core of the coding and decoding routines. Actually, I take that back.
|
||||
/* core of the coding and decoding routines. Actually, I take that back.
|
||||
*/
|
||||
/* At least when compiling with f2c, the upper bound of DO loops is */
|
||||
/* stored in a local variable before the DO loop begins, and then that is
|
||||
/* stored in a local variable before the DO loop begins, and then that is
|
||||
*/
|
||||
/* compared against on each iteration. */
|
||||
/* Similarly for lframe, which is given a value of MAXFRM in SETUP. */
|
||||
@@ -216,35 +216,35 @@ extern struct {
|
||||
/* nbits is similar to quant, and is given a value of 54 in SETUP. */
|
||||
/* corrp is given a value of .TRUE. in SETUP, and is only used in the */
|
||||
/* subroutines ENCODE and DECODE. It doesn't affect the speed of the */
|
||||
/* coder significantly whether it is .TRUE. or .FALSE., or whether it is
|
||||
/* coder significantly whether it is .TRUE. or .FALSE., or whether it is
|
||||
*/
|
||||
/* a constant or a variable, since it is only examined once per frame. */
|
||||
/* Leaving it as a variable that is set to .TRUE. seems like a good */
|
||||
/* idea, since it does enable some error-correction capability for */
|
||||
/* unvoiced frames, with no change in the coding rate, and no noticeable
|
||||
/* unvoiced frames, with no change in the coding rate, and no noticeable
|
||||
*/
|
||||
/* quality difference in the decoded speech. */
|
||||
/* integer quant, nbits */
|
||||
/* *** Read/write: variables for debugging, not needed for LPC algorithm
|
||||
/* *** Read/write: variables for debugging, not needed for LPC algorithm
|
||||
*/
|
||||
|
||||
/* Current frame, Unstable frames, Output clip count, Max onset buffer,
|
||||
/* Current frame, Unstable frames, Output clip count, Max onset buffer,
|
||||
*/
|
||||
/* Debug listing detail level, Line count on listing page */
|
||||
|
||||
/* nframe is not needed for an embedded LPC10 at all. */
|
||||
/* nunsfm is initialized to 0 in SETUP, and incremented in subroutine */
|
||||
/* ERROR, which is only called from RCCHK. When LPC10 is embedded into */
|
||||
/* an application, I would recommend removing the call to ERROR in RCCHK,
|
||||
/* an application, I would recommend removing the call to ERROR in RCCHK,
|
||||
*/
|
||||
/* and remove ERROR and nunsfm completely. */
|
||||
/* iclip is initialized to 0 in SETUP, and incremented in entry SWRITE in
|
||||
/* iclip is initialized to 0 in SETUP, and incremented in entry SWRITE in
|
||||
*/
|
||||
/* sread.f. When LPC10 is embedded into an application, one might want */
|
||||
/* to cause it to be incremented in a routine that takes the output of */
|
||||
/* SYNTHS and sends it to an audio device. It could be optionally */
|
||||
/* displayed, for those that might want to know what it is. */
|
||||
/* maxosp is never initialized to 0 in SETUP, although it probably should
|
||||
/* maxosp is never initialized to 0 in SETUP, although it probably should
|
||||
*/
|
||||
/* be, and it is updated in subroutine ANALYS. I doubt that its value */
|
||||
/* would be of much interest to an application in which LPC10 is */
|
||||
@@ -260,7 +260,7 @@ extern struct {
|
||||
/* removed. */
|
||||
/* Local state */
|
||||
/* It would be a bit more "general" to define S(LTAU), if Fortran */
|
||||
/* allows the argument of a function to be used as the dimension of
|
||||
/* allows the argument of a function to be used as the dimension of
|
||||
*/
|
||||
/* a local array variable. */
|
||||
/* IPOINT is always in the range 0 to DEPTH-1. */
|
||||
@@ -272,16 +272,16 @@ extern struct {
|
||||
/* initial values (all indices of P with second index equal to */
|
||||
/* IPTR are all written before being read in this subroutine). */
|
||||
|
||||
/* From examining the code carefully, it appears that all of these
|
||||
/* From examining the code carefully, it appears that all of these
|
||||
*/
|
||||
/* should be saved from one invocation to the next. */
|
||||
|
||||
/* I've run lpcsim with the "-l 6" option to see all of the */
|
||||
/* debugging information that is printed out by this subroutine */
|
||||
/* below, and it appears that S, P, IPOINT, and ALPHAX are all */
|
||||
/* initialized to 0 (these initial values would likely be different
|
||||
/* initialized to 0 (these initial values would likely be different
|
||||
*/
|
||||
/* on different platforms, compilers, etc.). Given that the output
|
||||
/* on different platforms, compilers, etc.). Given that the output
|
||||
*/
|
||||
/* of the coder sounds reasonable, I'm going to initialize these */
|
||||
/* variables to 0 explicitly. */
|
||||
@@ -299,9 +299,9 @@ extern struct {
|
||||
|
||||
/* Function Body */
|
||||
|
||||
/* Calculate the confidence factor ALPHA, used as a threshold slope in
|
||||
/* Calculate the confidence factor ALPHA, used as a threshold slope in
|
||||
*/
|
||||
/* SEESAW. If unvoiced, set high slope so that every point in P array
|
||||
/* SEESAW. If unvoiced, set high slope so that every point in P array
|
||||
*/
|
||||
/* is marked as a potential pitch frequency. A scaled up version (ALPHAX
|
||||
)*/
|
||||
@@ -391,11 +391,11 @@ n*/
|
||||
*pitch = p[*pitch + j * 60 - 61];
|
||||
}
|
||||
|
||||
/* The following statement subtracts one from IPOINT, mod DEPTH. I
|
||||
/* The following statement subtracts one from IPOINT, mod DEPTH. I
|
||||
*/
|
||||
/* think the author chose to add DEPTH-1, instead of subtracting 1,
|
||||
/* think the author chose to add DEPTH-1, instead of subtracting 1,
|
||||
*/
|
||||
/* because then it will work even if MOD doesn't work as desired on
|
||||
/* because then it will work even if MOD doesn't work as desired on
|
||||
*/
|
||||
/* negative arguments. */
|
||||
|
||||
|
Reference in New Issue
Block a user