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: Sat, 28 Apr 2012 14:36:46 -0400 [thread overview]
Message-ID: <4F9C38BE.3010301@interlinx.bc.ca> (raw)
In-Reply-To: <1335624964.2665.37.camel@palomino.walls.org>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
One more question...
On 12-04-28 10:56 AM, Andy Walls wrote:
>
> So I see SNR values from 0x138 to 0x13c ( 31.2 dB to 31.6 dB ) when you
> have problems. For 256-QAM cable signals, I think that is considered
> marginal.
I've never gotten my mind around SNRs and dBs, etc. Generally speaking,
am I looking for these "snr" values to go up or down (i.e. closer to 0
or further away) to make my signal better?
Cheers,
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-04-28 18:37 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 [this message]
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
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=4F9C38BE.3010301@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 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).