From: Andrew Benham <adsb@adsb.co.uk>
To: Russel Winder <russel@winder.org.uk>
Cc: Andy Furniss <andyqos@ukfsn.org>,
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: Mon, 14 May 2012 12:54:27 +0100 [thread overview]
Message-ID: <4FB0F273.6000303@adsb.co.uk> (raw)
In-Reply-To: <1336921909.9715.3.camel@anglides.winder.org.uk>
Of course it's not just the data for the London transmitters which needs
to be updated - most of GB has now switched to digital only with
different channel allocations.
I've been using the information from
http://stakeholders.ofcom.org.uk/broadcasting/guidance/tech-guidance/dsodetails/
to derive new data.
I don't know if it's just Crystal Palace, but one of the multiplexes
thinks it's using QPSK even though it's using QAM64 - this messes up
'scan' unless one reorders the frequency list.
Having done the scan, one then needs to replace 'QPSK' by 'QAM_64' in
the output.
See also:
http://www.adsb.co.uk/linuxtv/
--
Andrew Benham, Southgate, London N14, United Kingdom
The gates in my computer are AND OR and NOT, not "Bill"
next prev parent reply other threads:[~2012-05-14 11:54 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
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 [this message]
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=4FB0F273.6000303@adsb.co.uk \
--to=adsb@adsb.co.uk \
--cc=669715-forwarded@bugs.debian.org \
--cc=andyqos@ukfsn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.