On 10/11/05, Simpson, Richard <[EMAIL PROTECTED]> wrote: > > Mark- > > Yes, you are very close! I have just recently succeeded in getting both a > HD3000 and a PVR-150 to work in MythTV, and I believe the Myth part was the > hardest. I first setup the Zap2it account with the OTA channels I wanted to > capture, and downloaded it via mythtv-setup. Then I ran the Myth channel > scanner. Well, this was backwards from what I should have done. I ended up > with duplicate channel numbers in the mysql database, but only some of these > had corresponding records in the dtv-multiplex table, the latter being > populated by the scan program. I had to manually weed out the duplicates, > making sure the remaining channels had valid mplexid and xmltvid fields (if I > get these field names a little wrong, I going by memory).
Yep, this is exactly what I did, and you're right, I found a BUNCH of duplicates in the 'channel' database table. So, after backing up that table, I removed all of the duplicate entries, also making sure that my source #1 channels (the PVR card) didn't overlap the source #2 (the pcHDTV) Interestingly, the only two channels that had mplexid fields were 702 and 707, two channels that I had set up manually in previous steps. That's ok for now, though, if I have to add the others manually, I can live with that. > Make sure that there is a valid channel number in the startchan field (card > table?). Ah, for cardid #1 (the PVR card), there was a valid setting, but for cardid #3 (the pcHDTV card), there was nothing. I set it to 702, the first HD channel I can receive >The last piece of the puzzle was making sure the channels were assigned to a source in the channel config of mythtv-setup, then restart the backend. If any of these pieces are not in place, you get the famous 20 seconds of black screen, crashing backends, and meaningless error messages. I didn't check all of the channels, but I did make sure that 702 (my first HDTV channel) was set to a source that I'd previously set up in zap2it.com. > > The Myth database is not officially documented that I could find, and > additionally there are some deprecated tables left over from earlier > versions, so be wary of older postings and howtos. Here's were I found some > good information for MythTV >= 0.17: > http://www.ethics-gradient.net/myth/mythdvb2.html > > It addresses DVB-T, but it's applicable to ATSC. > > Richard. Well, I am at least getting a picture, but it is unwatchable :( The sound is nothing but static, and the picture is very choppy. After a few minutes, the mythfrontend process dies, and I have to kill it. In another terminal, I notice that CPU usage is pegged when playing back this content, even though my video card (nVidia 6200) is supposed to support on-the-fly MPEG decoding. Looks like I need to track this down, as well ... In my frontend logs, I'm seeing this line an awful lot: [mpeg2video @ 0x3795b4]MPEG motion vector out of boundary [mpeg2video @ 0x3795b4]mb incr damaged Could this have something to do with the bad output? Mark _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
