similar to: jitter buffer with variable size data

Displaying 20 results from an estimated 10000 matches similar to: "jitter buffer with variable size data"

2008 Mar 29
0
GCC/ELF Visibility patch
Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output
2008 Mar 29
2
GCC/ELF Visibility patch (fwd)
Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output
2011 Nov 17
1
Just getting noise
I'm only doing one frame using speex_encode_int greatly simplifies my code I'm not sure why the sample I was working off of was converting the shorts to floats then calling the other encode/decode methods. Based off of your suggestions I tried the following but I get the same result. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) {
2004 Dec 21
0
Jitter buffer
Hi Steve, Though it may work (haven't thought about all the details), I think it would be much more messy than just using a codec abstraction layer (the one in Speex or a custom one). I don't understand why you don't like that idea. Jean-Marc > And later, it might also be useful to have an API which takes a bunch > of SpeexBits, and gives the caller a way to split up the
2004 Dec 21
2
Jitter buffer
[sorry for the loss of proper attributions, this is from two messages]: [Me] >This is something I've encountered in trying to make a particular > asterisk application handle properly IAX2 frames which contain either > 20ms of 40ms of speex data. For a CBR case, where the bitrate is > known, this is fairly easy to do, especially if the frames _do_ always > end on byte
2009 Dec 02
0
The generic Jitter Buffer and its use
Hello all, I am currently investigating the JitterBuffer struct provided in the Speex library, and I am actually thinking about using it with two different codecs: namely, Speex-NB and AMR-NB. From looking at the code, it seems that JitterBuffer is capable of working for any codec. Both Speex-NB and AMR-NB (and probably also other narrowband codecs) produce 20 ms frames and the sampling frequency
2011 Dec 07
0
回复: 回复: (no subject)
I think it will looks like: void Encode(const char* infile, const char* outFile) { void* st; SpeexBits bits; ..... st = speex_encoder_init(mode); ..... speex_encode_int(st, input, &bits); ..... speex_bits_destroy(&bits); speex_encoder_destroy(st); } 2011/12/7 Steve Checkoway <s at pahtak.org> > > On Dec 7, 2011, at 0:00 , Denis Romashenko
2011 Nov 16
0
Just getting noise
The way I do this is to compute the number of frames (by dividing the size of my input by the number of bytes per frame and then calling speex_encode_int() that many times. Something like speex_bits_reset( &bits ); for( n = 0; n < num_frames; ++n ) { speex_encode_int( enc_state, (int16_t*)input_tail,
2004 Nov 17
3
Jitter buffer
Jean-Marc Valin wrote: >>Heh. I guess after playing with different jitter buffers long enough, >>I've realized that there's always situations that you haven't properly >>accounted for when designing one. >> >> > >For example? :-) > > I have a bunch of examples listed on the wiki page where I had written initial specifications:
2011 Nov 16
2
Just getting noise
Alright noted, I changed me code so that the state is created in the constructor and destroyed in the destructor of the object. However I'm still getting the same issue although I'm sure that would have bit me sooner or later. The new code is as follows. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) { short *in=(short*)inputBuffer;
2011 Dec 07
2
回复: 回复: (no subject)
On Dec 7, 2011, at 0:00 , Denis Romashenko wrote: > I'll try to explain. I want to create dll with only one function > "Encode" > that will encode file to speex format. In my application I will use > this > function from 16 threads, if it will work correct? Surely that depends on the implementation of your Encode function. If you use different encoder state
2007 Feb 14
1
To jitter buffer or not to jitter buffer?
Greetings list, Some time ago (probably about a year ago now) we disabled IAX jitter buffering on all our boxes because it was causing issues in a mixed 1.0 and 1.2 environment. One thing I've noticed over the last few months as more and more clients have moved from the 512k/1mb/2mb ADSL connections they were using onto "up to 8mb" connections is that whilst overall throughput is a
2013 Oct 29
0
[LLVMdev] Are Opcode and register mappings exposed anywhere?
Can't you just include the generated files? What different way would you like them exposed? On Mon, Oct 28, 2013 at 11:23 AM, Stephen Checkoway <s at pahtak.org> wrote: > > On Oct 28, 2013, at 2:02 PM, Tyler Hardin <tghardin1 at catamount.wcu.edu> > wrote: > > > See the source here: >
2013 Oct 28
2
[LLVMdev] Are Opcode and register mappings exposed anywhere?
On Oct 28, 2013, at 2:02 PM, Tyler Hardin <tghardin1 at catamount.wcu.edu> wrote: > See the source here: https://github.com/earl/llvm-mirror/blob/master/lib/Target/X86/InstPrinter/X86IntelInstPrinter.cpp. It looks like getRegisterName might do what you want, but I don't know where it's coming from. (Whether it's a function or a member of a super class. Hopefully, if it's
2013 Nov 15
0
[LLVMdev] Proposal: release MDNodes for source modules (LTO+debug info)
Taking a really quick at the gold code it looks like it tries to keep 8176 files open. I would suggest putting a breakpoint in Descriptors::close_some_descriptor and checking why it is failing to close the files. On 15 November 2013 11:03, Stephen Checkoway <s at pahtak.org> wrote: > > On Nov 15, 2013, at 10:19 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >
2013 Nov 20
0
[LLVMdev] Issues with inline assembly
On Nov 20, 2013, at 4:11 PM, Ghitulete Razvan <razvan.ghitulete at gmail.com> wrote: > On Wed, Nov 20, 2013 at 8:55 PM, Stephen Checkoway <s at pahtak.org> wrote: >> >> This has come up before <https://groups.google.com/forum/#!topic/llvm-dev/vomnIQjefzA>. I don't recall if there was a resolution. >> > > Thanks for the link, completely missed
2013 Nov 21
1
[LLVMdev] Issues with inline assembly
On Nov 20, 2013, at 1:26 PM, Stephen Checkoway <s at pahtak.org> wrote: > > On Nov 20, 2013, at 4:11 PM, Ghitulete Razvan <razvan.ghitulete at gmail.com> wrote: > >> On Wed, Nov 20, 2013 at 8:55 PM, Stephen Checkoway <s at pahtak.org> wrote: >>> >>> This has come up before <https://groups.google.com/forum/#!topic/llvm-dev/vomnIQjefzA>. I
2013 Nov 15
2
[LLVMdev] Proposal: release MDNodes for source modules (LTO+debug info)
On Nov 15, 2013, at 10:19 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > On 14 November 2013 18:01, Stephen Checkoway <s at pahtak.org> wrote: >> >> On Nov 14, 2013, at 8:19 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> >>> But gold has at most 2 objects loaded at any time. >> >> Are you sure about
2005 Sep 18
0
How does the jitter buffer "catch up"?
> > Is is possible to give a short hint about how the jitter buffer would > "catch up" when network condition have been bad and then get better? > > I'm using the jitter buffer with success now, but sometimes I have a > long delay that's caused by bad network conditions and then later when > the conditions get better, I would think we would want the audio to
2013 Nov 15
0
[LLVMdev] Proposal: release MDNodes for source modules (LTO+debug info)
Just a guess, but it might have something to do with the chrome build using thin archives. On 15 November 2013 11:30, Stephen Checkoway <s at pahtak.org> wrote: > > On Nov 15, 2013, at 11:16 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >> Taking a really quick at the gold code it looks like it tries to keep >> 8176 files open. I would suggest