[mythtv-users] Manually entering tv schedule info

[Nick Rout]

On Mon, Jan 10, 2011 at 8:40 AM, Adam Cooper Wood <a at acdubs.com> wrote:
>
> On Jan 9, 2011, at 1:32 PM, Raymond Wagner wrote:
>
> On 1/9/2011 13:17, Adam Cooper Wood wrote:
>
> On Jan 8, 2011, at 1:54 AM, Raymond Wagner wrote:
>
> On 1/8/2011 01:44, George Nassas wrote:
>
> On 2011-01-07, at 3:21 PM, Adam Wood wrote:
>
> I am interested in having mythtv record some time slots on a local channel
> for shows in the coming months (they do not submit their schedules to the
> schedule gods or however that process works). Can I safely add them to the
> database (beyond the 2 weeks of data SD gives me) or will mythfilldatabase
> erase them when it populates the db?
>
> I'm guessing you have a non-myth way to get good schedule data for this one
> channel and want it to work naturally with mythtv. If so it looks like it's
> not safe to mix your schedule data with that pulled in my mythfilldatabase.
> That's assuming your data is coming from Schedules Direct which, for most
> people in North America, is the case.
>
> Presumably they're going off an ad about a new show airing a month or two
> out, beyond the two weeks Schedules Direct offers.
>
> It's actually a schedule of local hockey & basketball games up through
> March. New info- it turns out that EIT data is actually transmitted for the
> channel! 'Perform EIT Scan' is ticked in mythbackend, and I also have
> 'useonairguide' flagged for the specific channel. Does this mean Myth should
> be pulling the data into MYSQL  or is this not how it works?
>
> If you have EIT enabled on those channels, MythTV will pull in whatever data
> is provided by the broadcaster and inserted into the database.  If need be,
> it will overwrite whatever show already exists at that point in the stored
> guide data.  If you are using both XMLTV and EIT data on the same channel,
> you will end up with all sorts of weird scheduling anomalies, and
> non-functional duplicate matching.
>
> In North America, EIT data usually gets you a few hours.  Some lucky people
> with gracious broadcasters may give you a day or two.  You will certainly
> not be getting events two months out through that interface.
>
> No- I realize that NOTHING will get me data one or two months out- not sure
> where that came from!
> But I hadn't thought to check if EIT data was only a few hours. I wrongly
> assumed that EIT data was available for at least a few days out.
> My next question- will my custom recording rule apply to EIT data or just to
> SD data?

It will appy to whatever is in the database, whether provided by SD,
an xmltv provider, or EIT.