From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Maury Markowitz <maury.markowitz@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: dtv-scan-table has two ATSC files?
Date: Thu, 10 Dec 2015 07:57:33 -0200 [thread overview]
Message-ID: <20151210075733.4abdcd16@recife.lan> (raw)
In-Reply-To: <BF55C1DA-2E39-4ACA-92C0-4E512E10196F@gmail.com>
Em Wed, 9 Dec 2015 20:04:57 -0500
Maury Markowitz <maury.markowitz@gmail.com> escreveu:
> I’m making some updates to the ATSC dtv-scan-tables. Two questions:
>
> 1)
> Why do we have "us-ATSC-center-frequencies-8VSB” *and* "us-NTSC-center-frequencies-8VSB”? They appear to be identical. The later could, theoretically, list NTSC encoded channels instead of 8VSB, but doesn’t actually do that. Suggest removing it?
Hmm... maybe we could, instead, keep one of them as a "complete" ATSC
possible channel list, and the other ones with the unregulated channels
stripped.
>
> 2)
> A number of the channel listings in those files have not been used for television use for several years now. Specifically channels 2 to 6 and everything from 51 and up were long ago sold off to cell phone use.
>
> Additionally, channel 37 was *never* used, at least in the US and Canada, because it interfered with radio astronomy (IIRC it was sitting on one of the Lyman lines).
For terrestrial TV, those are unused, but perhaps the ATSC/NTSC
channeling might still be used by some cable operator.
Also, those channeling files work on other Countries outside America,
like South Korea.
>
> Since scanning through all of these channels will no longer work, perhaps it would be time to remove them? It reduces the total scan list from 80 channels to only 45, and would greatly improve scan times.--
I rename one of the files to "us-ATSC-T-center-frequencies-8VSB" with just
the channels that are actually regulated for terrestrial (air) broadcast,
and keep the other file renamed to let is be clearer. Something like:
"us-ATSC-C-center-frequencies-8VSB" or even keeping it named as
"us-NTSC-center-frequencies-8VSB".
Regards,
Mauro
next prev parent reply other threads:[~2015-12-10 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 3:49 DVBSky T980C ci not working with kernel 4.x Nibble Max
2015-12-08 22:06 ` Torbjorn Jansson
2015-12-09 19:03 ` Timo Helkiö
2015-12-10 1:04 ` dtv-scan-table has two ATSC files? Maury Markowitz
2015-12-10 9:57 ` Mauro Carvalho Chehab [this message]
2015-12-10 12:22 ` Maury Markowitz
2015-12-10 2:47 ` [PATCH] us-ATSC-center-frequencies-8VSB: Added channel numbers in comments to make the file easier to use by comparing against local channel lists Maury Markowitz
2015-12-10 10:05 ` Mauro Carvalho Chehab
2015-12-10 12:44 ` [PATCH 2] ca-ON-Toronto: adding scan file for Toronto, Canada, added channel numbers Maury Markowitz
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=20151210075733.4abdcd16@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=maury.markowitz@gmail.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