[mythtvnz] Now I'm using two sources...
Steve Hodge
mythtvnz@lists.linuxnut.co.nz
Tue, 3 Jul 2007 14:58:17 +1200
------=_Part_129211_19100518.1183431497964
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 7/3/07, Nick Rout <nick@rout.co.nz> wrote:
>
>
> On Tue, July 3, 2007 2:23 pm, Steve Hodge wrote:
> > On 7/3/07, Barry Clearwater <barryc@bcsystems.co.nz> wrote:
>
> > In channel table:
> > chanid = 1001 channum = 1 sourceid = 1 callsign = 'One' xmltvid =
> > 1031.dbv.guide
> > chanid = 1002 channum = 2 sourceid = 1 callsign = '2' xmltvid =
> > 1032.dbv.guide
> > chanid = 2031 channum = 1 sourceid = 2 callsign = 'One' xmltvid =
> > 1031.dbv.guide
> > chanid = 2032 channum = 2 sourceid = 2 callsign = '2' xmltvid =
> > 1032.dbv.guide
>
> I take it from this that you can have the same channum on two different
> sources.
>
> I hadn't realised that before.
Yes. If the callsign and channel numbers of two channels are identical then
the channel will only appear once in the guide (and MythWeb). If the
callsigns are identical but the channums are not then the channel will
appear twice in the guide but the scheduler will treat them as the same
provided they have the same listings data. This allows people who have two
channels that are mostly the same, but have some differences, to use them
interchangably when a program appears on both versions without screwing up
when the channels differ (this doesn't happen in NZ at the moment).
Unfortunately it means that it is important that EPG listings for copies of
a single channel are identical otherwise the scheduler won't be able to use
them interchangably. That's why I keep telling people to use the same
listings data for FreeView channels and for Sky/terrestrial channels - there
are differences in the data between what Sky send and what FreeView send and
those differences can cause problems if you're using Sky data for one
version of a channel and FreeView data for another.
>
> > Get your listings.xml file. Run:
> > mythfilldatabase --update --file 1 -1 listings.xml
> > This will load the EPG data for channels 1001 and 1002. Then run:
> > mythfilldatabase --update --file 2 -1 listings.xml
> > This will load the EPG data for channels 2031 and 2032.
>
>
> It took me a while to twig to that when I set up the dvb-s card. The "1"
> or "2" parameter is not really intuitive and you forget what its for. A
> better syntax for mythfilldatabase might have been:
>
> mythfilldatabase --update --souceid 1 --days unlimited --file listings.xml
>
It's not ideal. It's confusing because the "-1" looks like another parameter
when it's actually an argument to the --file parameter.
Cheers,
Steve
------=_Part_129211_19100518.1183431497964
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On 7/3/07, <b class=3D"gmail_sendername">Nick Rout</b> <<a href=3D"mailt=
o:nick@rout.co.nz">nick@rout.co.nz</a>> wrote:<div><span class=3D"gmail_=
quote"></span><blockquote class=3D"gmail_quote" style=3D"border-left: 1px s=
olid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Tue, July 3, 2007 2:23 pm, Steve Hodge wrote:<br>> On 7/3/07, Bar=
ry Clearwater <<a href=3D"mailto:barryc@bcsystems.co.nz">barryc@bcsystem=
s.co.nz</a>> wrote:<br><br>> In channel table:<br>> chanid =3D 100=
1 channum =3D 1 sourceid =3D 1 callsign =3D 'One' xmltvid =3D
<br>> 1031.dbv.guide<br>> chanid =3D 1002 channum =3D 2 sourceid =3D =
1 callsign =3D '2' xmltvid =3D<br>> 1032.dbv.guide<br>> chani=
d =3D 2031 channum =3D 1 sourceid =3D 2 callsign =3D 'One' xmltvid =
=3D<br>> 1031.dbv.guide
<br>> chanid =3D 2032 channum =3D 2 sourceid =3D 2 callsign =3D '2&#=
39; xmltvid =3D<br>> 1032.dbv.guide<br><br>I take it from this that you =
can have the same channum on two different<br>sources.<br><br>I hadn't =
realised that before.
</blockquote><div><br>Yes. If the callsign and channel numbers of two chann=
els are identical then the channel will only appear once in the guide (and =
MythWeb). If the callsigns are identical but the channums are not then the =
channel will appear twice in the guide but the scheduler will treat them as=
the same provided they have the same listings data. This allows people who=
have two channels that are mostly the same, but have some differences, to =
use them interchangably when a program appears on both versions without scr=
ewing up when the channels differ (this doesn't happen in NZ at the mom=
ent). Unfortunately it means that it is important that EPG listings for cop=
ies of a single channel are identical otherwise the scheduler won't be =
able to use them interchangably. That's why I keep telling people to us=
e the same listings data for FreeView channels and for Sky/terrestrial chan=
nels - there are differences in the data between what Sky send and what Fre=
eView send and those differences can cause problems if you're using Sky=
data for one version of a channel and FreeView data for another.
<br></div><br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px s=
olid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">>=
;<br>> Get your listings.xml file. Run:<br>> mythfilldatabase --updat=
e --file 1 -1=20
listings.xml<br>> This will load the EPG data for channels 1001 and 1002=
. Then run:<br>> mythfilldatabase --update --file 2 -1 listings.xml<br>&=
gt; This will load the EPG data for channels 2031 and 2032.<br><br><br>
It took me a while to twig to that when I set up the dvb-s card. The "=
1"<br>or "2" parameter is not really intuitive and you forge=
t what its for. A<br>better syntax for mythfilldatabase might have been:
<br><br>mythfilldatabase --update --souceid 1 --days unlimited --file listi=
ngs.xml<br></blockquote></div><br>It's not ideal. It's confusing be=
cause the "-1" looks like another parameter when it's actuall=
y an argument to the --file parameter.
<br><br>Cheers,<br>Steve<br>
------=_Part_129211_19100518.1183431497964--