[xiph-rtp] Re: new RTP development list

[Silvia.Pfeiffer at csiro.au]

Zen,

rtp was designed to transport only one codec's bitstream per rtp stream, so speex+theora would be transmitted on 2 different connections and recombine them at the end via the timestamps.

Yet, recently many codecs have defined rtp payload formats for interleaved data to avoid the difficult task of resynchronisation, e.g. the DV over rtp spec (see http://www.ietf.org/rfc/rfc3189.txt).
These are however fixed interleaved, not possible to dynamically combine on the fly.

That's one of the reasons why we are working on Annodex over rtp to get dynamic interleaved payload formats. We're only at the beginning and I'm not sure what problems we'll run into and if it's possible at all. But it would be nice. :)

Silvia.



-----Original Message-----
From:	xiph-rtp-bounces at xiph.org on behalf of Tor-Einar Jarnbjo
Sent:	Thu 10/21/2004 7:42 PM
To:	illiminable
Cc:	xiph-rtp at xiph.org; Tor-Einar at Jarnbjo.de
Subject:	Re: [xiph-rtp] Re: new RTP development list

Torsdag, 21 oktober 2004, skrev "illiminable" <ogg at illiminable.com>:

>What i don't get is why there is going to be different protocols 
for each 
>codec.. wouldn't a single protocol for all ogg codecs be better ?

There are not different protocols for the different codecs, but there 
are content specific considerations to be taken on how to transport 
data from codec X over RTP. There are also codec specific notations 
on how to embed Vorbis, Theora or Speex in an Ogg stream and what 
is needed is a similar definition on how to embed Vorbis, Theora 
or Speex in RTP packets.

Tor


_______________________________________________
xiph-rtp mailing list
xiph-rtp at xiph.org
http://lists.xiph.org/mailman/listinfo/xiph-rtp