[vorbis-dev] RFC draft for Vorbis over RTP

Gregory Maxwell greg at motherfish-II.xiph.org
Wed May 26 16:21:29 PDT 2004



On Thu, 27 May 2004, Jack Moffitt wrote:

> > This certainly simplifies things in practice with in-band headers
> > or header request over http. Seems a bit of a wash if there's a separate
> > header stream.
>
> Not really.  If you are multicasting, the extra stream doesn't waste
> bandwidth unless people are pulling on it afaik.  So it's efficient.  On
> unicast, you might as well use a reliable transport since that will be
> faster.
Sort of.. Joining a multicast stream is actually a very expensive process
in any network larger than a subnet.
> So I think the full idea goes something like:
>
> Add a codebook id header to each rtp packet.  This 'id' would be
> incremented each time the source restarted if it had to switch codebooks
> (or if it can't know, increment always).
>
> Vorbis audio is sent as in the draft, or however in an RTP stream by
> itself.
>
> Headers can either be gotten by reliable means (HTTP probably) or from a
> separate header rtp stream, on which the headers are broadcast over and
> over.  For multicast, the separate RTP stream is recommended.  For
> unicast, reliable transport via HTTP is recommended.

It must be possible to dribble out the headers in litttle packets over a
couple of seconds if configured.. Sending the entire headers ever n
seconds as a linerate burst is unacceptable.

--- >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 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.



More information about the Vorbis-dev mailing list