similar to: CELT sample files

Hi All, I'm looking to package up celt for inclusion in Fedora as the next stable release of ekiga/opal will have support for it. I've run into two issues in compiling it into a rpm. The first is a show stopper, then second one not so much of an issue but thought I'd report it for reference. The first issue is due to the celtdec and celtenc explicitly define rpath. I get the

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

From: Thorvald Natvig <slicer at users.sourceforge.net> --- celt.pc.in | 2 +- configure.ac | 2 ++ libcelt/Makefile.am | 12 ++++++------ tests/Makefile.am | 2 +- tools/Makefile.am | 4 ++-- 5 files changed, 12 insertions(+), 10 deletions(-) diff --git a/celt.pc.in b/celt.pc.in index 98cc008..67a830b 100644 --- a/celt.pc.in +++ b/celt.pc.in @@ -10,5

A small issue, but missing. Something like this would be helpful: - printf ("celtenc (CELT encoder)\n"); + printf ("celtenc (CELT %s encoder)\n", CELT_VERSION); til

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 am trying to evaluate the quality of the CELT codec by using the 0.8.0 testcelt tool to encode and decode the input. I want to test different bitrates and selected the below parameters for 64, 96, 128, 196, 256kB: ./celt-0.8.0/libcelt/testcelt.exe 44100 2 256 46 $1.sw $1-64kb.sw ./celt-0.8.0/libcelt/testcelt.exe 44100 2 192 46 $1.sw $1-96kb.sw ./celt-0.8.0/libcelt/testcelt.exe 44100 2 128

Hello everyone, I would like to access the raw CELT encoded bytes by using the command line interface but I am having some difficulties. I do not know how to unpack the Ogg Vorbis wrapper and the STDOUT option just filled my command line with ASCI characters. Anyone have luck dumping the bytes to a text file? Also inputting them back to the celtdec function would be helpful information. Thanks,

# 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

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 all, I am the developer of the llcon software (llcon.sf.net) which is a software making it possible for musicians to play in real-time over the internet. Up to now I have used ADPCM or no audio coding. Gregory Maxwell was pointing me to the great CELT project. Using CELT has the advantage to be able to use higher sample rates, getting lower code rate and better error concealment. I have

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

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,

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, This isn't that new anymore, but I'd let everyone know that CELT 0.10.0 is out. We've improved the quality quite a bit since the last release and we fixed many bugs. For this release, Monty has written an extensive demo page at: http://people.xiph.org/~xiphmont/demo/celt/demo.html Although it's not final yet, it contains a lot of information of CELT, recent changes and

hey great job with the celt codec. im very eager to use it. im just wondering how? there is little to no documentation on how to use the celt codec. is there anyway to encode an icecast stream using the celt codec? or is there any software with celt support built in? thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi , We've downloaded the CELTV0.11.1 source code from celt-codec.org . But having trouble with mathops-test and tandem-test unit test that exercises internal components of CELT codec, please find attached document for each test case failure in details. Also could you please give some inputs on CELT Low complexity code and full version of the code, point me source code to CELT

Dear CELT Developers, I wrote a proposal on how to integrate CELT into Digital Radio Mondiale (DRM+). The CELT codec has been integrated in the Spark transmission software and SoDiRa receiver software. Please download the proposal here: http://www.drm-sender.de/celt_in_drm.pdf Suggestions and comments are welcome! A live on-air DRM+ transmission using CELT (v.0.7.1) for audio encoding was

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