SpeexRTP: Difference between revisions
Jump to navigation
Jump to search
m (→Speex over RTP) |
Basilgohar (talk | contribs) m (Reverted edits by Svererenov (talk) to last revision by Saoshyant) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=== Speex over RTP === | === Speex over RTP === | ||
While [[Ogg]] is the native file format for speex data, an RTP encapsulation is a natural fit with the codec's low latency | While [[Ogg]] is the native file format for speex data, an RTP encapsulation is a natural fit with the codec's low latency design. | ||
Fortunately, unlike [[Vorbis]] and [[Theora]], [[Speex]] has no required setup headers, so the application is easy. A [http://speex.org/drafts/draft-herlein-speex-rtp-profile-02.txt draft exists]. It just needs to be reviewed and then taken through the formal ratification process with the IETF. | Fortunately, unlike [[Vorbis]] and [[Theora]], [[Speex]] has no required setup headers, so the application is easy. A [http://speex.org/drafts/draft-herlein-speex-rtp-profile-02.txt draft exists]. It just needs to be reviewed and then taken through the formal ratification process with the IETF. | ||
[[Category:Speex]] | [[Category:Speex]] | ||
Latest revision as of 11:04, 5 December 2012
Speex over RTP
While Ogg is the native file format for speex data, an RTP encapsulation is a natural fit with the codec's low latency design.
Fortunately, unlike Vorbis and Theora, Speex has no required setup headers, so the application is easy. A draft exists. It just needs to be reviewed and then taken through the formal ratification process with the IETF.