[CELT-dev] CELT in ffmpeg and API questions
nicolas.george at normalesup.org
Wed Apr 20 05:10:36 PDT 2011
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 celt_bitstream_version_supported(celt_int32 version);
Since dynamic linking is supported, a build-time constant is not suitable.
Currently, I resorted to have libcelt generate a dummy header to get the
* The header_size is set to 56, while the header is actually 60 bytes. Is it
* It seems that the celt_*_destroy all accept NULL without choking, just
like libc's free. If this is on purpose, could it be stated in the
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
Url : http://lists.xiph.org/pipermail/opus/attachments/20110420/4265874d/attachment-0002.pgp
More information about the celt-dev