similar to: About speex quality

Nicer way: void* speexState = speex_encoder_init(&speex_wb_mode); int speexFrameSize, speexRate; speex_encoder_ctl(speexState, SPEEX_GET_FRAME_SIZE, &speexFrameSize); speex_encoder_ctl(speexState, SPEEX_GET_SAMPLING_RATE, &speexRate); SpeexPreprocessState* speexPreprocessState = speex_preprocess_state_init(speexFrameSize, speexRate); Jozsef -----Original Message----- From: Max

What are you trying to accomplish? My code sample was about how Flash Player microphone input in speex. If you want to do decode, please see speexdec.c Jozsef -----Original Message----- From: Max Lapshin [mailto:max.lapshin at gmail.com] Sent: Tuesday, March 30, 2010 8:53 AM To: Jozsef Vass Cc: speex-dev at xiph.org Subject: Re: [Speex-dev] Speex in flash player: how to work with? On Sat, Mar

First of all, Flash Player can only publish Speex at 16 kHz. 20 ms of audio (320 samples) will result in compressed payload size of 106 bytes (42.4 kbps). When Flash Player sends a TC message, there is 11 bytes TC message header and a single byte of audio message header. For more information, please see ActionScript 3 reference http://help.adobe.com/en_US/AS3LCR/Flash_10.0/ Jozsef

On Sat, Mar 20, 2010 at 12:04 AM, Jozsef Vass <jovass at adobe.com> wrote: > Nicer way: > > void* speexState = speex_encoder_init(&speex_wb_mode); > int speexFrameSize, speexRate; > speex_encoder_ctl(speexState, SPEEX_GET_FRAME_SIZE, &speexFrameSize); > speex_encoder_ctl(speexState, SPEEX_GET_SAMPLING_RATE, &speexRate); > SpeexPreprocessState*

rtmplite -- http://code.google.com/p/rtmplite/ -- can be used to record Speex .flv audio and a/v files from Flash/Flex applets, and ffmpeg can be used to extract the Speex audio from such files, which can also be replayed on Flash. > Date: Tue, 23 Aug 2011 14:53:52 -0700 > From: Jozsef Vass <jovass at adobe.com> > > The only way to do this is to publish from Flash Player and

The link is http://www.adobe.com/devnet/rtmp/. TC Message stands for TinCan message. It is 11 bytes long, first byte is message type, three bytes of payload length four bytes of timestamp and three bytes of stream ID. The first byte of the payload for audio message is the format byte and the rest of the byte is the payload. Jozsef ----- Original Message ---- From: Jeff Ramin <jeff.ramin

Thanks for the help folks, but I got this working a couple hours ago. =) I'm quite please after struggling with it for a few days. I just needed to take each audio tag from the FLV file and feed the contents of the tag (except for the first byte) to the jspeex decoder and write the results to a file. Jozsef - it is possible to specify 8KHz in the flash client and decode it as such. Speex

Hi Jozsef, this approach sounds interesting. Do have you have some source code available ? Thanks Mark -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On Behalf Of Jozsef Vass Sent: Friday, September 25, 2009 11:43 PM To: mark_schilling at gmx.de Cc: speex-dev at xiph.org Subject: Re: [Speex-dev] High CPU usage I have run into the same

http://bugzilla.netfilter.org/show_bug.cgi?id=704 CZ <huangj at qualcomm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #4 from CZ <huangj at qualcomm.com>

FLV contains TC messages? TC message payload contains a format byte and speex frames (up to eight). In the format byte 0xb0 indicates speex. Speex is always 16 kHz, 16 bit, mono. Jozsef Message: 1 Date: Mon, 16 Nov 2009 14:40:20 -0600 From: Jeff Ramin <jeff.ramin at singlewire.com> Subject: [Speex-dev] jspeex question To: speex-dev at xiph.org Message-ID: <4B01B8B4.8020904 at

Hi, I have generated a skyline plot of a tree in newick format using "ape". How can I plot the error bars for this graph? I only have the the tree data. un<-"((((8.1:0, 20.1:0):0, 6.1:3):123, (((((35.1:0, (22.1:0, (43.1:1, 29.1:0):0):0):4, 25.1:6):0, ((42.1:0, 21.1:0):3, (39.1:0, 2.1:0):3):1):8, (3.1:0, 7.1:0):8):48, (((((15.1:0, 14.1:0):0, 11.1:0):0, 37.1:0):0,

the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs

Hi Mark, Code below: int16_t* samples; int16_t* fbSilenceFrame; void *fSpeexState; float eng(0.f); int speexFrameSize(0); speex_encoder_ctl(speexState, SPEEX_GET_FRAME_SIZE, &speexFrameSize); for (int i = 0; i < speexFrameSize; i++) { eng += samples[i] * samples[i]; } if (eng / speexFrameSize < 3.f) { memcpy(samples, silenceFrame, speexFrameSize * sizeof(int16_t)); } where

Hi Jean-Marc I am using speex in my voip app (wideband mode). I have noticed that when VAD kicks in, CPU considerably increases (bitrate decreases to 4 kbps). It takes about 7 ms to encode one frame versus 0.5 ms (for speech). This happens regardless preprocessor is used. Although the issue seems to be driver dependent, it occurs on XP, Vista and Mac OS X. Besides complexity and quality, this

Sounds strange. Can you reproduce the problem with speexenc/speexdec? If so, can you send a short file that triggers that along with the exact command line? Jean-Marc Jozsef Vass a ?crit : > Hi Jean-Marc > > I am using speex in my voip app (wideband mode). I > have noticed that when VAD kicks in, CPU considerably > increases (bitrate decreases to 4 kbps). It takes > about 7

Hi Mark, the documentation (section 3.2.1) states: "The single that will affect the CPU usage of Speex the most is whether it is compiled for floating point or fixed-point. [...] On the x86 architecture, floating-point is generally faster, but not always. " And: "Until the VBR feature is ported to fixed-point, you will also need to configure with ?disable-vbr or define

Is there a document somewhere that describes speex-encoded FLV files? What is a TC message? Thanks. Jozsef Vass wrote: > FLV contains TC messages? TC message payload contains a format byte and speex frames (up to eight). In the format byte 0xb0 indicates speex. Speex is always 16 kHz, 16 bit, mono. > > Jozsef > > > Message: 1 > Date: Mon, 16 Nov 2009 14:40:20 -0600 >

blink : It use iLBC also. Voice over IP RTP: A Transport Protocol for Real-Time Applications RFC3550 RCTP: Real Time Control Protocol attribute in Session Description Protocol RFC3605 SRTP: The Secure Real-time Transport Protocol RFC3711 DTMF: Dual-tone Multi-frequency Signaling RFC2833 and inband MWI: Message Summary Event Package RFC3842 Speex and G722: Wide-band Internet Codecs G711, iLBC

I have run into the same issue. Before sending a frame to encoder, I calculate the energy. If it is less than a small threshold, I simply replace this frame with "silence frame," which is 320 random samples of values smaller than 3 (16 kHz). BTW, I have only experience this problem with certain USB headsets that provide you all 0 samples when muted. Jozsef

We have no feedback or information about iLBC usage, is almost not used at all looking at our usage charts. Adrian On Apr 12, 2010, at 3:44 PM, messaging bay wrote: > blink : It use iLBC also. > > Voice over IP > > RTP: A Transport Protocol for Real-Time Applications RFC3550 > RCTP: Real Time Control Protocol attribute in Session Description > Protocol RFC3605 >