Main Menu
Menu

Show posts

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 Menu

Messages - tonymy01

#286
IceTV EPG Content / Re: Stargate Universe
December 11, 2009, 01:30:12 PM
What the heck?  What is Ten doing there???  I know this is non-ratings silly season, but I love Futurama & Supernatural, and both of these are 1st runs.
#287
I was getting it for any channel where I setup a timer on the MC instead of Ice Interactive.    It seems the MC still reports the old channel names (despite choosing the ICE versions for each channel) and thus ICE thinks these don't exist in its system. 
#288
Beyonwiz / Re: "65534 minutes to get scheduler tasks"!
December 04, 2009, 11:40:06 AM
LOL.   So I gather the Topfield has enough problems about their interpretation of the protocol and using dodgy coding that they didn't see this issue :-) (I mean, who would use a signed integer for "number of minutes to wait" anyway)?
#289
Quote from: raymondjpg on December 04, 2009, 10:56:45 AM
Granted, but not the daylight savings offset I *thought* you were referring to. On a closer read of your original post I see what you were driving at (I think).
Hehe.  I should probably create a diagram one day to explain it better, I have explained this issue so many times now.   I understand it as I have worked into the nuts/bolts of this for EPG_uploader for the 5K.

Basically, the Topfield doesn't use the TOT table (GMT offset).   So to calculate an offset in manual time, it subracts your PVR date/time that your PVR is set to, from the broadcaster date/time sent in the TDT.    Even though this obtains a "GMT offset", it uses the full date/time of PVR and broadcaster to create what seems like something that should simply be a menu option, like what you get when you use AUTO time.

Regards

#290
It is a time offset problem... just a very *big* offset :-)

Quote from: raymondjpg on December 04, 2009, 09:34:25 AM
While I try to get my head around everything that you have said, the FTA EPG for the WIN channels is definitely *also* giving the incorrect date/time stamp.
This is because the EPG is sent with the correct GMT date/time for each EPG entry, no issues there.   EIT is sent and stored as GMT.   ICE does it this way, the technical standards state it should be this way.    The issue is your broadcaster TDT is stuffed, which has nothing to do with EPG (it is just that the first you witness of this is your EPG looks wrong, because of the stupid Topfield)... also when you channel surf the EPG, stupid Topfield force your PVR to change channels.   Try viewing one channel above/below Nein/Win, hit the red button to view the multi-channel mode, and notice the EPG looks correct for Win... just don't try to highlight the Nein/Win entry and press info, as the stupid Topfield forces the channel change which forces the TDT to be read which forces the dumb offset calculation (I presume you are running manual time?  Auto time doesn't have the stupid offset calculation but you have another issue of your PVR date/time suddenly jumping, which is a tad worse than Win looking wrong!)

Ok, just to clarify one or two more things (now I know what PVR model you have), and a mistake I probably made about ICE timers in my text above.

The ICE EPG and I believe timers are sent in GMT time.    So, if you run AUTO time, the timers will be set for the correct time (as AUTO time uses your menu setup GMT offset to both add to the EPG for display, and add to the timer timestamps for storage of the timers) and EPG will display for the correct time, however of course channel surfing to the dodgy channel will cause your PVR clock to shift (after about 30secs for the 5K, dunno for the 7100).  
If you run MANUAL time, then your PVR clock will be fine, but anything that requires adding offsets won't be fine as the Topfield uses stupid maths to calculate your GMT offset (by subtracting the broadcaster so-called GMT date/timestamp from your PVR manually setup date/timestamp).   Thus if you are on the dodgy channel when your timers come in from ICE, they will likely end up at the wrong date/time!!   (Timers are stored in the PVR in localtime, so the PVR ICE mode will convert the timers sent by ICE to localtime).    So your timers, if they are already in the PVR, will be ok, but any new ones might end up at the wrong time if you are on the dodgy channel at the time and running MANUAL time.

When I say timestamp, I mean date/time btw.

So, even though you think you are safe from dodgy broadcasters by running manual time, due to the stupidity of the algorithm Topfield uses for determining the PVR GMT offset, you will still end up with big troubles!

Regards
#291
ICE doesn't send the date, the broadcaster does.   ICE sends EPG info with GMT timestamps.   For you to view those on the PVR, the PVR adds what it thinks is your GMT offset (i.e. 11hours in daylight savings time), typically at "display" time, and you get your EPG displayed to you in local time.

So to just get this clear in your head, EIT is one thing (EPG) sent from the broadcaster, but there is also TDT & TOT tables sent.   TDT=time & date tables (which are in GMT also) and TOT=Time offset table, which is a table of what your local offset should be from GMT (and the next date that the offset changes, i.e effectively accommodates daylight savings).    Some (many?) PVRs don't use the TOT tables, they use a setup number in the PVR menu for GMT offset.

All ICE software /settings does in a PVR is block the broadcaster EIT (i.e. EPG) and allow this to be loaded up from files on the HDD or an internet connection to ICE instead.

If you have a Topfield, and your broadcaster is sending a very incorrect timestamp, you are going to have a bit of a problem.
Why? Read on-:
1. If you run AUTO time, the PVR gets its time from the broadcaster, and then adds the menu setup GMT offset.   So if you surf to the dodgy channel, within 30secs your PVR will have the wrong time.

2. If you run MANUAL time, the PVR only uses its internal clock, so the dodgy timestamp won't kill your PVR clock... however, here is the catch.   Stupid Topfield decided not to provide a menu option for GMT offset when you use manual time.   So how does your PVR know what to add to the EIT data to display it to you in local time?   The broadcaster timestamp... ouch.    So the PVR subtracts the broadcaster timestamp still from your safe manual time, and obtains a GMT offset based on that maths, adds it to the EIT tables for display to you (so only adds it for display, it doesn't add and store it).    This is why with a Topfield you have the EPG "jittering around" a bit when you channel surf, as they don't even round off the GMT offset calculation to the nearest 30mins!   So if your front panel clock is out by,  say, 1minute, all your EPG will be out by 1minute.   If your front panel clock is perfect, but the broadcaster is out by 10hours (because their work experience kid put the localtime instead of GMT time into the TDT setting in their equipment) then your EPG will be out by 10hours!!

The good thing about point 2 is that at least your timers will fire properly at approx the right time, if you used ICE to set your timers.   If you used your display EPG to set the timers, then of course their start date/time is going to be wrong.   There is a firmware patch mod for the 5K to support channel surfing the EPG without your PIG changing channels (picture in graphic).    If you use this strategy, you could ensure you are on a good channel (not the dodgy Win) before you open the GUIDE to set timers.     

I fixed this issue with 5Ks with the EPG_uploader TAP by blocking the PVR calculation when running manual time and then plonking in a TAP setup offset instead.    But if you have a 7K (not sure about the 2400 series), or don't run EPG_uploader in a 5K, you are at the mercy of the broadcasters whatever time/date setting you have in the PVR!!    You should be hassling Topfield to get their code for MANUAL clock a bit better, to support a proper offset like AUTO time users get.   Then both your front panel clock is safe (i.e. the main PVR clock) and the display of the EPG will be accurate.    If enough people hassle the hell out of topfield then they surely should look at this problem.

Regards
#292
Beyonwiz / Re: "65534 minutes to get scheduler tasks"!
December 03, 2009, 11:18:26 AM
Thanks Dan.

Yeah, my Interactive "upcoming shows" is a dogs breakfast at the moment, all shows from Tuesday lunch (12.45pm [Series recording queued up for device] [Keyword Record] Richard Hammond's Blast Lab ‘Episode 2 - The Weight of Liquids’ABC3) are queued, not transferred (well, at least according to the Interactive, I haven't checked in the Wiz).   So this is all Tuesday night and all Wednesday timers are queued.   The PVR has a 4am wakeup timer, so not sure why it didn't pick these up, unless of course they just became queued after 4am today?

The strange thing is, a show that has been a series for some time and recording happily for some time, "Hyperdrive" is also indicating queued, and this is tomorrow night, so I am clueless as to why this particular thing is happening, but I guess the Tuesday onwards stuff would be +5days from this schedule code stuff up.   Another thing that I am confused about is that I saw a show I wanted to record last night when sussing the widget out, so setup a timer from the Widget, and noticed the wiz was in standby, so powered it up and it got the schedule fine for this show, so why some things are transferring and some not remains a bit of a mystery.


I would give my right arm to have a logging system or view logs on the Interactive pages, rather than silly nearly meaningless icons.   The log should include things like when the entry was first queued in ICE interactive, when it was attempted to be transferred, logs of when the PVR was requesting stuff, logs of when ICE transferred stuff.
Not having any kind of real info of substance is literally creating a situation where people are reverse engineering the protocol between PVR and ICE just to see why stuff isn't or is coming through.
Regards
#293
IceTV EPG Content / Re: ABC3
December 03, 2009, 11:08:26 AM
I have a bucket load of exclamations for shows set to record on ABC3 at the moment  (I have a Beyonwiz, not sure if something needs to happen to get ICE locked to the new channel in the Wiz... I haven't deleted any channels in the Wiz, so the channel exists as far as I am aware, I have watched the place holder a couple of times... or was that 7TWO.... argh.. will check 2nite).  I have setup a keyword some time ago for "Richard Hammond" and there appears to be many timers of his show (ABC3 appears to be repeating the same ep many times, I guess I will setup a proper series recording for this now and choose no repeats).
#294
Beyonwiz / Re: "65534 minutes to get scheduler tasks"!
December 03, 2009, 02:46:27 AM
Just to add my extra 5cents (as Neon on the Wiz forums posted an image up and I decided to have a look at my status updates finally):

But mine is ok, it is getting schedules quite ok... in saying this though, I notice in my status:
65138, 65133, 65128minutes to get scheduler tasks. edit and now 65123minutes while typing this out here and looking over.
But the thing is, I saw a show I wanted to record tonight while quickly perusing the widget, set it up to record, then noticed the wiz was in standby (can see it in the other room just when I am sitting at my pc, and with my spare remote and very careful pointing, I can get the Wiz powered up), and noticed the recording VFD indicator a bit later (and then looking in the filelist it definitely recorded the show).
Maybe this is only going to be a problem if you leave your wiz on 24x7, but it picks up the schedule quite fine on power up.   Whatever it is, the Wiz is honouring the dodgy info that ICE is sending, and checking every 5mins... ouch.
Regards

#295
Beyonwiz / Re: "65534 minutes to get scheduler tasks"!
December 02, 2009, 11:37:26 PM
Mine picked up one i added only 20mins ago via the widget, haven't looked at the status itself (I tend to ignore that status normally, i guess you only really look there when you are trying to fault find, which I haven't had to do).
It suggests it is getting everything a bit too quick for the servers so they are telling it to hold back for a very long (or negative?) time.   Did you power up/down and thus effectively the Wiz is asking too quickly?
#296
Whoops, sorry about that.   I just figured no sane person would run with anything other than a padding priority of "none"  :D.  I have 5mins pre, 20mins post, priority none, and 99% of the time I am happy (albeit that I have to be careful when deleting stuff of ensuring, if it is a later show than the one on the same channel before it, I don't delete the end of the proceeding show).

I guess back to the o.p. question, it would be handy for some to have timers aggregate for some PVRs (not the Topfield 7100 though, given that file editing really isn't possible with that, certainly you can't delete a chunk of a file and claim back HDD space, nor separate a recording, anyway).  I think it may cause a few headaches for the ICE algorithms about what the PVR already has set vs what ICE is trying to schedule though...   and then you have the dozens of permutations about how people feel the combined filename should be put together for combined shows...

(PerlTGD is a nice solution for the 5K... you don't like the way it appends adjacent timer names together, well, given it is open sourced and partially configurable in the ini file anyway, just change it!).
#297
The Beyonwiz padding is ignored for back to back actually, it is really the networks screwing around by making their shows go past the advertised timeslot (to attract ratings and have people stay on a channel rather than move away to watch something start on another channel in the next timeslot).
#298
Windows Media Center / Re: No WIN Tas recordings
November 28, 2009, 09:52:43 AM
I get this on all channels that I set a recording via the Media Center now.
It all started when my stupid %^&*( USB tuner card and/or the way the Media Center software poorly works seems to "forget" I have a TV tuner connected from time to time (get the dreaded "there is no tuner on this PC" or some such message).   Re-plugging in the TV tuner doesn't do anything at this point, the only way to get it recognised again is to restart the "Windows Media Center Receiver Service" (in my services.msc) and then it detects the tuner fine again, but I have to do a full rescan (grr... was doing this on my Vista64 all the time, I wondered if this would carry over to W7 64.. it does).
After the rescan, I had no -IceTV options in my channel settings.   I installed the 3.0.0.4 Interactive app again, and it gives me the -IceTV options again, but I have to change every channel to point to that (painful with the silly channel ordering going on in the Media Center software...).   Anyway, after doing that yesterday, any timer I create from the media centre will now give a very rapid (every 5secs?) error message in the logs about that channel not existing (the name of the channel being the standard scanned channel name provided by the broadcaster).

So... long story short, and my guess of the issue is-   Now WIN have changed around their channels a bit to get WinHD and Go all working, I suspect that the media centre added the channel and altered the existing, but the ICE interactive app didn't know about this at the time of the install of course (as the channel wasn't there before, now is), and there is a bug in the way the Interactive app deals with "new" (or altered) channels scanned/found since the installation of Interactive.


edit:  copy of the relevant lines in the log file in C:\ProgramData\IceTV\Interactive\3.0 (why not 3.0.0.4... dunno):
27/11/2009 23:29:44.359: DEBUG There are 3 matching channels for channel number 3
27/11/2009 23:29:44.375: WARNING No matching IceTV channel for channelID 3 callsign Deleted(11/26/2009 08:03:22): SBS ONE
27/11/2009 23:29:44.378: INFO Locally scheduled: Type(Onetime) Id(!Generated!49a789c6848a4d44b4f48e6edd6ca1fb) Channel(7) StartTime(2009-11-27T12:50:00.0000000Z) Title(Family Guy)
27/11/2009 23:29:44.380: INFO Creating local task..
27/11/2009 23:29:44.420: DEBUG There are 3 matching channels for channel number 7
27/11/2009 23:29:44.438: WARNING No matching IceTV channel for channelID 7 callsign Deleted(11/26/2009 08:03:22): 7 Digital
27/11/2009 23:29:54.532: INFO Locally scheduled: Type(Series) Id(!Generated!289dd126f699451baee1371b970e27b3) Channel(3) StartTime(2009-12-02T18:20:00.0000000Z) Title(Japanese News)
27/11/2009 23:29:54.534: INFO Creating local task..
27/11/2009 23:29:54.558: DEBUG There are 3 matching channels for channel number 3
27/11/2009 23:29:54.564: WARNING No matching IceTV channel for channelID 3 callsign Deleted(11/26/2009 08:03:22): SBS ONE
27/11/2009 23:29:54.566: INFO Locally scheduled: Type(Series) Id(!Generated!289dd126f699451baee1371b970e27b3) Channel(3) StartTime(2009-12-03T18:20:00.0000000Z) Title(Japanese News)
27/11/2009 23:29:54.567: INFO Creating local task..
27/11/2009 23:29:54.606: DEBUG There are 3 matching channels for channel number 3
27/11/2009 23:29:54.623: WARNING No matching IceTV channel for channelID 3 callsign Deleted(11/26/2009 08:03:22): SBS ONE
27/11/2009 23:29:54.626: INFO Locally scheduled: Type(Onetime) Id(!Generated!49a789c6848a4d44b4f48e6edd6ca1fb) Channel(7) StartTime(2009-11-27T12:50:00.0000000Z) Title(Family Guy)
27/11/2009 23:29:54.627: INFO Creating local task..
27/11/2009 23:29:54.671: DEBUG There are 3 matching channels for channel number 7
27/11/2009 23:29:54.685: WARNING No matching IceTV channel for channelID 7 callsign Deleted(11/26/2009 08:03:22): 7 Digital
27/11/2009 23:30:04.775: INFO Locally scheduled: Type(Series) Id(!Generated!289dd126f699451baee1371b970e27b3) Channel(3) StartTime(2009-12-02T18:20:00.0000000Z) Title(Japanese News)

Both these were timers I setup in the Media Centre.   Once I found them and deleted them, the repeating rapid messages went away, and was able to set timers thru Interactive.

Regards
#299
What about other times in the day when the PVR fires up for a timer?   Mine is set to wake at 4am (least chance of disturbing a real timer at that time) and then whenever it has to wakeup for a timer.   So unless ICE pushes something *very* last minute thru, what you miss in the morning daily timer (10am for you) you will get later anyway, and will only be of consequence for timers the new timers for shows >5days out (ICE sets timers for up to 5days ahead).
#300
Quote from: prl on November 18, 2009, 02:23:52 PM
It would be really good if more technical information about the operation of IceTV was available from the people who really know how it works!
Absolutely!  I have been begging for this for yonks on these forums.  Such things as "what happens when a timeslot changes, how does ICE reschedule and deal with the existing timer on the PVR?", "how does ICE deal with current timers on the PVR that weren't set on ICE?", "why does ICE delete my view timer when I do a resend_all twice a year to deal with DST transition?" etc.    If ICE were a bit more forth coming with the mechanics of interactive, then we don't have to second guess all this stuff.   They don't have to give their detailed IP/protocols away, just give basic info.
Also, do all  PVRs use the same ICE URL?   Do all PVRs require DNS to be setup properly (i.e. is it a URL, or an IP address)?  etc.