From: Steven Toth <stoth@kernellabs.com>
To: Alex Ferrara <alex@receptiveit.com.au>
Cc: linux-media@vger.kernel.org
Subject: Re: HVR-2200 Australia DVB-T
Date: Tue, 15 Sep 2009 09:34:09 -0400 [thread overview]
Message-ID: <4AAF97D1.8030905@kernellabs.com> (raw)
In-Reply-To: <CED52FAC-4C8D-416C-B00E-5662F1F63E85@receptiveit.com.au>
> WIN TV
> Canberra:767500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:33:36:1
> root@kaylee:~/.tzap# tzap "WIN TV Canberra"
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> reading channels from file '/root/.tzap/channels.conf'
> tuning to 767500000 Hz
> video pid 0x0021, audio pid 0x0024
> status 00 | signal a9a9 | snr 002e | ber 0000ffff | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 0000ffff | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 0000ffff | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 0000ffff | unc 00000000 |
>
> Any help would be appreciated.
Sounds like a tuning issue. Either the Antenna is bad or the channels.conf
doesn't represent the actual center frequency or the channel or the tuner /
demod code is buggy.
Other people are having success with DVB-T HVR2200 so it's either a bug that
gets exposed by your environment or something else. mkrufky has some tuner
improvements pending for merge which are not in the saa7164 tree yet, you might
want to hold for a few days for these.
The other thing to double check is that the freqs in your channels conf do
actually represent the center of the DVB-T channel. I suspect they do, but
double check for good measure using the official Australian DVB-T antenna docs.
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2009-09-15 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 10:32 HVR-2200 Australia DVB-T Alex Ferrara
2009-09-15 13:34 ` Steven Toth [this message]
2009-09-27 12:14 ` Alex Ferrara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAF97D1.8030905@kernellabs.com \
--to=stoth@kernellabs.com \
--cc=alex@receptiveit.com.au \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox