linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-media@vger.kernel.org,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	stoth@kernellabs.com
Subject: Re: HVR-1600 QAM recordings with slight glitches in them
Date: Sun, 29 Apr 2012 09:02:46 +0200	[thread overview]
Message-ID: <4F9CE796.2030004@grumpydevil.homelinux.org> (raw)
In-Reply-To: <4F9C6D68.3090202@interlinx.bc.ca>

On 29-04-12 00:21, Brian J. Murrell wrote:
> On 12-04-28 04:39 PM, Brian J. Murrell wrote:
>> I typically have one more splitter downstream from that 3 way splitter
>> which is a 4 way splitter to feed all of the tuners on my Mythtv box and
>> introducing that splitter reduces the SNR at the HVR-1600 to between
>> "13c" and "13e" (31.6 - 31.8 dB).
> Interestingly enough, I moved the Myth backend to it's usual home, in
> the basement, right next to the incoming cable signal and replaced that
> 25' run that I had going to where it was temporarily with a smaller, say
> 10' run (of RG-59 so still room for improvement) and my SNR at the
> HVR-1600, even after all of the splitters is now "015c" or 34.8 dB.
>
> I'm still going to go replacing all of that RG-59 with shorter, custom
> made lengths of RG6 cables.  I can't go "too short" when making those
> can I or would even a 6-12 inch cable be perfectly fine?  I'm thinking
> of the runs between that last 4 way splitter and the tuners in the Myth
> backend.
>
> b.
>
Brian,

There is no minimum cable length for RF. Although for practical reasons 
i rarely go below 30 cm (1 ').
It should be possible for you to buy "drop cables" which have a length 
of 1m5 (about 5') and are commonly used in HE to connect equipment.

screw-on F-connectors are another source of problems. Crimping 
F-connectors are best, but those need a fitting crimp tool.

Cheers,


Rudy

  reply	other threads:[~2012-04-29  7:25 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 [this message]
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
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=4F9CE796.2030004@grumpydevil.homelinux.org \
    --to=rudy@grumpydevil.homelinux.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).