search for: jitter_buffer_update_delay

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 Jitter Buffer have a problem. > > It works p...

...From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: dimanche 18 mars 2007 23:07 To: Ouss Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Problem with the svn jitter buffer Ouss a ?crit : > I use the speex version of your jitter, and in speex_jitter_get, you always > call the jitter_buffer_update_delay. And what's the problem exactly? Jean-Marc > > > > -----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 sv...

pwk.linuxfan@gmx.de wrote: > On Sunday 08 July 2007 02:24, Thorvald Natvig wrote: > >> Next, and slightly unrelated question: >> Why does >> int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket >> *packet, spx_int32_t *start_offset); >> include the packet parameter? It's not used in the code, and it also >> makes the API slightly confusing as it's very unclear what that >> parameter should be :) >> > &g...

...buffer_get can return JITTER_BUFFER_INSERTION and JITTER_BUFFER_MISSING. In both situations speex_jitter_buffer.c makes the codec interpolate a frame. How are these conditions different, and is there a better recommended strategy for handling one versus the other? Am I correct that calling jitter_buffer_update_delay might eventually cause one or more buffered packets to be skipped? And in any case, what are the implications of having auto_adjust change the delay on every call to jitter_buffer_tick versus speex_jitter_buffer.c's strategy of making it contingent upon the "activity level" of...

...in speex_callbacks.c, it seems the speex_default_user_handler first unpacks 4 bits as size, then advances 8*size + 5 bits. First of all, shouldn't that be 5 bits for size (to match manual)? And where did that '+ 5 bits' come from? Next, and slightly unrelated question: Why does int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t *start_offset); include the packet parameter? It's not used in the code, and it also makes the API slightly confusing as it's very unclear what that parameter should be :)

Hello, I think that the new Jitter Buffer have a problem. It works perfectly when I call the speex_jitter_put every 20ms (on my lan) but in other case (with big latency on Internet connexion), it doesn't works. The old version is OK in all cases. Hope it will helps. Thanks Ouss -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ferPacket packet; packet.data = buffer; m_Mutex.Aquire(); ret = jitter_buffer_get(m_JitterBuffer, &packet, 0); if(ret != JITTER_BUFFER_OK) { ZeroMemory(packet.data, maxLength); } jitter_buffer_tick(m_JitterBuffer); jitter_buffer_update_delay(m_JitterBuffer, &packet, NULL); m_Mutex.Release(); } else { ZeroMemory(buffer, maxLength); } }

...in@usherbrooke.ca] > Sent: dimanche 18 mars 2007 23:07 > To: Ouss > Cc: speex-dev@xiph.org > Subject: Re: [Speex-dev] Problem with the svn jitter buffer > > Ouss a ?crit : >> I use the speex version of your jitter, and in speex_jitter_get, you > always >> call the jitter_buffer_update_delay. > > And what's the problem exactly? > > Jean-Marc > >> >> >> -----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 >...

...; is there a better recommended strategy for handling one versus the > other? At this point, the only way to do an insertion with libspeex is to pretend a packet was lost. But this is just an implementation issue, the two cases could be implemented differently. > Am I correct that calling jitter_buffer_update_delay might eventually > cause one or more buffered packets to be skipped? And in any case, > what are the implications of having auto_adjust change the delay on > every call to jitter_buffer_tick versus speex_jitter_buffer.c's > strategy of making it contingent upon the "act...

...gt; >> ret = jitter_buffer_get(m_JitterBuffer, &packet, 0); >> >> if(ret != JITTER_BUFFER_OK) >> { >> ZeroMemory(packet.data, maxLength); >> } >> >> jitter_buffer_tick(m_JitterBuffer); >> jitter_buffer_update_delay(m_JitterBuffer, &packet, NULL); >> m_Mutex.Release(); >> } >> else >> { >> ZeroMemory(buffer, maxLength); >> } >> } >> >> _______________________________________________ >> Speex-dev mailing list >> Spee...

Hi, I'm one of the people working on the Rockbox project (http://www.rockbox.org) which is an open source alternative firmware for a range Digital Audio Players. Recently we integrated support for the Speex codec using libspeex and seems to work well. If you could add Rockbox to your list of software that supports Speex, that'd be great. So that's the introduction done. Now for

...EXPORT int jitter_buffer_get_another(JitterBuffer *jitter, JitterBufferPacket *packet) { int i, j; for (i=0;i<SPEEX_JITTER_MAX_BUFFER_SIZE;i++) @@ -733,7 +733,7 @@ } /* Let the jitter buffer know it's the right time to adjust the buffering delay to the network conditions */ -int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t *start_offset) +EXPORT int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t *start_offset) { /* If the programmer calls jitter_buffer_update_delay() directly, automatically disable aut...

...> m_Mutex.Aquire(); > > ret = jitter_buffer_get(m_JitterBuffer, &packet, 0); > > if(ret != JITTER_BUFFER_OK) > { > ZeroMemory(packet.data, maxLength); > } > > jitter_buffer_tick(m_JitterBuffer); > jitter_buffer_update_delay(m_JitterBuffer, &packet, NULL); > m_Mutex.Release(); > } > else > { > ZeroMemory(buffer, maxLength); > } > } > > _______________________________________________ > Speex-dev mailing list > Speex-dev@xiph.org > http://lists.xiph.org/m...

...EXPORT int jitter_buffer_get_another(JitterBuffer *jitter, JitterBufferPacket *packet) { int i, j; for (i=0;i<SPEEX_JITTER_MAX_BUFFER_SIZE;i++) @@ -733,7 +733,7 @@ } /* Let the jitter buffer know it's the right time to adjust the buffering delay to the network conditions */ -int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t *start_offset) +EXPORT int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t *start_offset) { /* If the programmer calls jitter_buffer_update_delay() directly, automatically disable aut...

...>len;j++) > packet->data[j] = jitter->buf[i][j]; > /* Remove packet */ > speex_free(jitter->buf[i]); > @@ -438,7 +438,7 @@ > /* Let the jitter buffer know it's the right time to adjust the buffering delay to the network conditions */ > int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket *packet, spx_uint32_t *start_offset) > { > - int i, j; > + int i; > float late_ratio_short; > float late_ratio_long; > float ontime_ratio_short; > diff -bu ../../../speex/libspeex/kiss_fft.c libspeex/kiss_fft.c > ---...

..._buffer_get(m_JitterBuffer, &packet, 0); >>> >>> if(ret != JITTER_BUFFER_OK) >>> { >>> ZeroMemory(packet.data, maxLength); >>> } >>> >>> jitter_buffer_tick(m_JitterBuffer); >>> jitter_buffer_update_delay(m_JitterBuffer, &packet, NULL); >>> m_Mutex.Release(); >>> } >>> else >>> { >>> ZeroMemory(buffer, maxLength); >>> } >>> } >>> >>> _______________________________________________ >>&...