[mythtv] devel/rtp: multiple IPTV streams, same port-no

Niels Ole Kirkeby nok at kirkeby.nu
Sun Apr 29 06:51:43 UTC 2012


I believe you miss the point: It is not just a call to setsockopt(). You
can only have one socket for all multicast-streams. Whether you have 1, 4
or 8 iptv-tuners, they should all use the same socket. At least if any of
them might use the same point-no. As for me :-)

I assume this is the case for all multicast-streams. Thus any streams using
the same port-no needs to use the socket and PKTINFO even thou the
functionality is not related.




2012/4/29 Daniel Kristjansson <danielk at cuymedia.net>

> On Sat, 2012-04-28 at 23:09 +0200, Niels Ole Kirkeby wrote:
> > Hi
> >
> > I was trying to figure out why devel/rtp didn't work for me and found
> > a major (if you're struck by it) flaw in the multicast handling in
> > MythTV. The problem is that my provider delivers streams like
> > udp://222.111.222.xx:2000. That is for all streams the port-no is the
> > same. In Linux, basically only the port-no differentiates the various
> > udp-streams. Thus I noticed a strange phenomena in MythTV: two
> > iptv-tuners recording two different streams but all data goes to the
> > first stream !
>
> Just a bug, what you are describing should be handled by the
> setsockopt call on line 225 of iptvstreamhandler.cpp.
>
> -- Daniel
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-dev/attachments/20120429/6dd9261a/attachment.html>


More information about the mythtv-dev mailing list