[vlc-devel] [PATCH] Merge VoD module into RTP stream output module

David Glaude david.glaude at gmail.com
Sat Oct 30 16:32:57 CEST 2010


Le 30 octobre 2010 10:27, Rémi Denis-Courmont <remi at remlab.net> a écrit :

> Le samedi 30 octobre 2010 09:00:29 Pierre Ynard, vous avez écrit :
> > > This is a silly problem. Payload types are scoped to the RTP session
> > > / the SDP m-line. Since VLC never streams more than one payload
> > > format per RTP stream, there is no risk of conflict. We might as well
> > > hard-code value 96 for all dynamic payload types.
> >
> > We could also implement streaming several payload types in the same RTP
> > session,
>
> Yes, but that's rarely useful. First, the design of RTP implicitly limits
> this
> to payload types with equal timestamp frequency. Otherwise delay jitter
> computations and synchronization would go crazy. Second, I have to expect
> many
> receivers will fail miserably, including current VLC.
>

> that would provide an alternative to TS muxing in order to
> > stream without needing SDP.
>
> You are not supposed to multiplex concurrent streams on the same RTP
> session.
>

I second this...

The whole point in RTSP+RTP is that you use RTSP to gather information about
various "uniplex" concurrent stream describe into an SDP format and then
make as many individual RTP connection for each stream (audio, video, ...).

There is however one well known multiplexing in use and documented that VLC
support on the client side: rtsp-over-http also known as QT http fallback.
Basically it take a single TCP connection for control and data and it
multiplex the stream on this connection. There is a trick with a POST and a
GET that are link together to make it work. Unfortunately some (but not all)
proxy (I mean http proxy) do not play nicely with that way of streaming.

I don't know if it is relevant to your work on the VoD module... but it is
definitively something that lack inside VLC to make it look like a real
Streaming Server (such as Darwin Streaming Server) and have a chance to be
access by user behind NAT or Firewall that are not RTP/UDP friendly.

David Glaude
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20101030/55b5f33c/attachment.html>


More information about the vlc-devel mailing list