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

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

* dst_test:

* dst_test:

+

+

==TODO==

+

+

The lack of maintenance means that there is now a backlog of improvements to be made by whoever is interested.

+

+

* 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 the less ambiguous ''dvbscan'' is better than just ''scan'' in a gerneral purpose system where all sorts of things can be scanned (with scanners, fax machines, barcode readers, etc.).

+

+

* 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.

Note: DEVELOPER / MAINTAINER WANTED! Dvb-apps is almost unmaintained, with the exception of DVB-T scan files which are regularly updated. It is an important set of utilities, and is available in most distros, but releases are not made (at least not since 2006) and there is no roadmap for future development. Hell there
aren't even any upstream version numbers and the distros don't agree on what to call the package or the constituent apps. Unsatisfied demand for new features has led to szap-s2 and scan-s2 for example, but it would be best to keep fragmentation under control. If you think you can do better (honestly who can't?) then please jump in and help !! Contact linux-media@vger.kernel.org.

There are some very old tarballs, compressed in tar.bz2 and tar.gz formats.

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

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

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

dst_test:

TODO

The lack of maintenance means that there is now a backlog of improvements to be made by whoever is interested.

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 the less ambiguous dvbscan is better than just scan in a gerneral purpose system where all sorts of things can be scanned (with scanners, fax machines, barcode readers, etc.).

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.