Hi,
yes, you are right. If the sequence number is continous across all streams it
would be hard to find lost frames and so on. But I think demuxing only based on
the SSRC wouldn't solve the problem with the sequence numbers at all. I think
it would be necessary to give each RTP stream its own continous sequence
numbering.
BTW, the system where I should integrate the new conferencing software is using
a proprietary streaming protocol based on RTP. And it uses only one port, one
SSRC but different sequence numbers for the audio and video streams.
The transmitter part of farsight looks quite complicated. So, I'm currently
thinking about using the RtpBin element (and the others) directly.
Cheers,
Andreas
-----Ursprüngliche Nachricht-----
Von: Olivier Crête [mailto:olivier.cr...@collabora.com]
Gesendet: Fr 07.10.2011 15:46
An: Auer, Andreas
Cc: farsight-devel@lists.sourceforge.net
Betreff: Re: AW: [Farsight-devel] Receiving audio and video streams on the same
port
Hi,
On Fri, 2011-10-07 at 09:27 +0200, Auer, Andreas wrote:
> thanks for the answer. Wouldn't it be possible to demux the RTP
> streams
> with the payload type of the RTP header? I think there is also this
> rtpptdemux
> element.
No, multiplexing baed on the payload type is a terrible idea.. Because
the sequence numbers are continous across all payload types, so it makes
it very painful to find discontinuities after you've split it.
The better way to multiplex is by SSRC, but that mean you must decide
the SSRCs in advance and negotiate them, which standard SIP doesn't do.
> Just to be sure, only the current transmitter architecture prevents
> the use
> of the same port!? I guess, the RTP elements (bin, session,
> source, ...) would
> allow the use of the same UDP port if the RTP streams are demuxed
> before they
> are sent to the gstrtpbin. Is this correct?
Yes, if you do it correctly, you only need to change the transmitter
architecture to be able to demultiplex the stream before feeding it into
rtpbin.
Olivier
> -----Ursprüngliche Nachricht-----
> Von: Olivier Crête [mailto:olivier.cr...@collabora.com]
> Gesendet: Do 06.10.2011 16:59
> An: Auer, Andreas
> Cc: farsight-devel@lists.sourceforge.net
> Betreff: Re: [Farsight-devel] Receiving audio and video streams on the
> same port
>
> Hi,
>
> On Thu, 2011-10-06 at 13:41 +0200, Auer, Andreas wrote:
> > Hi,
> >
> > Right now, I created an app which streams a video and receives one
> RTP
> > video stream. Now, I want
> > to extend the app and add an audio stream (sending and receiving).
> But
> > I have to receive the audio
> > stream on the same UDP port as the video because I want to integrate
> > the system into an existing
> > one.
> > Is it possible with Farsight2 to receive audio and video streams on
> > the same UDP port?
>
> Short answer: currently, no
>
> Longer answer: How do you demux the audio and video if they are on the
> same port? Make it work would mean changing the transmitter
> architecture
> a bit, but it isn't impossible to do. And we may have to do it anyway
> because of WebRTC.
>
> --
> Olivier Crête
> olivier.cr...@collabora.com
>
>
>
--
Olivier Crête
olivier.cr...@collabora.com
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Farsight-devel mailing list
Farsight-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/farsight-devel
