From: Jiri Slaby <jirislaby@gmail.com>
To: pfister@linuxtv.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: dvb-tools: scan_data/cz-all: 4th multiplex has FEC 3/4
Date: Thu, 06 Dec 2012 10:40:01 +0100 [thread overview]
Message-ID: <50C067F1.5010606@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 8 bytes --]
--
js
[-- Attachment #2: scan.patch --]
[-- Type: text/x-patch, Size: 1414 bytes --]
# HG changeset patch
# User Jiri Slaby <jirislaby@gmail.com>
# Date 1354786687 -3600
# Node ID c72238053530a0ad8e446af2cce0cb8d14c9640a
# Parent 96025655e6e844af2bc69bd368f8d04a4e5bc58b
scan_data/cz-all: 4th multiplex has FEC 3/4
Not 2/3. This I inappropriatelly got from the website. But it is
wrong. 3/4 is definitely correct. Change that so that we can actually
tune that multiplex.
diff -r 96025655e6e8 -r c72238053530 util/scan/dvb-t/cz-All
--- a/util/scan/dvb-t/cz-All Tue Jun 26 22:28:54 2012 +0200
+++ b/util/scan/dvb-t/cz-All Thu Dec 06 10:38:07 2012 +0100
@@ -42,11 +42,11 @@
T 778000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
T 786000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
# multiplex 4
-T 506000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
-T 546000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
-T 642000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
-T 658000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
-T 666000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
-T 754000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
-T 810000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
-T 818000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
+T 506000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
+T 546000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
+T 642000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
+T 658000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
+T 666000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
+T 754000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
+T 810000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
+T 818000000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
reply other threads:[~2012-12-06 9:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50C067F1.5010606@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=pfister@linuxtv.org \
/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).