All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akihiro TSUKADA <tskd2@yahoo.co.jp>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: RFC: dvbzap application based on DVBv5 API
Date: Fri, 30 Dec 2011 15:46:21 +0900	[thread overview]
Message-ID: <4EFD5E3D.8090305@yahoo.co.jp> (raw)
In-Reply-To: <4EFCC9A7.9050907@redhat.com>

> [channel name]
> 	property = value
> ...
> 	property = value

Currently, at least gstreamer's dvbbasebin and mplayer assumue that
the channel configuration file has the format of one line per channel.
So when I personally patched them to use v5 parameters,
I chose the one-line-per-channel format of
  <channel name>:propname=val|...|propname=val:<service id>, for example,
 NHKBS1:DTV_DELIVERY_SYSTEM=SYS_ISDBS|DTV_VOLTAGE=1|DTV_FREQUENCY=1318000|DTV_ISDBS_TS_ID=0x40f2:103
, to minimize modification (hopefully).
I understand that it is not that difficult nor complicated 
to adapt applications to use the ini file style format,
but the old one line style format seems slightly easier.

and I wish that the channel configuration can allow nicknames/aliases,
as the canonical channel name can be long to type in or difficult to remember correctly.
If I remember right, MythTV has its own database,
and it would be convenient if we could share the database,
because applications currently have their own channel configuration separately,
and the configuration change like new service or parameter changes must be
propagated manually.

regards,
Akihiro

  reply	other threads:[~2011-12-30  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29 20:12 RFC: dvbzap application based on DVBv5 API Mauro Carvalho Chehab
2011-12-30  6:46 ` Akihiro TSUKADA [this message]
2012-01-04 16:13   ` 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=4EFD5E3D.8090305@yahoo.co.jp \
    --to=tskd2@yahoo.co.jp \
    --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.