missig guide data?

**rapier** · 16-03-2005, 08:47 AM

Originally Posted by Wanted

Did anyone else run out of TV1 and TV2 data at around 11pm last night? I have other channels up to Saturday but channel 1 and 2 have none.

Yeah, my TV1 & TV2 has got nothing in it. Anyone know what has happened?

**jaidev** · 16-03-2005, 11:02 AM

Originally Posted by rapier

Yeah, my TV1 & TV2 has got nothing in it. Anyone know what has happened?

Yeah TVNZ happened. Fixed now in latest slice..

**thomson** · 16-03-2005, 02:18 PM

Originally Posted by timmy

I'm just about done (final bit of testing) on an updated par ser.
This will included predicted data, I have no idea how this will affect Thompson's predicted guide data step if he continues to use it.

Thanks for the warning, but any predicted data would be more than welcome by anyone with a TiVo

I am guessing you have renumbered the StationDay's so that predicted data can be updated by future slices? This post has a small writeup on the reason for it. Of course the current sequential scheme would also work if there was a database/file held somewhere that mapped the sequence numbers to a Station+Day. You just need to be able to update existing (predicted) entries already existing in the database.

**timmy** · 16-03-2005, 03:04 PM

umm no. ur the slice expert dude...

i'm working on the guide data just using some basic SQL to pull forward data where it doesn't exist but has show up the last two weeks.

cool?

TiM

**thomson** · 16-03-2005, 06:16 PM

Originally Posted by timmy

I'm working on the guide data just using some basic SQL to pull forward data where it doesn't exist but has show up the last two weeks.

Hmm... an example of the problem you may encounter is as follows... if you predict information for TV2 next Wednesday and give the StationDay a ServerId of 1234500... then a few days later when you get the real schedule for that day and you then give the StationDay a differnet ServerId then there is likely to be two schedules in the database for TV2 for Wednesday - and I have no idea which would be used...

The trick is to use a number which can be predicted (such as ChannelId+DayNum) so that when it comes time to update it you simply overwrite it (using a later version number).

The other thing to watch is that you probably want to alter the ProgramId for the predicted shows otherwise they will not be recorded as they will be the same as the previous weeks Id, and TiVo will not record the same programme twice within a 28 day period.

**thomson** · 18-03-2005, 11:09 AM

Code:

GAP: Station TV1     Fri 18 Mar 16:05 - 19:00 (2 hours, 55 minutes)
GAP: Station TV1     Sun 20 Mar 01:35 - 01:00 (-35 minutes)
GAP: Station TV1     Sun 20 Mar 02:10 - 01:35 (-35 minutes)
GAP: Station TV1     Sun 20 Mar 02:00 - 02:10 (10 minutes)
GAP: Station TV1     Sun 20 Mar 02:00 - 06:00 (3 hours)
GAP: Station TV1     Sun 20 Mar 08:00 - 12:00 (3 hours)
GAP: Station TV1     Mon 21 Mar 06:00 - 09:00 (3 hours)
GAP: Station TV2     Fri 18 Mar 22:00 - 01:00 (3 hours)
GAP: Station TV2     Sat 19 Mar 07:00 - 10:00 (3 hours)
GAP: Station TV2     Sun 20 Mar 01:20 - 01:00 (-20 minutes)
GAP: Station TV2     Sun 20 Mar 02:40 - 01:20 (-140 minutes)
GAP: Station TV2     Sun 20 Mar 02:00 - 06:00 (4 hours)
GAP: Station TV2     Mon 21 Mar 18:00 - 21:30 (3 hours, 30 minutes)
GAP: Station TV3     Sat 19 Mar 07:00 - 10:30 (3 hours, 30 minutes)
GAP: Station TV3     Sat 19 Mar 13:00 - 16:00 (3 hours)
GAP: Station TV3     Sun 20 Mar 05:30 - 05:30 (-60 minutes)
GAP: Station TV3     Mon 21 Mar 15:00 - 18:00 (3 hours)
GAP: Station Prime   Sun 20 Mar 02:00 - 02:00 (-60 minutes)
GAP: Station Prime   Mon 21 Mar 21:45 - 00:20 (2 hours, 35 minutes)
GAP: Station C4      Sun 20 Mar 04:00 - 04:00 (-60 minutes)

**thomson** · 21-03-2005, 02:37 PM

The attached image is the output from the GDchecker TivoWeb module.

Code:

GAP: Station TV1     Fri 25 Mar 13:25 - 15:40 (2 hours, 15 minutes)
GAP: Station TV2     Mon 21 Mar 18:00 - 21:30 (3 hours, 30 minutes)
GAP: Station TV3     Mon 21 Mar 15:00 - 18:00 (3 hours)
GAP: Station TV3     Thu 24 Mar 15:00 - 18:00 (3 hours)
GAP: Station TV3     Fri 25 Mar 06:00 - 09:10 (3 hours, 10 minutes)
GAP: Station TV3     Fri 25 Mar 21:15 - 00:40 (3 hours, 25 minutes)
GAP: Station Prime   Mon 21 Mar 21:45 - 00:20 (2 hours, 35 minutes)
GAP: Station C4      Fri 25 Mar 21:00 - 01:00 (4 hours)

**thomson** · 06-04-2005, 12:34 PM

Code:

GAP: Station TV1     Thu  7 Apr 03:30 - 06:00 (2 hours, 30 minutes)
GAP: Station TV1     Thu  7 Apr 15:05 - 18:00 (2 hours, 55 minutes)
GAP: Station TV1     Fri  8 Apr 00:40 - 03:00 (2 hours, 20 minutes)
GAP: Station TV1     Sat  9 Apr 03:00 - 06:00 (3 hours)
GAP: Station TV1     Sun 10 Apr 09:00 - 12:00 (3 hours)
GAP: Station TV1     Mon 11 Apr 06:00 - 09:00 (3 hours)
GAP: Station TV2     Thu  7 Apr 09:10 - 12:00 (2 hours, 50 minutes)
GAP: Station TV2     Thu  7 Apr 15:30 - 15:31 (1 minute)
GAP: Station TV2     Mon 11 Apr 01:25 - 03:25 (2 hours)
GAP: Station TV2     Mon 11 Apr 12:00 - 15:00 (3 hours)
GAP: Station TV3     Sun 10 Apr 18:00 - 21:30 (3 hours, 30 minutes)
GAP: Station TV3     Mon 11 Apr 06:00 - 09:00 (3 hours)
GAP: Station Prime   Wed  6 Apr 15:00 - 18:00 (3 hours)
GAP: Station Prime   Thu  7 Apr 15:00 - 18:00 (3 hours)
GAP: Station Prime   Fri  8 Apr 18:00 - 21:40 (3 hours, 40 minutes)

**Wanted** · 06-04-2005, 01:25 PM

Bring on the predicted data. I missed Firefly last night because of a gap in TV3 listing..... now it's personal

**SeanOffShotgun** · 06-04-2005, 06:42 PM

Originally Posted by Wanted

Bring on the predicted data. I missed Firefly last night because of a gap in TV3 listing..... now it's personal

That's why this Guide Data Checker is useful. Using it I knew a few days ahead that TV3 had gaps (1 channel among many).

In the current circumstances everybody should be using this module.

Instead of ~moaning~, do what I did and offer to help.