From: Jelle de Jong <jelledejong@powercraft.nl>
To: wk <handygewinnspiel@gmx.de>
Cc: linux-media@vger.kernel.org
Subject: Re: w_scan 20090502, why is the new country code necessary, its breaking my systems
Date: Tue, 02 Jun 2009 10:07:40 +0200 [thread overview]
Message-ID: <4A24DDCC.3090700@powercraft.nl> (raw)
In-Reply-To: <4A23C321.6010608@gmx.de>
wk wrote:
> Hello Jelle,
>
> > My w_scan version 20081106 stopped working on my Debian system. I had
> > the following errors:
> > ERROR: Sorry - i couldn't get any working frequency/transponder
> >
> > So I first checked if there was a wscan update.
>
> No reception for some reason - probably the new version will show the
> same result.
I am know using w_scan version 20090528 and this version works partly
and does also not loop. The error still sometimes happens, something
changed in the device modules... The device is not always stable, i have
to repluging the device and then the scanning works again. Sorry for the
lack of further info, no messages in dmesg...
>
> > I had to make a new argument line:
> > ~/.wscan/wscan -t 3 -A 1 -E 0 -O 0 -c NL -X tzap >
> ~/.wscan/channels.conf
>
> "-A 1" is wrong for you, please omitt this one, it's used outside Europe
> only.
> "-O 0" is default anyway, not needed
>
I am know using the bellow command, i use some default values, since I
am afraid these option can change in the future and break my system.
~/.wscan/wscan -f 1 -c NL -X tzap -R 1 -T 1 -E 0 -O 0 -t 3 >
~/.wscan/channels.conf
> > This is very troubling for me because I must have a scan command that
> > works in complete Europa and not in one country. This is because I have
> > traveling systems that need to scan for channels on every stop.
> >
> > Why :-( please explain and try to fix this regression that a country
> > code is needed?
>
> w_scan tends to be used now to be used also in other countries - with
> different settings
> - frequency lists
> - frequency offsets from center frequency
> - Symbolrates
> - channel bandwidths
> - Modulations ( QAM_128 for example in FI, QAM_64 and QAM_256 otherwise )
> At the beginning w_scan was made to work in Germany only. But with the
> time more and more additions were made
> and at some point one has to find a compromise. Either prolong scanning
> time to be endless, omitt new features or change command line options.
>
> If you need the some behaviour working in many european countries, you
> may simply use "-c DE". It will give nearly the same result as the old
> versions.
>
Is there a way you can do a scanning without selecting a country, a scan
time of 25min is acceptable, as long as the result works? If not how can
i made an automated scanning that works in The Netherlands, Norway,
Germany and Belgum and France (one command) that works in all countries?
> > I was hoping for auto signal strength detection and automatic filtering
> > depending on the signal strength to remove duplicated channels from
> > different broadcast towers.. what work is being done to realize this,
> > and can I help by donating resources?
>
> As soon we have dvb drivers which give some reliable and *comparable*
> signal strength information
> signal information *across all frontends* this would be possible, not
> earlier. But i guess it will never happen.
Me-TV and kaffeine show the signal strength I don't know if wscan can do
the same. The smart signal strength stuff is really mandatory I have
seen people go from Linux to mac only to get proper dvb-t scanning and
signal detection support. Any ideas?
>
> Best Regards,
> Winfried
Best regards,
Jelle de Jong
next prev parent reply other threads:[~2009-06-02 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 12:01 w_scan 20090502, why is the new country code necessary, its breaking my systems wk
2009-06-02 8:07 ` Jelle de Jong [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-31 19:37 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=4A24DDCC.3090700@powercraft.nl \
--to=jelledejong@powercraft.nl \
--cc=handygewinnspiel@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox