System Change 22:15 on the 25th May

[mve]

re register worked but getting TBA on all channels? Anyone got an idea of whats wrong? I've got through the setup ok and after 20 or so phone attempts I got through but no channel info.....

[jrg]

A number of my main stream channels (ITV1, C4, C5, etc) don't have any listings data before Friday 3rd June.

An update.

(For Freeview) Channel 4 is now showing data for Monday 30th, but not Tuesday through Thursday.

I can't see any particular pattern on what is or isn't there:
Nothing for ITV1LON until Friday, nor BBC3, BBC4, CH5, ITV2, YESTDAY, C4P1, MORE4, E4, FIVER, FIVEUSA, QUEST, SKYNEWS,
Nothing until next Saturday for FILM4, ITV2P1F, E4P1, ITV1P1LN, CBEEB, BBCPARL, ALJAZFV
and also some gaps for ITV4.

If its useful to anyone, I can see in the tclient log the requests for:

UK01005_15124-15138.slice.gz
UK01006_15124-15138.slice.gz

and here's the loading sections:

Code: Select all

05/29:22:13:46: /tvbin/TClient: dbload UK01005_15124-15138.slice...
05/29:22:15:45: /tvbin/TClient: sizeTotal = 209524
05/29:22:15:45: /tvbin/TClient: sizeThisFile = 209378
05/29:22:15:45: /tvbin/TClient: sizeDone = 209378
...
05/29:22:15:45: /tvbin/TClient: dbload UK01006_15124-15138.slice...
05/29:22:15:50: /tvbin/TClient: sizeTotal = 209524
05/29:22:15:50: /tvbin/TClient: sizeThisFile = 146
05/29:22:15:50: /tvbin/TClient: sizeDone = 209524


I've also just noticed some sort of computation for channels, pre-request, going on. Here's some samples:

Code: Select all

05/29:22:13:29: /tvbin/TClient: HOLE INFO: station=ITV1LON sId=7200305 lastDay=15123
05/29:22:13:29: /tvbin/TClient: Station 833933 last day is 15122 (lastDay=15122)
05/29:22:13:29: /tvbin/TClient: Hole found in 833934 at 15123
...
05/29:22:13:30: /tvbin/TClient: HOLE INFO: station=FILM4 sId=7200225 lastDay=15123
05/29:22:13:30: /tvbin/TClient: Station 833956 last day is 15122 (lastDay=15122)


Does it simply not realise that it has a gap before the data it has, or can it not backfill? I assume the requested URLs incorporate the day range (15124-15138). Is there anything else useful in the log for diagnosis?

[Alek]

I just checked ch 4. I have epg till 6/6


Alek

[mrtickle]

Holes in the guide data have been problematic in the past. It's one of the reasons I wrote the GD checker module for tivoweb as they are very hard to spot otherwise.

I remember people being advised by customer services to re-run guided setup with a different postcode, and then re-run it again with your real postcode. "Clear Programme Data & To Do List" didn't fix it for those people . So it must have been a problem with the lineups. I'm speculating that the reason the advice was to change postcodes and back was so that the lineups could be re-built without any stations being removed from the user's tivo (which would wipe SPs for those stations).

That 'fix' is going to be difficult if we are all on a single postcode.

[Automan]

Could it not be setup on the servers with a different post code of each lineup?

e.g.
01000 Sky
02000 Freesat
03000 Freeview
04000 Virgin Cable
05000 TalkTalk Cable
00000 Empty to zap all data.

Automan.

[jrg]

Holes in the guide data have been problematic in the past.

...

So it must have been a problem with the lineups. I'm speculating that the reason the advice was to change postcodes and back was so that the lineups could be re-built without any stations being removed from the user's tivo (which would wipe SPs for those stations).

I've been thinking more about this, overnight. Does the server track what it thinks the TiVo has downloaded? The AltEPG post says

"The Alternative EPG system relies on the unique TCID , date & time stamps to determine what guide slices to provide your TiVo."

suggesting that the server does maintain state about the client, such as what I've already retrieved. So if it thinks I downloaded the full set of data, but then doesn't also track that I wiped guide data and redid a guided setup, then of course it's not going to provide the gaps on the next call...