Hi Michael, Yeah you got me... I haven't got the mplayer setup yet... Anyway it's not hard though... but there are some glitches while mplay is using oss, it sometimes says device is busy (after fresh reboot), and it either output video with no sound for a few seconds or simply quit... but I used the alsa-oss wrapper script and it's working fine! It is great to see some output after all these efforts... I'll do some google on mythtv settings and try to locate the problem... Thank you very much. ~Guang From: Michael Krufky <mkrufky@xxxxxxxxx> To: Guang Zhu <zeegrr@xxxxxxxxxxx> CC: mkrufky@xxxxxxx, linux-dvb@xxxxxxxxxxx Subject: Re: [linux-dvb] Driver Help On DVICO FusionHDTV5 Lite Date: Thu, 29 Dec 2005 13:09:39 -0500 On 12/29/05, Guang Zhu <zeegrr@xxxxxxxxxxx> wrote: > Thanks Michcael, that worked. Now I have the correct devices, and I can do > channel scanning with mythtv-setup (also with atscscan), but the problem is > when I use mythfilldatabas, it gave following message at the end: > > 2005-12-29 10:48:35.962 Connecting to backend server: 127.0.0.1:6543 (try 1 > of 5) > Connection timed out. > You probably should modify the Master Server settings > in the setup program and set the proper IP address. > error resceduling id -1 in ScheduledRecording::signalChange > > But according to the instruction, I am supposed to run mythfilldatabase > prior to mythbackend, right? I actually see some channel entries in mysql, > but when I start mythbackend, it says > > 2005-12-29 10:49:10.369 DVB#0 ERROR - Unable to find channel in database. > 2005-12-29 10:49:10.369 DVB#0 ERROR - Failed to get channel options for > channel 3. > > And when I start mythfrontend, and start watching, it says > > 2005-12-29 10:52:39.929 DVB#0 WARNING - No data from card in 1 second. > 2005-12-29 10:52:39.995 Couldn't read data from the capture card in 15 > seconds. Stopping. > > I tried using azap on the frequencies from the output of atscscan, but it > says > > video pid 0x0000, audio pid 0x0000 > status 00 | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | > status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | > FE_HAS_LOCK > status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00002735 | > FE_HAS_LOCK > status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | > FE_HAS_LOCK > status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | > FE_HAS_LOCK > status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | > FE_HAS_LOCK > status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | > FE_HAS_LOCK > > So I am not sure that if this is still a driver issue or something wrong the > settings? Thanks NOT A DRIVER ISSUE! The output from azap indicates that everything is working properly... Your problem is in your mythtv setup -- I cant help you with that here, it's off-topic.... There's a mythtv-users mailing list - you can ask for help there. Meanwhile, here's a way to test your card... you already have azap running.... keep it running, but be sure to use the -r parameter: azap WABC_HD -r ... It should report : FE_HAS_LOCK ... do not kill it... Open up another shell, and run: mplayer /dev/dvb/adapter0/dvr0 -cache 8192 -framedrop This will show the stream on your screen..... (use man mplayer to learn about the other command-line arguments -- you do not need to use -cache 8192 or -framedrop, but these are needed on some slower systems) This WILL work.... (unless you dont have mplayer installed) Cheers, Mike Krufky
