[mythtv] CRCIpNetworkRecorder questions
anaerin at gmail.com
Mon Jul 31 17:18:35 UTC 2006
On 7/31/06, Steve Daniels <steve.p.daniels at googlemail.com> wrote:
> > -----Original Message-----
> > From: mythtv-dev-bounces at mythtv.org [mailto:mythtv-dev-bounces at mythtv.org]
> > On Behalf Of Mironov M.S.
> > Sent: 31 July 2006 18:00
> > To: Development of mythtv
> > Subject: [mythtv] CRCIpNetworkRecorder questions
> > Hi All!
> > My provider use multicast UDP MPEG2-TS streams. With
> > CRCIpNetworkRecorder I can receive this stream using URL like this
> > udp://188.8.131.52:5500?multicast=1
> > But I must use one card for one channel. It is not comfortably. With my
> > provider I can view only one channel at one time (bandwidth limit). So
> > for me best solution is use one "card" that can switch multicast streams.
> > I see 2 variants:
> > 1. Add support for individual URL for channels to CRCIpNetworkRecorder
> > (e.g. add CRCIpNetworkChannel class for support channel switching and
> > modify channel editor)
> > 2. Create new receiver based on CRCIpNetworkRecorder code
> > What is the best solution?
> I very, very much like the first idea :-)
As do I.
And it'd then be a "Trivial" matter to create a SAP/SDP listener to
auto-populate the channel tables (In a similar way that the EIT
scanner does with EPG information) and have a full(ish) IPTV reciever
I guess the next question would would happen with multiple "cards". Do
they all have independant "channel lists"? If so, could you have one
"Card" listening on one interface, and one on another (Say card 0 on
eth0, card 1 on eth1, card 2 on wlan0 for example)? And what about
sharing channel lists for people who DO have the bandwidth to record
more than one stream?
Then all we'd need is RTP/RTCP for Video-On-Demand and we'd be all set. :)
Robert "Anaerin" Johnston
More information about the mythtv-dev