This portion of the RFC is gramatically incorrect and
confusing:
The RTP payload MUST be padded to provide an integer number of
octets as the payload length. These padding bits MUST be all zero.
This padding is only required for the last frame in the packet, and
only to ensure the packet contents ends on an octet boundary.
<p>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
<p>--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'speex-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
Jean-Marc Valin wrote:> AFAIK the padding changed with the latest draft and there's now a > function in speex_bits that does it all for you (and it's also called by > speex_bits_write). What that does is that it inserts a special > terminator, which allows a variable number of frames per packet without > any overhead.Does the stable release support the new draft? Is this the latest draft? http://www.ietf.org/internet-drafts/draft-herlein-speex-rtp-profile-01.txt Thanks, Ben <p> -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> The RTP payload MUST be padded to provide an integer number of > octets as the payload length. These padding bits MUST be all zero. > This padding is only required for the last frame in the packet, and > only to ensure the packet contents ends on an octet boundary.AFAIK the padding changed with the latest draft and there's now a function in speex_bits that does it all for you (and it's also called by speex_bits_write). What that does is that it inserts a special terminator, which allows a variable number of frames per packet without any overhead. Jean-Marc -- Jean-Marc Valin, M.Sc.A., ing. jr. LABORIUS (http://www.gel.usherb.ca/laborius) Université de Sherbrooke, Québec, Canada -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: Ceci est une partie de message numériquement signée. Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20040114/3b357e18/signature-0001.pgp
> This portion of the RFC is gramatically incorrect and > confusing: > > The RTP payload MUST be padded to provide an integer number of > octets as the payload length. These padding bits MUST be all zero. > This padding is only required for the last frame in the packet, and > only to ensure the packet contents ends on an octet boundary.I'm updating the internet draft for the RTP profile, and note your comment... but it looks OK to me, and looks like we need it still. Comments? Keep, drop, change? The example that follows this paragraph seems to make it all clear... Greg --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Le sam 28/02/2004 à 07:05, Greg Herlein a écrit :> > This portion of the RFC is gramatically incorrect and > > confusing: > > > > The RTP payload MUST be padded to provide an integer number of > > octets as the payload length. These padding bits MUST be all zero. > > This padding is only required for the last frame in the packet, and > > only to ensure the packet contents ends on an octet boundary. > > I'm updating the internet draft for the RTP profile, and note > your comment... but it looks OK to me, and looks like we need it > still.Didn't we change that paragraph to "These padding bits MUST be a zero followed by all ones."? Jean-Marc -- Jean-Marc Valin, M.Sc.A., ing. jr. LABORIUS (http://www.gel.usherb.ca/laborius) Université de Sherbrooke, Québec, Canada -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: Ceci est une partie de message numériquement signée. Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20040228/e02b68dc/signature-0001.pgp