Anybody know how mythfilldatabase works internally?<br><br><div class="gmail_quote">On Sat, Dec 19, 2009 at 10:22 AM, Myth User <span dir="ltr"><<a href="mailto:mythtv@heathsworld.com">mythtv@heathsworld.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I have been trying to get my channels working in .22 for a couple months now. Since the channel scanner broken and cannot distinguish sub-channels,<br>
<br><a href="http://www.gossamer-threads.com/lists/mythtv/users/410531?search_string=channel%20scanner;#410531" target="_blank">http://www.gossamer-threads.com/lists/mythtv/users/410531?search_string=channel%20scanner;#410531</a><br>
<br>I have resorted to using scte65scan to pull a sql file together which looks pretty accurate except for missing a few channels I could add manually (See attached SQL file). I imported the SQL file and the channels appear properly and seem to work fine when tuning. Next step is to get guide data from SD. Schedules direct is not willing to match my QAM channels numbers as I receive them through my cable provider so I have to manually match based off xmlid's. If I edit 1 channel manually and add the xmlid, the next mythfilldatabase duplicates that id across several other channels. For example if I edit channel 9-1 and add 52345 for the ID, the next mythfilldatabase attaches 52345 to my imported channel 90 as well. 90 is TBN but has the guide data for channel 9-1.<br>
<br>Can anyone tell me how mythfilldatabase can change my channel xmlids? And since schedules direct has failed to match my local cable QAM channels (very disappointing I might add), how can I manually pull the guide data.<br>
<br>Thanks.<br><br>
<br>
</blockquote></div><br>