similar to: Bug (and fix) for speex_jitter_buffer.c

Daniel Schmidt a ?crit : > I found the cause of the problem. The function shift_timings can > produce overflows in the timing array if the jitter is huge or the > time units are very short. After changing the timing values' type from > spx_int16_t to spx_int32_t it seems to work. Hmm, I always assumed there wouldn't be any overflows. What parameter range are you using that

Hi, I have a few questions about the speex_jitter_buffer when used with DTX here goes: I want to use the speex_jitter_buffer with muliple streams (multi client) and with DTX so that clients will only transmit data when they are actually saying anything, but Im unsure of how the ticking is handled. I have 1 x SpeexJitter struct per client stream Im using portaudio and Im planning on

Dear speex developers and users, I'm considering adopting the speex jitter buffer for use with a different codec in a voice conferencing system and would be very grateful if those more acquainted with it could help me with some questions. The speex_jitter_buffer.c wrapper seems to maintain (buffer?) one packet-frame ("current_packet") in addition to the packets already

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] Sent: dimanche 18 mars 2007 23:07 To: Ouss Cc:

Hi, It seems like there's a missing ... #ifdef __cplusplus extern "C" { #endif ... somewhere near the beginning of speex_jitter_buffer.h (I'm looking at the latest SVN version). Otherwise, there is nothing to match the "#ifdef __cplusplus" near the end of the file. Inserting the lines above allows my code to compile. (BTW, Speex has been working like a charm

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. > >

Hello Jean-Marc, thank you for your reply. > > I found the cause of the problem. The function shift_timings can > > produce overflows in the timing array if the jitter is huge or the > > time units are very short. After changing the timing values' type from > > spx_int16_t to spx_int32_t it seems to work. > Hmm, I always assumed there wouldn't be any overflows.

Hi Zachary, Zachary Schneirov a ?crit : > The speex_jitter_buffer.c wrapper seems to maintain (buffer?) one > packet-frame ("current_packet") in addition to the packets already > tracked by the JitterBuffer itself. Why is this necessary? That's in case there's more than one frame per packet. That way, it finds the packet, decodes the first frame it contains, and

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 > > >

I am trying to compile speexclient.c. I downloaded all the files to ~/speex- 1.2beta1/include When I call ./compile.sh I get the following errors, speexclient.c: In function 'main': speexclient.c:164: error: 'SPEEX_PREPROCESS_SET_ECHO_STATE' undeclared (first use in this function) speexclient.c:164: error: (Each undeclared identifier is reported only once speexclient.c:164:

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:

Josh, Yes, you can change VBR quality or ABR average bitrate at any time. You don't need to do anything special. I use this feature (changing VBR quality midstream) from time to time and it's quite convenient. Tom Joshua Gargus <schwa at fastmail.us> wrote: > > Hi there (from speex-dev newbie), > > Is it possible to change the target VBR on the fly? The

Hi ! I am working with the speex client example which is on http://svn.xiph.org/trunk/speex/speexclient/ and it does not seem to work out of the box for me. I am always getting this warning messages: warning: jitter_buffer_get() : packet too large to fit. Size is 70. Do you have any idea of why this might be happening ? Thanks in advance, Lorenzo Fundar? Garc?a Universit? de Technologie de

Hi. After changing my code to construct 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

Hi Jean, > Actually, Speex has Packet Loss Concealment (PLC) > builtin. If a packet > is missing, instead of repeating the previous one, > just try decoding by > passing NULL instead of the SpeexBits struct. > Thanks, I have made the above changes and the effect seems to be better now. > > I think jitter buffering is more correct way to > solve > > this problem

On May 5, 2008, at 6:58 PM, Jean-Marc Valin wrote: > Joshua Gargus wrote: >> Our app needs to support multiple media types, so GStreamer would >> seem >> to be the obvious choice. However, voice quality is paramount for >> us. Are there any disadvantages to using the Speex plugin for >> GStreamer as opposed to directly coding to the Speex API? > >

[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

Hello Jean-Marc, Hello speex-dev-people, Jean-Marc Valin wrote: > All I can suggest is having a look at my simple client at: > http://people.xiph.org/~jm/speexclient/ Unfortunately, this does not compile: <<<<< snip >>>>> bjoern@phobos:~/beleg/speex/speexclient-0.0-dev$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether

On Fri, Apr 11, 2008 at 6:53 PM, Joshua Gargus <schwa at fastmail.us> wrote: > Fantastic! Thanks Tom. > > (if only it was possible to change the VBR target on the fly for the > H264 codec we've licensed :-) ) Theora might be able to do that. Some other folks more closely tied with Xiph probably can comment more on that issue. -- Keith Kyzivat SIPez LLC. SIP VoIP, IM

> Message: 1 > Date: Thu, 15 Jul 2010 00:19:43 -0600 > From: devi at purpletalk.com > Subject: [Speex-dev] Speex Echo Cancellation > To: speex-dev at xiph.org > Message-ID: <20100715001943.pr04hvtxsc8k04so at mail.purpletalk.com> > Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; > format="flowed" > > Hi > > I am using speex