similar to: memory violation in mode_create() !

?? hi ?Jean-Marc, ? thanks for your answer. But still I am struggling to find a reasonable upper limit for the RAM sizes. ? You say we need 4.5/9.0 kB for enc/dec per channel. But are those sizes really independent of any settings, like frame_size, bitrate, complexity, etc. ? ? at least in our configuration I find these requirements:? ?- native stack: < 2.1kB (enc or dec) measured by RealView

Hi guys, It looks to me like line 955 in celt.c should be: effectiveBytes = vbr_rate>>(3+BITRES); otherwise it seems like "effectiveBytes" is 8 times larger than it should be (at least if it's really meant to be bytes). Cheers, John Ridges

We are transmitting CELT encoded packages over a lossy channel, where from time to time complete packages do not arrive at the decoder. My questions: 1. What will be the best pattern to be fed into the decoder in order to minimize the audible impact and make best use of internal states from last block (like overlapp-add history etc.) and best blending with next block ? 2. Does this pattern

Hi guys, I'm currently working on a CELT implementation for FMOD, and one of the things we want to do is have all memory required allocated beforehand. This is before we have any information about what sounds will be played. We would like to create all of our CELTDecode instances up front. Because celt_mode_create() requires a sample rate and number of channels passed in, this

hi Jean-Marc, the memory after the allocated space is definitely destroyed. It took me some time to find out why. I expected local arrays to be allocated on stack, not on the heap. The function get_required_bits allocates a local array uint32[] which will be located on heap right after the array fromcompute_pulse_cache(), what made me think it was written behind its end. I am sorry for the

Hello, I needed to apply the attached little patch rep_clz to get __adddf3 working on 32Bit x86 Linux. __adddf3 doesn't seem to be part of the Library on any currently supported Platforms. But if support for plattforms without FPU should be added this probably is the correct version. Christoph -------------- next part -------------- A non-text attachment was scrubbed... Name: rep_clz.patch

Hi everyone, I've just changed the API for CELT, but at least there's a good reason for that. It's now possible to use the same mode data for both mono and stereo. So here's the change: - The celt_mode_create() function has a "channels" parameter - The celt_encode_create() and celt_decoder_create() functions now have an additional "channels" parameter. - I

Hi I noticed a crash issue when I passed the following values: celt_mode_create(96000, 258, &e); CELTMode->mdct.kfft[0] is not initialized after calling?clt_mdct_init() and when?celt_mode_destroy() is called it tries to dereference this value in kiss_fft_free(). -- Bjoern Here's the callstack: !kiss_fft_free(const kiss_fft_state * cfg=0x00000000) ?Line 650 + 0x3 bytes

Is this a common warning? The decoder doesn't return an error on it, but I see it a lot in my test application on windows. It is non existent on my linux box. I haven't tried mingw yet. please note that I'm using visual studio 2008 w/the vcproj that Bjoern Rasmussen made for 0.5.2 (w/some file references removed) at the moment and it is giving a lot of C4554 warnings

Hi Guys, I've just been looking into STATIC_MODES. My plan is to generate and store the modes as part of our sound banks when they are encoded. I have noticed that even with STATIC_MODES turned on, celt_mode_create still allocs and generates the fft and prob members (via pitch_state_alloc and quant_prob_alloc respectively). I also notice that in dump_modes.c, these two members are just

Hi All, Would it be possible to encode n channels with the CELT api? I can't find a negative or positive in the CELT docs; all I could find is c a check on the nr of channels in wav_io.c in the CELT tools. No clear insight on wheter or not the channels parameter in celt_mode_create can be > 2. Answers on the list were (thanks!): - Sure, You just encode each channel and then store the

I am having trouble understanding the stack allocation scheme when using a C55xx device. From what I can tell, the GLOBAL_STACK_SIZE is set in arch.h to 100,000 bytes (when using FIXED_POINT), which is then used in the ALLOC_STACK macro found in stack_alloc.h. This macro seems to say, if global_stack==0, then call celt_alloc_scratch, found in os_support.h, which in turn attempts to allocate (using

I have been using CELT ver 8 for some time, but am now attempting to use the latest git (ver 11+). However, I am having problems with modes. I don't completely understand what is going on in the following code. Could you provide some guidance on what parameters are now acceptable? I am trying to create a stereo channel with Fs=48000 and 128 byte frames, but get NULL returned from the

I seem to be having trouble creating correct modes for a 44100 samplerate. In reading the header file it says an even value from 64 to 512 I believe (going off memory) for the frame_rate but celt_mode_create returns a null mode. I can get it all working if I use 48000 with 480 frame_rate. I guess in short what is the best way to calculate the optimal mode for latency. Thanks Mike -- Sent

Hi all, I'm trying to build the celt package on the Texas TMS320VC5510 DSK. I think there are some #define for it in the code, but I'm doing something wrong. Is there any documentation about it? So far I'm building with the TI_C5X_ASM;CONFIG_TI_C55X #define. Any help? Thank you. Giovanni

I realize this is ancient history, but I am trying to compile Ver 8.1 (from the download page) using Fixed Point and am getting compile errors as follows: argument of type "celt_sig *" is incompatible with parameter of type "celt_int16 *" libcelt81_orig_DSP/libcelt celt.c line 321 1304524612394 19769 argument of type "celt_sig *" is incompatible

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, I am looking into fixed-point code of the CELT decoder for real-time application. Here are some questions.. [1] array, window[] The array, window[] is being initialized from a function below in modes.c. This array is being initialized differently for the decoder, depending on frame size and sampling freq. of the bitstream .. Could you provide us with fixed-point code for initialization of

Optimize opus encode (float only) usecase using ARM NE10 library. Mainly effects opus_fft and ctl_mdct_forward and related functions. This optimization can be used for ARM CPUs that have NEON VFP unit. This patch only enables optimizations for ARMv7. Official ARM NE10 library page available at http://projectne10.github.io/Ne10/ To enable this optimization, use --enable-intrinsics

Optimize opus encode (float only) usecase using ARM NE10 library. Mainly effects opus_fft and ctl_mdct_forward and related functions. This optimization can be used for ARM CPUs that have NEON VFP unit. This patch only enables optimizations for ARMv7. Official ARM NE10 library page available at http://projectne10.github.io/Ne10/ To enable this optimization, use --enable-intrinsics