[marc.bau]

If wlan is not the best or the epg download is slow/hang on bad wlan the raspbmc stops responding. I'm sure this is a bug of pvr as it does not recover at all and seems not having any timeouts. This also happens if you play a tv channel, stop and switch to a different channel. In this case the raspbmc often stops responding. I often waited 20minutes and powecycled it than.

This is not the way how this should work.

[krustyreturns]

20 minutes, that sucks all right. For all your threads, can you provide some background info: How many channels are you trying to download data for, and how many days of data did you set in xbmc for the Epg?

[marc.bau]

I tested with 3 and 14 days. I prefer to use 14 days :-)

I'm not sure how many channels will be synced... My media center lists 965 channels. In the serverwmc I have disabled all encrypted channels... So it should be less, but still a lot of channels. But they are not changing... Caching and hidden background update can solve all these issues. :-)

[krustyreturns]

If you look at the status screen of serverwmc, it will tell you how many channels you have transferred to the pi, and how many programs (900 channels x 14 days) it transferred.

[marc.bau]

1000 channels, 600 recording and 14 days epg should work, isn't it? :-)

Why is there no timeout on downloading channels, epg and recordings - if network is weak - raspbmc locks up completly. Can you add a timeout for this, please?

[Dilligaf]

Do you actually receive all 900 channels? WMC>Settings>TV>Guide>Edit Channels If you click on Auto Select WMC will attempt to tune all guide channels and uncheck the ones you don't receive, it will take a while.

[nickr]

If wlan is not the best or the epg download is slow/hang on bad wlan the raspbmc stops responding. I'm sure this is a bug of pvr as it does not recover at all and seems not having any timeouts. This also happens if you play a tv channel, stop and switch to a different channel. In this case the raspbmc often stops responding. I often waited 20minutes and powecycled it than.

This is not the way how this should work.

This is the third goddamned thread you have posted this in.

[marc.bau]

Well, 3 independend issues. Topic is clear.

[krustyreturns]

1000 channels, 600 recording and 14 days epg should work, isn't it? :-)

Why is there no timeout on downloading channels, epg and recordings - if network is weak - raspbmc locks up completly. Can you add a timeout for this, please?

Most people wouldn't try this above even with a strong internet connection, and a much more powerful computer than a pi. I salute your determination though . If you want this timeout enforced you need to take this to the pvr development forum, the addon cannot control this.

I wonder why a timeout would be better than just limiting what the pi imports though.

[scarecrow420]

Yeah at least if you limited it to the channels you might actually watch, you would have something working. If it times out while loading then you would have nothing? Or if you wanted it so that when it times out, you have however much it managed to get loaded by then, then yeah why not just configure WMC to hide channels in the first place then you dont have a varying number of loaded channels based on how much it got done in each refresh before it hit the timeout!

[marc.bau]

Timeout should not break a well running download. It should timeout if connection get's broken and connection to backend is no longer possible. This makes all stuck today. I never said i'd like to download only 10%.

The root cause is an unhandled exception, a broken network connection. There are other places that work well this way and show you a timeout popup message. e.g. Mkv streaming has shown me this at least once, when i rebooted the wlan switch.

[scarecrow420]

It still sounds like you would have a pretty unworklable situation if it pops up time outs and retries etc. You still dont have a quick and seamless ability to watch TV. Have you tried a wired network connection, to see how fast you might get things? How many of these 1000 channels do you actually want to be able to view in XBMC or did you ever view in WMC? As we already mentioned, your setup (channels etc) is one of the most extreme we've heard of, so given that, why are you trying to run things on one of the lowest power devices that supports XBMC and over a seemingly subpar wireless network as well?

[marc.bau]

Per opdenkamp the hang is not handled properly by the pvr addon and therefore a bug in wmc addon. See http://forum.xbmc.org/showthread.php?tid=183391.

Please ask him how this need to be handled if you have questions. He looks like one of the maintainers of pvr core if I'm not totally wrong.

(2014-01-14 22:38)marc.bau Wrote:
4. If network connection to backend get's broken while downloading - xbmc gets stuck. You cannot reboot raspbmc in this case. As example I waited 30 minutes and then powercycled the raspi as it stopped somewhere in between channels or epg or recordings. I was made to do this this very very often as the nano wlan stick was not the best idea here (weak connection).

(2014-01-15 10:58)opdenkamp Wrote:
"This situation is not propperly handled by xbmc if it comes to live tv. If network get's broken while viewing a movie I get a timeout message box. I expect the same here.
this isn't handled properly by the add-on that you're using"

[scarecrow420]

can you please post a debug XBMC log and fresh ServerWMC log showing the problem to pastebin and update here with the links? also make sure you provide commentary on what actions you did and at what timestamps.

Have you tried an alternative network connection?