[Feature] Receive local http streams with PCH C200

[cnow]

Hello folks,
My request is: I want to stream content from my Dreambox 800 (or other sources) in my private network to PCH C200. The PCH is in my home cinema and I unfortunately don't have TV-reception there but LAN.

From my PCH I try to access the http-stream via link: http://192.168.0.15:8001/1:0:1:336:1C2D:...000:0:0:0: but it doesn't work and I get the well known "Could not play" error. Btw. I'm using the current firmware from june 3rd '11. I read several threads and hundreds of posts regarding this topic but without a solution.

Obviously there are a few limitations with the PCH, which cause my problem:

• PCH cannot handle streams without a given length
• PCH cannot connect to streams, where the source is in the same private subnet (e.g. 192.168.x.x)
• PCH is unable to handle a http-port around 80xx
  

Please note that these limitations are only collected informations out of other threads. Maybe these are the cause for my problem - maybe not.
I kindly ask to implement this feature as this was one of the main reasons (not the only one :-) ) to buy this unit. PCH A100 was able to do this...so I thought C200 - as the bigger brother - of course can handle streams from my STB. :-(

Links regarding this topic:
http://www.networkedmediatank.com/showth...?tid=49028
http://www.networkedmediatank.com/showth...?tid=37577
http://www.networkedmediatank.com/showth...?tid=30622
http://www.networkedmediatank.com/showth...?tid=29558
http://www.networkedmediatank.com/showth...?tid=29292

best regards,
cnow

[accident]

you gave all this information except how are you starting the stream.

[cnow]

(06-10-2011 12:25 PM)accident Wrote:  you gave all this information except how are you starting the stream.

Hello accident,
thanks for your reply! I created a new webservice @PCH with the url to a special website of my dreambox. I use a Dreambox plugin called "Stream-Webpage-Generator" http://]http://koti.mbnet.fi/devnull/suo...eamwebpage which generates a webpage on my Dreambox with the urls needed to stream tv channels. (url format for each channel is like the example in my first post)
As this showed the "Cannot play" message I tried to enter the direct url to one tv channel. But this also did'nt work.

I have several other units here (notebook, Android phone/tablet) which can receive streams from my Dreambox without problem so I think the problem is not related to the Dreambox itself?

best regards,
cnow

[john_C200]

I think this shold be dealt with as a bug rather than a features request (particularly the subnet issue). If there are no objections from the mods, I will add it to Mantis - AFAIK it hasn't been covered yet.

Should be a strong case thanks to cnow's efforts in collating the relevant posts.

[accident]

The 200 series has never been great at mpeg ps streams but it should at least try to play it.. There are multiple "players" in the unit so if it's going to the wrong one then that could be the issue. This shouldn't hurt any other devices but generally a tag also has an attribute of vod="" in it for non-folder rips..

This is generally what a gaya link to a single file or http stream would look like..

Code:

<a href="http://host:port/restofurl" vod="">play stream</a>

---

(06-10-2011 01:01 PM)john_C200 Wrote:  I think this shold be dealt with as a bug rather than a features request (particularly the subnet issue). If there are no objections from the mods, I will add it to Mantis - AFAIK it hasn't been covered yet.

Don't bother with mantis, there is no bug here. (although there are quirks with mpeg ps streams. myihome, llink, dnla, upnp, playon, etc etc etc are all examples of working local subnet http streaming

[emveepee]

I've reported (not to mantis though, since they aren't true bugs) a few quirks with http streaming on the NMT's, mostly related to content that is growing. To make it work, I feel the http server needs to be NMT aware and not report short Content-Length, and it should always return full buffers. Also the initial reads must be very careful to to fill the pre-buffer, since it can treat 0 byte reads during the the pre-buffering as end-of-file.

Martin

[beerw0lf]

I've had a similar http-streaming problem with audio. On my network I have a MPD-server, which is set to stream music over http-stream on private network: http://192.168.1.1:8888. Stream is OGG-encoded, but I don't think thats the problem since I can play OGG-files without any problems.

I've also tried to crawl through a ton of forum posts. I thought my problem was with the "same subnet" issue. Yesterday I moved the streaming server to another network (172.16.1.1) and had a router between the two networks. My config was as follows: PCH on 192.168.1.0/24, PC also on 192.168.1.0/24 and the streaming server on 172.16.1.0/24. I was able to listen the stream from my PC client, but not from PCH. I didn't know there was a port issue also. I will try a different port setting in my server today.

To start the stream I've tried a manual netradio setting and a static html file, with a link play stream. So far I've been unable to listen my local network radio stream, which is a huge disappointment.

[doomsword65]

It would be nice to have more information about what is (or isn't) supported by the c-200 concerning to local streaming. I tried (without success) to stream different video streams from VLC in my local subnet without success. I tried different containers, different video/audio profiles, many different ports but I had only failures: the player seems to connect but after 15-20 seconds it disconnects. I used a HTTP stream.

[accident]

So the general theme here seems to be unlimited size live streams, video or audio... Has anyone tried it using another protocol? IIRC rtsp and mms is also supported but don't quote me on that and I'm not sure if the apps your using support that. also perhaps the upnp:// which should run it as http might be more friendly.. (assuming it supports that also)..

[pchuser_rf]

Quote:Hi! I come again with news. I just now use sniffer for a get talking C200 with TVersity....
In first C200 send "HEAD" request... and TVersity just send metadata of http stream.
I think it's just a test of stream.
In second C200 send "GET" request... and now TVersity send stream...

Question to a Sybas: It is possible to force C200 to send GET-request without HEAD-request?

Related Thread

http://www.networkedmediatank.com/showth...ight=udpxy

[cnow]

Thanks pchuser_rf!
I already read this thread but without understanding the technical background e.g. what is udpxy and how to use this.
Maybe this helps to narrow down the problem.
Actually I try to grab some network specialist in order to configure my router to route between two subnets. This was one of the ideas I got from one of the other threads. Just trying...
I get the impression that I have a powerfull device with pulled handbrake...
best regards,
cnow

[leons]

I'm waiting sice c 200 came out for udpxy, but it's too loong. I reed same things in forum but noting hapend.
I will wait for c 300.

[Locosam]

*bump*
Anyone got the zap stream from Dreambox to work with the c-200?
I have read tons of links, but nothing seems to be working.
Ive been trying to solve this sh*t for a few days now..

[pacha2]

I can stream from the Dreambox to the popcorn using the streampage plugin mentioned above by cnow which generates a new page for the PCH to stream from.

I'm using a DM800 with the latest version enigma2-plugin-extensions-streamwebpage_0.0.3-r3_all.ipk streaming to an A110.

It does not seem to support zapping but will stream the current channel by viewed.

[sugatam]

(04-29-2012 04:39 PM)pacha2 Wrote:  I can stream from the Dreambox to the popcorn using the streampage plugin mentioned above by cnow which generates a new page for the PCH to stream from.

I'm using a DM800 with the latest version enigma2-plugin-extensions-streamwebpage_0.0.3-r3_all.ipk streaming to an A110.

It does not seem to support zapping but will stream the current channel by viewed.

Are you streaming to the 200 series? The whole issue is around how the 200 series treats streams without a Content-Length header, and there was never a problem with the 100 series. And given how many different times it has been raised over the last 2.5 years, I very much doubt if it'll ever be fixed