From: David Liontooth <lionteeth@cogweb.net>
To: Olli Salonen <olli.salonen@iki.fi>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: dvbv5-scan needs which channel file?
Date: Tue, 30 Dec 2014 00:23:37 -0800 [thread overview]
Message-ID: <54A26109.1040109@cogweb.net> (raw)
In-Reply-To: <CAAZRmGxoOTf9f4gq05RgbcD44tmiySMXo-_ZHtBQX0pw6ZXPUA@mail.gmail.com>
Ah, thank you Olli -- much appreciated!
If dvbv5-scan expects the initial scan files in the new DVBV5 format,
does that mean that these still somewhat mysterious "initial scan files"
have to be supplied, as in the link to the dtv-scan-tables? How are
these "initial scan files" themselves generated?
Surely there must be thousands of different dvb signal locations -- is
linux-tv going to try to maintain these thousands of scan tables for
download? What do users do when their particular location is not
represented in the dtv-scan-tables.git?
Finally, I'm using gnutv to record television; I imagine it still only
accepts the old format? What's the new alternative?
Cheers,
David
On 12/29/14, 11:55 PM, Olli Salonen wrote:
> Hello David,
>
> Coincidentally I was just yesterday working with dvbv5-scan and the
> initial scan files. dvbv5-scan expects the initial scan files in the
> new DVBV5 format. w_scan is not producing results in this format.
>
> The scan tables at
> http://git.linuxtv.org/cgit.cgi/dtv-scan-tables.git/ are in the new
> format. Some of them are a bit outdated though (send in a patch if you
> can update it for your area).
>
> The v4l-utils package also includes tools to convert between the old
> and the new format.
>
> Cheers,
> -olli
>
>
> On 29 December 2014 at 22:09, David Liontooth <lionteeth@cogweb.net> wrote:
>> Greetings --
>>
>> How do you actually use dvbv5-scan? It seems to require some kind of input
>> file but there is no man page and the --help screen doesn't say anything
>> about it.
>>
>> Could we document this? I tried
>>
>> $ dvbv5-scan
>> Usage: dvbv5-scan [OPTION...] <initial file>
>> scan DVB services using the channel file
>>
>> What is "the channel file"? Maybe the channels.conf file? (I created mine
>> using "w_scan -ft -A3 -X -cUS -o7 -a /dev/dvb/adapter0/")
>>
>> $ dvbv5-scan /etc/channels.conf
>> ERROR key/value without a channel group while parsing line 1 of
>> /etc/channels.conf
>>
>> So it knows what it wants -- but what is it? Or is this a matter of dvb
>> versions, and my /etc/channels.conf is in the older format?
>>
>> Very mysterious.
>>
>> Cheers,
>> David
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-30 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 20:09 dvbv5-scan needs which channel file? David Liontooth
2014-12-30 7:55 ` Olli Salonen
2014-12-30 8:23 ` David Liontooth [this message]
2014-12-30 13:15 ` Olli Salonen
2014-12-30 15:49 ` David Liontooth
2014-12-31 2:11 ` Mauro Carvalho Chehab
2014-12-31 2:16 ` Mauro Carvalho Chehab
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=54A26109.1040109@cogweb.net \
--to=lionteeth@cogweb.net \
--cc=linux-media@vger.kernel.org \
--cc=olli.salonen@iki.fi \
/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.