similar to: CELT 0.5.2 is out

Problems building celt-0.5.2 for blackfin. Use the following to configure: #!/bin/sh # bfinconf # Set up configuration to cross compile on blackfin ./configure \ --host=bfin \ --enable-fixed-point \ CC=bfin-uclinux-gcc \ CFLAGS='-O2 '\ '-mfast-fp '\ '-ffast-math '\ '-Wall -Dlinux '\ '-D__linux__ '\ '-fno-strict-aliasing '\

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,

Dear all, Sorry for this simple and maybe stupid question, I'm working in the implementation of opus for ARMv7e microcontroller using a library CMSIS/DSP used to calculate the CFFT and MDCT based on the DCT-IV. my question is: In the implementation of Celt you have used a fixed length CFFT equal to 1920, I want to know if there is some issues which can appear if a change that configuration

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

Hi everyone, I'd just like to announce CELT 0.11.1 (sorry about failing to announce 0.11). The bit-stream is now is "soft-freeze", which means we won't change it unless we find bugs -- which we did between 0.11 and 0.11.1. The API should also be close to the final API. Compared to 0.10.x there are also small quality improvements, mostly at high bit-rate. I'd also like

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 everyone, I've made several posts recently about CELT being "replaced" by the Opus codec ( http://opus-codec.org/ ) and I thought it was time to give an update on what's going on. As many of you know, I've been involved at the IETF on this new Opus codec, which essentially merge (a modified version of) Skype's SILK codec with CELT. This is more than just two codecs

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, For those interested in reading more on CELT, here's another paper that just got accepted. That one focuses on the low-complexity mode and is based on 0.5.1. J.-M. Valin, T. B. Terriberry, G. Maxwell, A Full-Bandwidth Audio Codec with Low Complexity and Very Low Delay, Accepted for EUSIPCO 2009. http://people.xiph.org/~jm/papers/celt_eusipco2009.pdf Cheers, Jean-Marc

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 breaking compatibility) on the encoder side. There are several other optimisations and bug fixes included. The API has also been slightly modified, so code using CELT will have to be updated (only minor

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 breaking compatibility) on the encoder side. There are several other optimisations and bug fixes included. The API has also been slightly modified, so code using CELT will have to be updated (only minor

Hi, folks, I have an old CELT thing that I'm updating to Opus and I'm trying to get individual pieces upgraded.  My first task is upgrading the CELT encoder to Opus. The old CELT thing treated the L and R channels as independent mono streams, encoded them somehow with CELT to form one bitstream, sent one bitstream across, and then unpacked it manually after the decoder. Can I do that

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

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

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, 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 am a newbe here, so I hope I am not asking something crazy. I was looking on the Celt downloads and I noticed that the latest command line builds were for version 0.6. I know it is still early in development, and that the devs probably don't have time for developing CL versions for everything. since I know nothing about sourcecode and whatnot, I was wondering if there was a fairly simple

# make make all-recursive make[1]: Entering directory `/tmp/celt-0.7.0' Making all in libcelt make[2]: Entering directory `/tmp/celt-0.7.0/libcelt' /bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -s -O3 -march=i686 -fvisibility=hidden -W -Wstrict-prototypes -Wall -Wextra -Wcast-align -Wnested-externs -Wshadow -Wno-parentheses

Is there a particular reason why CELT grabs 100KB of stack immediately? Is that really required or can that be trimmed down some/a lot? -a