From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-media@vger.kernel.org
Cc: stoth@kernellabs.com
Subject: Re: HVR-1600 QAM recordings with slight glitches in them
Date: Wed, 02 May 2012 23:29:57 -0400 [thread overview]
Message-ID: <4FA1FBB5.8050106@interlinx.bc.ca> (raw)
In-Reply-To: <CAGoCfiwB2jZfeZ2aSQ7FSG-k5XDGJY_ykLPSD3Y3rbrUXmuOdg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]
On 12-04-29 08:09 PM, Devin Heitmueller wrote:
>
> I don't know why you're not seeing valid data on femon with the 950q.
> It should be printing out fine, and it's on the same 0.1 dB scale.
> Try running just azap and see if the SNR is reported there.
$ azap -c ~/last-channel-scan.prev 100-3
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 651000000 Hz
video pid 0x0000, audio pid 0x07c1
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 1f | signal 0000 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
...
Doesn't seem to be useful values.
> This indeed feels like a marginal signal condition problem, and Andy's
> assertion is well founded that the mxl5005/s5h1409 isn't exactly the
> best combo compared to more modern tuners and demodulators (Hauppauge
> switched to the tda18271 and s5h1411 for the newer revision of the
> HVR-1600).
Well, now that the coax connector has come loose on the digital tuner
(i.e. it spins albeit with enough friction that screwing a coax connector
on and off is still quite doable but it would seem spins enough to have
broken the connection internally and thus the tuner no longer receives
signal) maybe it's time to cut my losses here and just consider this
HVR-1600 garbage. I've wasted more than enough time on what's turned
out to just be marginal hardware. ~sigh~
I wonder if I can still find the supported hardware rev. of the KWorld
UB-435 around anywhere. The local computer store has one for $40 but
they have no way of telling me if it's the new hardware rev. or the old
one.
Cheers,
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-05-03 3:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 3:30 HVR-1600 QAM recordings with slight glitches in them Brian J. Murrell
2012-04-24 22:42 ` Andy Walls
2012-04-25 3:07 ` Brian J. Murrell
[not found] ` <1335624964.2665.37.camel@palomino.walls.org>
2012-04-28 18:08 ` Brian J. Murrell
2012-04-28 21:48 ` Andy Walls
2012-04-28 18:36 ` Brian J. Murrell
2012-04-28 20:39 ` Brian J. Murrell
2012-04-28 22:21 ` Brian J. Murrell
2012-04-29 7:02 ` Rudy Zijlstra
2012-04-29 15:27 ` Brian J. Murrell
[not found] ` <CAAMvbhH2o6SZVBU4D2dvUUVuOhtzLdO-R=TCuug7Y9hgZq2gmg@mail.gmail.com>
2012-04-30 0:09 ` Devin Heitmueller
2012-05-03 3:29 ` Brian J. Murrell [this message]
[not found] ` <CAGoCfiy2-93qxtZJrOf40NBVkimBwQr6wDsThiCTMoPM8mFyeQ@mail.gmail.com>
2012-05-03 12:16 ` Devin Heitmueller
2012-05-03 12:18 ` Devin Heitmueller
2012-05-03 15:37 ` Andy Walls
2012-05-03 16:06 ` Brian J. Murrell
2012-05-03 16:51 ` Devin Heitmueller
2012-04-28 21:57 ` Andy Walls
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=4FA1FBB5.8050106@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=linux-media@vger.kernel.org \
--cc=stoth@kernellabs.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.