This file gives some insight to the file changes between the tivo_canada
mkconfigfiles.pl headend system and the new oztivo system. If you don't
know what mkconfigfiles.pl is, then there is no point in reading this file!

I have rearranged the existing file formats somewhat. This is a bit outdated,
but it will give you some feel for the changes. First up, stations.list is
nearly identical to config-channels.ini for now. However, I have some
ideas which I'll describe below.

Headends
========

Each state's files are in a directory, e.g QLD/

In QLD/ we have these headend files:

	QLD/Brisbane.head
	QLD/DBS.head
	QLD/GoldCoastNorth.head
	QLD/GoldCoast.head

Each state must have a DBS.head and one or more other *.head files. The
other *.head files are the TiVo cable headends, and all of these *.head
files are pretty much like the old config_slice files.

Here is what has changed with the headend files. I've removed the
baseheadend, baselineup, lineuptype parameters from the file and added
a [lineups] section which names the lineup files in this headend. We
can deduce the value of baseheadend and baselineup from the contents of
the lineupfile, e.g QLD/Digital_FTA.lnup has "provider: 04008" so we
get baseheadend=8004008, baselineup=8004008. The lineuptype is now kept
in the lineup files and not the headend files.

As you look through the headends, you will see that the DBS.head contains
all the cable, satellite and digital FTA lineups for the state. For a
region like Brisbane.head, the headend file contains the analog FTA
lineup, the state digital FTA lineup and all the state cable lineups.

Lineups
=======

In QLD/ we have these lineup files:

	QLD/Aurora_Sat.lnup
	QLD/Austar_Sat.lnup
	QLD/Brisbane_Analog_FTA.lnup
	QLD/Digital_FTA.lnup
	QLD/Foxtel_Analog_Cable.lnup
	QLD/Foxtel_Sat.lnup
	QLD/Foxtel_Digital_Cable.lnup
	QLD/Foxtel_Digital_Sat.lnup
	QLD/GoldCoast_Analog_FTA.lnup
	QLD/Optus_Cable.lnup

These are pretty much like the old *.conf files. I have removed the zipcode
line because the zipcode is just the headend's zipcode. I have added the
lineuptype textually as one of the following:

	lineuptype: Antenna
	lineuptype: Cable
	lineuptype: Digital
	lineuptype: Satellite

Satellite => 17 in the slices, the rest => 1 for now but it may give us
flexibility later.

Stations
========

I want to try and reduce the number of stations, because we are going to
end up with a lot of them. Many stations are actually identical, but we
are forced to create several to have different fccchannelnums. I want to
reuse the same station-id in _different_ headends so I can reset the
analog channel number. My suggestion is:

[ABV2]
affiliation=Australian Broadcasting Corporation
city=Melbourne
country=Australia
dmanum=613
doguidedata=True
fccchannelnum=2
name=ABC Melbourne
parser=ABC|Yahoo|Austar
serverid=7300002
state=VI
tmsid=1087
urlparams_abc=ABC
urlparams_austar=ABC
urlparams_ebroadcast=2&state=Melbourne&fta=1
urlparams_yahoo=92843
zipcode=03000

[ABC-Vic]
reuse=ABV2
fccchannelnum=40

So as long as ABV2 and ABC-Vic are not in the same headend (and thus not
in the same analog FTA lineup), we can use the same data from Wktivoguide
to populate guide data for both channels. This will also help to speed
Wktivoguide up.

reuse= means to load all the parameters from the named station, but each
one can then be overwritten. This also means that if the URLs change, we
only have to change one line of the stations file.