search for: speex_manual

Hi, I've been looking at using speex over RTP. Section 3.3 of draft-ietf-avt-rtp-speex-05 states that: "For the purposes of packetizing the bit stream in RTP, it is only necessary to consider the sequence of bits as output by the Speex encoder [speex_manual], and present the same sequence to the decoder." So, I assume that I just pass the whole contents of the RTP packet (less the RTP header) to the decoder, regardless of whether it contains multiple frames of encoded data. I can then see two alternatives: 1. the decoder decodes all of the dat...

...+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > Figure 1: RTP payload for Speex > > 3.3. Speex payload > > For the purposes of packetizing the bit stream in RTP, it is only > necessary to consider the sequence of bits as output by the Speex > encoder [speex_manual], and present the same sequence to the decoder. > The payload format described here maintains this sequence. > > A typical Speex frame, encoded at the maximum bitrate, is approx. 110 > > > > Herlein, et al. Expires December 7, 2007 [Page 6] >...

...+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: RTP payload for Speex 3.3. Speex payload For the purposes of packetizing the bit stream in RTP, it is only necessary to consider the sequence of bits as output by the Speex encoder [speex_manual], and present the same sequence to the decoder. The payload format described here maintains this sequence. A typical Speex frame, encoded at the maximum bitrate, is approx. 110 Herlein, et al. Expires November 30, 2007 [Page 6] Internet-Draft Spee...

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

...+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: RTP payload for Speex 3.3. Speex payload For the purposes of packetizing the bit stream in RTP, it is only necessary to consider the sequence of bits as output by the Speex encoder [speex_manual], and present the same sequence to the decoder. The payload format described here maintains this sequence. A typical Speex frame, encoded at the maximum bitrate, is approx. 110 Herlein, et al. Expires December 7, 2007 [Page 6] Internet-Draft Spee...

...t : > Hi, > > I've been looking at using speex over RTP. Section 3.3 of > draft-ietf-avt-rtp-speex-05 states that: > > "For the purposes of packetizing the bit stream in RTP, it is only > necessary to consider the sequence of bits as output by the Speex > encoder [speex_manual], and present the same sequence to the decoder." > > So, I assume that I just pass the whole contents of the RTP packet (less > the RTP header) to the decoder, regardless of whether it contains > multiple frames of encoded data. I can then see two alternatives: > > 1. the...

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