[CELT-dev] llcon software using CELT

Jean-Marc Valin jean-marc.valin at usherbrooke.ca
Sun Aug 16 12:04:35 PDT 2009

Hi Volker,

Volker a écrit :
> I have now finished the inclusion of CELT in llcon, replacing all 
> previous audio codecs. CELT is now the core technology in llcon.

Cool. Thanks for letting us know. Is this already available in a
release? If so, I'd like to add llcon to our software list. Just as a
note, it's probably a good idea to include the bitstream version number
somewhere in the protocol to make sure you don't end up with problems
with the CELT bit-stream changes (CELT isn't frozen yet).

> To proceed with an official llcon release, I have some questions 
> regarding CELT:
> - Gregory was suggesting an implementation in CELT so that different 
> CELT streams could be mixed up without adding additional coding delay (I 
> require this in my llcon server). Are there any plans in that direction? 
> If yes, when can I expect to get the code?

There are plans, but it's not that high on the todo list because it does
not have bit-stream implications (i.e. it could be done at any time).
However, if you (or someone else) would like to work on this, we can
guide you.

> - Since CELT is now a core component in llcon, is it allowed to use some 
> CELT text or logo in the main window of llcon?

There is currently no logo for CELT, but assuming you use CELT
unmodified (i.e. with no extension or breakage), then you are allowed to
use the name or any logo.

> - To be able to compile the CELT code in Visual Studio, I had to replace 
> all "restricted" and "inline" by "__restricted" and "__inline". It would 
> be nice if there would exist global defines for those key words so that 
> they could easily be changed depending on the used compiler.

All you need to do is create a config.h file that does
#define restrict
#define inline __inline

or whatever. You can have a look at the win32/config.h file in the Speex



More information about the celt-dev mailing list