similar to: Celt modes

? There seems to be a memory violation when calling celt_mode_create(48000, 240). ? The function compute_pulse_cache() calls celt_alloc (the second one, bits=celt_alloc()) in order to allocate 343 byte, but it is using about 872 bytes at that location, which will be deleted by the following allocations. ? In this case the following encoder call crashes at first run. ? Sorry, my time is very

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'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 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

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

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

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

On Tue, 14 Oct 2008, Jean-Marc Valin wrote: > Diana Cionoiu a ?crit : >> Hi Jean-Marc, >> >> 1. Why CELT versus Speex? > > There's nearly no overlap between Speex and CELT. CELT is much higher > quality, very low latency, and of course, higher bit-rate than Speex. So > it really depends on the application. > >> 2. What's the RTP payload for CELT,

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, 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

Hi Jean-Marc, 1. Why CELT versus Speex? 2. What's the RTP payload for CELT, so we can add it in Yate? 3. What are the SDP declaration parameters? Diana Jean-Marc Valin wrote: > Hi everyone, > > I'm happy to announce CELT version 0.5.0. This release includes > simplifications to the bit allocation code and includes a new > low-complexity mode that can be enabled (without

Hello all, This is slightly off-topic, but should be of interest to some people on this list. I just released version 0.3.2 of the CELT ultra low-delay audio codec (http://www.celt-codec.org/). CELT is designed to encode high quality speech and music with less than 10 ms delay and at rates starting from around 32 kbit/s. This version is "special" in that it is the basis for some

hi. i am currently adding celt support to netjack. very nice to see a free low-latency codec :) i currently dont require robustness against packet loss, because the sync code of netjack does not handle packet loss very gracefully. how much bandwidth is wasted for this feature ? is it sensible, to have the data downsampled berfore encoding , in order to reduce bandwidth ? i suspect that just

On Thu, 16 Oct 2008, Jean-Marc Valin wrote: > Aymeric Moizard a ?crit : >>> None of that is defined yet, though I'm open to suggestions on how to do >>> the mapping. >> >> CELT/44100 and CELT/48000 >> a=fmtp:105 stereo=on >> >> probably a latency value? > > It would definitely need a frame_size value > >> "CELT"

Hi all I have spent the last three days evaluating CELT on our supported platforms. I found a bug in quant_bands.c, that due to processor/compilation differences did not cause an issue on x86 platforms, but is a problem on the MIPS processor embedded devices. When decoding on the MIPS devices, there was a lot of noise added during the decoding, the noise is mainly in the 15 khz to 21 khz range.

I have build celt with FIXED_POINT option (latest 0.6.1 as well as from the git repo) on windows. However I am not getting a valid output (all samples are saturated) when I try to decode with this version. The input file was encoded with the same fixed point version. Does fixed point version work at all? Following are the command line settings; Samplerate; 48000 Channels: 2 Framesize: 256

I know the focus for Opus is low delay, but I've been watching its development with interest because of the potential for audiobook/podcast use, where latency is practically irrelevant. I hear the upcoming USAC codec will give good results for this niche (though listening test results don't seem to be available to the public yet), but I also hear it'll be extremely patent

Hi everyone, I've recently been making various changes to the way the modes work and the supported frame size. On new feature that may be of interest to some is that CELT should soon support changing the frame size dynamically within a stream. By that I mean varying the amount of audio (in time) transmitted at once, not the compressed size -- which has always been variable. That would

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, I'd like to know the reasons why CELT supports only signals with sampling frequency in the range of 32-96 kHz. In effect, it can clearly outperform speex at high bitrates, and has potential to be used in high quality voice communications even for 11, 16 and 22 kHz speech signals. It could also compete with SILK codec (to be soon released by Skype). See this page for more specifications