[Speex-dev] Re: compatibility issues.
caroundw5h at yahoo.com
Fri May 25 08:00:56 PDT 2007
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 up with the best way i want to put it all together later.
unless i'm missing something-and tell me if i am-my question still stands: "packet is larger than the allocated buffer, truncating input" is the error mesg
i'm getting. I'll check out the speex_encoder_ctl(enc_state,SPEEX_GET_FRAME_SIZE,&frame_size); function to capture this. but i wanted to know if there was something i was overlooking.
Jim Crichton <jim.crichton at comcast.net> wrote: For a streaming application like VOIP, you collect 20 ms of samples, feed
this through the encoder, stick it in an RTP packet, and send if over the
network. On the receive side you feed packets through a jitter buffer to
the decoder, and then copy the output audio to your output device. Speex
runs efficiently on most compilers, so the real-time requirement is not a
big deal, as long as you know how to do this with your operating system (if
you have one).
You do not need Ogg containers for something like this, just search the
archives for RTP references and you will find much more.
Look at the SpeexClient application provided in the source tree, and at the
testenc examples in the libspeex directory. The Speex part of things is
pretty easy (thanks to Jean-Marc). It is the audio interface for your
specific platform and the call setup protocals (e.g. SIP) where the real
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
----- Original Message -----
Cc: ; ; "Jean-Marc Valin"
Sent: Thursday, May 24, 2007 11:30 PM
Subject: Re: [Speex-dev] Re: compatibility issues.
> I am also working on VOIP application.
> Now the speexenc.exe is used to encode a wav/raw file. However, in real
> voice communication, the voice keep recording from the microphone and how
> we employ speex to compress the voice and send over the network?
> Quoting Greg :
>> okay that questioned is answered, thank you.
>> I am interested in using speex in a VOIP application. do i need to put it
>> the ogg contianer format in order to encode/decode and send it? or will
>> "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
>> and using the speex_bits_init_buffer() function to create a bigger
>> However i
>> want to keep latency in mind and make them as small as possible.
>> i apologise if the questions seem simple but i've working at this for
>> and i'm a little stump. a indication in the right direction would be
>> thank you in advance,
>> Jean-Marc Valin wrote: > does this have
>> anything to do with the message on the example code:
>> > "the packing used is not compatible with speexenc/speexdec" i know it
>> > may sound stupid but it is my first time using speex lib. as well i
>> > had assumed this was so and tweaked the decoder code to decode the
>> > same file that the example encode code made, but i get a "packet is
>> > larger than allocated buffer could not resize buffer, truncating
>> > input" message.
>> Well, the note says it all. It's just not compatible. speexenc/dec pack
>> Speex data into an Ogg container, while the sampleenc/dec code just
>> creates an incompatible ad-hoc format just to demonstrate how to use
>> Speex (without bothering with the heavy Ogg code).
>> Building a website is a piece of cake.
>> Yahoo! Small Business gives you all the tools to get online.
> Speex-dev mailing list
> Speex-dev at xiph.org
Sucker-punch spam with award-winning protection.
Try the free Yahoo! Mail Beta.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Speex-dev