Re: [AVT] "RTP Payload format for uncompressed video" with ancillary data

[Randell Jesup <rjesup at wgate.com>]

Alejandro Cabrera Obed <aco1967 at gmail.com> writes:
>I've read the past mail about "RTP payload format for uncompressed
>video" as a proposed standard. I'm studying the way to transmit HDTV
>video uncompressed using this RFC, but I know that for the moment it´s
>not possible to transmit both audio and video data with this RFC.
>
>If I read this paragraph from the RFC: "In instances where ancillary
>data is being transmitted the sender and receiver can disambiguate 
>between ancillary and video data via scan line numbers. That is, the 
>ancillary data will use scan line numbers that are not within the
>scope of the  video frame.", I ask you:
>
>Is it possible to consider the audio data from the HDTV standard as
>"ancillary data" and so transmit also the audio within the RTP Payload
>format for uncompressed video with no synchronization problems with
>the video data ???

        This is an uncompressed video stream.  RTP with multiple types of
media is normally handled by sending multiple streams, and synchronizing
via RTCP and timestamps.  If you want to send an MPEG2 transport stream,
that's a different beast.  If you want to define an "uncompressed video
plus audio" streamtype, and an RTP packetization for it, you're free to
do so - though most other people probably don't see the need for it.

Ancillary data is typically stuff like close-captioning data, etc.

-- 
Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team
rjesup at wgate.com


_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt