The dvb-apps package source code is available from the [[LinuxTV]] website and can be retrieved via [http://www.linuxtv.org/repo/#mercurial Mercurial (Hg)] or by downloading a tarball, compressed in either [http://www.linuxtv.org/download/dvb/linuxtv-dvb-apps-1.1.1.tar.bz2 tar.bz2] or [http://www.linuxtv.org/download/dvb/linuxtv-dvb-apps-1.1.1.tar.gz tar.gz] format. (Note: The build procedure is very simple -- (a) uncompress the download (not required if you pulled the sources with Hg); (b) in a command shell, cd to the top directory level of the sources; (c) run 'make' and then 'sudo make install').

+

The dvb-apps package source code is available from the [[LinuxTV]] website and can be retrieved via [http://www.linuxtv.org/repo/#mercurial Mercurial (Hg)].

−

Alternatively, if the package is maintained in a repository available for your "distro", then you can obtain a pre-built version with your package manager. Note, however, that not all Linux distributions ('distro's') refer to the package by the proper "dvb-apps" name. The Debian package name for it, for example, is "dvb-utils". In other cases, you may also sometimes see it called "dvbtools". This is an unfortunate situation, as it introduces an element of confusion; additional to the fact that [[DVB tools]] is itself the name of another project (not associated with LinuxTV) that features its own set of DVB related utilities. In any regard, the following provides a few examples with common distros

+

The download and build procedure is very simple:

+

+

hg clone http://linuxtv.org/hg/dvb-apps # download the tarball link below and extract if you don't have mercurial.

+

cd dvb-apps

+

make

+

sudo make install

+

+

There are some very old tarballs, compressed in [http://www.linuxtv.org/download/dvb/linuxtv-dvb-apps-1.1.1.tar.bz2 tar.bz2] and [http://www.linuxtv.org/download/dvb/linuxtv-dvb-apps-1.1.1.tar.gz tar.gz] formats. The latest [http://linuxtv.org/hg/dvb-apps/archive/tip.tar.gz tarball] of dvb-apps is provided by Mercurial (Hg).

+

+

Alternatively, if the package is maintained in a repository available for your "distro", then you can obtain a pre-built version with your package manager. Note, however, that not all Linux distributions ('distros') refer to the package by the proper "dvb-apps" name. The Debian package name for it, for example, is "dvb-utils". In other cases, you may also sometimes see it called "dvbtools". This is an '''insane''' situation, which creates much confusion; additional to the fact that [[DVB tools]] is itself the name of another project (not associated with LinuxTV) that features its own set of DVB related utilities. In any regard, the following provides a few examples with common distros

**[[Scan|scan]]: the original [[Frequency scan|frequency scanning]] tool used to generate channel lists

+

**[[dvbscan]]: another [[Frequency scan|frequency scanning]] tool used to generate channel lists .... some distro package managers have rebranded this as "scandvb" ... also note that "atscscan", if included, is simply a copy of dvbscan. The DVB or ATSC protocol is determined by a tuning file feed to these programs. Tuning files are kept in the scan/atsc, scan/dvb-[csth] directories. This program discovers carriers on candidate frequencies and also determines ''sub-channels''. ''sub-channels'' may be the main program at a lower data rate or completely new content. With the output produced, a short name can be used to identify the frequency and the streams needed to get a ''channel''.

+

**[[Zap|czap, szap, tzap]]: tuning utilities for DVB-C, DVB-S, DVB-T. These change the channel/sub-channel as identified by the file output by ''scan'' above.

+

**[[Zap|azap]]: tuning utility for ATSC.

+

**util/gnutv - Tune, watch and stream your TV. I.e. a DVB UI.

+

+

*General Utilities:

+

**util/dvbdate - Read date time information from the currently tuned multiplex.

**util/zap - *Just* tunes a digital device - really intended for developers. Note that this is a seperate app then those ''*zap'' utilities listed above.

+

**util/atsc_epg - Recent versions of dvb-apps include a program to print out the next three hours worth of programs on a given frequency (for ATSC only).

+

+

*Hardware Specific Utilities:

+

**util/av7110_loadkeys - A utiltity to load IR remote keymaps into an av7110 based card using the /proc/av7110_ir interface

+

**util/dib3000-watch - Monitor DIB3000 demodulators

+

**util/dst-utils/dst-test - Utilities for DST based cards.

+

**util/ttusb_dec_reset - Reset a TechnoTrends TTUSB DEC device.

===/test directory===

===/test directory===

Line 40:

Line 88:

*test_dvr: Record a partial transport stream of selected PIDs to a file or a full stream if supported by the hardware

*test_dvr: Record a partial transport stream of selected PIDs to a file or a full stream if supported by the hardware

−

===/util directory===

+

==TODO==

−

*loadkeys: a utility to setup IR control keymaps using /proc/av7110_ir interface

+

−

*dvbdate: read date time information from the currently tuned multiplex

+

* Start numbering the versions. Yes, with a repo every commit is a kind of version, but in the real world of distros and end users you need to define version numbers as easy reference points.

−

*dvbnet: DVB network interface manager (IP over DVB)

+

* Tag versioned releases and make src tarballs for the distros.

−

*dvbtraffic: PID analysis of currently tuned multiplex

+

* Add ChangeLog and TODO files (and keep them up to date of course).

−

*[[Scan|scan]]: the original [[Frequency scan|frequency scanning]] tool used to generate channel lists

+

* Review the names of the apps and change where necessary. Perhaps ''scan'' is too ambiguous a name in a general-purpose system where all sorts of things can be scanned (with scanners, fax machines, barcode readers, etc.).

−

*[[dvbscan]]: another [[Frequency scan|frequency scanning]] tool used to generate channel lists .... some distro package managers have rebranded this as "scandvb" ... also note that "atscscan", if included, is simply a copy of dvbscan

+

* Implement API version 5 scanning and zapping for DVB-S2 channels. See [[S2API]], [[scan-s2]] and [[szap-s2]]. There's a work undergoing to implement support to DVB API v5 for ISDB-T that also adds DVB API v5 to other transports at [http://linuxtv.org/hg/~mchehab/dvb-apps-isdbt2/].

−

*[[Zap|azap, czap, szap, tzap]]: tuning utilities for DVB.

+

* Improve the channels.conf file format so that one file can represent all the channels. Need to

−

* femon: monitor frontend status

+

**(a) identify the source (S13.0E, S19.2E, Terrestrial, etc)

−

* gnutv: simple ;-) DVB UI

+

**(b) identify the delivery system (DVB-S, DVB-S2, DVB-T etc)

−

* dib3000-watch:

+

**(c) be able to represent all the parameters required for all the delivery systems in a unified way. For example DVB-S2 has some new paramters (e.g. rolloff). The "VDR" format was expanded for this, but in a messy way.

−

* zap: note that this is a seperate app then those ''*zap'' utilities listed above

+

* Make sure there is one true format -- no "zap" versus "VDR" format confusion.

−

* dst_test:

+

* Merge all the *zap programs. You unified the channels.conf file so this is next.

There are some very old tarballs, compressed in tar.bz2 and tar.gz formats. The latest tarball of dvb-apps is provided by Mercurial (Hg).

Alternatively, if the package is maintained in a repository available for your "distro", then you can obtain a pre-built version with your package manager. Note, however, that not all Linux distributions ('distros') refer to the package by the proper "dvb-apps" name. The Debian package name for it, for example, is "dvb-utils". In other cases, you may also sometimes see it called "dvbtools". This is an insane situation, which creates much confusion; additional to the fact that DVB tools is itself the name of another project (not associated with LinuxTV) that features its own set of DVB related utilities. In any regard, the following provides a few examples with common distros

/util directory

dvbscan: another frequency scanning tool used to generate channel lists .... some distro package managers have rebranded this as "scandvb" ... also note that "atscscan", if included, is simply a copy of dvbscan. The DVB or ATSC protocol is determined by a tuning file feed to these programs. Tuning files are kept in the scan/atsc, scan/dvb-[csth] directories. This program discovers carriers on candidate frequencies and also determines sub-channels. sub-channels may be the main program at a lower data rate or completely new content. With the output produced, a short name can be used to identify the frequency and the streams needed to get a channel.

czap, szap, tzap: tuning utilities for DVB-C, DVB-S, DVB-T. These change the channel/sub-channel as identified by the file output by scan above.

util/zap - *Just* tunes a digital device - really intended for developers. Note that this is a seperate app then those *zap utilities listed above.

util/atsc_epg - Recent versions of dvb-apps include a program to print out the next three hours worth of programs on a given frequency (for ATSC only).

Hardware Specific Utilities:

util/av7110_loadkeys - A utiltity to load IR remote keymaps into an av7110 based card using the /proc/av7110_ir interface

util/dib3000-watch - Monitor DIB3000 demodulators

util/dst-utils/dst-test - Utilities for DST based cards.

util/ttusb_dec_reset - Reset a TechnoTrends TTUSB DEC device.

/test directory

diseqc: Sends various diseqc sequences on a SAT frontend.

set22k: Legacy tone switching for SAT frontends.

setvoltage: Legacy voltage switching for SAT frontends.

setpid: Set video and audio PIDs in the demux (only for hardware MPEG decoder)

video: tiny video watching application

test_sections: Hex dump of section data from stream.

test_sec_ne: Like test_sections, but also test Not-Equal filter mode.

test_pes: Hex dump of PES data from stream.

test_tt: Demonstrate teletext decoding from PES data.

test_av: Test audio and video MPEG decoder API.

test_vevent: Test VIDEO_GET_EVENT and poll() for video events

test_stc: Test DMX_GET_STC.

test_stillimage: Display single iframes as stillimages

test_dvr: Record a partial transport stream of selected PIDs to a file or a full stream if supported by the hardware

TODO

Start numbering the versions. Yes, with a repo every commit is a kind of version, but in the real world of distros and end users you need to define version numbers as easy reference points.

Tag versioned releases and make src tarballs for the distros.

Add ChangeLog and TODO files (and keep them up to date of course).

Review the names of the apps and change where necessary. Perhaps scan is too ambiguous a name in a general-purpose system where all sorts of things can be scanned (with scanners, fax machines, barcode readers, etc.).

Implement API version 5 scanning and zapping for DVB-S2 channels. See S2API, scan-s2 and szap-s2. There's a work undergoing to implement support to DVB API v5 for ISDB-T that also adds DVB API v5 to other transports at [1].

Improve the channels.conf file format so that one file can represent all the channels. Need to

(a) identify the source (S13.0E, S19.2E, Terrestrial, etc)

(b) identify the delivery system (DVB-S, DVB-S2, DVB-T etc)

(c) be able to represent all the parameters required for all the delivery systems in a unified way. For example DVB-S2 has some new paramters (e.g. rolloff). The "VDR" format was expanded for this, but in a messy way.

Make sure there is one true format -- no "zap" versus "VDR" format confusion.

Merge all the *zap programs. You unified the channels.conf file so this is next.