From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-media@vger.kernel.org
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>, stoth@kernellabs.com
Subject: Re: HVR-1600 QAM recordings with slight glitches in them
Date: Thu, 03 May 2012 12:06:46 -0400 [thread overview]
Message-ID: <4FA2AD16.6080807@interlinx.bc.ca> (raw)
In-Reply-To: <e2d13409-d6fc-47aa-9597-727dd6f7c3ec@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
On 12-05-03 11:37 AM, Andy Walls wrote:
> Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
>>
>> Also, which version of the HVR-1600 is this? The one with the
>> mxl5005s or the tda18271? You can check the dmesg output to tell (and
>> if you cannot tell, please pastebin the dmesg output so I can look).
http://brian.interlinx.bc.ca/hvr-1600-dmesg
> IIRC, Brian had a MXL5005s/S5H1409 variant.
The latter part sounds familiar from femon and gnutv.
> I think Brian might have a bad cable or connector or splitter in the run feeding the hvr1600.
The same 4-way splitter fed the HVR-950Q and the HVR-1600 and cables
were swapped just about every way they could be to try to get the
HVR-1600's SNR up.
But as I mentioned before, it's now completely non-functional due to the
coax connector on the card having become loose enough to turn (with some
effort, so screwing an female F-connector on/off was still quite
doable). Perhaps it was marginal before due to that same problem. I
guess I will never know... unless I try cracking this thing open and
reconnecting whatever has gotten disconnected -- if Hauppage won't RMA
it for me. They seem to be pretty silent about that now though after an
initial e-mail exchange.
If not, I've got my eye on a KWorld UB435-Q if I can determine that it's
a hardware rev. 1 unit somehow since the store doesn't want to take it
out of the box to check for me. It's less than half the price of an
HVR-950Q at $40, as much as I would love to stay loyal with Hauppage --
this coax connector on my HVR-1600 coming loose, aside.
Cheers,
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-05-03 16:07 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
[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 [this message]
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=4FA2AD16.6080807@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=dheitmueller@kernellabs.com \
--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.