From: Andy Furniss <andyqos@ukfsn.org>
To: Russel Winder <russel@winder.org.uk>
Cc: Mark Purcell <mark@purcell.id.au>,
linux-media@vger.kernel.org,
Darren Salt <linux@youmustbejoking.demon.co.uk>,
669715-forwarded@bugs.debian.org
Subject: Re: Fwd: Bug#669715: dvb-apps: Channel/frequency/etc. data needs updating for London transmitters
Date: Sun, 13 May 2012 15:23:06 +0100 [thread overview]
Message-ID: <4FAFC3CA.7070008@ukfsn.org> (raw)
In-Reply-To: <1336906328.19220.277.camel@launcelot.winder.org.uk>
Russel Winder wrote:
> On Sun, 2012-05-13 at 11:15 +0100, Andy Furniss wrote:
> [...]
>> Transmission mode changed from 2k to 8k in the uk after analogue switch off.
>
> Of course. I just failed to make that change in my files. With that
> changed I got some response from gnome-dvb-setup but it only analysed
> one multiplex.
>
>> Chris Rankin already posted UK, Crystal Palace on here.
> [...]
>> T 490000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE # London .
>> T 514000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE # London .
>> T 545833330 8MHz 2/3 NONE QAM256 AUTO AUTO AUTO # London .
>> T 482000000 8MHz 3/4 NONE QAM64 8k 1/32 NONE # London .
>> T 506000000 8MHz 3/4 NONE QAM64 8k 1/32 NONE # London .
>> T 529833330 8MHz 3/4 NONE QAM64 8k 1/32 NONE # London .
>
> Should that be 545833000 instead of 545833330, and 529833000 instead of 529833330?
>
Possibly - I think if you calculate by hand from channel number and add
or take the offset if it it <channel>+ or - then you do get the extra 33.
I don't live in London, but using a slightly newer w_scan for my
transmitter gave different output from that, with the 330 -> 000.
Maybe it depends on the device, mine was a DVB T2 pctv nanostick and gave -
#------------------------------------------------------------------------------
# file automatically generated by w_scan
# (http://wirbel.htpc-forum.de/w_scan/index2.html)
#! <w_scan> 20120128 1 0 TERRESTRIAL GB </w_scan>
#------------------------------------------------------------------------------
# location and provider: Tacolneston UK
# date (yyyy-mm-dd) : 2012-03-10
#
# T[2] [plp_id] [system_id] <freq> <bw> <fec_hi> <fec_lo> <mod> <tm>
<guard> <hi> [# comment]
#------------------------------------------------------------------------------
T 642000000 8MHz 2/3 NONE QAM64 8k 1/32 NONE # East Anglia
T 745833000 8MHz 2/3 NONE QAM64 8k 1/32 NONE # East Anglia
T 777833000 8MHz 2/3 NONE QAM64 8k 1/32 NONE # East Anglia
T 666000000 8MHz 3/4 NONE QAM64 8k 1/32 NONE # East Anglia
T 706000000 8MHz 3/4 NONE QAM64 8k 1/32 NONE # East Anglia
T2 0 16417 802000000 8MHz AUTO AUTO AUTO AUTO AUTO AUTO # East
Anglia
next prev parent reply other threads:[~2012-05-13 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 10:05 Fwd: Bug#669715: dvb-apps: Channel/frequency/etc. data needs updating for London transmitters Mark Purcell
2012-05-13 10:15 ` Andy Furniss
2012-05-13 10:52 ` Russel Winder
2012-05-13 14:23 ` Andy Furniss [this message]
2012-05-13 15:11 ` Russel Winder
2012-05-13 16:07 ` Andy Furniss
2012-05-13 16:55 ` Andy Furniss
2012-05-14 11:54 ` Andrew Benham
2012-05-17 20:22 ` Thomas Kernen
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=4FAFC3CA.7070008@ukfsn.org \
--to=andyqos@ukfsn.org \
--cc=669715-forwarded@bugs.debian.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@youmustbejoking.demon.co.uk \
--cc=mark@purcell.id.au \
--cc=russel@winder.org.uk \
/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).