Thought it was guide data issue, but maybe not

Forum rules
Get Help using the Schedules Direct service. NOTE: application issues are probably better resolved via the application's support methods. If you post here, at least include your application name!
Post Reply
rconstantine
Posts: 13
Joined: Sat Sep 01, 2007 12:43 pm

Thought it was guide data issue, but maybe not

Post by rconstantine »

see viewtopic.php?f=6&t=213&hilit=#p1125 for the whole issue.

Basically, I'm missing one channel's data. It's a digital OTA so I had to do a scan to pull it in. However, it comes up twice during the scan with the second one overwriting the first. So I think my database must have a bad entry. How can I figure out what I need to change in the DB so that the guide data (which exists and was checked by rkulagow) hooks up with the right channel? Notice in my other message that I mention the lack of XMLTVIDs for all digital channels. Now, didn't I read somewhere that the IDs for the channels changed or something since we moved from Z2I to SD? Was there a DB schema update for that? Is there something there I could look for to see if there's an error?

Any help is appreciated.

rconstantine
Posts: 13
Joined: Sat Sep 01, 2007 12:43 pm

Re: Thought it was guide data issue, but maybe not

Post by rconstantine »

For anyone who cares or may face a similar issue, it turned out my DB entry for this channel was screwed up. Not sure how it happened. Anyway, I changed chanid to 2101 from 2102 and everything seems okay. On an different matter, I didn't see that another channel was getting the correct data, but tuning to the wrong channel. For that one, I changed the serviceid from 3 to 2 and everything is now fine pending more tests and recordings.

Post Reply