Umm.. .hahaha, as if a commercial company can record FTA TV, and sell it to people, who are you kidding really if you think there is some eutopia where that would be possible ??? :P
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: farbar1 on April 13, 2011, 07:56:53 AMThis time of year it is because of the dst transition.Thanks to most pvrs being too stupid to add the correct gmt offset to the ice utc data, what the pvr reports back to Ice won't match what its really meant to record, so ice throws up the exclamation as it can't find the timers it asked to set when the pvr reports back next.
I'd like to understand why this happens as well but there has not been a lot of response that I can see. Does nobody know?
Quote from: frankonthenet on April 04, 2011, 03:19:46 PMtry creating a second device and select that one instead. Make sure you don't have duplicate lcns, make sure your clock including timezone etc are correct, make sure in your network that there is no potential of an ip clash by using dhcp or making sure all fixed ip addresses are unique.
Thanks for the assistance.
Device is set and same on both IceTV and PVR.
generic channel/time names.
Any other suggestions?
Quote from: mich@el on March 31, 2011, 08:06:33 AMThe duplicates I am referring to are not at ICE, they are on your PVR (if you receive two broadcasts of the same or overlapping channels for example, and end up with two ABC2 (LCN22) for example, or, in the case of newer firmware, an LCN22 and an LCN350+ both showing the same thing).
7. On the IceTV site, confirmed that there were no duplicate LCN's