public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: wk <handygewinnspiel@gmx.de>
To: Jelle de Jong <jelledejong@powercraft.nl>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] automated w_scan, duplicated channels and signal strength filtering
Date: Sat, 01 Nov 2008 11:22:33 +0100	[thread overview]
Message-ID: <490C2DE9.9090809@gmx.de> (raw)
In-Reply-To: <490B6241.7020102@powercraft.nl>

Hello Jelle,
> When a scan is completed it list all found channels, in the file, (see
> attachment) however this also include duplicated channels with other
> frequencies and strange channels that are from local unusable broadcast.
>   
That's most probably what your provider sends inside NIT (network 
information table).
w_scan reads it's informations from there. Sometimes these informations 
are wrong.
> The issue here is that signal strength is not used to filter out
> duplicated channels, only the best strongest signal should come in the
> channel list, and channels without identifiers should be removed.
>
> How can we do this? Is somebody able to fix these issues?
>
>   
It's not possible to use signal information since nearly every dvb cards 
sends other information for signal strength,
please read the discussion regarding SNR/strength some days ago here on 
the list. From application point of view
the signal strength information doesnt contain any useful data as long 
it's not standardized and reliable across all frontends.
Therefore i decided not to use signal strength. Otherwise some frontends 
would not work.

Signals without identifiers will not be removed, since some of them have 
their channel names inside EIT information or
inside private data (i.e. Prmiere) and deleting these channels would 
make other users really unhappy. ;)
Most of these channels are encrypted, so try to avoid them with -E 0 .
But channels without video *and* audio will be removed instead.

> [1] http://wirbel.htpc-forum.de/w_scan/index2.html
>
> ps. I can't find any contact info for the developer of w_scan.
>   
email contact is included in the header of each source file. 
Nevertheless, should be inside README too, you're right.

Regards,
Winfried



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-11-01 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 19:53 [linux-dvb] automated w_scan, duplicated channels and signal strength filtering Jelle de Jong
2008-11-01 10:22 ` wk [this message]
2008-11-01 18:41   ` Jelle de Jong

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=490C2DE9.9090809@gmx.de \
    --to=handygewinnspiel@gmx.de \
    --cc=jelledejong@powercraft.nl \
    --cc=linux-dvb@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