oztoppy Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 3 of 3      Prev   1   2   3
IanL-S

Moderator
Registered:
Posts: 605
Reply with quote  #31 
Yes, I am definitely having network issues that are preventing the TAP initiating. Could be too many switches between the Toppy and the router, or the large number of devices. 

Those of you who have been members of the Forum for a while will recall that I no longer adhere to the adage that "A man cannot have too many Toppys". Then there are the usual smart phones, tablets, notebook computers, desktop computers, smart TVs, Apple TV, Chromecast .....

The good news is that my unique network issues aside (could be a firewall issue) the TAP is quite easy to set up. I am still trying to get it to work on my network. 
0
DeltaMikeCharlie

Mostly Harmless
Registered:
Posts: 249
Reply with quote  #32 
I have been working on timer integration and I thought that I would document what the TAP does with timers.

Firstly, the TAP maintains pre-padding and post-padding configuration settings.  When a new ICE timer arrives, these are added before the actual timer is created.

If creating the new timer would result in a conflict with an existing timer or timers, the TAP will look at all of the fully covered EPG entries and create a merged timer with the pre/post padding applied.

If the conflict occurs with a recurring timer (daily, weekly, etc) then the recurring timer is rolled forward, cloned as a one-time timer and the clone is modified leaving the original recurring timer ready for its next scheduled trigger.

When a programme is deleted on ICE, the TAP will match PVR timers based on channel/time/duration.  If it finds a timer with a single fully covered EPG event, that timer will be deleted.  If, however, a matching timer is found that covers multiple full EPG event, the TAP will chop out the ICE timer from the front/middle/end of the PVR timer.  Padding is added to the remaining fragment(s) and new timers are created.  Recurring timers are rolled forward and cloned here too.

I am now working on communicating timers manually created on the PVR back to ICE so that the user has a full picture of their timer portfolio.  The firmware does not advise when timers are triggered or deleted, so it is a matter of constantly checking for changes in the timer list and then acting on the difference.  Fiddly, but not impossible.

With regards to SmartEPG, the next public version will contain a modification that can understand the padding information of a new ICE timer.  If the EPG changes and SE tries to modify the timer, it will respect the padding that was in place.  iceConnect also tells SE that it is OK to combine timers, so if there is an ICE timer that conflicts with a subsequent SE search, SE should merge the 2 timers.

Thoughts or comments?
0
IanL-S

Moderator
Registered:
Posts: 605
Reply with quote  #33 
The procedures described would work very well for me. I really appreciate the effort you are putting into this project.

Ian
0
davidmorr

Senior Member
Registered:
Posts: 177
Reply with quote  #34 
If only Topfield were an ongoing product and was more reliable, this would be great......
0
davidmorr

Senior Member
Registered:
Posts: 177
Reply with quote  #35 
How is this project going DMC?
0
DeltaMikeCharlie

Mostly Harmless
Registered:
Posts: 249
Reply with quote  #36 
It's going OK.  The TAP is called iceConnect.  It can:
  • Receive EPG data from ICE.
  • Send ICE EPG data to SmartEPG.
  • Receive timer recordings from ICE. (New, Modify, Delete)
  • Send timers created on the PVR to ICE. (New, Modify, Delete)
Timers are not handled 1:1, instead, existing and overlapping timers are detected and merged or split based on the new or updated timers.

This is what SmartEPG looks like with EPG data imported from ICE.  You can see that there is a repeat flag, fields for actors and directors, date produced, series, episode, etc.  With SmartEPG, you can configure it to ignore repeats by setting the string "+repeat:yes" to a value of "-90".

SmartEPG with iceConnect.jpg 
SmartEPG with iceConnect No Repeats.jpg 
The same extra information is also available with the native firmware EPG.

PVR & iceConnect.jpg 
Here are the timers listings.  All of these timers were created on the PVR and sent to ICE.  It's not shown here, but I did some integration work with SmartEPG and timers created in ICE show a special icon within SmartEPG.  "The Five" have created a special version of SE that works with iceConnect, I'm not sure it that version is publicly available yet.

SmartEPG with iceConnect Timer List.jpg 
ICE TV Timers.png 
I have tested it on two PVRs that I have (2400 & 7160) and it seems to be semi-stable-ish.  I also have one beta tester who has done a lot of stability testing and debugging for me.

There have been a number of unexpected reboots, both on my PVRs and on my tester's PVR.  My reboots have recently stabilised dramatically since I tweaked a single startup parameter.  The stability of my beta tester is still below par, but there is a possibility that this may be due to other factors with their PVR.  Investigations are ongoing in that regard.

I was thinking about opening the testing to a second trusted user, however, several months ago some family issues arose that required me to take a substantial break from iceConnect.  Those issues have only recently been resolved, and I am yet to get fully back into the swing of things.

If anybody has an ICE subscription and a spare PVR and would like to give some testing a go, please let me know via PM.

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.