Lines Matching full:vorbis
12 RTP Payload Format for Vorbis Encoded Audio
24 This document describes an RTP payload format for transporting Vorbis
26 Vorbis data and the delivery mechanisms for the decoder probability
31 details necessary for the use of Vorbis with the Session Description
61 RFC 5215 Vorbis RTP Payload Format August 2008
81 5.1. Example Fragmented Vorbis Packet . . . . . . . . . . . . . 15
118 RFC 5215 Vorbis RTP Payload Format August 2008
123 Vorbis is a general purpose perceptual audio codec intended to allow
127 in the same league as MPEG-4 AAC. Vorbis is also intended for lower
133 Vorbis encoded audio is generally encapsulated within an Ogg format
136 Vorbis packets are used in the payload.
159 For RTP-based transport of Vorbis-encoded audio, the standard RTP
161 data. The payload headers are used to associate the Vorbis data with
163 following packet contains fragmented Vorbis data and/or the number of
164 whole Vorbis data frames. The payload data contains the raw Vorbis
165 bitstream information. There are 3 types of Vorbis data; an RTP
175 RFC 5215 Vorbis RTP Payload Format August 2008
201 details). For Vorbis RTP, the following values are used.
224 to Section 4.1 of [VORBIS-SPEC-REF].
232 RFC 5215 Vorbis RTP Payload Format August 2008
239 SHOULD be chosen that designates the payload as Vorbis.
250 first Vorbis packet in the RTP payload. The clock frequency MUST be
275 This 24-bit field is used to associate the Vorbis data to a decoding
289 RFC 5215 Vorbis RTP Payload Format August 2008
302 Vorbis Data Type (VDT): 2 bits
304 This field specifies the kind of Vorbis data stored in this RTP
305 packet. There are currently three different types of Vorbis
306 payloads. Each packet MUST contain only a single type of Vorbis
310 0 = Raw Vorbis payload
312 1 = Vorbis Packed Configuration payload
314 2 = Legacy Vorbis Comment payload
321 payload. This provides for a maximum number of 15 Vorbis packets in
327 Raw Vorbis packets are currently unbounded in length; application
328 profiles will likely define a practical limit. Typical Vorbis packet
333 fragmentation, the Vorbis data packet size SHOULD be kept
346 RFC 5215 Vorbis RTP Payload Format August 2008
352 | length | vorbis packet data ..
357 Each Vorbis payload packet starts with a two octet length header,
359 payload, and is followed by the raw Vorbis data padded to the nearest
360 byte boundary, as explained by the Vorbis I Specification
361 [VORBIS-SPEC-REF]. The length value is stored as a network byte
364 For payloads that consist of multiple Vorbis packets, the payload
366 each of the Vorbis packets in the payload.
368 The Vorbis packet length header is the length of the Vorbis data
371 The payload packing of the Vorbis data packets MUST follow the
372 guidelines set out in [RFC3551], where the oldest Vorbis packet
373 occurs immediately after the RTP packet header. Subsequent Vorbis
376 Audio channel mapping is in accordance with the Vorbis I
377 Specification [VORBIS-SPEC-REF].
403 RFC 5215 Vorbis RTP Payload Format August 2008
408 Here is an example RTP payload containing two Vorbis packets.
425 | length | vorbis data ..
427 .. vorbis data |
429 | length | next vorbis packet data ..
431 .. vorbis data ..
433 .. vorbis data |
436 Figure 4: Example Raw Vorbis Packet
440 number of Vorbis frames set to 2. Each of the Vorbis data frames is
447 Unlike other mainstream audio codecs, Vorbis has no statically
460 RFC 5215 Vorbis RTP Payload Format August 2008
464 a Vorbis stream, and are included as special "header" packets at the
465 start of the compressed data. In addition, the Vorbis I
466 specification [VORBIS-SPEC-REF] requires the presence of a comment
498 information, it MUST NOT decode the raw associated Vorbis data until
504 the packet type bits set to match the Vorbis Data Type. Clients MUST
517 RFC 5215 Vorbis RTP Payload Format August 2008
522 A Vorbis Packed Configuration is indicated with the Vorbis Data Type
523 field set to 1. Of the three headers defined in the Vorbis I
524 specification [VORBIS-SPEC-REF], the Identification and the Setup
547 [VORBIS-SPEC-REF]: Identification, Comment, Setup.
574 RFC 5215 Vorbis RTP Payload Format August 2008
631 RFC 5215 Vorbis RTP Payload Format August 2008
641 As mentioned above, the RECOMMENDED delivery vector for Vorbis
648 following shows the Packed header payload for each chained Vorbis
688 RFC 5215 Vorbis RTP Payload Format August 2008
723 Unlike the loss of raw Vorbis payload data, loss of a configuration
733 Vorbis Data Type flag set to 2 indicates that the packet contains the
738 in the Vorbis I Specification [VORBIS-SPEC-REF].
745 RFC 5215 Vorbis RTP Payload Format August 2008
777 Each RTP payload contains either one Vorbis packet fragment or an
778 integer number of complete Vorbis packets (up to a maximum of 15
781 Any Vorbis data packet that is less than path MTU SHOULD be bundled
782 in the RTP payload with as many Vorbis packets as will fit, up to a
792 The RTP payload containing the last fragment of the Vorbis packet
802 RFC 5215 Vorbis RTP Payload Format August 2008
809 5.1. Example Fragmented Vorbis Packet
811 Here is an example of a fragmented Vorbis packet split over three RTP
813 the 4-octet Vorbis headers.
832 | length | vorbis data ..
834 .. vorbis data |
841 packets field is set to 0, and as the payload is raw Vorbis data, the
859 RFC 5215 Vorbis RTP Payload Format August 2008
879 | length | vorbis data ..
881 .. vorbis data |
887 is set to 0. For large Vorbis fragments, there can be several of
916 RFC 5215 Vorbis RTP Payload Format August 2008
936 | length | vorbis data ..
938 .. vorbis data |
943 This is the last Vorbis fragment payload. The Fragment type is set
950 As there is no error correction within the Vorbis stream, packet loss
952 fragmented Vorbis packets as the client will have to cope with the
954 client MUST discard all the remaining Vorbis fragments and decode the
955 incomplete packet. If we use the fragmented Vorbis packet example
961 kept and the incomplete Vorbis packet decoded.
973 RFC 5215 Vorbis RTP Payload Format August 2008
980 Subtype name: vorbis
1011 Ogg Vorbis I specification: Codec setup and packet decode.
1030 RFC 5215 Vorbis RTP Payload Format August 2008
1062 Subtype name: vorbis-config
1087 RFC 5215 Vorbis RTP Payload Format August 2008
1100 Vorbis encoded audio, configuration data
1144 RFC 5215 Vorbis RTP Payload Format August 2008
1149 o The subtype name ("vorbis") goes in SDP "a=rtpmap" as the encoding
1160 If the stream comprises chained Vorbis files and all of them are
1166 in the rtpmap attribute SHOULD match the current Vorbis stream or
1185 a=rtpmap:98 vorbis/44100/2
1201 RFC 5215 Vorbis RTP Payload Format August 2008
1214 data apply to Vorbis audio over RTP as well. See the RTP
1258 RFC 5215 Vorbis RTP Payload Format August 2008
1292 Moffitt, J., "RTP Payload Format for Vorbis Encoded Audio", February
1295 Kerr, R., "RTP Payload Format for Vorbis Encoded Audio", December
1301 Short, B., "The audio/rtp-vorbis MIME Type", January 2008.
1303 Thanks to the AVT, Vorbis Communities / Xiph.Org Foundation including
1315 Vorbis RTP Payload Format August 2008
1360 [VORBIS-SPEC-REF] "Ogg Vorbis I specification: Codec setup and
1362 http://xiph.org/vorbis/doc/Vorbis_I_spec.html".
1372 RFC 5215 Vorbis RTP Payload Format August 2008
1378 http://vorbis.com/".
1429 RFC 5215 Vorbis RTP Payload Format August 2008
