similar to: [PATCH 1/1] add selftest for virtio-net

Selftest is an important part of network driver, this patch adds selftest for virtio-net, including loopback test, negotiate test and reset test. Loopback test checks whether virtio-net can send and receive packets normally. Negotiate test executes feature negotiation between virtio-net driver in Guest OS and virtio-net device in Host OS. Reset test resets virtio-net. Following last patch, this

Selftest is an important part of network driver, this patch adds selftest for virtio-net, including loopback test, negotiate test and reset test. Loopback test checks whether virtio-net can send and receive packets normally. Negotiate test executes feature negotiation between virtio-net driver in Guest OS and virtio-net device in Host OS. Reset test resets virtio-net. Following last patch, this

On 08/27/2014 09:45 AM, Hengjinxiao wrote: > Selftest is an important part of network driver, this patch adds selftest for > virtio-net, including loopback test, negotiate test and reset test. Loopback > test checks whether virtio-net can send and receive packets normally. Negotiate test > executes feature negotiation between virtio-net driver in Guest OS and virtio-net > device

Hi, I'm using the echo cancellation api and I would like to clarify the 'frame_size' parameter used in speex_echo_state_init(frame_size,filter_length). In the 'docs' it says: "...where frame_size is the amount of data (in samples)you want to process at once..." So... here are my questions: if I use stereo input/output do I have to put the samples doubled ? For

Hi All, i need your help in determining the problem in the following sample code (taken from speex manual) for fixed point encoding. i tested encoding a 160 sample frame and then decoding it back But The problem is that the decoded frame is totally different from the original frame(see output below).What is the possible reason for this?.thanks for any help #include<stdio.h>

Hi Jean, Thank you for your reply. Ok... I'm gonna use 'samples per channel' everywhere I see 'samples'... but what about the 'speex_echo_playback' function ? it does the following loop: ... for (i=0;i<st->frame_size;i++) st->play_buf[st->play_buf_pos+i] = play[i]; ... So... if frame size is 'samples per channel' it will copy only half the

Hello everyone I've a following problem with the speex codec. I'm developing application that is supposed to read sounds from the microphone with DirectSoundCapture. Unfortunately when I want to compress and decompress the sound buffer from DirectSound I only have jitter. Maybe you have some code samples how to compress standard DS buffers: LPDIRECTSOUND8 lpDS = NULL;

Hi i'm developing a sort of VoIP application for my ipaq using speex... I'm still at beginning and i have many problems encoding and decoding my wav files....output is only noise! Why? I'm using Libspeex 1.1.3, Embedded VisualC++ 3.0, Ipaq 3850(206 MHz Intel® Strong ARM 32-bit RISC Processor) PocketPC 2002 (Windows CE 3.0). Libspeex is complied with the definition of

Attached is the amended second patch. It now extends the multistream API as well to 80/100/120 ms and incorporates changes based on Mark's comments. Thanks, Felicia On Mon, Jun 13, 2016 at 4:21 PM Felicia Lim <flim at google.com> wrote: > Hi Mark, Jean-Marc, > > Thanks for your comments. > > On Sun, Jun 12, 2016 at 6:34 AM Mark Harris <mark.hsj at gmail.com>

Hi Steve, thanks for the advice. I placed the appropriate functions outside the while statement but I still get this error at the while loop: First-chance exception at 0x004010fa in SPXDEC.exe: 0xC0000005: Access violation reading location 0x0000000c. Unhandled exception at 0x004010fa in SPXDEC.exe: 0xC0000005: Access violation reading location 0x0000000c. It looks like the same error. I've

hey guys, I just compiled an application similar to sampledec.c (for speex 1.1.10) and it was fine but when I executed it, the app exited without doing anything. I'm using MS VC 6.0 and this was all I got - First-chance exception in sampledec.exe : 0xC0000005: Access Violation. Has anyone encountered this / does anyone know how to deal with it? by the way, sampleenc executed perfectly... When

> > This is as expected. The build system is trying to get a git revision > string out of the source tree to compile in for reference. If you're > building from a downloaded source .zip, there won't be any git > information available and it will fall back to the hard-coded release > string. That's why the error isn't fatal to the build. Ok, this seems

I have problem with coding and decoding. I record voice from mic coding and write to file. And when I read from file and put it on sound card it's terrible sound. Have sameone can help me? #include <speex.h> #include <stdio.h> #include <fcntl.h> #include <sys/ioctl.h> #include <sys/soundcard.h> /*The frame size in hardcoded for this sample code but it

Hi all, Please a moment to look my source code, this is very similar to example of the documentation. I added FIXED_POINT flag. My source code compile and build but not decode correctly (the error may be in the while). I work with eVC 4.0 and pocket pc 2003. Someone know what is the error? Thanks. Rodrigo. #include "speex.h" #define FRAME_SIZE 160 void CPlayerDlg::OnButton3() {

Hi Felicia, A few comments: > - /* CELT can only support up to 20 ms */ > subframe_size = st->Fs/50; > - nb_subframes = frame_size > st->Fs/25 ? 3 : 2; > + nb_subframes = frame_size/subframe_size; This will use six 20ms frames to make a 120ms packet, even for SILK-only mode where frames can be up to 60ms. For SILK, two 60ms frames would be a more

Hello, in my project im using speex 1.2rc1 and the preprocessor VAD seems to only separate complete silence from not complete silence frames. The Speex Manual, you can read "The voice activity detector (VAD) provided by the preprocessor is more advanced than the one directly provided in the codec." but if you go to the source code in preprocess.c line 995 "/* FIXME: This VAD

Hi Jean-Marc, Thanks for your response. Please find the details as below. *Backtrace we got for this crash:* #0 0x0000000000800c54 in opus_decode_frame (st=0x38906b8f99d09c5, data=0xf0aa10b4ef1008ae <Address 0xf0aa10b4ef1008ae out of bounds>, len=-188613428, pcm=0x6e80016085efd57, frame_size=44037315, decode_fec=58716895) at src/opus_decoder.c:384 #1 0x00000000008009c0 in

Please provide the input file that produces this with opus_demo. On 16/04/15 03:24 AM, Suresh Thiriveedi wrote: > Hi Jean-Marc, > > Could you please update if you got a chance to look into. As I > mentioned, I don't see the same issue in 1.1.1, but I don't see any > difference in 1.1.1 other than optimization based on the architecture. > This optimization could have

Hi Ulrich, thanks for the suggestion. My concern is that one of the valid inputs is "2.5", which would require conversion to an int, e.g. x10, but doing something like this would start to affect the code readability. On Mon, Jun 27, 2016 at 3:02 PM Ulrich Windl < Ulrich.Windl at rz.uni-regensburg.de> wrote: > Hi! > > A note on style: Looking at this chunk of the patch

It seems that speex (speex 1.0.4 on OSX 10.3.9) is writing over the input buffer (with what looks like a sine wave). Included below is a short program that demonstrates the problem. Is this a bug, or am I doing something wrong? I don't see this behavior mentioned in the docs. I don't really need the input buffer, but I'm guessing this problem is related to a high pitched sound