similar to: V8.1 Fixed Point

These were used because the entropy coder originally came from outside libcelt, and thus did not have a common type system. It's now undergone enough modification that it's not ever likely to be used as-is in another codec without some porting effort, so there's no real reason to maintain the typedefs separately. Hopefully we'll replace these all again somedate with a common set

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

Tim, et al, I have run into several problems with V0.8.0. I will address them seperately. 1. My compiler is complaining about the following code in celt.c which seems to define metric first as celt_word32, then as celt_word16. Am I mis-interpreting something? ?? VARDECL(celt_word32, metric); ?? ALLOC(metric, len, celt_word16); Thx MikeH -------------- next part -------------- An HTML attachment

We were trying to normalize bands that didn't actually exist (e.g., the last band with 320-sample frames at 32kHz). Thanks to John Ridges for the report. --- libcelt/celt.c | 24 +++++++++++++++++------- 1 files changed, 17 insertions(+), 7 deletions(-) diff --git a/libcelt/celt.c b/libcelt/celt.c index 31d35f8..287c720 100644 --- a/libcelt/celt.c +++ b/libcelt/celt.c @@ -1137,6 +1137,7

Here some Blackfin inline assembly, mainly picked and adapted from speex. It's helps a little on my BF537 eval board. Julien -------- /** @file fixed_bfin.h @brief Fixed-point operations for the ADI BF5xx DSP family */ /* Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: -

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

--- libcelt/Makefile.am | 6 +- libcelt/bands.c | 26 +++++++++- libcelt/bands.h | 2 +- libcelt/celt.c | 23 +++----- libcelt/pgain_table.h | 133 ------------------------------------------------- libcelt/quant_pitch.c | 117 ------------------------------------------- libcelt/quant_pitch.h | 44 ---------------- 7 files changed, 37 insertions(+), 314

When I removed the special case for EC_ILOG(0) in commit 06390d082dcdfa8addb3dde337543bc0f0ebae44, it broke ec_dec_uint() with _ft=1 (which should encode the value 0 using 0 bits). This feature was tested by ectest.c, but not actually used by libcelt. An assert has been added to ec_dec_uint() to ensure that we don't try to use this feature by accident. ec_enc_uint() was actually correct,

--- libcelt/bands.c | 43 ++++++++++++++++++++++++------------------- libcelt/bands.h | 6 ++---- libcelt/celt.c | 6 ++---- 3 files changed, 28 insertions(+), 27 deletions(-) diff --git a/libcelt/bands.c b/libcelt/bands.c index d0c3498..315cce8 100644 --- a/libcelt/bands.c +++ b/libcelt/bands.c @@ -247,23 +247,6 @@ void compute_pitch_gain(const CELTMode *m, const celt_norm_t *X, const

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

# 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

Gents, I am getting the following compile error on V11.1 "declaration may not appear after executable statement in block". This occurs in two places in celt.c. ============================================================================ ==================== #ifdef FIXED_POINT #ifndef DISABLE_FLOAT_API CELT_STATIC int celt_encode_with_ec_float(CELTEncoder * restrict st, const

Hello, I'm building packages for Slackware and I've just tried to upgrade Slackware 13.37's CELT package to version 0.11.3, which apparently was released last year, but I've omitted it because it was not announced on the site. Anyway, now that I try build with the following configuration in my SlackBuild script: CFLAGS=$SLKCFLAGS -O2 \ CXXFLAGS=$SLKCFLAGS -O2 \

Hi, I am facing problem when using CELT for iPad. I wonder if someone have experience with that, or someone have idea why it happened. I was able to compile libCelt (and lib Ogg) for iPad (iOS 4.2) and for iPad Simulator I added those libraries to my application, and it was successfully compiled and linked, but once the application start it immediately crash (even if I am not using any of the

Hi. I am glad to inform everyone here that support for decoding using libcelt was just pushed to ffmpeg. It raised a few API questions or issues: * At least while it's experimental, having a constant in the library for the supported bitstream version would probably be useful. Something like that comes to mind: extern celt_int32 celt_bitstream_version; or, even better: int

? 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

Hi JM, When porting my project to the Mac, I found that the definition for "celt_int16" and "celt_uint16" are wrong for the MacOS X Framework in celt_types.h, and need to be changed to "int16_t" and "u_int16_t" respectively. Just thought you ought to know. John Ridges

?? 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 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'd like to add support for CELT in a C# application. To do so, I'd like to build CELT as a static library using VS which I would then wrap with C++/CLI so I can access the encode/decode funtionality from within C#. Is it possible to compile CELT using Visual Studio? The first issue I ran into was that VS doesn't support the 'restrict' keyword. It does have __restrict which