From: e9hack <e9hack@googlemail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH]Fix a bug in scan, which outputs the wrong frequency if the current tuned transponder is scanned only
Date: Tue, 02 Dec 2008 20:43:36 +0100 [thread overview]
Message-ID: <49358FE8.9020701@googlemail.com> (raw)
In-Reply-To: <c74595dc0812020849p4d779677ge468871489e7d44@mail.gmail.com>
Alex Betis schrieb:
> I don't understand what's wrong with NIT advartised frequency?
> For example, many satelite sites (such as lyngsat) have different
> frequencies listed for the same channel, generally a difference of 1 MHz
> here and there.
If I do scan the tuned transponder only (parameter '-c'), scan will copy all NIT entries
to the same transponder data. The output contains the last frequency, which was found. On
DVB-C, the NIT contains the frequencies of all transponders. If VDR has tuned to the
113MHz transponder and I scan this transponder, I should got 113MHz and QAM64 modulation,
but I get e.g. 466MHz and QAM256 modulation. The frequency changes on every scan.
-Hartmut
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-12-02 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 12:51 [linux-dvb] [PATCH]Fix a bug in scan, which outputs the wrong frequency if the current tuned transponder is scanned only e9hack
2008-12-02 16:34 ` Christoph Pfister
2008-12-02 16:49 ` Alex Betis
2008-12-02 19:43 ` e9hack [this message]
2008-12-02 20:05 ` Alex Betis
2008-12-02 22:07 ` e9hack
2008-12-03 7:23 ` Alex Betis
2008-12-03 17:13 ` e9hack
2008-12-03 19:04 ` e9hack
2008-12-03 21:28 ` Alex Betis
2008-12-08 20:21 ` e9hack
2008-12-08 20:36 ` Alex Betis
2008-12-08 21:00 ` e9hack
2008-12-02 19:22 ` e9hack
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=49358FE8.9020701@googlemail.com \
--to=e9hack@googlemail.com \
--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