similar to: speex_bits_write_whole_bytes problem

Hi everybody, I need clarification about speex_bits_write function usage. There is an example usage of it. nbBytes = speex_bits_write(&bits, cbits, MAX_FRAME_BYTES); I examine the content of this function and which value should I set to MAX_FRAME_BYTE. In speexenc project, it is 2000 and in manual it is 200. For example, I set it to 200 but the length of bits->chars is 250

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

I'm trying to use speex on OMAP's DSP using dsp gateway, and have some questions. The code almost works (within few next days I'll post a some kind tutorial and patches), but it seems to be a little bug in bits.c. The code looks like this void speex_bits_read_from(SpeexBits *bits, char *chars, int len) { ////////////////// bla-bla-bla /////////////////// for (i=0;i<len;i++)

Thanks a lot for your explanations. Is it right I understand? if I've set SPEEX_SET_BITRATE to 16000(bps) this means that output is 16000/8=2000 bytes and I should set MAX_FRAME_BYTES and the length of cbits to 2000. Is it right? Maybe it is simple question but your answer is important for me, actually thanks a lot for your helps. Yasemin The last argument should simply be the size of your

After searching the mailing list archive (I forgot to do that before posting, sorry!) I found the solutions: 1) The documentation has a mistake: The bit terminator is NOT set automatically! (I'm using the latest speex version!) It has to be set manually using speex_bits_insert_terminator(&bits); 2) speex_decoder_int() has to be called as long, as it returns -1. After that, all frames

Hi everyone, I've recently done some major internal changes in Speex aimed at reducing RAM (by nearly a factor of 2!) and improving quality of the fixed-point. In doing so, I might have accidently broken a few things. I'd like to hear feedback on the current svn code to make sure I fix any regression before the next release. I'm already aware that --enable-vorbis-psy is broken and

Hello, I'm porting CELT 0.7.1 to an embedded platform and unfortunately (at least for me) CHAR is defined as 16 bits. I now got the vocoder compiling but when i compare the encoded output with a windows build, they don't match. Among the other problems i think that the char definition is one of the biggest players. I've seen in arch.h the following definitions: /* 2 on TI C5x DSP */

Hello there, I thought I would contribute to this wonderful project but noting a simple but problematic bug in speex_bits_read_whole_bytes(). SITUATION: I have a large stream of frames with NO breaks or length indicators inbetween each frame. For this reason, I call speex_bits_read_whole_bytes() and fill it to MAXIMUM in a loop while calling speex_decode() until there are no more bytes to read.

Greetings, I've just started porting speex to a TI C5509 DSP. It doesn't look like it's going to be too painful, but there are a couple of quirks about the C5x. 1) chars are 16 bits because memory addresses are for 16bit words 2) ints and short are also 16 bits (so sizeof(char) = sizeof(short) = sizeof(int) = 1) 3) the c5x is essentially big endian My plan is to change int and

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

It would be nice to have the following function added to the speex bits... void speex_bits_read_from_buffer( SpeexBits * const bits, void * const buff, const int buf_size) { bits->bytes = (char*)buff; bits->buf_size = buf_size; bits->nbBits = buf_size << 3; bits->bytePtr = 0; bits->bitPtr = 0; bits->owner = 0;

Jamey, There is a previous posting in the speex archives with a link to the dsp c5x patch. Archive link: http://lists.xiph.org/pipermail/speex-dev/2004-October/002847.html Patch link: http://lists.xiph.org/pipermail/speex-dev/attachments/20041029/facb8c73/spee x-1.1.6-jeh1-0001.bin But that patch is very different (much smaller) then the dsp c5x patch at

In bits.c\speex_bits_pack there is logic to reallocate the bits buffer. In that section there is a call to speex_memset_bytes which appears to wipe out all the old bytes. I found when I encoded a multi-frame message that needed less than the default 2000 bytes for bits->chars, everything worked fine. However, when I encoded a longer message that triggered the realloc code in speex_bits_pack,

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

When encoding many frames, I get a write access exception. It appears the "bits" structure has a fixed-size buffer (allocated in speex_bits_init()), and speex-encode() pukes when it overruns it. I understand I could just initialize bits with a bigger buffer, or watch the buffer and stop encoding when it gets full. But I don't want to care about compressed frame sizes, nor *can* I

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

Hi, Sorry! Marc Gimpel. I wrote it in a false thread before. It was my first time. :-) I have to write a small programm which should be able to record speeches and in addition synchronize the recorded speeches with measuring data. My idea is to record the speech in the normal way with speex and without ogg. If a sync message was received, i write a custom in-band messages using mode 13

Hello Arnaud, You posted this question a long long time ago, however I found your answer so I decided to post it anyway in case somebody else have the same problem as you and me. You were actually very close in finding your solution. The function DoWritedbf is an internal function from the foreign package. To access it outside of the package just do: foreign:::DoWritedbf so in your line:

Hi, I want to take a .wav and generate a bytestream that I can feed direct to speex_decode(). The speexenc program appears to produce it wrapped up in an ogg stream, and it doesn't have any sort of "raw" mode. I've tried hacking on it to remove the ogg parts, but I must have got it wrong, as my decode dies after decoding 160 bytes (which I believe is one frame) with an