Reply to thread

Message

<blockquote data-quote="Stinky" data-source="post: 134978" data-attributes="member: 13028">Hi guys, sorry for the late replay - I haven't checked the forum in a while.I just replied to framerate via PM, but here's the jist of it:My server listens for MP clients to request a channel (among other things). Once a channel is requested, I use the telnet interface to VLC to create a redirected stream (udp-&gt;rtsp) and then pass the new stream name to the client. I have two NICs in the server with routing tables set up - one to my LAN, one to the IPTV network. I also created my own DB table to hold the mapping between a channel ID (as used in the rest of MP) to a MRL used by my cable provider. Setup is cumberome. I run the MP server setup only to use the DB structures (parts of the client talk directly to the remote DB and not to the server) and then disable the MP server in favor of my homebrew one. The routing tables were easy to set up, the DB table data was a pain to capture, clean and format. A new DB table needs to be created as well but this would be easy to script. I like this solution since I still get to use the EPG and it looks just like the &quot;stock&quot; version of MP. WAF is high on this one.At this point, there's two glitches: 1) my server does not import EPG data. I just re-enable the MP version every now and then.2) VLC takes a second to connect to the stream and start pumping it out. If the client tries to connect to it too quickly, VLC goes to 100% CPU. I bumped to a 3GHz CPU but the real solution lies in properly implementing threading in the server I wrote.I haven't even looked at recording functionality but I don't see it as being real difficult. Scheduling conflicts would be non-existant and the only limitation on how many channels could be streaming at the same time is your CPU and NIC bandwidth. This is written in Delphi, BTW.</blockquote>

[QUOTE="Stinky, post: 134978, member: 13028"] Hi guys, sorry for the late replay - I haven't checked the forum in a while. I just replied to framerate via PM, but here's the jist of it: My server listens for MP clients to request a channel (among other things). Once a channel is requested, I use the telnet interface to VLC to create a redirected stream (udp->rtsp) and then pass the new stream name to the client. I have two NICs in the server with routing tables set up - one to my LAN, one to the IPTV network. I also created my own DB table to hold the mapping between a channel ID (as used in the rest of MP) to a MRL used by my cable provider. Setup is cumberome. I run the MP server setup only to use the DB structures (parts of the client talk directly to the remote DB and not to the server) and then disable the MP server in favor of my homebrew one. The routing tables were easy to set up, the DB table data was a pain to capture, clean and format. A new DB table needs to be created as well but this would be easy to script. I like this solution since I still get to use the EPG and it looks just like the "stock" version of MP. WAF is high on this one. At this point, there's two glitches: 1) my server does not import EPG data. I just re-enable the MP version every now and then. 2) VLC takes a second to connect to the stream and start pumping it out. If the client tries to connect to it too quickly, VLC goes to 100% CPU. I bumped to a 3GHz CPU but the real solution lies in properly implementing threading in the server I wrote. I haven't even looked at recording functionality but I don't see it as being real difficult. Scheduling conflicts would be non-existant and the only limitation on how many channels could be streaming at the same time is your CPU and NIC bandwidth. This is written in Delphi, BTW. [/QUOTE]

Verification