similar to: Missing 'extern "C" {' in speex_jitter_buffer.h ?

Hi, I'd like to report a bug in speexclient/speex_jitter_buffer.c. In the function speex_jitter_get(), after the line: packet.data = data; add the line packet.len = 2048; If this variable is uninitialized, then in jitter_buffer_get() (in jitter.c), the predicate "jitter->packets[i].len > packet->len" is undetermined. When this happens, the wrong amount of

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

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

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

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

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

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

Fantastic! Thanks Tom. (if only it was possible to change the VBR target on the fly for the H264 codec we've licensed :-) ) Cheers, Josh On Apr 11, 2008, at 2:39 PM, Tom Grandgent wrote: > 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

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, I've a couple of questions about the jitterbuffer. First of all, I'm a bit confused about the code to use. Googling the subject I've find that there are, or there were, two jitter buffers, a generic one and a speex-specific one, is this still true or they've been joined? Downloading the 1.2rc1 source code there's no trace of the SpeexJitter structure and wrapper functions

I wasn't able to find anything in the list archives, please forgive me if this question has been asked before... 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? In

Hi, I'm using clang ast for a while now to do meta compilation, and I just fell into a problem when trying to parse vulkan library which has extern "C" in it. Every symbol inside extern "C" seem to be striped from the TU and ast. I tried to #undef __cplusplus and this time I got the symbols into the AST. I first supposed it was a problem with missing includes or else, but

Full_Name: Byron Ellis Version: 1.2.2 OS: all Submission from: (NULL) (140.247.105.95) R_ext/Arith.h #ifdef MAIN #define extern #endif #ifdef __cplusplus extern "C" { #endif these two should be reversed. Its never a problem because builds aren't done against C++ compilers, but its still an error (just a low priority one). also, you could change that to #ifdef __cplusplus extern

I am not able to #include "R_ext/Altrep.h" from a C++ file. I think it needs two changes: 1. add the same __cplusplus check as most of the other header files: #ifdef __cplusplus extern "C" { #endif ... #ifdef __cplusplus } #endif 2. change the line R_new_altrep(R_altrep_class_t class, SEXP data1, SEXP data2); to

Hi all, As some of you may know there some subtle distinction between C and C++ structs, thus one should wrap/annotate them roughly like below. ... #if defined(__cplusplus) extern "C" { #endif struct foo { int bar; ... }; ... #if defined(__cplusplus) } #endif In order to work around the lack of these users can wrap the header inclusion in the same way. For example:

Signed-off-by: Emil Velikov <emil.l.velikov at gmail.com> --- include/uapi/drm/drm.h | 16 ++++++++++++++++ include/uapi/drm/drm_fourcc.h | 8 ++++++++ include/uapi/drm/drm_mode.h | 8 ++++++++ include/uapi/drm/drm_sarea.h | 8 ++++++++ 4 files changed, 40 insertions(+) diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h index 3683250..452675f 100644 ---

Hi! what about #if !defined(__cplusplus) || defined(__STDC_CONSTANT_MACROS) in front of the constant macros for visual c to emulate the behaviour of stdint.h more precisely? -Jochen

--- include/llvm-c/Core.h | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/include/llvm-c/Core.h b/include/llvm-c/Core.h index 3ffaddd..becba7f 100644 --- a/include/llvm-c/Core.h +++ b/include/llvm-c/Core.h @@ -33,6 +33,10 @@ #ifndef LLVM_C_CORE_H #define LLVM_C_CORE_H +#ifndef __STDC_LIMIT_MACROS +#define __STDC_LIMIT_MACROS +#endif + #include

On 2010-03-16 14:22, Josh Gargus wrote: >> If more than one speaker receives the *same* signal, it doesn't >> matter the number of speakers. It only gets tricky when the >> speakers are playing slightly different signals (e.g. from a stereo >> song). > > Does "tricky" mean that the Speex AEC won't handle such situations > well? Or just that you