search for: caroundw5h

...ide i appreciate the work you've done on speex and turned to it because it was cited as a very decent codec specifically for COIP Please let me know what are the common folders to link for an application, and whether or not there is any other documentation about speex i'm missing. thanks. caroundw5h compile log: Compiler: Default compiler Building Makefile: "G:\Code\Projects\X3\X3_TESTS\Makefile.win" Executing make clean rm -f ../X3_DEPENDANTS/speex_1.2beta1/libspeex/speexTest.o speexTest.exe gcc.exe -c ../X3_DEPENDANTS/speex_1.2beta1/libspeex/speexTest.c -o ../X3_DEPENDANTS/spe...

It's not an include file missing. This is a link error. You need to link with libspeex (or whatever it's called when you build it). Jean-Marc Quoting Caroundw5h <caroundw5h@yahoo.com>: > Hi Jean, > > I'm trying to compile the encode.c and or the test programs that are on the > site and in libspeex respectively. however, i keep getting some undefined > references to the basic speex functions(see compiler log). a query on google &gt...

...pecific hardware/software platform that you >> plan to use, then someone may be able to point you to examples for >> the audio interface software. >> >> - Jim >> >> ----- Original Message ----- From: <alex@gorex.com.hk> >> To: "Greg" <caroundw5h@yahoo.com> >> Cc: <greg@mytantrum.com>; <speex-dev@xiph.org>; "Jean-Marc Valin" >> <jean-marc.valin@usherbrooke.ca> >> Sent: Thursday, May 24, 2007 11:30 PM >> Subject: Re: [Speex-dev] Re: compatibility issues. >> >> >>>...

...als (e.g. SIP) where the real work is. If you identify the specific hardware/software platform that you plan to use, then someone may be able to point you to examples for the audio interface software. - Jim ----- Original Message ----- From: <alex@gorex.com.hk> To: "Greg" <caroundw5h@yahoo.com> Cc: <greg@mytantrum.com>; <speex-dev@xiph.org>; "Jean-Marc Valin" <jean-marc.valin@usherbrooke.ca> Sent: Thursday, May 24, 2007 11:30 PM Subject: Re: [Speex-dev] Re: compatibility issues. > HI, > I am also working on VOIP application. > Now the...

...t; If you identify the specific hardware/software platform that you plan to > use, then someone may be able to point you to examples for the audio > interface software. > > - Jim > > ----- Original Message ----- > From: <alex@gorex.com.hk> > To: "Greg" <caroundw5h@yahoo.com> > Cc: <greg@mytantrum.com>; <speex-dev@xiph.org>; "Jean-Marc Valin" > <jean-marc.valin@usherbrooke.ca> > Sent: Thursday, May 24, 2007 11:30 PM > Subject: Re: [Speex-dev] Re: compatibility issues. > > >> HI, >> I am also worki...

okay that questioned is answered, thank you. I am interested in using speex in a VOIP application. do i need to put it in into the ogg contianer format in order to encode/decode and send it? or will it work "as is"? if the latter then: "the packet is larger than the allocated buffer" message: whats your recomendaton for fixing that? i was thinking simply getting the size of

...e real work is. If you identify the specific hardware/software platform that you plan to use, then someone may be able to point you to examples for the audio interface software. - Jim ----- Original Message ----- From: <alex@gorex.com.hk> To: "Greg" <caroundw5h@yahoo.com> Cc: <greg@mytantrum.com>; <speex-dev@xiph.org>; "Jean-Marc Valin" <jean-marc.valin@usherbrooke.ca> Sent: Thursday, May 24, 2007 11:30 PM Subject: Re: [Speex-dev] Re: compatibility issues. HI, I am also working on VOIP...

HI, I am also working on VOIP application. Now the speexenc.exe is used to encode a wav/raw file. However, in real time voice communication, the voice keep recording from the microphone and how can we employ speex to compress the voice and send over the network? Thanks Quoting Greg <caroundw5h@yahoo.com>: > okay that questioned is answered, thank you. > > I am interested in using speex in a VOIP application. do i need to put it in > into > the ogg contianer format in order to encode/decode and send it? or will it > work > "as is"? if the latter then: &g...

i don't think so. this is my current code: for(i=0; i<samples;i++){ /*only get max 320 bytes at a time so bits can handle*/ Client->raw_audio[i] = *input++; Client->temp_audio[i] = Client->raw_audio[i]; Client->session_File[ndx] = Client->temp_audio[i]; ndx+=1; } speex_bits_reset(&ebits);

i'm trying to find the speex_preprocess_run fuction and checked in the speex/speex_preprocess.h but the prototype isn't there. I'm using 1.2beta1 checked the trunk and it seems to say that is the right header. wondering if anyone else has/had this issue and if its resolved or my lib just got corrupted somehow. thanks Greg --------------------------------- Be a better

I don't know too much about echo cancellation so forgive me if the question seems silly. i was wondering is it possible to have the echo canceler be taken care of by speex instead of the develper having to code it in his/her application? ----------------no sig --------------------------------- Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search.

Hi, i have some code that gives me a "warning: Buffer too small to pack bits" mesage. looking at the libspeex source/bits.c i see the warning in a a function named speex_bits_pack. i'm not using this function. can someone tell me where this may be coming from since i've had a similiar problem before and had that fixed. i can't seem to pinpoint this one. thanks Greg

Hi, I've enocded and decoded a file using speexencexe/speexdec.exe respectively. However when i use the example code to encode a file and use speexdec.exe to decode it; not only do i get a file that is 3kb larger than if i had encoded it with the .exe but also I get a "this doesn't look like a speex file" message, and it is unable to decode it. I've checked around and it

thanks for the reply Jim. I'm actually well aware of the packaging, setup and teardown of sessions,and have the audio interface part figured out and implemented (Port Audio). The speexclient.c encapsulate audiocapture,encoding,sending and decoding. for my purposes now i've implemented my code more modular. first so i could understand each piece of the software involved and so i could come