[vorbis-dev] RFC draft for Vorbis over RTP

[Monty]

On Thu, May 27, 2004 at 01:17:45AM +0200, 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.
> 
> 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.
> 
> Metadata happens in a separate channel.  I'm not sure whether this is
> something RTCP should be used for (probably not), or if we should just
> make a metadata rtp stream (is there not one of these already?).

This is the original design as jack and I discussed it years ago, BTW.
It's overall the conceptually cleanest and easiest to extend to
unforseen uses in the future.  It's also more complex from a code
standpoint... although once that code is written, likely no more
expensive to use.

Monty
--- >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.