search for: rfc5574

Hi everyone, After years of effort, the Speex RTP payload format is now approved as an RFC: http://www.rfc-editor.org/rfc/rfc5574.txt Many thanks to everyone who participated. Enjoy! Jean-Marc

Hi everyone, After years of effort, the Speex RTP payload format is now approved as an RFC: http://www.rfc-editor.org/rfc/rfc5574.txt Many thanks to everyone who participated. Enjoy! Jean-Marc

...ishsound.git;a=blob;f=src/libfishsound/speex.c;h=ac435cba37354d85c2852ce4c7c6305490c0d585;hb=HEAD#l342 but the number of frames in a packet is up to your application. For an Ogg stream it will be a field in the speex_header, for RTP using SDP it is calculated from ptime according to section 5.6 of RFC5574: http://tools.ietf.org/rfc/rfc5574.txt Without SDP, section 3.5 states: "The Speex decoder [SPEEX] can detect the bit-rate from the payload and is responsible for detecting the 20 msec boundaries between each frame." but I don't know how that translates into libspeex calls....

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 15/04/2010 01:30, Conrad Parker wrote: > >> But how can I know the size of each speex frame into a multiframe payload? > > use speex_bit_read_from() just once on the packet, then call > speex_decode() once for each frame. > > Conrad. Thanks for the reply, Conrad. What is not clear for me (and I didn't found it on the

I need to stream speex-encoded audio over RTP, which doesn't seem to be standardized yet, so I'm gonna roll my own code. I control both the sending and receiving sides, so I can pretty much do what I want. I want each packet to contain 20ms worth of audio (sampled at 8KHz), and I'm encoding using a constant bit rate and quality:6. Q: how do I determine how many bytes of data go into

Jeff, RFC-5574 is standards-track: http://tools.ietf.org/html/rfc5574 so, while it's not an approved standard, it's more standardized than a lot of interoperable traffic on the internets these days. The RFC specifies packetization guidelines, which is basically that you put one or more frames in a packet, and then pad the rest with 0 bits until you have a...

...that shows how many bytes/bits of data >are produced by the speex encoding process for a given amount of time >sampling rate and quality setting? > > >On 11/01/2010 09:41 AM, Steve Kann wrote: >> Jeff, >> >> RFC-5574 is standards-track: http://tools.ietf.org/html/rfc5574 so, >> while it's not an approved standard, it's more standardized than a lot >>of >> interoperable traffic on the internets these days. >> >> The RFC specifies packetization guidelines, which is basically that >>you >> put one or more frames in...

...the speex encoding process for a given amount of time >>> sampling rate and quality setting? >>> >>> >>> On 11/01/2010 09:41 AM, Steve Kann wrote: >>>> Jeff, >>>> >>>> RFC-5574 is standards-track: http://tools.ietf.org/html/rfc5574 >>>>so, >>>> while it's not an approved standard, it's more standardized than a lot >>>> of >>>> interoperable traffic on the internets these days. >>>> >>>> The RFC specifies packetization guidelines, which is basic...

.... Is there a document anywhere that shows how many bytes/bits of data are produced by the speex encoding process for a given amount of time sampling rate and quality setting? On 11/01/2010 09:41 AM, Steve Kann wrote: > Jeff, > > RFC-5574 is standards-track: http://tools.ietf.org/html/rfc5574 so, > while it's not an approved standard, it's more standardized than a lot of > interoperable traffic on the internets these days. > > The RFC specifies packetization guidelines, which is basically that you > put one or more frames in a packet, and then pad the rest with...

...there is: "There are efforts underway to make Speex an IETF-blessed format; A draft of 'RTP Payload Format for the Speex Codec' is available" which has a link to: http://speex.org/docs/drafts/draft-herlein-speex-rtp-profile-02.txt but probably should be: http://tools.ietf.org/html/rfc5574 Thanks, Justin

...ta >> are produced by the speex encoding process for a given amount of time >> sampling rate and quality setting? >> >> >> On 11/01/2010 09:41 AM, Steve Kann wrote: >>> Jeff, >>> >>> RFC-5574 is standards-track: http://tools.ietf.org/html/rfc5574 so, >>> while it's not an approved standard, it's more standardized than a lot >>> of >>> interoperable traffic on the internets these days. >>> >>> The RFC specifies packetization guidelines, which is basically that >>> you >>...

...r a given amount of time >>>> sampling rate and quality setting? >>>> >>>> >>>> On 11/01/2010 09:41 AM, Steve Kann wrote: >>>>> Jeff, >>>>> >>>>> RFC-5574 is standards-track: http://tools.ietf.org/html/rfc5574 >>>>> so, >>>>> while it's not an approved standard, it's more standardized than a lot >>>>> of >>>>> interoperable traffic on the internets these days. >>>>> >>>>> The RFC specifies packetization...