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

#91
I would use it at the moment.   As per your prob, I had too many timers on Monday also (and Sunday!).   I noticed @#$% My Dad Says has a repeat encore later in the night according to ICE on Go! (but.... I set a timer for it for this week, and instead it was a double ep of 2.5 Men Ep....GRRRR).
Regards
#92
Topfield / Re: Best way to detect timer clashes
February 15, 2011, 08:00:49 PM
Last night was a bad night for me too.   Thanks to this crazy multi-channeling junk (losing HD grr), the networks had 5 shows I wanted to watch/record at 8.30pm last night (on Seven, Ten, Eleven, ABC2 and 7MATE).   So I figured I would watch the ABC2 one live and juggle my prefs between my Topfield 5k (I use perlTGD to set timers for that using ICE data) and the Wiz (going against what I record typically on the Wiz vs Topfield just to get everything) but then didn't get home from work till 11pm.. doh.
#93
Topfield / Re: Topfield 2460 not receiving reservations
February 10, 2011, 04:23:52 AM
On the Beyonwiz, duplicate channels cause all sorts of headaches for a number of reasons.
1. the Beyonwiz builds out the on screen EPG using PID information, but if it gets 2 lots of the same PIDs from 2 broadcast locations, it only datafills one of them (grr).
2. duplicate PIDs means duplicate LCNs (this has now been fixed with the Wiz, now the so-called worst reception duplicate gets renumbered up to 350+).  Duplicate LCNs is a big big big problem... which LCN gets the timer?   If ICE says to the PVR "set a timer for LCN10" but you have two LCN10s, which one will record?  What happens if one has very very poor reception compared to the other?   You might end up with recordings with zero bytes, as there was no reception at the time.   The recording looks fine on your HDD, it shows "LCN10 NCIS 60mins" but when you go to play it, it jumps straight to the next recording (as it has next to zero bytes since you had next to zero reception on that duplicate that evening).  Delete duplicates, it is the only way to ensure you know what you (and ICE) are going to record.    And what about clash detection?  ICE uses the reported information from your PVR about which LCNs have which timers, it is going to throw a spanner in the works if you have setup timers on both of the duplicates.

The ICE protocol is a little "fragile" when something out of the ordinary confuses it, and duplicate LCNs is one thing that can really muck things up.
Regards
#94
I think you are missing something.   In standby mode, the unit is not capable of operating *anything* on the main motherboard.   The only thing powered up is the front panel, it has enough smarts in it to know the time, and to know the next time it should fire up the power line going to the main motherboard to get the motherboard software booted.
You can help that along on a regular basis by creating a view timer, this is not a hack, this is a way of ensuring that on a (in Peter & mine and many many other's cases) daily basis, the unit wakes up (i.e. boots up!) in order to download the timer information from ICE.   Not a hack in any way, just a smart thing to do.    The unit goes back into standby at the end of the view timer, and you have perfect power saving compared to a TiVo like "standby" which merely turns off the video output (i.e. no power saving whatsoever compared to complete motherboard shutdown which the Beyonwiz and Topfield and I am sure most PVR models do).
Regards
#95
Topfield / Re: Problems with Topfield 7100 and 2400.
February 08, 2011, 02:12:28 AM
Did you pick the right device ID when you setup your ICE account on both your PVRs?   Each device requires a unique deviceID (and you need to manually pick it at setup, well, if like the Beyonwiz).
#96
Topfield / Re: Topfield 2460 Time creep
February 07, 2011, 12:38:34 AM
The Topfield handling of time is quite frankly, garbage.   In so called "manual time" mode, since you don't set a GMT offset in the settings menu when you select manual time (but you do when you select auto go figure) the Topfield tries to be smart but is very very dumb, and uses the broadcaster timestamp to subtract from your manually set time and it uses that figure as the GMT offset.    ICE sends EPG (and timers) as GMT/UTC (in fact, the FTA guide is sent the same, as UTC).   The dumb Topfield in manual time mode adds this number it calculates to the EPG entry to display to you what it thinks the EPG is in local time (rather than UTC time).   If your local broadcaster is out by, say, an hour with their timestamp information, your EPG (and any timers that ICE set, or timers *you* set from the EPG) will be out by an hour.   So in fact, running manual time doesn't remove you from the problems of dodgy broadcast timestamps at all!  It makes things worse for you if you run ICE, since timers are created when the unit polls ICE (and a new timer is ready to send) and therefore is dependant on what channel you are on at the time for how accurate the GMT offset will be (the Toppy dynamically calculates this offset).  

And thanks to the dodgy method the Topfield uses to determine your GMT offset, if, say, your manual set clock is out by 3mins vs the broadcaster, you will see all your EPG items are starting/ending at strange times like 8.33 or 8.27 for example.   For dynamic EPG viewing, this is not a big deal, but for timer setting, of course it can be a huge deal.    I told Topfield way back when I discovered this issue with the 5K (manual time mode) many many years ago that they were better off having a fixed number to set for the offset, just like when you set it for Auto time, (e.g. +10hours for eastern states), and the EPG and timers would be 100% accurate to the way the broadcaster or ICE intended...

This post is pure speculation for your model, but based on some discussions like yours, I suspect the issue that was in the 5K, 7100, 7100+(I think) is no better in other Topfield models.
#97
XMLTV (General) / Re: Import xml feed.
January 28, 2011, 09:23:04 AM
An add on for what?  I use the ICE XMLtv feed to parse into the PerlTGD app running on my SLUG for my Topfield 5K, is that the kind of question you are asking?  What is "int"?
#98
I can imagine that this could come about if your daily/one off timers you create happen to overlap or co-incide with ones that ICEtv would set due to a keyword match or series recording, then ICE will try to manage that timer (inc delete... ).

As you notice, any timers you create manually do indeed light up red dots in the iceguide, but normally ICE doesn't delete or muck about with them.   I see that for my daily wakeup/view only timer at 4:00am on ABC where ICE shows this in the guide sometimes.
#99
Or if like the Topfield 5K (and I believe 7x00 series) press the OK/list key while watching live TV, this will bring up a channel list, delete the 10/1/11/12 channels (confirm which frequency/RF channel they are all on before deleting, in the cities it is typically VHF11), and then go to the installation/setup menu and do a scan on VHF11.   It seems most PVRs and TVs didn't cope well when Ten swapped around a couple of LCNs but kept the PIDs the same (the PVR didn't notice the swap).
Regards
#100
IceTV EPG Content / Re: Eleven or 12?
January 16, 2011, 02:49:36 PM
Press the OK/list button and follow the onscreen menus.
#101
What is the programming guide and how is it different to their website tv guide?
#102
General Discussions / Re: Surround sound?
January 02, 2011, 11:14:28 AM
It seems 5.1 and HD is dead in this country now (for FTA).
#103
Beyonwiz / Re: DP-lite missing some episodes
December 31, 2010, 05:55:46 PM
Another thing to check is that you haven't restricted the timer to "1 per day" as this used to bite me all the time (now the default is "record all" rather than 1 a day, but still, it is something to check).
#104
This goes to show that ICE is *still* not deleting recordings when it has a schedule change.  This is one of the most annoying bugs left with ICE, that they don't first check to see if there are any people with timers set on the show they are about to move/delete/whatever, before moving/deleting/whatever from the guide, but of course the timer is already set on the PVR/whatever, and then ICE will see the timer on your PVR and think "wow, they want to record all day, well I will show red dots in the guide for all the shows that overlap their locally set** timer"...

**Obviously not locally set, it was originally set by ICE, but once ICE moves the timeslot, the timer as far as ICE is concerned looks like a locally set one, so they mark their guide accordingly that you have this timer on particular timeslots.
#105
Quote from: tonymy01 on November 24, 2010, 09:51:58 PM
Ice, can we PLEEEEEEEEEEEEEEEEEEEEEEEEAASE delete timers built from keywords, rather than delete the keywords themselves,
YAY, the update you just did today finally fixes this, I can now select any recording and just cancel the recording (rather than the underlying keyword or series).   Thanks ICE.   Now you just need to fix a quirk with when I select some timers they are entirely empty (no show description, no details within the timer whatsoever except "add favourite"), and it will be perfect.
Phone Samsung Galaxy S with Optus JP5 Froyo (and JPM speedmod kernel).
Regards