<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
An update since these series of messages.<br>
* I can now view hdtv OTA programs in Myth using the HD3000.<br>
* I can now load the cx88-dvb drivers from boot.<br>
<br>
I had two main problems for these symptoms: I didn' know which drivers
to use for the HD3000 and when I could load them manually, I still had
problems viewing them in MythTV and mplayer (using the
~.azap/channels.conf file.). mplayer worked much better, though, then
MythTv. This complicated matters.<br>
<br>
======================<br>
The first problem was solved by reading:<br>
<a class="moz-txt-link-freetext" href="http://pchdtv.com/forum/viewtopic.php?t=1041&highlight=dtvsignal+build">http://pchdtv.com/forum/viewtopic.php?t=1041&highlight=dtvsignal+build</a><br>
<br>
The key for me was to reorder cx88-dvb to come before cx88-blackbird <span
class="postbody">in /lib/modules/<kernel ver>/modules.pcimap.<br>
After I reorderd and commented out ALL cx88... lines in modprobe, dvb
drivers loaded fine.<br>
<br>
Note that before I also found a thread (don't have the reference) that
indicated to:<br>
cp -r /dev/dvb/* /etc/udev/devices/<br>
so that the adapter0 directory and it's files would exist at startup.
Don't know if this makes a difference, but I did copy them.<br>
</span><br>
======================<br>
The second problem was actually several problems.<br>
<br>
---<br>
1. Channels and Scanning - <br>
I created another Zap2It profile for OTA ATSC channels in my area (in
addition to my analog cable one.) I just picked all of the ATSC
channels in my area and no others.<br>
<br>
In mythtv-setup I asked it to clear the channels database which went
fine. I then scanned channels for the PVR-250 (which is connected to
analog cable - comcast) - no problem. I then scanned for OTA ATSC for
the HD3000 which also went fine. <br>
<br>
After exiting mythtv-setup, I ran mythfilldatabase. It completed both
the cable NTSC dB and the OTA ATSC dB fine. However, it created a
completely separate ATSC listings than the scanned channels (the cable
NTSC filled fine.) So, I was left with duplicate channels: the scanned
channels from the channel scan in mythtv-setup and the downloaded
listings from Zap2It. To be more precise, most of the channels were
duplicated, but some were not. This is because some of the channels
that I checked off in Zap2It were not found when scanning in
mythtv-setup.<br>
<br>
How to resolve this? I found this thread:<br>
<a class="moz-txt-link-freetext" href="http://www.gossamer-threads.com/lists/mythtv/users/149939?search_string=tune%20atsc%20OTA;#149939">http://www.gossamer-threads.com/lists/mythtv/users/149939?search_string=tune%20atsc%20OTA;#149939</a><br>
where jason beck has a recipe for filling the correct freqid, mplexid
and serviceid in the channel table in mysql dB.<br>
This gave me a clue on where to look and how to resolve the two
listings.<br>
Instead of running mysql command line, I instead used:<br>
MySQL Query Browser<br>
from :<br>
<a class="moz-txt-link-freetext" href="http://www.mysql.com/products/tools/">http://www.mysql.com/products/tools/</a><br>
This is much handier than the command line. You can easily copy and
paste between tables.<br>
In a nutshell, I took the content of the "frequency" record from the
dtv_multiplex table and using the mplexid as key copied it to "freq_id"
in the channel table. The channels that were scanned in mythtv-setup
had mplexid, serviceid and atscid filled in already. But, the freq_id
was not. <br>
I then made sure that these same records were filled in for the
channels that were downloaded from Zap2It.<br>
<br>
That left me with duplicate ATSC channels in the mythtv database with
freq_id, serviceid, atscid identical. I also copied the xmltvid from
the dnl'd Zap2It channels to the scanned channels. I tried to fill in
as much as I could for the duplicate channels (renaming one set of
channles so I could tell them apart in the channel guide.) I ran
mythfilldatabase and the scanned channels (which didn't have any
listings) were filled with data.<br>
<br>
However, I do not know if there is more to do in the mysql database or
not.
LiveTV does work and I can flip between channels (except for a problem
that I note below.) If there are other records that I need to copy,
please let me know.<br>
<br>
One thing that I SHOULDN'T have done was to select ALL of the ATSC
channels in Zap2It. Instead, I should have checked off only the
channels that I was able to receive at my home when checking channels
with mplayer and the ~/.azap/channels.conf. However, I didn't know
which ones because of the next problem below. I would suggest that if
you are at this point, try to obtain each of your channels clearly in
mplayer first. Then, check the ones that you can receive (and want to
receive) online at Zap2It before you run mythfilldatabase.<br>
<br>
---<br>
2. Antenna amp: When checking channels with mplayer, some worked some
of the time and some were a mess... basically it seemed to be a crap
shoot.<br>
Well... my Antenna amplifier has an FM Trap that was not engaged. When
I switched it on, BINGO, channels popped in and it made the debugging a
bit easier... to say the least. I was then able to go thru each channel
using:<br>
<br>
mplayer dvb://<channel_name><br>
<br>
to check for reception. (just cp ~/.azap/channels.conf
~/.mplayer/channels.conf to make this handy feature work)<br>
<br>
=======================<br>
Continued Problems:<br>
<br>
--<br>
Duplicate channels: <br>
Yeah.. I have duplicate channels in the EPG, but I don't which ones I
should delete. I don't know if I filled in all the necessary records in
the channel table and don't know how this table relates to dtv_signal
table. The way I figured I find out is to actually flip thru the
channels in LiveTV to see what works.<br>
<br>
--<br>
LiveTV Channel Scanning:<br>
But, when I switch channels it seems that MythTV randomly picks the
next channel. For instance I have these channels in the program listing:<br>
2_1#<br>
2_2#<br>
2-1<br>
4_1#<br>
4_2#<br>
4-1<br>
4-2<br>
5_1#<br>
5-1<br>
7_1#<br>
7_2#<br>
7-1<br>
7-2<br>
etc...<br>
<br>
switching up from 2_1# sometimes I get 4_1#, sometimes I get 4-1 and
sometimes 4-2. There doesn't seem to be any reasoning behind it.<br>
<br>
Since there doesn't seem to be any reason, I don't know which ones to
delete.<br>
<br>
--<br>
Sub-channels:<br>
How do you switch from something like 4-1 to 4-2?<br>
<br>
--<br>
Segfault<br>
Seems that if I tune to a atsc channel that doesn't come in well,
mythfrontend will segfault and the backend crashes too.<br>
<br>
All in all, I'm now doing pretty well. I still have to load lircd in
rc.local like this:<br>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Kate, the KDE Advanced Text Editor">
<br>
/sbin/service lircd stop<br>
usleep 1000000<br>
/sbin/depmod -a<br>
usleep 1000000<br>
/sbin/modprobe lirc_i2c<br>
usleep 1000000<br>
/sbin/service lircd start<br>
<br>
I don't know why it doesn't start up at boot. But, HD3000 is working
pretty well. Yeah!<br>
<br>
brad<br>
<br>
</body>
</html>