search for: speex_lib_ctl

Hi, Right now, I'm thinking of adding a speex_lib_ctl() call that would support SPEEX_GET_VERSION (and return a string) or SPEEX_GET_MAJOR_VERSION and SPEEX_GET_MINOR_VERSION (and return ints). I'm open to other suggestions though. If there's anything you'd like to see in the API for 1.2, say it now. ...and no, I won't add a speex_do_a...

...spx_ilog2 _spx_cos_pi_2 spx_cos_norm spx_exp2 spx_atan In nb_celp.c: nb_encoder_destroy nb_decoder_destroy In quant_lsp.c: lsp_quant_nb lsp_unquant_nb lsp_quant_high lsp_unquant_high In speex.c: speex_encoder_destroy speex_decoder_destroy speex_encode speex_decode nb_mode_query wb_mode_query speex_lib_ctl In speex_callbacks.c: speex_inband_handler speex_std_mode_request_handler speex_std_low_mode_request_handler speex_std_high_mode_request_handler speex_std_vbr_request_handler speex_std_enh_request_handler speex_std_vbr_quality_request_handler speex_std_char_handler speex_default_user_handler In...

...TX mode? > At least that's why I kept it. Of course it *can* be used (and needs fixing). It just seems few people did :-) > So, what's the next step towards intergartion? I guess it should > be somehow made available from Speex API level, e.g. with > new speex_decoder_ctl() or speex_lib_ctl() request? I have > no idea about the best way here, and would appreciate your > advices. I don't think it should be a _ctl() call because there's too much potential for confusion. I would just keep it as a separate API call like you have. I'd tend to put it in speex_bits.h, so I...

...now version 1.1.6 is out. Changes are: * Improved jitter buffer (now actually works!) * Denoiser tuning * Improved echo canceller (please send feedback) * Support for Symbian OS (thanks to Conrad Parker) * Gapless playback for speexenc/speexdec * Run-time identification of Speex version with a new speex_lib_ctl() call * Moved the includes to /usr/include/speex/ Jean-Marc -- Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> Universite de Sherbrooke -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: C...

...n 9882) +++ speex.def (working copy) @@ -2,49 +2,71 @@ ; speex.def ; LIBRARY +NAME libspeex.dll EXPORTS ; -speex_encoder_init -speex_encoder_destroy -speex_encode -speex_encoder_ctl -speex_decoder_init -speex_decoder_destroy -speex_decode -speex_decoder_ctl -speex_mode_query -speex_lib_ctl -speex_lib_get_mode -speex_bits_init -speex_bits_init_buffer -speex_bits_destroy -speex_bits_reset -speex_bits_rewind -speex_bits_read_from -speex_bits_read_whole_bytes -speex_bits_write -speex_bits_write_whole_bytes -speex_bits_pack -speex_bits_unpack_signed -speex_bits_unpack_unsigne...

Alexander Chemeris wrote: > On 2/16/08, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: >>> Oh, you're right, inband handling is different, but it's a matter of one >>> flag, passed to functioin. Probably not that much to keep code DRY. >> Well, let's first merge your code and then we'll see about possible >> simplifications. >

...ory > In quant_lsp.c: > lsp_quant_nb > lsp_unquant_nb > lsp_quant_high > lsp_unquant_high No need for that if you just want 8 kbps. > In speex.c: > speex_encoder_destroy > speex_decoder_destroy > speex_encode > speex_decode > nb_mode_query > wb_mode_query > speex_lib_ctl No need for that if you're not using them in your code. > In speex_callbacks.c: > speex_inband_handler > speex_std_mode_request_handler > speex_std_low_mode_request_handler > speex_std_high_mode_request_handler > speex_std_vbr_request_handler > speex_std_enh_request_handl...

...er_destroy > nb_decoder_destroy > > In quant_lsp.c: > lsp_quant_nb > lsp_unquant_nb > lsp_quant_high > lsp_unquant_high > > In speex.c: > speex_encoder_destroy > speex_decoder_destroy > speex_encode > speex_decode > nb_mode_query > wb_mode_query > speex_lib_ctl > > In speex_callbacks.c: > speex_inband_handler > speex_std_mode_request_handler > speex_std_low_mode_request_handler > speex_std_high_mode_request_handler > speex_std_vbr_request_handler > speex_std_enh_request_handler > speex_std_vbr_quality_request_handler > spee...

On Sun, May 16, 2004 at 06:03:47PM -0400, Jean-Marc Valin wrote: > Right now, I'm thinking of adding a speex_lib_ctl() call that would > support SPEEX_GET_VERSION (and return a string) or > SPEEX_GET_MAJOR_VERSION and SPEEX_GET_MINOR_VERSION (and return ints). > I'm open to other suggestions though. If there's anything you'd like to > see in the API for 1.2, say it now. ...and no, I won...

> Sounds reasonable. You could also overload the existing speex_*_ctl() > calls to take SPEEX_GET_LIB_VERSION, SPEEX_GET_LIB_MAJOR_VERSION, etc. > > What people are really asking for here is a way to determine at for > conditional compilation (i.e. at configure time) what calls are > available. Runtime methods would be nice too, for prebuilts to be able to determine what they

> Right now, I'm thinking of adding a speex_lib_ctl() call that would > support SPEEX_GET_VERSION (and return a string) or > SPEEX_GET_MAJOR_VERSION and SPEEX_GET_MINOR_VERSION (and return ints). > I'm open to other suggestions though. If there's anything you'd like to > see in the API for 1.2, say it now. ...and no, I won...

...de" (which nobody ever uses I guess!). I'm not sure, but I guess it may be used in VBR or DTX mode? At least that's why I kept it. So, what's the next step towards intergartion? I guess it should be somehow made available from Speex API level, e.g. with new speex_decoder_ctl() or speex_lib_ctl() request? I have no idea about the best way here, and would appreciate your advices. > > It would be good to define - it is very misleading for newcomers > > as it is now. And I would like to say, that from user point of view > > "frame" meaning all "layers"...

...9;s why I kept it. > > Of course it *can* be used (and needs fixing). It just seems few people > did :-) > >> So, what's the next step towards intergartion? I guess it should >> be somehow made available from Speex API level, e.g. with >> new speex_decoder_ctl() or speex_lib_ctl() request? I have >> no idea about the best way here, and would appreciate your >> advices. > > I don't think it should be a _ctl() call because there's too much > potential for confusion. I would just keep it as a separate API call > like you have. I'd tend to p...

>>>>> "Malcolm" == Malcolm Baldridge <speex@paypc.com> writes: Malcolm> Well, for compile-time, I'd think that an #ifdef would do the Malcolm> trick. How? VERSION isn't included anywhere except in speex_init_header(), and I do not see any other symbols that encode the version.... That said, I looked at the code for speex_encode_int and friends since

...gt; In nb_celp.c: nb_encoder_destroy nb_decoder_destroy >> >> In quant_lsp.c: lsp_quant_nb lsp_unquant_nb lsp_quant_high >> lsp_unquant_high >> >> In speex.c: speex_encoder_destroy speex_decoder_destroy >> speex_encode speex_decode nb_mode_query wb_mode_query speex_lib_ctl >> >> >> In speex_callbacks.c: speex_inband_handler >> speex_std_mode_request_handler speex_std_low_mode_request_handler >> speex_std_high_mode_request_handler speex_std_vbr_request_handler >> speex_std_enh_request_handler speex_std_vbr_quality_request_handl...

I originally posted these classes because they turned out nice in my application, were reasonably generic, and I thought they'd be useful to other people. I figured it was a chance to give something back to the community. I eventually discovered that this was a bad idea and took them offline mainly for the following reasons: 1) Supporting the various versions of Speex is a nuisance,

Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> wrote: > > > 1) Supporting the various versions of Speex is a nuisance, mainly > > because there is no #define or API call to query the version. > > It is possible to get the version using speex_lib_ctl(int request, void > *ptr). Possible requests are SPEEX_LIB_GET_MAJOR_VERSION, > SPEEX_LIB_GET_MINOR_VERSION, SPEEX_LIB_GET_MICRO_VERSION, > SPEEX_LIB_GET_EXTRA_VERSION, and SPEEX_LIB_GET_VERSION_STRING. Also, > what do you mean by version problems? The API hasn't changed at all for...

...printf ("\n"); printf ("More information is available from the Speex site: http://www.speex.org\n"); printf ("\n"); printf ("Please report bugs to the mailing list `speex-dev at xiph.org'.\n"); } void version() { const char* speex_version; speex_lib_ctl(SPEEX_LIB_GET_VERSION_STRING, (void*)&speex_version); printf ("speexdec (Speex decoder) version %s (compiled " __DATE__ ")\n", speex_version); printf ("Copyright (C) 2002-2006 Jean-Marc Valin\n"); } void version_short() { const char* speex_version; spe...

On Fri, Apr 4, 2008 at 12:19 AM, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > Jahn, Ray (R.) a ?crit : > > > Dear Speex codec community: > > > > I am working on conversion of voice files. I could not figure out how to use speexdec.exe 1.2.3 in piped mode in order to avoid the creation of the potentially large intermediate *.wav or *.pcm files. Any

...urn (*((SpeexMode**)state))->enc_ctl(state, request, ptr); } -int speex_decoder_ctl(void *state, int request, void *ptr) +EXPORT int speex_decoder_ctl(void *state, int request, void *ptr) { return (*((SpeexMode**)state))->dec_ctl(state, request, ptr); } @@ -215,7 +215,7 @@ -int speex_lib_ctl(int request, void *ptr) +EXPORT int speex_lib_ctl(int request, void *ptr) { switch (request) { Index: libspeex/modes.c =================================================================== --- libspeex/modes.c (revision 14645) +++ libspeex/modes.c (working copy) @@ -337,7 +337,7 @@ /* D...