similar to: Trouble in decoding speex on PC

Dear Speex Devs, One more problem from my side. I had earlier queried about bad quality of speex. For this run, I changed the memory mode option in CCStudio to none from large. (I will explain this if required.) Now, I am trying to run speex on C55x in real time. Find a code snippet from my main function below. Basically, I am getting the error mentioned in the subject line. Weird thing is

Hi, Being relatively new to speex code I have a question regarding the use (and necessity) of the variable skip_group_delay found in the testen.c file, namely in writing to fout : fwrite(&out_short[skip_group_delay], sizeof(short), FRAME_SIZE-skip_group_delay, fout); the variable skip_group_delay is effectively used once then set to zero for all subsequent uses. What is its purpose

Dear subscribers: I am using the following code to read a large number of big text files: library(sqldf) tempd <- file(XXXX) tempdx <- sqldf("select * from tempd", dbname = tempfile(), file.format = list(header = T, sep="\t", row.names = F)) The problem is: all my numberical variable become factor (maybe because these columns all contain missing value). It would be

Hello all, I have searched and have not yet identified a solution so now I am sending this message. In short, I need to split my data into training, validation, and testing subsets that keep all observations from the same sites together ? preferably as part of a cross validation procedure. Now for the longer version. And I must confess that although my R skills are improving, they are not so

Hi There: I was wondering if there is a way to read FORTRAN list data (similar to IDL's readf function). I often use FORTRAN for most of my number crunching, and use something like IDL to visualize and perform statistical analysis on that data. Since the each file is rather large (>100 Mb), formatting the output into columns or tables is impractical, hence the "list"

Jean-Marc, The following patch makes the above two read functions const correct. Cheers, Erik diff --git a/include/speex/speex_bits.h b/include/speex/speex_bits.h index a26fb4c..234ec53 100644 --- a/include/speex/speex_bits.h +++ b/include/speex/speex_bits.h @@ -77,7 +77,7 @@ void speex_bits_reset(SpeexBits *bits); void speex_bits_rewind(SpeexBits *bits); /** Initializes the bit-stream

i belong to india. i am making pbx using sangoma fxo card. i want that when ever call comes to my PSTN line i should see the no from where call is coming. so i have to configures chan_dahdi.conf according to my region. i checked dahdi.conf and in that they have mentioned for india

hi friend need ur help in dial plan, i want to allow exten 2000 to 2005 can make call outside and exten 2006 to 2010 can not make call outside. heres my dial plan. ? sip.conf ? [general] port = 5060 bindaddr = 0.0.0.0 context = others [2000] type=friend context=outside secret=1234 host=dynamic [2001] type=friend context=outside secret=1234 host=dynamic [2002] type=friend context=outside

Hi, I am using speex 1.2beta2 on a narrowband 16-bit, 8khz system that has a severe program space problem and will not fit speex in its normal operation. In an attempt to shrink speex I placed a breakpoint in every function and ran a decode and encode and removed the breakpoints that I hit. in the functions that had a breakpoint that I didn't hit I commented out those functions (as well as

Hello, I'm new on DSP and i want to implant speex echo canceller on the Blackfin DSK version of speex to work on the BF533 EZ-KIT LITE But i can perform the echo canceller to work This is my code, so if somebody can tell me where i'm wrong //----------------------------------------------------------------------------- // CallBackFunction() - Gets called by the audio pseudo-driver

I'm trying to use the speex API, and I think I'm missing something. I'm running on Mac OSX Tiger, and the attached microphone is a iSight. If I call the "speex_encode_int" function, and then immediately call the "speex_decode_int" function, shouldn't I get back the same data? i.e. in my example code, shouldn't the two arrays contain at least similar

This patch will export new speex functions in the generated library, such as speex_encode_int as well as the preprocessor, echo-cancellation and jitterbuffers. The ordinals used matches the 1.1.6 release from the speex.org website, so any new library created with this def file should be binary compatible with that one. -------------- next part -------------- Index: speex.def

for the bits init I am using speex_bits_set_bit_buffer and I don't use the write to or read from because the data is already in the buffer I am reading from and I am writing to the final buffer so I don't need to move arrays around. what part is the vocoder part of the decode? Thanks for your help! -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/06/07

I'm glad to hear that my data size can be shrunk considerably, however I do not know the minimum values that I would set the static arrays to be. I hate to be a bother but could you tell me the minimum values for these arrays/structures in the state structure? Thanks! encode: stack winBuf excBuf swBuf lagWindow old_lsp old_qlsp mem_sp mem_sw mem_sw_whole mem_exc mem_exc2 pi_gain pitch

Thank you, I really appreciate the help. -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/07/07 8:34 AM >>> Michael Jacobson a ?crit : > I'm glad to hear that my data size can be shrunk considerably, > however I do not know the minimum values that I would set the static > arrays to be. I hate to be a bother but could you tell me the >

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output