All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Stoeber <tobi@to-st.de>
To: linux-media@vger.kernel.org
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Upcoming DVB-T channel changes for HH (Hamburg)
Date: Tue, 27 Jan 2009 13:09:22 +0100	[thread overview]
Message-ID: <497EF972.6090207@to-st.de> (raw)
In-Reply-To: <19a3b7a80901270237n761240bbn2627f782ddbffa29@mail.gmail.com>

Hi Christoph,

Just had a look at your zip archive and the files.

Christoph Pfister schrieb:
> I've updated my de-files:
> - fixed the url (inserted the wrong one by accident)
> - fixed vhf channels (they were using 8mhz because my trigger was wrong)
> - add the the "# CHxy: name of programs" information
> - 563 MHz --> 562 MHz (their pdf seems to use a wrong frequency for channel 32)

You are right. 562 MHz as nominal frequency is correct, because for 
DVB-T this is calculated 306 MHz + channel number x 8 MHz. VHF would be 
142.5 MHz + channel number x 7 MHz.

It's just a centre frequency used for tuning purposes. The DVB-T signal 
should (ideally) use a 8 MHz width space from 559.25 MHz to 567.25 MHz 
for Ch 32.

> But I haven't looked at the new documents proposed in this thread yet.

I didn't compare that either. Could also be difficult, because of 
different revision dates.

Looking through your files in the zip archive, it rose some questions in 
my mind:

a) is it really useful to have scan files by federal state (Bundesland)?

Just let me explain with an example. I live in Sachsen-Anhalt on the 
north of the Harz Mountains area. To effectivly ("best") use DVB-T I do 
combine both transmitters in Sachsen-Anhalt (Mt. Brocken) and from 
Niedersachsen (Braunschweig). This is because some channels are only 
available from a specific transmitting site (private channels only from 
Braunschweig, RBB only from Brocken). The same applies to other regions 
in Sachsen-Anhalt (south east will have reception from Sachsen and 
Thüringen, north east from Berlin / Brandeburg etc.)

I think, this situation will also apply to other federal states.

=> I personally would prefer to stay with or alternatively provide a 
region based file, so I could look up and combine the regions of 
interest. What do you think?

b) Conflicting information

In your "Sachsen-Anhalt" scanfile you list on Ch 24 the ARD multiplex 
with (Halle-Stadt):

T 498000000 8MHz 2/3 NONE QAM64 8k 1/4 NONE
# CH24: Das Erste, arte, Phoenix, EinsFestival

which is for a large part of Sachsen-Anhalt useless (we can't receive 
that), as we actually receive on Ch 24 (from Braunschweig)

T 498000000 8MHz 2/3 NONE QAM16 8k 1/4 NONE
# CH24: RTL, RTL II, Super RTL, VOX

=> have a look at QAM, its QAM64 in your scanfile and QAM16 for Ch24 we 
actually receive.

=> Does it matter, e.g. would instead of the unreceivable Ch24 from 
Halle-Stadt the Braunschweig Ch24 be found? (I did not test this).

c) You clearly missed out some information. I noticed for instance Ch 37 
in Leipzig (Sachsen) which is the "Leipzig 1" multiplex

Please have a look at the already posted link to SLM or my homepage:

http://www.to-st.de/content/projects/dvb-t/dvbt-sender-leipzig.de.html

On the other hand I doubt, that it would be a useful entry into a 
"Sachsen" scanfile because reception is limited to the area of the city 
of Lepzig.

As I have no overview of regional "special projects" in other area, such 
  omissions in the files may apply to other areas too.

@Barry

Just as a sidenote and for historical purposes I may point you to:

http://www.ifn.ing.tu-bs.de/itg/docs/030403Braunschweig/ITG030403Hoehne_Frequenzplanung.pdf

which gives an overview how in 2003 the concept for the north of Germany 
had been planned. This information is obsolete and has changed, but the 
document show a bit, how decisions evolved in consideration of federal 
state and "Medienanstalt" boundaries (e.g. Bremen) etc.

Regards, Tobias

  reply	other threads:[~2009-01-27 12:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 17:15 [linux-dvb] Upcoming DVB-T channel changes for HH (Hamburg) BOUWSMA Barry
2009-01-23 20:01 ` Tobias Stöber
2009-01-23 20:26 ` Tobias Stöber
2009-01-23 22:43   ` BOUWSMA Barry
2009-01-26 20:28     ` Christoph Pfister
2009-01-26 23:24       ` BOUWSMA Barry
2009-01-27  8:30         ` Tobias Stöber
2009-01-27 14:32           ` BOUWSMA Barry
2009-01-27 15:57             ` Tobias Stoeber
2009-01-27 14:36           ` hermann pitton
2009-01-27  8:39         ` Tobias Stöber
2009-01-27 10:37           ` Christoph Pfister
2009-01-27 12:09             ` Tobias Stoeber [this message]
2009-01-27 16:50               ` BOUWSMA Barry
2009-01-27 22:46                 ` Tobias Stoeber
2009-01-28  0:12                   ` hermann pitton
2009-01-28  1:34                     ` Tobias Stoeber
2009-01-28  2:16                   ` BOUWSMA Barry
2009-01-28 12:55                 ` Tobias Stoeber
2009-01-28 21:01                   ` BOUWSMA Barry
2009-01-29 10:32                 ` Christoph Pfister
2009-01-29 13:48                   ` BOUWSMA Barry
2009-02-07 18:53                     ` Christoph Pfister
2009-02-10 11:06                       ` BOUWSMA Barry
2009-01-27 16:52               ` Christoph Pfister

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=497EF972.6090207@to-st.de \
    --to=tobi@to-st.de \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@vger.kernel.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 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.