From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dvbsnoop: new package dvbsnoop
Date: Thu, 10 Jan 2013 20:27:03 +0100 [thread overview]
Message-ID: <50EF1607.5010806@googlemail.com> (raw)
In-Reply-To: <20130109210728.6a51c9c9@skate>
Hello Thomas,
Am 09.01.2013 21:07, schrieb Thomas Petazzoni:
>> + DVB analyzer / MPEG analyzer program to monitor, analyze, debug,
>> + dump or view dvb/mpeg/dsm-cc/mhp stream information (TS, PES,
>> + SECTION) (e.g. digital television) send via satellite, cable or
>> + terrestrial.
>
> Could you include a bit more details here? You have a lot of nice
> details in your commit log, what about copy/pasting them here?
I don't know what you exactly mean. Do you want more details in the
commit message or more explanation here on the mailing list?
I thought while everybody can read the commit message I don't have to
explain it twice. :-/
And the webpage of dvbsnoop is written very well and the author can
explain it's work better than me (I think).
So what is dvbsnoop?
Dvbsnoop is just a simple tool to analyze, view or debug a transport
stream (TS), program elementary stream (PES) or even a program stream
(PS). This input comes mostly direct from a frontend (satellite or cable
tuner inside a set-top box for example) via DVB APIv3 to view into a TS,
a demux to view PES or PS (also mostly inside the set-top box or even
PCI Card) or even from a file (recorded TS).
The device files are differ from hardware to hardware this can be given
as parameter to dvbsnoop.
Dvbsnoop itself doesn?t do the tuning on the frontend, this has to be
done by external helpers or manually driver call. It just takes the data
from it an do the parsing.
The dvbsnoop tool was written while developing the software Neutrino on
the set-top box DBox2 [1]. It was useful to see if the GUI Neutrino was
working correct with the digital data from the frontend or from a NFS Share.
In the last time Rainer Scherg doesn't has worked on dvbsnoop because
it's doing what it should. Some parts are re workable, the complete
latest standards for integrating the MPEG4 standards (DVB-[S,C,T]*2*)
are just "it works". Some flags for this dvbsnoop don?t know right now.
> Should be _LICENSE_FILES even if there is only one file.
O.K. Will rework this.
[1] http://en.wikipedia.org/wiki/DBox2
Regards
Carsten
next prev parent reply other threads:[~2013-01-10 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:03 [Buildroot] new package dvbsnoop Carsten Schoenert
2013-01-09 17:03 ` [Buildroot] [PATCH] packages/dvbsnoop: " Carsten Schoenert
2013-01-09 17:34 ` Yann E. MORIN
2013-01-09 18:56 ` [Buildroot] [PATCH v2] " Carsten Schoenert
2013-01-09 18:56 ` [Buildroot] [PATCH] dvbsnoop: " Carsten Schoenert
2013-01-09 20:07 ` Thomas Petazzoni
2013-01-10 19:27 ` Carsten Schoenert [this message]
2013-01-10 19:45 ` Thomas Petazzoni
2013-01-10 19:57 ` Carsten Schoenert
-- strict thread matches above, loose matches on Subject: below --
2013-01-13 13:00 [Buildroot] [PATCH v3] dvbsnoop: new package Carsten Schoenert
2013-01-13 13:00 ` [Buildroot] [PATCH] dvbsnoop: new package dvbsnoop Carsten Schoenert
2013-01-13 20:04 ` Peter Korsgaard
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=50EF1607.5010806@googlemail.com \
--to=c.schoenert@gmail.com \
--cc=buildroot@busybox.net \
/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