search for: celtdec

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

...p 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 following errors when building the packages: celt.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/celtdec ['/usr/lib64'] celt.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/celtenc ['/usr/lib64'] **********************************...

...uilddir)/libcelt/libcelt.la +tandem_test_LDADD = $(top_builddir)/libcelt/libcelt at LIBCELT_SUFFIX@.la diff --git a/tools/Makefile.am b/tools/Makefile.am index c7678b6..65099ce 100644 --- a/tools/Makefile.am +++ b/tools/Makefile.am @@ -15,7 +15,7 @@ noinst_HEADERS = wav_io.h bin_PROGRAMS = celtenc celtdec celtenc_SOURCES = celtenc.c wav_io.c skeleton.c -celtenc_LDADD = $(top_builddir)/libcelt/libcelt.la $(OGG_LIBS) +celtenc_LDADD = $(top_builddir)/libcelt/libcelt at LIBCELT_SUFFIX@.la $(OGG_LIBS) celtdec_SOURCES = celtdec.c wav_io.c -celtdec_LDADD = $(top_builddir)/libcelt/libcelt.la $(OGG_LIB...

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

Is it all right to discuss CELT here? I haven't seen any specific mailing list for it yet. I would like to ask if someone could provide me one or two sample Ogg CELT files, so I could test detection in ogginfo. I know CELT content isn't really supposed to be around as files since it would lose all the format's latency advantages, but I assume people can create them if need be. -Ivo

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

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

...aw 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, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20110601/717f50a7/attachment-0002.htm

Hello all, after FOMS I decided to take a look at the opus library and I found that I could improve a bit the build system and cleanup the code a little bit. Most of the changes to the code has been suggested by my two tools cowstats and missingstatic (part of the ruby-elf gem if you care). HTH, Diego