The MythTV setup is working pretty well. Other than a few remaining configuration issues, my only problem has been that fairly often, the video data feed fails. The error message I get is: DVB#0 Data read from DMX - This is for debugging with transform.c That message is from mythtv (dvbrecorder.cpp), where it is trying to read from the DVB stream. Does this happen with other DVB cards (is it a MythTV issue, or could this be something related to the driver)? Also -- I ended up getting the last channel added to my MythTV configuration by editing MythWeb to include three more attributes that needed to be configured: mplexid, serviceid, and atscsrcid. Once I figured out the settings, and edited them in MythWeb, I was able to tune the channel I wanted. -Todd On 7/12/05, Todd Ignasiak <ignasiak@xxxxxxxxx> wrote: > Okay, I was able to get the FusionHDTV stuff working with QAM256, and > with MythTV. > > For QAM, I just switched my cable to the other RF input. Apparently > the OTA/Cable association with the inputs is just a function of the > Fusion Windows software. After doing a full ATSC scan, I did a > QAM256 scan, and it recognized most of my channels. > > After tweaking around with the MythTV channel configuration a bit, I > still don't understand it.. but it's working. I just manually > entered the frequencies associated with the various QAM channels (I > used the Mythweb UI, but it could probably be done in other ways). > Also, make sure the "Starting Channel" is defined as a valid channel > number when setting up the input connection. If it's not a valid > channel, MythTV doesn't give any decent feedback, it just shows black > screen. > > > The QAM channel scan in MythTV picked up most of my available HD > channels, which are just retransmissions of the OTA ATSC channels > (PSIP data and all). So, MythTV sees the channel, including the call > letters and subchannels. There are also a couple non-ATSC, but > unencrypted, channels on my local cable system, such as ESPN-HD. The > channel scan did not pick these up, so I need to figure out how to > manually add them. > > > -Todd > > BTW -- The MythTV channel configuration is _terrible_. I hope it's > not so bad when dealing with standard NTSC or PAL broadcasts. I > wish they would use an easier config format for the basic system > config stuff, like a simple text file. I'm sure the MySQL stuff is > great for guide data, but for application config it just makes > everything overly complex. (sorry, just had to rant a bit after > struggling with this stuff.. I know this is not a MythTV list..) > > On 7/12/05, Todd Ignasiak <ignasiak@xxxxxxxxx> wrote: > > I stuck with the mm1 kernel (which included the qam256 initialization patch). > > > > I'm still trying to figure out all the channel config stuff. But, I > > downloaded the dvb-utils, and used azap, dvbtraffic, and dvbscan to > > test it. Then, I captured a sample using: > > > > cat /dev/dvb/adapter0/dvr0 > test.ts > > > > I used vlc to check the output, and I had a perfect segment of "The Cosby Show"! > > > > So, it seems to be basically working.. I just need to get up to speed > > on the configuration and usage of the various apps. I'll keep > > playing around with it, and MythTV, to see what I can get functioning. > > > > > > Also - the capture I got was from an ATSC OTA signal, not QAM256. > > I'll also try that out, to see if I can figure out switching between > > the two RF inputs, etc. > > > > Thanks, > > Todd > > > > On 7/12/05, Michael Krufky <mkrufky@xxxxxxx> wrote: > > > Todd: > > > > > > I am CC'ing this to the linux-dvb list. In the future, please cc this > > > stuff to the list, as this information could help other people. If you > > > are not subscribed to the list, I highly recommend it. > > > > > > Todd Ignasiak wrote: > > > > > > >I built the rc2-mm1 kernel last night (with the TS patch from last > > > >night applied). I will build the mm2 kernel today. > > > > > > > > > > > If you already have applied the > > > dvb-lgdt3302-qam256-initialization-fix.patch, then don't bother with > > > -mm2 ... There is another bug in -mm2 that requires the patch in the > > > video4linux tree (from my previous email) in order for anything to > > > work. You have nothing to gain from -mm2 besides the > > > dvb-lgdt3302-qam256-initialization-fix.patch. > > > > > > >With the mm1 kernel, I was able to get some success. The MythTV > > > >channel scan worked for ATSC OTA channels (the scan showed the channel > > > >names from the PSIP data). But, I was not able to actually view > > > >anything yet. I'm a MythTV newbie, so I'm still trying to figure > > > >out all the Myth stuff to determine what is working & what is not. > > > > > > > > > > > I can't get mythtv to work with my board at all... I haven't had a > > > chance to mess with it yet. I have been putting off re-partitioning my > > > hard drive in order to install debian sarge. Hopefully mythtv will be > > > easier to deal with once I get around to that. I have been testing > > > using a combination of azap and mplayer. Xine has given me successfull > > > results as well (but no audio). If you need directions on how to run > > > this, let me know. > > > > > > >Also, one quick question on the Fusion -- In the Windows software, > > > >it treats one RF input as OTA and the other as Cable, and they must be > > > >connected appropriately. With your driver, is there a hard > > > >association between the RF input and the type? I didn't see any way > > > >in MythTV to specify which RF input into the tuner should be used. > > > > > > > Does your board have TWO coaxial input jacks? I think that you have the > > > Gold-Q board. My Gold-T board only has one coax input... I don't have > > > the answer for you on this one... maybe someone else knows, or you might > > > be able to ask the mythtv guys. If you find the answer, please let us > > > know ;-) > > > > > > -- > > > Michael Krufky > > > > > > > > > > > >
