From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: RFC: dvbzap application based on DVBv5 API
Date: Thu, 29 Dec 2011 18:12:23 -0200 [thread overview]
Message-ID: <4EFCC9A7.9050907@redhat.com> (raw)
In order to test the large chunk of patches I've made those days, I wrote
a dvbzap application using DVBv5 API, based on tzap.
It is at my experimental v4l-utils tree, at branch dvb-utils:
http://git.linuxtv.org/mchehab/experimental-v4l-utils.git/shortlog/refs/heads/dvb-utils
in order to test, please use:
git clone git://linuxtv.org/mchehab/experimental-v4l-utils.git
While I tested it only with ISDB-T, it will likely work with DVB-T, ATSC and DVB-C,
if CA is not needed.
TODO:
- Add proper support for Satellite delivery systems. It will likely
recognize a DVB-S zap file, but it won't work, as polarization setting were not
implemented, nor any DISEqC commands;
- Add support for CA;
- Be more flexible with regards to the channels.conf files.
One of the changes I'm experimenting with this tool is to define a new format to
show DVBv5 channels/transponders.
As you likely know, the current formats on the existing DVBv3 tools are
standard-dependent. Even the existing DVBv5 applications I'm aware of currently
write the channels file on a DVBv3, due to compatibility issues.
So, a new format for channels is needed.
The current code has one function to write on a new format. I lacks a parser for it
(it shouldn't be hard to write one - a few hours should be enough for doing that).
The format I'm thinking is to use:
[channel name]
property = value
...
property = value
This allows the same format to be used by any DVBv5 supported delivery system.
It will even allow to mix channels from different delivery systems on the same file.
This could be useful for devices like DRX-K, that supports multiple delivery
systems with different parameters.
As an example, this is what it produces from a DVB-T zap file:
[TV Brasil SD]
VIDEO_PID = 769
AUDIO_PID = 513
SERVICE_ID = 16161
DELIVERY_SYSTEM = DVBT
FREQUENCY = 479142857
INVERSION = AUTO
BANDWIDTH_HZ = 6000000
CODE_RATE_HP = AUTO
CODE_RATE_LP = AUTO
MODULATION = QAM/AUTO
TRANSMISSION_MODE = AUTO
GUARD_INTERVAL = AUTO
HIERARCHY = NONE
The same entry without audio/video/service ID's (like the ones used
by scan) would look like:
[CHANNEL]
DELIVERY_SYSTEM = DVBT
FREQUENCY = 479142857
INVERSION = AUTO
BANDWIDTH_HZ = 6000000
CODE_RATE_HP = AUTO
CODE_RATE_LP = AUTO
MODULATION = QAM/AUTO
TRANSMISSION_MODE = AUTO
GUARD_INTERVAL = AUTO
HIERARCHY = NONE
My next steps with regards to this tool are to:
1) convert a scan tool to use the same libraries as dvbzap is
using, in order to generate an output file for scan with the same format;
2) to implement a parser for the new format (this should be easy, so maybe
I'll start with this).
Comments, ideas, patches, etc are welcome.
Regards,
Mauro
next reply other threads:[~2011-12-29 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 20:12 Mauro Carvalho Chehab [this message]
2011-12-30 6:46 ` RFC: dvbzap application based on DVBv5 API Akihiro TSUKADA
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=4EFCC9A7.9050907@redhat.com \
--to=mchehab@redhat.com \
--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.