2008-11-19, 11:11 PM
I previously got good service out of Yapi2xml with one tuner. Naturally, so many things have changed, including possibly the performance of the Yahoo server, that I really have no idea what's going on. Now I have two tuners, a 1250 OEM(885), and a 1250MCE. Both have identical reception characteristics.
The program guide wasn't working. My thoughts vacillated between something wrong with the Yapi2xml local data, or a damaged db3 file. Except for the blankness, the guide was arranged logically, with apparently correct channel mappings.
Faced with a persistently blank program guide, today I deleted the db3 file. I then reinstalled the tuners and scanned both, ATSC only, picking up an identical set of stations. Yapi2xml appears to have delivered data to the disk, though I have no way of checking for validity.
I then proceeded to "map digital channels", and this is where things went kaflooey. It seems that those stations which were actually scanned were automatically assigned channel numbers. But the analog channels, for which there is no tuner, were all brought in as channel zero. In order to tidy things up, I deleted each analog channel and reinstalled it with a digital channel number. For example, Channel 3, an analog channel, was reinstalled with Channel Number 301, for which I already have an appropriate Yapi2xml mapping.
Then I began to have the "but I thought I..." experience. Under the tab "Channels", I discover that the re-added channels now have numbers incrementing from 4401. Coincidentally, there is a digital station with channel number 4401.
I kept working at it, and continued to have "But I thought I..." experiences. I deleted the mis-configured channels, and added them again. Once again, they show up in the "Channels" tab, and "Remove unreferenced channels" has no effect. The program guide remains blank.
The more I work at it, the worse it gets. Eventually, my thinking tilted toward the idea that maybe something in the EPG is poisoning the database.
Has anyone found that, perhaps, Schedules Direct is a solution to the above?
The program guide wasn't working. My thoughts vacillated between something wrong with the Yapi2xml local data, or a damaged db3 file. Except for the blankness, the guide was arranged logically, with apparently correct channel mappings.
Faced with a persistently blank program guide, today I deleted the db3 file. I then reinstalled the tuners and scanned both, ATSC only, picking up an identical set of stations. Yapi2xml appears to have delivered data to the disk, though I have no way of checking for validity.
I then proceeded to "map digital channels", and this is where things went kaflooey. It seems that those stations which were actually scanned were automatically assigned channel numbers. But the analog channels, for which there is no tuner, were all brought in as channel zero. In order to tidy things up, I deleted each analog channel and reinstalled it with a digital channel number. For example, Channel 3, an analog channel, was reinstalled with Channel Number 301, for which I already have an appropriate Yapi2xml mapping.
Then I began to have the "but I thought I..." experience. Under the tab "Channels", I discover that the re-added channels now have numbers incrementing from 4401. Coincidentally, there is a digital station with channel number 4401.
I kept working at it, and continued to have "But I thought I..." experiences. I deleted the mis-configured channels, and added them again. Once again, they show up in the "Channels" tab, and "Remove unreferenced channels" has no effect. The program guide remains blank.
The more I work at it, the worse it gets. Eventually, my thinking tilted toward the idea that maybe something in the EPG is poisoning the database.
Has anyone found that, perhaps, Schedules Direct is a solution to the above?