I don't usally do this, but I'm going to repost something I posted
over on the Myth-Users list:
----------------------
First off, try these directions, if you haven't already:
http://www.rsmas.miami.edu/personal/angel/mythtv/air2pc-howto.html
They were the foundation i started with to make mine work (FC3,
Air2PC, Myth 0.17)
I ran into the permissions thing as well, and once I got the DVB
driver loading correctly at boot, they all went away.
Second, working with HD channels is REALLY messed up right now. Badly.
Even in the latest CVS. It took me most of (2) days to get mine
right.. Here's what turns out the be the recipe to success, at least
for me.
1. Run the channel search in the mythv-setup program (also found in
/usr/src/mythtv/setup/setup if you checked out from CVS and put it in
/usr/src). Let it add ALL the channels it finds. This is the only
place you're going to get ASTC information the backend needs to tune.
2. Go create an HD specific profile on Zap2IT for the channels you
want to use. Map that profile to the HD card. Run mythfilldatabase to
get some data in.
3. Open the channel editor in mythweb, and start carving up. Important
things are XMLID's (for program data) ATSC PID information. I did a
little bit in phpmysql as well, but when I was done I'd combined all
the right things from the channel search and zap2it. Basically I took
the ATSC info, and moved it into the Zap2it channel entries, and then
made all my "searched" channels not visible. if you remove a channel
from either listing, it gets added back, either when you run
mythfilldatabase, or run a channel search again, so it's better to
leave it there, but not visible.
Let me know how this goes, I'm happy to help a fellow air2pc'r.
On Fri, 25 Feb 2005 08:42:51 +0100, Niklas Peinecke <n.peinecke at web.de> wrote:
> Hello Clemens,
>> let me first state, that I have no idea about ATSC, but I think I could
> give you some assistance.
>>clemens at dwf.com wrote:
> [...]
> > and I get
> >
> > [root at mythtv .azap]# more /root/.azap/channels.conf
> > KNME:599000000:8VSB:0:0
> > KASA:551000000:8VSB:0:0
> > KASY:659000000:8VSB:0:0
> > KWBQ:563000000:8VSB:0:0
> > KRQE:485000000:8VSB:0:0
> > KOAT:515000000:8VSB:0:0
> > KOB:545000000:8VSB:0:0
> > KLUZ:641000000:8VSB:0:0
> > KNAT:533000000:8VSB:0:0
> > KNMD:189000000:8VSB:0:0
> > KAZQ:491000000:8VSB:0:0
> > KCHF:195000000:8VSB:0:0
> >
> > The channels found, and there frequencies are correct, but I dont
> > know what the :8VSB:0:0 is trying to tell me.
> >
> > Anyone? Jump right in here...
>> Well, I think 8VSB is something technical for ATSC, but the two numbers
> should be the video and the audio PID (see below).
>> >
> > All of the stations broadcast from the top of Sandia Peak, about
> > 5 miles away and 5000 ft higher than we are here in the city, so
> > the signal strength is high for all of them.
> >
> > Choosing just one at random, I see:
> >
> > [root at mythtv ~]# azap kob
> > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> > tuning to 545000000 Hz
> > video pid 0x0000, audio pid 0x0000
> > status 1f | signal fad0 | snr dbaa | ber 00007ff8 | unc 00000000 |
> > FE_HAS_LOCK
> > status 1f | signal fa60 | snr da90 | ber 000003e0 | unc 00000000 |
> > FE_HAS_LOCK
> > status 1f | signal fab0 | snr dcc4 | ber 00000898 | unc 00000000 |
> > FE_HAS_LOCK
> > status 1f | signal faf0 | snr dbaa | ber 00000860 | unc 00000000 |
> > FE_HAS_LOCK
> > status 1f | signal fab0 | snr d8ba | ber 000009b0 | unc 00000000 |
> > FE_HAS_LOCK
> > status 1f | signal fa20 | snr da32 | ber 000007e8 | unc 00000000 |
> > FE_HAS_LOCK
> >
>> This looks good.
>> [...]
> >
> > 2005-02-24 17:49:27.975 DVB#0 AutoPID Complete - PAT/PMT Loaded for service
> > 2005-02-24 17:49:27.975 DVB#0 Service is FTA
> > 2005-02-24 17:49:27.975 DVB#0 ERROR - No PIDS set, please correct your
> > channel setup.
> > 2005-02-24 17:49:28.988 DVB#0 WARNING - No data from card in 1 second.
> >
> > No idea what AutoPID is trying to do, and I have no Idea what to do to respond
> > to
> >
> > ERROR - No PIDS set, please correct your channel setup.
> >
> > on the third line.
> >
> > ---
> >
> > So what have I missed?
> > Whats my next step?
> >
> > I have seen the PID thing mentioned, but with no real example of what is needed
> > to fix the problem. This wasn't something I saw with the other cards and the
> > other drivers...
>> PIDs are identification numbers that tell the software, where to expect
> audio and video data in the transport stream (a TS can contain many of
> them, so one needs to know, which to select). For some reason your
> initial scan set these two PIDs to 0 which is not correct. If you can
> find out the PID numbers from some other source (maybe windows or the
> net) you can enter them manually, then tuning should work.
>> However I have no idea, why scan might fail.
>> Good luck,
>> Niklas
>> _______________________________________________
> linux-dvb mailing list
>linux-dvb at linuxtv.org>http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb>