Difference between revisions of "TheoraRTP"

From XiphWiki
Jump to: navigation, search
(just a placeholder; we can crib from vorbis for most things.)
 
(update)
Line 2: Line 2:
  
 
This page maintains design consensus for the RTP payload format for Theora video. This is useful in interactive and multicast streaming.
 
This page maintains design consensus for the RTP payload format for Theora video. This is useful in interactive and multicast streaming.
 +
 +
=== Drafts ===
 +
 +
Current version of the draft is being written using the XML markup defined in [http://xml.resource.org/public/rfc/html/rfc2629.html RFC2629]. Text and HTML versions of the current draft state are available here:
 +
*[http://svn.xiph.org/trunk/theora/doc/draft-barbato-avt-rtp-theora-00.txt draft-barbato-avt-rtp-theora-00.txt]
 +
*[http://svn.xiph.org/trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml draft-barbato-avt-rtp-theora-00.xml]
  
 
=== Issues ===
 
=== Issues ===

Revision as of 08:11, 1 March 2006

Theora over RTP

This page maintains design consensus for the RTP payload format for Theora video. This is useful in interactive and multicast streaming.

Drafts

Current version of the draft is being written using the XML markup defined in RFC2629. Text and HTML versions of the current draft state are available here:

Issues

As with Vorbis, the issue is the decoder setup configuration carried in the bitstream headers which must be transmitted reliably.

We can probably just ignore the keyframe issue and let the client spin until it sees one.

Design

The issues are very similar to Vorbis, so we can probably copy that draft in some detail.

How should timestamps work? Frames like in Ogg? Real time? Some associated audio timebase?