[mythtv-users] SchedulesDirect Changes

[R. G. Newbury]

On 26/09/14 01:23 PM, Jay Foster wrote:
> I looked at the setup instructions at
> https://github.com/SchedulesDirect/mfdb-json/tree/API-20140530#installation
> and have some concerns about this not working for my situation.
>
> I am OTA only.  I currently have two "lineups" (zip codes) selected on
> the SD website in order to get listings for the channels that I
> receive.   I receive stations from both "lineups" on each tuner
> (input).  My interpretation of the setup instructions is that going
> forward, there will be a one-to-one relationship between the input and
> the "lineup".  That simply isn't true for me.
>
> The concept of a lineup has little meaning for OTA users.  A lineup is a
> list of channels that someone else thinks one should get based on a zip
> code, but does not reflect the channels one actually does receive.  I
> have a list of channels and their associated XMLTV IDs. I just need
> listings for those, and don't care about what "lineup" someone else put
> them in.  Will it still be possible to select more than one "lineup" per
> MythTV input going forward?

Two uses of lineup: A 'lineup' is firstly a construct that mythtv uses 
to list the channels which a particular tuner can receive. Any tuner 
linked to that 'lineup' is expected to be able to tune to and record 
from any channel in that list.

At TMS/Gracenote/SchedulesDirect a lineup is a list of channels (which 
tuning info) which the provider transmits from a particular source. So 
Comcast may have one 'real' channel "7" pushed as cable "8" in one place 
and cable "9" in another. This is fine for cable and even satellite, as 
the channel layouts rarely change *and* you can always get *all* of them.

SD and the sd-utility also have access to pro-forma lineups which list 
all of the channels which is is expected a user could receive OTA in a 
particular zip-code. Not always correct, of course.

In the cable case, we know all the channels. In the OTA case we do not.

The sd-utility expects that you will do a scan to exactly determine the 
channels you can actually receive. With mythfilldatabase you must have 
done something a little odd, to have 2 actual SD lineups linked to the 
same tuner. I didn't think that was possible using mythtv-setup.

(It is reasonably trivial if you don't mind doing some mysql surgery!)

I don't think that restriction applies with sd-utility. When you do your 
scan, you will 'see' all of the channels and add them to mythconverg. 
That is a 'videosource' which contains channels which can be tuned by 
the tuner linked to that videosource.

I am reasonably sure that mfdb-json pulls data solely on the basis of 
the xmltvid channel numbers which you have in your channel list and 
marked as 'visible'.

(Rob Kulagowski can confirm that.)



              R. Geoffrey Newbury