similar to: does installed lib support _int()s ?

Displaying 20 results from an estimated 3000 matches similar to: "does installed lib support _int()s ?"

2004 Aug 06
2
Re: does installed lib support _int()s ?
>>>>> "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
2004 Aug 06
4
Re: does installed lib support _int()s ?
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_all_the_work_for_me() call :)
2005 Sep 03
2
Library export file for Win32 (patch)
This patch will export new speex functions in the generated library, such as speex_encode_int as well as the preprocessor, echo-cancellation and jitterbuffers. The ordinals used matches the 1.1.6 release from the speex.org website, so any new library created with this def file should be binary compatible with that one. -------------- next part -------------- Index: speex.def
2004 Aug 06
2
1.1 api suggestion
On Mon, Apr 19, 2004 at 02:46:44AM -0400, Jean-Marc Valin wrote: > OK, I'll try to do *something* about it. It'll be either "support the > 1.0 ABI" or "make sure the link will break". While the former would be > nice, I'm not sure I want to really want to force 1.2 to have the same > ABI as 1.0.x. More on this when I have some time to think about it.
2004 Aug 06
0
does installed lib support _int()s ?
> Assuming one prefers to use the speex_encode_int() and > speex_decode_int() when available, but fallback to speex_encode() > and speex_decode() if an older version if the lib is installed, > how does one best make the determination? Well, for compile-time, I'd think that an #ifdef would do the trick. The only way you could do it at RUNTIME is if you perform a dlopen() on the
2005 Jun 22
1
Newbie - Encoding PCM
Hi all, i've to encode voice from a voicemodem. I choose speex 1.0.5 for its quality in voice encoding. I've tried to implement an encoder but unsuccesfully. Here's my code: /* ============ SPEEX stream ENCODER ============================================ */ int SPEEX_EncodePCM(struct _IDA_ClientSocket *IDA,char *buffer,unsigned char *PCM,int num_samples) { /* buffer point to the
2007 Nov 04
2
WaveIn/WaveOut and Speex
Thank you for such a quick response. The only reason I started with Char buffers is because WaveIn and WaveOut on Windows XP accept/emit WAVEHDR structures, which store audio data in LPSTR, which is Char*. typedef struct { LPSTR lpData; DWORD dwBufferLength; ... } WAVEHDR; When I was going from Char to float and back looked very wrong to me as well, but I was just not
2011 Nov 16
2
Just getting noise
Alright noted, I changed me code so that the state is created in the constructor and destroyed in the destructor of the object. However I'm still getting the same issue although I'm sure that would have bit me sooner or later. The new code is as follows. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) { short *in=(short*)inputBuffer;
2011 Nov 17
1
Just getting noise
I'm only doing one frame using speex_encode_int greatly simplifies my code I'm not sure why the sample I was working off of was converting the shorts to floats then calling the other encode/decode methods. Based off of your suggestions I tried the following but I get the same result. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) {
2008 Mar 29
0
GCC/ELF Visibility patch
Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output
2005 Sep 19
1
Samples per frame.. fixed or variable with configuration?
I'm having trouble with a Speex VOIP effort ... my first use of Speex. My development platform is Windows XP, but I intend to bring this up on OS X as well. At the moment, I send across speex frames (say 4 per packet... a configurable setting), and the settings of both encoder and decoder are simply fixed in code at the moment (wideband, short format input). I am fairly confident that I
2008 Mar 29
2
GCC/ELF Visibility patch (fwd)
Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output
2005 Oct 17
1
Function call order on libspeex
Hello, I intend to make a speex port for freescale DSP56F800/E. I downloaded the source code, but I not realize which function are called in which order for encode after calling speex_encode (or speex_encode_int) and speex_decode (or speex_decode_int). Could anybody help me on this? Thanks in advance Alexandre Penna
2004 Aug 06
3
1.1 api suggestion
Hi Jean-Marc, randoms, I've been playing with the 1.1.x api, more specifically modifying code to conditionally build against the 1.0.x api or the 1.1.x api. Code written for 1.0.x builds, with a few warnings, against 1.1.x. The major API change is of course that the type of PCM buffers has changed from float to int. This causes a few warnings related to speex_encode() and speex_decode()
2004 Aug 06
4
speex_encode / speex_encode_int ... already sorry =)
Hi, i know this question has already been asked, i've checked mailing list logs but ... I didn't figure out the solution for my question. I want to use basic functionnality of speex, only VAD, no pre/post filter, even no VBR. But i *really* want to use less mem/cpu i can. So in which format should i pass data to speex_encode(_int) , float or short ? I quickly looked at the source code
2005 Feb 09
2
encoding speex, (insanity looming)
Hi All, I'm very new to speex and in fact handling audio at all, it seems I have run in to a problem I seem unable to fix. I'm trying to take audio from a microphone using alsa, then encode it as speex and save to disk. I have been wondering if it has something to do with endian type, but speexenc and speexdec works fine. Currently I have the following setup: Platform:
2005 Feb 09
1
encoding speex, (insanity looming)
Hi Tom, Thanks for your reply, I'm having a few difficulty's following you advise. You mention that I should be calling 'speex_encoder_int' & 'speex_decoder_int', I'm having problems finding these functions in the speex header. I am currenlty calling speex_encoder_init & speex_decoder_init in my test code, I have repeated the relevent bits of the example
2005 Apr 26
1
tgAudioCodec.zip
I have (finally) posted my Speex wrapper classes. They are at: http://www.grandgent.com/spx/tgAudioCodec.zip I followed your recommendations and they worked fine with 1.1.0. However, I'm still having the same problem with 1.1.7 that I had the last time I tried to upgrade. I'm using the same code with both versions, except for calling speex_encode_int instead of speex_encode, and
2007 Nov 04
3
WaveIn/WaveOut and Speex
Hello, I know my question has been asked before because I spent the last week searching the web for how to use Speex in combination with WaveIn/WaveOut and I ran into a few posts, but none of them answer the question. There is still a lot of confusion how to use WaveIn/WaveOut and Speex by junior developers such as myself. Even after examining code for SpeexDec and SpeexEnc, I cannot get clear
2004 Aug 06
2
Re: does installed lib support _int()s ?
> 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