search for: 01111

Hello, *Background:* The RFC 5574 suggests the RTP payload format for the speex codec. The payload formation is straight forward; the encoded frames are to be concatenated one after another. Once we have appended desired number of frames, we have to pad the stream with 01111 sort of sequence to ensure that payload ends on a octet boundary. *Observation:* I am using the speex encoder at 2150 Kbps (by setting the quality to 0). For a frame of 20 ms ~ 160 samples (considering 8000 samples per second as the sampling rate), the encoder is giving me encoded output of 6 byte...

...lo, > > _*Background:*_ > The RFC 5574 suggests the RTP payload format for the speex codec. The > payload formation is straight forward; the encoded frames are to be > concatenated one after another. Once we have appended desired number of > frames, we have to pad the stream with 01111 sort of sequence to ensure > that payload ends on a octet boundary. > > _*Observation:*_ > I am using the speex encoder at 2150 Kbps (by setting the quality to 0). > For a frame of 20 ms ~ 160 samples (considering 8000 samples per second > as the sampling rate), the encoder is gi...

...kground:*_ > > The RFC 5574 suggests the RTP payload format for the speex codec. The > > payload formation is straight forward; the encoded frames are to be > > concatenated one after another. Once we have appended desired number of > > frames, we have to pad the stream with 01111 sort of sequence to ensure > > that payload ends on a octet boundary. > > > > _*Observation:*_ > > I am using the speex encoder at 2150 Kbps (by setting the quality to 0). > > For a frame of 20 ms ~ 160 samples (considering 8000 samples per second > > as the samp...

...(there have been more changes than just this one), but I feel the line above isn't clear enough. Maybe change it to something like this, to make the wording more similar to the rest of the specification Quantized linear predictor coefficient shift needed in bits (NOTE: these bits must be 00000-01111. Originally this was a signed integer, but negative shifts were never implemented). Or perhaps: Quantized linear predictor coefficient shift needed in bits (NOTE: First bit must be zero. Originally this was a signed integer, but negative shifts were never implemented). Any thoughts? Kind regard...

...one), but I feel the line above isn't clear enough. Maybe change it to >> something like this, to make the wording more similar to the rest of the >> specification >> >> Quantized linear predictor coefficient shift needed in bits (NOTE: these >> bits must be 00000-01111. Originally this was a signed integer, but >> negative shifts were never implemented). >> >> Or perhaps: >> >> Quantized linear predictor coefficient shift needed in bits (NOTE: First >> bit must be zero. Originally this was a signed integer, but negative shifts...

...than just this > one), but I feel the line above isn't clear enough. Maybe change it to > something like this, to make the wording more similar to the rest of the > specification > > Quantized linear predictor coefficient shift needed in bits (NOTE: these > bits must be 00000-01111. Originally this was a signed integer, but > negative shifts were never implemented). > > Or perhaps: > > Quantized linear predictor coefficient shift needed in bits (NOTE: First > bit must be zero. Originally this was a signed integer, but negative shifts > were never implemen...

How can I add some size to SPEEX encoded packets without affecting decoding results? I need it to fit smaller (due to VAD) packets in CBR acm-wav file. i.e. I have 10 bytes packet with 0.02s of silence (only background noice without speech). I need to fit it in 16kbps CBR wav file, so I need to put 30 additional bytes to this packets, but decoder should still decode only 0.02s of background

Hello there I'm having trouble decoding speex frames when using 32KHz audio and quality setting 4. If I encode three frames and then decode the three frames then the speex_bits_remaining() still reports that there are bits remaining. All other band modes and qualities reports that the buffer is emptied. Here's an example that shows 4 bits remaing in the buffer after the frames have

...e line above isn't clear enough. Maybe change it to >>> something like this, to make the wording more similar to the rest of the >>> specification >>> >>> Quantized linear predictor coefficient shift needed in bits (NOTE: these >>> bits must be 00000-01111. Originally this was a signed integer, but >>> negative shifts were never implemented). >>> >>> Or perhaps: >>> >>> Quantized linear predictor coefficient shift needed in bits (NOTE: First >>> bit must be zero. Originally this was a signed integ...

After searching the mailing list archive (I forgot to do that before posting, sorry!) I found the solutions: 1) The documentation has a mistake: The bit terminator is NOT set automatically! (I'm using the latest speex version!) It has to be set manually using speex_bits_insert_terminator(&bits); 2) speex_decoder_int() has to be called as long, as it returns -1. After that, all frames

Hello, Is there a simple way to take an input, and convert the decimal integers to binary? In this case, I have a CSV file, and I need to convert the first column of every line to binary. Thanks. -- Jason Thibodeau [[alternative HTML version deleted]]

...just this one), but I feel the line above isn't clear enough. Maybe change it to something like this, to make the wording more similar to the rest of the specification >>>> >>>> Quantized linear predictor coefficient shift needed in bits (NOTE: these bits must be 00000-01111. Originally this was a signed integer, but negative shifts were never implemented). >>>> >>>> Or perhaps: >>>> >>>> Quantized linear predictor coefficient shift needed in bits (NOTE: First bit must be zero. Originally this was a signed integer, but...

Hello to all speex developers, I have question regarding payload length of narrowband speex in RTP. I were watching tcpdump of the xlite softphone and have found that it uses weird payload length namely 75 Bytes I went through various source and without success. To be clear: For 8000Hz sample in 20 ms that is 160 samples per frame. This makes 50 frames per sec. modes bit-rate 8 kbit/s

...2 00:49:52 ssd99 dovecot: auth: Debug: http-client: peer 127.0.0.1:579: Peer no longer used; will now cancel pending connections (0 connections exist) Jul 12 00:49:52 ssd99 dovecot: auth: Debug: http-client: peer 127.0.0.1:579: Peer cancel Jul 12 00:49:57 ssd99 dovecot: auth: Debug: client in: AUTH#01111#011PLAIN#011service=imap#011secured#011session=gv5ZWxNUOoYCGhai#011lip=185.53.173.74#011rip=2.26.22.162#011lport=993#011rport=34362#011local_name=ourdomian1.com#011resp=<hidden> Jul 12 00:49:57 ssd99 dovecot: auth: Debug: policy(sales at ourdomian1.com,2.26.22.162,<gv5ZWxNUOoYCGhai>): P...