similar to: BYTES_PER_CHAR

Hi, My name is Riccardo Micci i downloaded the CELT source code and I compiled it under Windows. This is meant to be a preliminary study for my company's project. When i run CELT it encodes and decodes the file back saying "Encoder matches decoder!!". When i try to play the output though the result is just noise and clicks. The only changes I've applied are some #defines to

Hi, We're using Celt 0.7.1 at the moment. We're thinking to update the code to a newer version of it. Is there an appreciable complexity (decoding time) difference among versions (0.7.1 - 0.8.1 - 0.9.1 - 0.10 - 0.11.1)? If so, which one is the fastest? Thanks Regards Riccardo Riccardo Micci Senior DSP Engineer, Wireless Group Cambridge Consultants Science Park, Milton Road

Hi, In order to fit the decoder in memory in our embedded architecture we set the MAX_PERIOD #define equal to the frame size. This doesn't affect the code bit accuracy in normal decoding. The #define it's used celt_decode_lost function though. Is it possible to get celt_decode_lost to work with a value different from the default? Thanks Riccardo Riccardo Micci Senior DSP Engineer,

Hi, I'm using Celt version 0.7.1 in low complexity mode (i.e. no pitch information). In case a packet is lost i was planning to use the celt_decode_lost function. I realised though it uses pitch information inside. Does the celt_decode_lost function still works with no pitch information? Are there some changes to be done? Thanks Regards Riccardo Riccardo Micci Senior DSP Engineer,

Hi, I'm testing CELT 0.7.1 speed performance and I'm focusing now on the complexity switch. I've dug in the archive and i found some information. Is it still true that there are two ranges? - 0-2 low complexity mode - 3-10 high complexity mode If no input is given is 2 hence low complexity mode the default setting? Does the complexity mode affect decoding as well? Thank you Best

Hi, Our DSP has a built-in bitrev instruction so we're exploring the possibility of calculating the bitrev every time instead of filling the table during initialisation, hence saving some memory. Our frame size is fixed to 320 samples. The two FFTs sizes for normal block and short block are 160 and 40 respectively. It's not really clear how the function

Hi, I was checking complexity modes of CELT 07.1 encoder. If i got it correctly everything is driven by pitch_available variable set in celt_encoder_create function. By default it's set to 1 hence high complexity mode is used all the time. I tried to disable it and although i couldn't hear any particular difference in the decoded audio quality, the cycle count of the encoder dropped

Hi, I've recently successful built and run CELT under Windows using "testcelt.c" example file. Since I'm about to port it on a embedded platform i activated the FIXED_POINT #define. I included fixed_generic.h and without other changes to the code i tried to encode and decode the same file i previously used. The output though is completely saturated i.e. it jumps from -32768 to

Hi, We're testing CELT (version 0.7.1) error resilience capability. We've used already celtdec packet-loss options. Hence we know what to expect in case of whole packet loss. How does Celt respond to a broken encoded packet? Is it always better to discard it and decode the missing frame through decode_lost? We have the hardware capability of protecting the frame with multiple CRCs.

Hi, I'm using Celt 0.7.1 in fixed math mode. In the celt_encode function, if the variable has_pitch is true, the function pitch_search is called. Within this function the find_best_pitch subfunction is called. Here the variable "float score;" is defined. Is this right? I was expecting not to see any float declaration in the fixed math code. Is it possible to redefine it as

eds to drag in the source and header files from the libcelt directory into = the project and define HAVE_CONFIG_H is the project's pre-processor definit= ion. The tricky part is to build a config.h file. To get it to work on VS some = of the important settings include. =20 #define CELT_BUILD #define USE_ALLOCA #undef VAR_ARRAYS #undef restrict #undef HAVE_STDINT_H #undef inline #define

Hi, Fiddling with Celt i found a possible bug. I'm using CELT 0.7.1, frame size 256, sample rate 32k and bitrate 64k. Here is the scenario: decoding side, celt_decode function. The "dec" structure is created at each function call and it's initialized with ec_dec_init function. The attribute "end_byte" is not initialized though. Decoding a file the behaviour is the

Hi, Does Celt (in particular version 0.7.1) exploits correlation between the two channels in stereo mode? In practice, is it possible to use the two channels as two mono signals without affecting quality? Thanks Best Regards Riccardo Riccardo Micci Senior DSP Engineer, Wireless Group Cambridge Consultants Science Park, Milton Road Cambridge, CB4 0DW, England Switchboard: +44 (0)1223

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

An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20091029/e587399d/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: tmezo.vcf Type: text/x-vcard Size: 345 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20091029/e587399d/attachment.vcf

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

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

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 Jamey, Really cool to see Speex being ported to the C55xx and I'd be glad to integrate the changes required in Speex (and the style's fine with me). Here are a couple comments on the patch you sent (I looked at it, but haven't compiled). 1) The changes you made to the pack un unpack functions would only work if the 16-bit chars are "big endian" (relative to the two bytes