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

#181
IceTV EPG Content / Re: 24 - Incorrect Listing
April 06, 2010, 08:32:51 PM
Listed where?  It is ok for me with the widget and web and Beyonwiz guide.   Perhaps you are looking at the FTA guide rather than ICE, or it only impacts certain areas (certainly not like that in the ICE Sydney guide).
#182
IceTV EPG Content / Re: Daylight Saving Drama
April 06, 2010, 12:23:20 PM
No, ICE stores as UTC based.   The issue is that the PVR adds the current GMT offset at the time of the reception of the data from ICE.  So if your PVR was set to +11hours, it would have added 11hours to the ICE data, making the timers 1hour later than they should have been.   Well, this is certainly how it behaved for the Beyonwiz anyway.   All timers were for 1hour later than they should be (for the shows where ICE didn't muck up the transition themselves, for those ones they were 2 hours out, and a repeat timer an hour earlier when ICE must have realised their mistake).  If you didn't change your clock, then they would have recorded at the right time, but of course if you fixed your clock but didn't fix the timer, they would have recorded at the wrong time.
Regards
#183
The problem is #1 because of DST.  It even screwed up ICE this time, they forgot to adjust their schedule (or adjusted it the wrong direction), and so every timer sent to our devices at the time of the ICE stuff up was out by an hour to what it should have been.   When ICE fixed up this issue, unfortunately they don't do their housekeeping duties and fix up the mess left behind, and as a result, your PVR/device ends up with timers for shows you had no idea you wanted.    I had this for shows around the time Durham county was meant to start on ABC2, and 24 on 72.   If the show you originally wanted to record spanned across two shows on the ICE guide, they put a dot on each slot.   Then DST ends proper, all is back to normal, you get the GMT offset in your device set to normal, information back to ICE gets sent correctly (localtime-GMToffset=UTC time for the show to start, ICE works with UTC times), but now the timers are for times that don't match the original times, but ICE highlights whatever it knows about time, date & channel wise on your device.
#184
You left the search at the default setting "record only 1 per day".... that is a really really really stupid setting and ICE should stop that being a default immediately!
#185
My doughnuts remained as doughnuts, luckily whatever causes that MSG "Invalid Task Action" behaviour clears itself after about 12hours (or some other event??) after doing the resend all, and it is back to normal (bar the stupid doughnuts), with new shows scheduled (either through the PVR GUI or further down the week from ICE) thankfully being scheduled and indicated properly.   I did have triangles for all the clashes when ICE didn't bother purging the timers that were one hour out when I tried the initial resend all though!
I think ICE haven't quite got the protocol working correctly to both the Topfield and Beyonwiz.   It is 99% for the Wiz, enough to work effectively even with the doughnuts, but it is frustrating for the end user as there is next to no feedback or information about why things are failing or not behaving as they should apart from silly meaningless symbols with no messages attached (triangles, doughnuts).   Buggered if I know why the doughnuts are there for me, all the shows are scheduled to record at the correct timeslots for them (now, after I manually fixed them all)..
#186
You get red dots without the magnifying glass for 2 reasons.
1.  It is an interactive series recording instead
2.  The PVR/device you are setting the timer on has a timer set for that timeslot on it, and thus ICE highlights by way of a red dot to show you this.

Regards
#187
You can see which keyword, it will say it is part of a keyword recording, if you click that keyword it will take you to your "my shows" page and less obviously highlight the keyword or series recording entry that initiated the timer (that silly thing gets me every time also, why it just doesn't tell you the lousy keyword that it matched on is beyond me, instead of highlighting an entry in a big pile of entries which is easily missed if that entry is not on your screen at the time and you have to scroll up or down to find it).

edit: ooooh, I wonder if there has been an enhancement snuck in!
I click on one of my upcoming shows with the magnifying glass on it (e.g. Lost), and get:
This show matched the Keyword Record: lost fox

Ahh, maybe it is when I go  to alter a series recording, it takes me to a highlighted entry, but for keywords it tells you there on the spot?
#188
I wonder whether this not understanding the resend-all message has been around the past public f/w release and perhaps earlier.  The last time I used this was last DST transition which was September last year of course, which proceeded the last public release by a bit.

Wow, just looked in interactive (my upcoming timers) and the only non-doughnuts I have now are the timers I manually set from the Wiz GUI about 45mins ago for the known shows missing (e.g. tonight's F1 gaps, e.g. Durham County on Tuesday).   So some communications are happening from Wiz to ICE...   Also Bones is there, but I realised Bones was a repeat so removed it from the Wiz, dunno what is going on there.
#189
Hehe

I thought now everything is in the right timeslot and just a few gaps (thanks to me manually purging the erroneous ones from the GUI), I would try a resend all one more time to fill the missing gaps, and resend all *still* gives the same MSG "Invalid Task Action" message on the Wiz status bar next time it updates after choosing that option.   Argh.  
Time to purge all and start again.
#190
This morning, take 2, I found the Wiz didn't do the MSG "Invalid Task" which was nice.   I don't know how the 4am wakeup timer went, but the first thing I did when I powered up now is go straight to the ICE status screen, and was suprised to see it finally do the

Try to get scheduler state
Get scheduler state: OK
Try to send scheduler state
Send scheduler state: OK

wow!   So then checking my timer list... oh dear, 2 timers for every show where creating the correct time for the timer didn't cause a clash.   But still ICE insisted I wanted ugly betty & colbert report & young ones recorded, and not the original shows for those timeslots.
Thankfully due to this error I was getting the past few days (Invalid task), I didn't have any timers past Tuesday, so there is no mess past Tuesday and all is back to normal for then.

I have deleted the shows that I don't want recorded and/or at the wrong timeslot, and won't tempt fate with the resend all recordings, clearly that is now broken to the Wiz.    I have actually never believed that would solve the issue of every timer out by an hour, despite others indicating in the Beyonwiz forums that this was all they did.    As from what I can see, ICE doesn't really delete much from the PVR, only add stuff.
#191
Others have mentioned this message in the past, and it appears I am getting it every time now:
Wait 25minutes to get scheduler tasks"... drats, wait, watch as ICE tells it every 5mins how long to wait and/or the Wiz is indicating how long to go, and then, at the end of all the waiting-
Try to get scheduler tasks.
Wait 30minutes to get scheduler tasks.
MSG "Invalid task action" (the message in question).

This has only started since I tried the "resend all" from the account settings the other day, to tidy up the mess I believe ICE has made of Sunday's shows (had the wrong timeslot for a number of shows, that must have been corrected during the week but of course the damage was done for any timers that had been sent in the beginning).
And I am not talking about the quirk (major annoyance!) of the Wiz adding the *current* GMT offset at the time of receiving the timer to add it to the Wiz timer tables, this of course means every timer is out by an hour.    So every show I wanted to be recorded for Sunday, if it hadn't clashed due to too many shows overlapping, had 2 timers for it in adjacent (well if it was a 1hour show it was adjacent) timeslot.

Does ICE send deletes for mistakes or timeslot shifts?   Does the resend all do any kind of mess clean up?   Why does the resend all cause the Beyonwiz issues and indicate MSG "Invalid task action" in the Beyonwiz GUI ICE setup screen (where it shows the running log of getting ICE schedule/guide data)?

It appears I will need to purge the rest of the timers for this week and give "resend all" another shot, but I am not holding my breath, in the past when I did this it basically told the ICE interactive engine "hey, he deleted this timer from the GUI for this week, he obviously doesn't want to record this show for this week so we won't record it for him, even if the resend all is used" and then I have to manually go through every show I wanted to record and choose the "record" option from the ICE web gui.

Oh, one more thing, since doing the resend all (and trying again tonight), all shows have been showing up as doughnuts in the ICE GUI, I guess because the Wiz is not accepting the resent data and reporting the "Invalid task action" error.

And... finally, ICE is showing shows queued to record that I clearly don't want to record, and not showing red dots/doughnuts on shows that I do (but only for Tuesday?), e.g. it is showing Ugly Betty is scheduled but 24 is not, same with Young Ones AND Colby Report vs Durham county, these are on adjacent timeslots (1hour apart) and I expect if ICE simply looks at the show date/time it sees in the Wiz vs the ICE schedule, it would think this same thing for many more shows during the week (as all the Wiz timers are currently an hour out until either the resend-all tidies it all up or I manually do it Sunday morning before I go out so it will catch the F1 etc that is on Sunday evening).

Another edit:
The last timer the Wiz has is Tuesday evening.   For some reason, even the Wiz thinks it is recording Ugly Betty and The Colbert Report, which is strange, as I thought the Wiz used the EPG it knew about at timer creation to label these timers (as evidenced by when the LAN connection dies/is removed for over 5 days, and you plug it in and it first contacts ICE and gets the scheduled events first before it gets the EPG, and so the timers it creates have effectively no name... well *channelName).   Or is this a case of "whoops" for ICE not adjusting the guide correctly at the beginning of the DST change transition, and then later fixing it?  Others have mentioned 7/7HD being out of synch, and others have also noticed ABC similarly impacted.

Anyway, an utter disaster of a transition this time around ICE,  I was expecting the Wiz to set timers for 1hour out, but not for it to get incorrect EPG also at the beginning and set it for 2 hours out effectively.   Please ensure in future you get the transition sorted out well in advance of the event, and have your data auto-adjust on DST transition before it gets sent to our units.   So right now every timer on the Wiz is a mess, and I can't resend all as something is clearly getting confused between Wiz and ICE right now, even with the correct GMT offset setup in the Wiz.  

Regards
#192
Topfield / Re: Invalid scan freq
April 04, 2010, 12:33:57 AM
Sounds like you may have cycled the tv-out accidentally.   You need to choose the option on your remote to change the resolution on the Topfield, I forgot what the button is called but it is in your manual and reasonably obviously labelled (maybe vformat?).  It cycles through all your options, so slowly cycle it thru until you get the image on your screen then check the settings are correct in the video output menu.
Regards
#193
There is definitely post processing of sorts.   As the guide ICE sends is in GMT, but when you are looking at it, you are looking at it in some kind of local time.   Of course which unit you view the guide with will be the difference between the way it displays the data being done poorly, or well.
e.g. Beyonwiz simply adds the *current* GMT offset to the EIT guide data to display it to you.   Thus is out by an hour after the transition until you fix your GMT offset.   A better unit would look up tzdata and determine DST date/time transition and apply the correct offset on the fly, rather than the current offset.

Regards
#194
It seems that ICE mucked up Ten and Seven on early Sunday when it comes to setting interactive timers at least, but now the guide is fine.   This is evidenced by my PVR having 2 timers for each show on adjacent timeslots.
#195
The beyonwiz can be explained.  It adds the GMT offset that it is *currently* at to the GMT based data ICE feeds out.   So the time will be wrong by an hour for all timers that are set after the transition at the moment.   We were nutting this out on the Wiz forums (someone wanted to go away and was asking how to deal with the date/time & timer changes) and realised that if you don't touch your clock, it will record at the right time.   But of course if you pull your clock one hour back as you should, then all the timers will start at the wrong time.   You have to do a resend-all after the DST transition period (and after you fix the Wiz clock) to get the timers back to the right time.   As for eyetv, I would have expected better from that package!!   A more software oriented package should be using TZdata and know the date/time transition and be adding the correct offset to the timers etc to have them set for the right time.   Oh well!

edit:  and if you hadn't already noticed, ICE marks the online iceguide with your locally set timers too.   So ICE sees your PVR has a timer set for 6.30 (instead of 7.30) and highlights the 60min ep instead of the V ep...