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

#466
Can you look at the ICE data on the media centres at all (raw files I mean?).   Or do an XML download of the ICE data for your area.   This will prove that in all likelihood it is not the ICE data that is the problem.   The ICE data is definitely GMT.   So I don't know how the VMC converts GMT data to show it to you in local time.   It is this conversion that I reckon the VMC is getting wrong.    It may use the broadcaster timestamps to achieve this, and thus it may be your broadcaster in your area is sending something wrong in their broadcast stream. I am talking about the TOT=time offset table or TDT=time and date table, which by itself is nothing to do with the EIT/EPG, but obviously a box needs to know both the GMT timestamp & date, and then the offset to apply to understand the localtime, and also use either that offset or simply a manually set offset to add to the EPG (from free to air OR ICE, either are the same as both are GMT) to display it to you in the correct localtime.
Regards
#467
I can explain how this could happen in a PVR, but I know nothing about VMC.
ICE data is GMT/UTC.   A PVR adds the known GMT offset to the data to display it to you in your local time.    With Topfield 5K PVRs, the way it calculates the GMT offset if you run your PVR clock in manual time (to avoid dodgy broadcaster timestamps) is really dumb.   It subtracts your PVR manual crystal run clock time from the broadcaster timestamp (broadcaster timestamps are in GMT) and thus obtains a GMT offset.   It then applies this to the GMT based EPG data (from the broadcaster or from ICE) and bobs your uncle, EPG displayed in local time.    The issue arrises with this strategy that if your unit clock is out by say, 3minutes (lets say 3mins fast), then when it uses this strategy it will thus calculate your GMT offset to be 10hours&3mins, and thus your EPG will look like it is 3minutes ahead of what it should be (shows starting at 8.33 instead of 8.30 for example).
If the broadcaster GMT timestamp is dodgy (because some local broadcasters are hopeless and can't adjust their broadcasting clocks properly!), then you will get the same result, EPG out by however many minutes (or hours!!) your broadcaster clock is out by.
If the PVR is in AUTO time, it only uses the broadcaster clock for your main PVR clock, but in AUTO time you setup a GMT offset yourself, so this fixed GMT offset is applied to the GMT based EPG and you will always get accurate EPG this way (shame that if the broadcaster timestamp is dodgy your PVR clock will vary wildly!!)
Regards
#468
Beyonwiz / Re: Timers get the wrong program names!!
April 15, 2009, 04:38:28 PM
I had this phenomenon just 2 days ago with the MotoGP (Tuesday morning actually, so not quite 2 days ago).   When I was going to set a manual timer for it (as ICE hadn't updated their schedule to put the rescheduled MotoGP in) I was looking to see if there was a show starting at about the 3.45-4am time on TenHD and noticed that the Nascar was at that time (but starting considerably earlier) so I wasn't going to be lazy and create a timer for that show.   I was going to (but forgot) go onto the Wiz and set a manual timer for 3.45am.   Anyway, cutting a long story short, ICE updated interactive to have the MotoGP in some time on Monday night (just before I put the Wiz into standby) and as such, the MotoGP was scheduled ok.   Just to be sure (I wasn't entirely trusting of the red dot in the widget), I checked the ICE interactive web also and saw it was definitely a red dot and not a donut.   I turned on the Wiz for 5mins *just in case* early hours of Tuesday morning.   So it had plenty of opportunity to get the updated guide.
Anyways, the file recorded was "Nascar"... but at the MotoGP times....
I am starting to think JS your assumptions are correct that the timer name just isn't sent/interpreted by the Wiz, only the timeslot, duration and channel LCN are.  So the Wiz, when it polls ICE and finds a new timer, uses its CURRENT guide to decide what to name the timer.   There is also a bit of jiggery pokey with the Wiz with timer names starting with an "*" that causes this guide syncing stuff to happen, but I thought it was at the time of the recording it obtained that info to name the recording properly, rather than at the time the timer was created, but who knows with NO DOCUMENTATION OF THIS PROCESS!

Similarly:
This is the first time in ages the filename has been wrong, but certainly it seems everytime ICE realise a mistake in the scheduling and update the timeslot for a show, it is dumb luck whether it understands that the timer you have for timeslotX should be deleted and moved to timeslotY.    It seems if timeslotX corresponds with a new show (due to the reschedule to, say, later in the evening), ICE thinks "oh, do they want to record that show now also", and you end up with something recorded on the original timeslot, and your rescheduled actual show recorded.   So ICE isn't correctly sending through a delete when the schedule changes for a show in other words.    Luckily though it will create a timer for the new timeslot, but bad luck if  you had a clash on timeslotX and miss out on something you might want because ICE didn't delete timeslotX.....
Regards
#469
Too late for me, one of the OneHD threads on dtvforums I have subscribed to gave it away.   I was a little upset, but (highlight to read): then driving to work today "triple J" of all stations gave both AFL and motor sport news. 
#470
Wonder when it was fixed, as according to the web guide I now have that timer set (not queued, actually set) and I switched off my Wiz at about midnight tonight?   I presume you fixed it a little earlier than your post here?
Thanks anyway, great to have this in, as I completely forgot to set a manual timer tonight and couldn't be bothered switching on my amp, TV & Wiz again just to set the timer :-)
Cheers!  :)
#471
Hmm, according to ICE it will be repeated Wednesday 7.30pm on One/OneHD also... just in case :-)
#472
I record Speedweek also, and have in the past, looked to see that Speedweek is something boring like boats or drags (actually they aren't always boring, but I don't get the time to watch hours of motor sport unless I really like it) and sometimes when I see it is that I delete the file and purged a WRC because of that once.... so it is annoying not having them separated.
#473
I am trying to think if this is the behaviour I observe if I setup the series recording to record first runs only and the show happens to be a repeat... dunno for sure...
#474
Well I have setup Bones as a normal series recording (not keyword recording) and it hasn't recorded in ages due to Seven not showing any new eps for ages (they have been repeats for the last couple of months).
But Keyword searching doesn't honour the repeat flags, so that is a bit weird....
Regards
#475
Quote from: johnmw1 on April 10, 2009, 07:54:52 AM
and of course I have all of my ABC program timers set to record from ABC HDTV
I can't answer your main problem, but why "of course"???  Do you know that ABC is lucky to broadcast 1 or 2 (real) HD shows a week?   So all you are recording is their SD material upscaled, and thus taking up more HDD space for potentially less quality than the SD version (as upscaling if not done right can lower the quality of the SD image).
Back to your ABCHD problem, do you have a full guide listed for ABCHD?  The default for ICE is to send only the shows that ABC broadcasts in HD for the week, and if you scan through you will see this is very sparse indeed (at the moment I notice only 10minute kiddies shows in true HD).   If this is the case, then you can alleviate this problem by going into your account settings and choosing to copy all the SD guide into the HD guide, and this will fill up the gaps.   I don't know how ICE behaves when you setup timers on these "copied" EPG entries though (you would presume it would let you record the shows off ABCHD if you *really* wanted to...)
Regards
#476
Topfield / Re: Topfield 7100 ftp question
April 09, 2009, 05:43:04 PM
http://forum.itopfield.com.au/default.aspx
Not sure the ICE forum is the right place to be discussing the ins& outs of something completely unrelated to ICE.
But the recordings are MPEG2 transport streams and they tend to not start on GOP boundaries which can throw many progs esp WMP.   "The KMPlayer" is a great way to play recordings with "errors" in them, much better than WMP.   Or you could parse the recording thru projectX first, which ignores the dodgy frames at the start of the recording and cleans it up to be a legal M2P or elementary streams which you can then put into an editor or DVD authoring package etc.
Regards
#477
Beyonwiz / Re: IceTV & channel mapping
April 08, 2009, 02:04:18 PM
The problem with a channel mapping screen is look at all the problems it causes with the Topfield.    The way the ICEguide works now to the Beyonwiz is perfect, it matches the LCN info in the ICEguide data and it is foolproof.   By having two XML LCN channels for the one guide entry is going to create lots of problems.   Can't you have two queensland regions, and call one of them "Regional Qland Seven=7" and "Regional Qland Seven=6" or something like that, you wouldn't need to create another load of data as what you have said is that you already have the data there.
Regards
#478
Topfield / Re: TV service list prob chan 21 & 22
April 07, 2009, 11:51:03 PM
I think ABC had the scrolling ticker line thingy across the screen for a few weeks saying about the changes, like SBS recently did also (did you delete your SBS channels when you rescanned, if you didn't you will probably find that they are jumbled up a bit too, world news has gone now and it is called sbs digital 2 or something like that, and you will find if you didn't delete you will end up with two SBS HD channels, not that the Toppy 5K can decode/play those anyway).
Regards
#479
Topfield / Re: TV service list prob chan 21 & 22
April 07, 2009, 09:49:22 PM
The Topfield and dtvforums probably explain this.   ABC made changes yonks ago.   Unfortunately simply rescanning doesn't pick up that the LCNs have been mapped to the opposite video streams now, so you need to actually delete the LCN 21 and 22 entries from the Toppy list (hit ok while watching TV and follow the on screen prompts to delete).   Then do a partial scan of ABC (VHF12 in the main areas, although you could be on a UHF repeater depending on where you are).   You do this from the installation menu.
Regards