similar to: Description of how CELT packs into Ogg?

Hi all, Just found out about this codec and I'm really impressed. I compiled celt-0.5.2.tar.gz on my desktop and tried out a few tests. I then did a native fixed point arm compile on my beagleboard which also worked a treat. Before I get started with the library I was trying to see if I could grab some real time audio, encode it and write to a file using arecord in conjunction with

I have been trying some different sample rate and bitrate combinations to get a feel for how CELT behaves. I then encoded it with a couple of different frame sizes and sample rates. There were some small differences, but nothing horrible. So, I decided to run with 24KHz sample rate with 16 bit samples. This seemed like a reasonable tradeoff against the quality degradation that my folks

Hi, I am running celt 0.11.1 on my mac which is running osx lion. I invoke celt such as so: celtenc original.wav output.oga I do not see any files being encoded, the wave file is stereo 16 bit at 44.1kHz. Any ideas on why this is not working? I also tried the opus git repo for the latest sources, but that also does not produce an encoded file. Thanks -- -baeksanchang -------------- next

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

Hi, I'm currently testing libcelt (celt-0.9.1) on my Openwrt/Kamikaze RDC-3210 platform and although I'm able to Crosscompile on my Ubuntu 10.10 machine without errors, the resulting celtenc doesn't seem to work properly. Ran ./configure via the Openwrt makefile first (activating fixed-point) ; I first produce a S16_LE Raw PCM file (48Khz, stereo) : test.pcm Then I try to encode

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

So, once all those things are in place what Andrew says WILL happen? I think plans as important as that deserves an announcement. Roadmap for the project? Future directions for the main committers? Are there patent issues? Date: Mon, 11 Jul 2011 20:45:14 -0400 > From: Gregory Maxwell <gmaxwell at gmail.com> > Subject: Re: [CELT-dev] Mailing list and project shutdown >

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

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

I saw the custom API, but nothing explicitly says "CELT-only" just "custom sample rate and frame size". I'll dig further now that you've pointed me in a direction. Thanks, -a On 7/6/15, 6:18 PM, Jean-Marc Valin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I believe what you want is called Opus custom (OPUS_CUSTOM in the > code).

I need to test the latency of a system that I ported CELT to. I'd like to set a flag when the stream "changes". In order to see the stream "change", I'd like to be able to scan the compressed CELT directly to set the flag. ie. I'd like to be able to find a byte or two that change reliably between two values when the stream "changes". I don't

Hi, To enable stereo in celtenc do I need to change anything other than #define CHANNELS 1 to #define CHANNELS 2 The reason is after I do this the audio sounds distorted. Please let me know if I need to do anything else or whether I need to investigate what's happening at my end further. Paul.

Josh, Automake 1.10 on OSX is giving me warnings like the following: test/Makefile.am:50: wildcard *.raw: non-POSIX variable name test/Makefile.am:50: (probably a GNU make extension) test/Makefile.am:50: wildcard *.flac: non-POSIX variable name test/Makefile.am:50: (probably a GNU make extension) test/Makefile.am:50: wildcard *.oga: non-POSIX variable name

On 6/7/14, 1:55 AM, Jean-Marc Valin wrote: > Actually... no! 24-bit can indeed be useful as extra margin and Opus > can actually represent even more dynamic range than 24-bit PCM. That's > not the case for 192 kHz. There's no "margin" that 192 kHz buys you > over 48 kHz. You can do as much linear filtering as you like, the > stuff above 20 kHz isn't going to

Hi list, I have been trying to get the new file extension for Ogg FLAC (.oga) to work with Amarok. But it does not look to be possible due to limitations in the xine and gstreamer engines. Maybe the move to .oga was prematurely? I have done some testing with other players?including Banshee, Quod Libet, and others?but have not had any success with playing the .oga files. Only player I have

I'd like to create a polar plot similar to those created by the polarFreq function in the openair package. However, this package seems to be specific to wind speed and direction, and requires a "ws" (wind speed) and a "wd" (wind direction) column. My data is unrelated to wind speed, but I'd like to be able to get a plot that does what polarFreq's plots do; I'd

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

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that