[mythtv-users] anomalies encountered updating to/for Schedules Direct
D. Hugh Redelmeier
hugh at mimosa.com
Wed Sep 19 04:25:35 UTC 2007
| From: Michael T. Dean <mtdean at thirdcontact.com>
Thanks for your help.
| On 09/18/2007 02:17 PM, D. Hugh Redelmeier wrote:
| > 2) It wasn't obvious to me how to delete an individual Video source in
| > mythtvsetup. I've since learned that, in the Video sources screen,
| > if you move the cursor to the source that you wish to delete, you
| > can type "d" to request to delete it. Is this documented
| > somewhere?
| You shouldn't delete the video source to switch to Schedules Direct.
| See http://mythtv.org/docs/mythtv-HOWTO-24.html#ss24.3 . Doing so was
| your first mistake and caused all the other issues in 3-5...
That turns out not to be the case. I did not delete the video source.
I added a new one.
| > 3) I left Zap2it as a source and added SchedulesDirect as a new source.
| > I then switched all my Input connections to use Schedules Direct
| > instead of Zap2it. This seems reasonable: during the transition
| > period, I'd like to be able to go back to Zap2it.
| > I ran into a problem that I think is related to this. After
| > apparently working for a couple of weeks, my guide information
| > stopped at 8PM last night. I tried all sorts of variations on
| > mythfilldatabase to try to fix it. Even though Zap2it was not used
| > by any input connection, and Schedules Direct was being used, the
| > Zap2it failure apparently blocked guide updating (even though the log
| > seemed to show Schedules Direct processing). I edited the Zap2it
| > source to actually use Schedules Direct. Once that was done, the
| > guide was correctly populated.
Yesterday I changed the video source named zap2it to actually use
Schedules direct. That appears to be what fixed the problem reported
in (3). But I don't see why.
More information about the mythtv-users