similar to: rtp payload lenth

Hi, (moving back to the list as some bits can be useful to everyone) > I am sure that 75 is the length of payload only. Confirmed > I also don't have idea for the package containing data of a length 46. > > To make everything more clear, Payload type in rtp packages is 97. > SDP defines the stream as > a=rtpmap: 97 SPEEX/8000 That's a dynamic payload number, so it

Not sure what a payload of 75 bytes could be. Are you sure that doesn't include the 12-byte RTP header? Other than that, maybe it's using wideband (although there's nothing that corresponds exactly to 75 bytes. If you send me the hexdump for one packet, I may be able to find out what it is. Jean-Marc Pawel Cyrta wrote: > Hello to all speex developers, > > I have question

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

Hi, Is is possible to have no problems with VBR speex mode "on" and send multiple frames in one RTP packet? I can't find that in IETF draft. As Jean-Marc said previously, speex decoder recognise the mode of each frame by looking on first 5 bits, thus there shouldn't be a problem with receiving & decoding speex bitstream. However, I found multiple speex frames (say 2) with

Hello, thank you for responding. I'm sure I'm confusing something, but I did not explicitly set either kHz or kbps, I just set the mode to narrowband, and traced through libspeex's code to see that sample_rate was 8000 something, I'm guessing Hz. My assumption was: if you set PA to nb-mode, then you should encode 160 bytes to 21. Is that mistaken? ys On 6/13/07, Jean-Marc Valin

Do not forget to add the "Copying conditions" to the RFC. Check http://wiki.debian.org/NonFreeIETFDocuments That page contains a section titled "Template for RFC authors to release additional rights". To follow that guideline a section like the following should be added: x. Copying conditions The author(s) agree to grant third parties the irrevocable right to

Hi all We are about to send an updated version of the internet draft "RTP Payload Format for the Speex Codec" to the IETF AVT working group. Before submitting we would like your input, if you have any comments or input please send them to the mailing list. If we don't get any comments in 1 week (by 22. May 2007) we will go ahead and submit it to the IETF. Of course you can comment

Looks good to me. Jean-Marc Alfred E. Heggestad a ?crit : > Hi > > Please find an updated version of the Speex I-D attached. The only > change is addition of the copyright conditions in Appendix A, > as requested by Ivo. > > Many thanks for your input. > > I will give you a few more days before submitting to AVT working group > > > /alfred > > Ivo

Hello, the voice-communication TeamSpeak (www.teamspeak.org) is currently testing a version that supports speex codecs. The quality for high bitrates is quite good. BUT, the low-bandwidth speex codecs that are currently used arent very good. What I did to find this out: I comprared a speex AVB with 6.3 KBit/sec (total, overhead for packets and stuff included) and the 6.3 Kbit/sec Celp Codec

I had expected that the default bitrate for the encoder would be the same as setting it to OPUS_AUTO, but I'm getting difference results: >opusenc --comp 4 sample.wav sample.opus Encoding using libopus 1.3-rc2 (audio) ----------------------------------------------------- Input: 8 kHz, 1 channel Output: 1 channel (1 uncoupled) 20ms packets, 25 kbit/s VBR Preskip: 312

Hi, On http://www.speex.org/docs/manual/speex-manual/node11.html#SECTION001140000000000000000 the bitrate for Speex Wideband mode 9 and 10 is 9 34,400 10 42,400 On http://tools.ietf.org/html/draft-ietf-avt-rtp-speex-03 the bitrate for Speex Wideband mode 9 and 10 is 9 34.2 kbit/s 10 42.2 kbit/s I believe the draft contains the right values: E.g. mode 10 Narrowband mode 7 -> 492

Hello all, This is slightly off-topic, but should be of interest to some people on this list. I just released version 0.3.2 of the CELT ultra low-delay audio codec (http://www.celt-codec.org/). CELT is designed to encode high quality speech and music with less than 10 ms delay and at rates starting from around 32 kbit/s. This version is "special" in that it is the basis for some

Hi, I''ve seen some time ago a function which, given a string like "this is a very long string" would return , for example limitin it to 10 chars "this is a..." , but I can''t remember where..... I''ve searched throwth the apis of rails and ruby itself and I can''t find it. Thanks everybody..

The latest revision of the draft RTP Profile is attached for review. This will be submitted to the IETF Audio-Video Transport Working Group for consideration immediately, so if you have any more comments, let us know. In addition, we will be applying for an official MIME type. Note that the AVP code and the MIME type in this latest revision have been changed from "SPX" to

Hi all, Please find below an updated Speex Internet Draft document. It would be good if we could book some time for discussion on Speex at the IETF meeting in Vienna (scheduled for 14th July). The cutoff for submission is 9:00am EDT, (GMT -04:00), 30th June. Comments and feedback welcomed! Regards Phil

On Tue, Dec 17, 2002 at 11:55:21PM -0800, Greg Herlein wrote: > If such a thing happens, discussion of the RTP profile draft > would be most welcome - please get responses back to the > list! Now, if this were finalised before the conference then we could do a demo and use it for broadcasting the lectures streams around the world... What is currently the best way of doing this? I'm

Hello ! I use Slackware Linux on a box for routing and SNAT for a small network: |eth0: 80.97.108.1| | | |eth1: 192.168.1.1| ..........| my network (192.168.1.0/24)| I search for a tool show-me on real time the trafic made by all/one IPon the interface eth1, somethings simple ; EX: 192.168.1.10 ........... x kbit/s 192.168.1.11 ........... y kbit/s 192.168.1.12

Hi List, Now I will send to you more specific what I am trying to do. I have one Asterisk Channel where receives Midia Frames in the codecs format: Speex UltraWideBand and Speex NarrowBand. When I use Speex NarrowBand the Asterisk is able to convert this frame to G711. But when I use Speex UltraWideBand the Asterisk don't convert it. Then I need in my Asterisk Channel Source include the Speex

Because a wideband signal has both a narrowband part and a wideband part the first part of the wideband decode is to call the narrowband decode. In the fixed point version the signal generated from the narrowband decode is downshifted at the end. In this same version the wideband then upshifts the signal by the same amount. I would like to do away with the downshift on the narrowband side

>Dear Speex developers >I am going to port Speex on LPC2368 >I tested Speex encoding and the mesurments shows ~40ms cpu time for one >frame >Do you know who ported speex to NXP or other 32bit platform? >Best Regards >Zohar fox I have an own optimisation for Speex for different versions of ARM architecture. Here is Measurements of performance for STM32 72 MHz. 4000