search for: speex_jitter_get

...a JitterBufferPacket and passing that to speex_jitter_put, my program works with the new jitter buffer using the wrapper functions (speex_jitter_* instead of the new jitter_buffer_*). However, a lot of warning: did you forget to call jitter_buffer_tick() by any chance? is displayed. Looking at speex_jitter_get, the logic seems to be as follows: if there is another frame in the previously fetched packet, decode it and call jitter_buffer_tick else get a new packet and decode first frame. But when a new packet is fetched, jitter_buffer_tick isn't called, so if I only have one frame per packet, it wi...

Since r12660, the speex_jitter_get with high latency doesn?t works, I have no sound. Before this release, the speex_jitter_get works in all conditions. speex_jitter_get return void, then I cannot know the reason of this problem. Regards Ouss -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca...

...nstead of the new jitter_buffer_*). Oops, I forgot to make sure I keep the API stable for the old buffer. Any thoughts on the change (revert or continue as is)? > However, a lot of > warning: did you forget to call jitter_buffer_tick() by any chance? > is displayed. > > Looking at speex_jitter_get, the logic seems to be as follows: > > if there is another frame in the previously fetched packet, decode it and > call jitter_buffer_tick > > else get a new packet and decode first frame. > > But when a new packet is fetched, jitter_buffer_tick isn't called, so if I &g...

[The following is perhaps a long question and even off-speex topic,] [but if anyone can at least point me in the right direction for ] [alternate sources of information, I'd really appreciate it. ] When speex_jitter_get(...) is called and there is no buffer/data to return, would I not want to know that there is no true data to play? If I turn around and queue 20ms of silence to play for the sound-card, the sound card will never be able to "catch-up" with the datastream when it starts to feed actual voic...

...flexible implementation and can more easily be adjusted to contain additional information with each packet. >> But when a new packet is fetched, jitter_buffer_tick isn't called, so if I >> only have one frame per packet, it will never be called. >> >> Is this a bug in speex_jitter_get, or am I doing something wrong? > > This is definitely a bug in speex_jitter_get() because it hasn't been > updated for changes in the "generic" jitter buffer. I'll fix that. Thanks :)

...jitter buffering is more correct way to > solve > > this problem but I think this is not so easy. Is > there > > got any source code to reference from? > > Look for the speex_jitter.h header. I tried to implement it but I don't really understand the parameters for the speex_jitter_get() and speex_jitter_put() function. I have the following questions: Since the second parameter of speex_jitter_put() is a char* and the second parameter of speex_jitter_get() is a short*, does it mean that these two function will actually replace speex_bits_read_from() and speex_decode_int()? A...

I use the speex version of your jitter, and in speex_jitter_get, you always call the jitter_buffer_update_delay. -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: dimanche 18 mars 2007 13:06 To: Ouss Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Problem with the svn jitter buffer > I think that the new Jit...

Mike Taht wrote: > > > On 5/3/06, *Jean-Marc Valin* <Jean-Marc.Valin@usherbrooke.ca > <mailto:Jean-Marc.Valin@usherbrooke.ca>> wrote: > > > I must say I really like the generalized jitter buffer though :) > It's a > > cleaner and more flexible implementation and can more easily be > adjusted > > to contain additional

On May 3, 2006, at 7:40 PM, Jean-Marc Valin wrote: > >> Yes. Jean-Marc has made the API more similar. >> >> Jean-Marc: Have you looked at the API we have for the >> asterisk/iaxclient jitterbuffer? > > Just did. > >> It's pretty close to what you have now -- the major difference is >> that >> your jb still assumes it can

On 5/3/06, Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca> wrote: > > I must say I really like the generalized jitter buffer though :) It's a > > cleaner and more flexible implementation and can more easily be adjusted > > to contain additional information with each packet. This looks interesting to tie into asterisk's jb and plc code as well.

Hi Ouss, Can you test again? I think I found and fixed the problem. Jean-Marc Ouss a ?crit : > Since r12660, the speex_jitter_get with high latency doesn?t works, I have > no sound. > Before this release, the speex_jitter_get works in all conditions. > speex_jitter_get return void, then I cannot know the reason of this problem. > > Regards > > Ouss > > > > -----Original Message----- >...

...g is handled. I have 1 x SpeexJitter struct per client stream Im using portaudio and Im planning on using the callback to iterate through all the buffers getting decoded frames. There is no upper limit (in theory) to how many client streams/buffers there can be and as far as I can see the speex_jitter_get(..) performs quite a bit of code. In this case just to iterate through all buffers calling get(...) is quite inefficient so Im considering implementing a int buffer_has_data(SpeexJitter* jitter) { int count = 0; jitter_buffer_ctl(Jitter->packets, JITTER_BUFFER_GET_AVALIABLE_COUNT, &...

...estion: > Do I understand it that I should not put every incoming packet through the > jitter buffer? > > The way my code works today is: > > 1) Packet read from socket > 2) Call speex_jitter_put(...) with the just-arrived packet > 3) Read one packet from jitter buffer using speex_jitter_get(...) function > 4) Feed just read-from-jitter packet to the sound card for playback > > This will in fact feed one 20msec batch of sound to play at the sound card > for every packet received from the speex encoder at the other end. > > I know I may sound a bit slow-on-the-pickup h...

On May 3, 2006, at 9:12 PM, Jean-Marc Valin wrote: >> We just return a frame with the return value JB_DROP, which tells the >> caller to drop this frame, and call jb_get again. >> >> When the caller is done with the jitterbuffer, it calls jb_getall() >> repeatedly, until it's empty, and then it can discard all the frames. > > Hmm, looks a bit error-prone to

On May 3, 2006, at 9:54 PM, Jean-Marc Valin wrote: >> Perhaps, but then you need to assume that the jitterbuffer can just >> throw away the data, and that limits how you can use it. In object- >> oriented terms, you might want to pass objects to the JB, and then >> call a destructor on them. In C terms, you may want to allocate >> frames via malloc(), and then call

...estion: > Do I understand it that I should not put every incoming packet through the > jitter buffer? > > The way my code works today is: > > 1) Packet read from socket > 2) Call speex_jitter_put(...) with the just-arrived packet > 3) Read one packet from jitter buffer using speex_jitter_get(...) function > 4) Feed just read-from-jitter packet to the sound card for playback > > This will in fact feed one 20msec batch of sound to play at the sound card > for every packet received from the speex encoder at the other end. > > I know I may sound a bit slow-on-the-pickup h...

> Yes. Jean-Marc has made the API more similar. > > Jean-Marc: Have you looked at the API we have for the > asterisk/iaxclient jitterbuffer? Just did. > It's pretty close to what you have now -- the major difference is that > your jb still assumes it can "own" the data passed in -- it copies it, > and it destroys it at will. With the API I put together,

...kip a frame to reduce latency. ... Question: Do I understand it that I should not put every incoming packet through the jitter buffer? The way my code works today is: 1) Packet read from socket 2) Call speex_jitter_put(...) with the just-arrived packet 3) Read one packet from jitter buffer using speex_jitter_get(...) function 4) Feed just read-from-jitter packet to the sound card for playback This will in fact feed one 20msec batch of sound to play at the sound card for every packet received from the speex encoder at the other end. I know I may sound a bit slow-on-the-pickup here, but at the risk of soun...

> We just return a frame with the return value JB_DROP, which tells the > caller to drop this frame, and call jb_get again. > > When the caller is done with the jitterbuffer, it calls jb_getall() > repeatedly, until it's empty, and then it can discard all the frames. Hmm, looks a bit error-prone to me. Especially considering I still have to explain that "no, you

...e. But In other computers the same code return 1. After I add the function speex_preprocess(), speex_bits_write() return 1 when it is silence in all computers. Besides, I found another problem. I enabled VAD and DTX. I called speex_preprocess() before speex_encode(). I used speex_jitter_put() and speex_jitter_get() to decode. When I played the voice data after I call speex_jitter_get(), I can hear nothing. The sound disappeared. Thanks Jonathan <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message...